Back to Home / #debian / 2021 / 05 / Prev Day | Next Day
#debian IRC Logs for 2021-05-14

---Logopened Fri May 14 00:00:44 2021
00:02-!-jm_ [] has joined #debian
00:02-!-jm_ is "." on #debian
00:03<alexandrogonsan_>Do you have anything else to tell me?
00:04<Sqrt{not}>many different things can cause a short hang of the computer
00:05<Sqrt{not}>you are on the right track, using this tool. look every time when it hangs, and try to find a pattern. it is usually not easy to find it.
00:05-!-hele [] has joined #debian
00:05-!-hele is "hele" on #debian-next #debian
00:05<Sqrt{not}>could be something about the network, or the memory is all full, or cpu use sudddenly is too much.
00:07<alexandrogonsan_>sometimes all the features I monitor are ok but still crashes quickly.
00:07<alexandrogonsan_>Thank you very much
00:07<Sqrt{not}>what do you mean "crashes" ?
00:08-!-f10 [] has quit [Read error: No route to host]
00:08-!-thomasross [] has quit [Ping timeout: 480 seconds]
00:08-!-f10 [] has joined #debian
00:08-!-f10 is "f10" on #debian-kde #debian
00:08-!-dippy [] has joined #debian
00:08-!-dippy is "realname" on #debian
00:09-!-dippy [] has quit []
00:10<alexandrogonsan_>how to send packages to be available in apt install?
00:11<jm_>send them where?
00:11<alexandrogonsan_>laptop slows down, the screen starts to update slowly.
00:12-!-dippy [] has joined #debian
00:12-!-dippy is "realname" on #debian
00:12<alexandrogonsan_>to the server to download by the command apt install
00:12<alexandrogonsan_>package publishing type
00:13<jm_>you mean how to create your own repository?
00:13-!-dippy [] has quit []
00:15<alexandrogonsan_>what would that look like?
00:15<jm_>let's first clear up what you are trying to do, as I am still not sure
00:16<alexandrogonsan_>to publish an application Do I need to create a repository? but will it be available to the user without the user having to make changes to sources.list?
00:17-!-polymetric [] has joined #debian
00:17-!-polymetric is "polymetric" on #debian
00:17<alexandrogonsan_>i want my app to be downloaded by apt command as 'sudo apt install -y my-app'
00:17<jm_>right, no, user will only see packages that are part of repositories they have in their sources
00:18<alexandrogonsan_>so I want to add my app to the debian repository
00:18<alexandrogonsan_>how do I do that?
00:20<jm_>it's a process,
00:26-!-secntech [] has joined #debian
00:26-!-secntech is "tp" on #tor-project #suckless #redditprivacy #Qubes_OS #privacytech #freedombox #debian #cryptoparty
00:27<alexandrogonsan_>thank you, i will verify
00:28-!-mode/#debian [+l 695] by debhelper
00:28-!-f10 [] has quit [Read error: No route to host]
00:32<somiaj>alexandrogonsan_: You can always make your own repo for your apps, though first step if your app meets the DFSG is to cerate a package that meets debian policy, second is to follow the instructions on to try and find a sponsor.
00:32-!-f10 [] has joined #debian
00:32-!-f10 is "f10" on #debian-kde #debian
00:32-!-diogenes_oftc [~diogenes_@] has joined #debian
00:32-!-diogenes_oftc is "Nicolas" on #debian
00:36-!-hele [] has quit [Ping timeout: 480 seconds]
00:38-!-liquidsnake [] has quit [Quit: Leaving]
00:42-!-allorder [] has joined #debian
00:42-!-allorder is "allorder" on #debian-quebec #debian
00:43-!-f10 [] has quit [Read error: No route to host]
00:43-!-f10 [] has joined #debian
00:43-!-f10 is "f10" on #debian-kde #debian
00:50-!-alexandrogonsan_ [c88db24f@] has quit [Quit: Connection closed]
00:50-!-ol [~quassel@2406:e003:852:ff01:8e89:a5ff:feca:57fe] has quit [Ping timeout: 480 seconds]
00:51-!-f10 [] has quit [Read error: No route to host]
00:53-!-freshtube [~freshtube@] has quit [Quit: Leaving]
00:55-!-freshtube [~freshtube@] has joined #debian
00:55-!-freshtube is "realname" on #redditprivacy #debian
00:55-!-f10 [] has joined #debian
00:55-!-f10 is "f10" on #debian-kde #debian
01:04-!-f10_ [] has joined #debian
01:04-!-f10_ is "f10" on #debian
01:04-!-f10 [] has quit [Read error: Connection reset by peer]
01:07-!-nuc [] has quit [Read error: Connection reset by peer]
01:09-!-nuc [] has joined #debian
01:09-!-nuc is "realname" on #debian
01:16-!-f10_ [] has quit [Ping timeout: 480 seconds]
01:16-!-richard_h [~richard@2406:e001:8:a900:6e62:6dff:fe05:ae29] has joined #debian
01:16-!-richard_h is "purple" on #debian
01:20-!-nuc [] has quit [Read error: Connection reset by peer]
01:20-!-nuc [] has joined #debian
01:20-!-nuc is "realname" on #debian
01:26-!-gnugr [] has quit [Read error: Connection reset by peer]
01:39-!-lunc [~omnd@] has joined #debian
01:39-!-lunc is "lunc" on #debian #oftc #help
01:42-!-richard_h [~richard@2406:e001:8:a900:6e62:6dff:fe05:ae29] has quit [Quit: Leaving.]
01:43-!-AnonDragonFly [] has joined #debian
01:43-!-AnonDragonFly is "zerosquad,,," on #debian
01:57-!-czesmir [] has joined #debian
01:57-!-czesmir is "Stefan" on #debian
02:06-!-nu-c_ [] has quit [Read error: No route to host]
02:07-!-nu-c [] has joined #debian
02:07-!-nu-c is "realname" on #debian
02:07-!-AnonDragonFly [] has quit [Quit: No Ping reply in 180 seconds.]
02:08-!-texou [] has quit [Ping timeout: 480 seconds]
02:08-!-live [~live@2600:1700:a941:4b0::505] has joined #debian
02:08-!-live is "Live session user" on #debian
02:08-!-live [~live@2600:1700:a941:4b0::505] has quit []
02:13-!-AnonDragonFly [] has joined #debian
02:13-!-AnonDragonFly is "zerosquad,,," on #debian
02:19-!-AnonDragonFly [] has quit [Quit: No Ping reply in 180 seconds.]
02:20-!-AnonDragonFly [] has joined #debian
02:20-!-AnonDragonFly is "zerosquad,,," on #debian
02:24-!-AnonDragonFly_ [] has joined #debian
02:24-!-AnonDragonFly_ is "zerosquad,,," on #debian
02:30-!-dj [~dj@] has joined #debian
02:30-!-dj is "realname" on #debian
02:30-!-AnonDragonFly [] has quit [Ping timeout: 480 seconds]
02:31-!-dj [~dj@] has quit []
02:31-!-arnoldoree [] has joined #debian
02:31-!-arnoldoree is "Arnold Opio Oree" on #virt #qemu #debian-meeting #debian-tech #debian
02:32-!-andibmu [~andi@] has joined #debian
02:32-!-andibmu is "Andreas B. Mundt" on #debian-meeting #debian #debian-next #debian-offtopic #debian-edu #debian-lan
02:34-!-freshtube [~freshtube@] has quit [Quit: Leaving]
02:36-!-os_ [~Usama@] has joined #debian
02:36-!-os_ is "realname" on #debian-next #debian
02:40-!-chipps [~chipps@] has quit [Remote host closed the connection]
02:43-!-chipps [~chipps@] has joined #debian
02:43-!-chipps is "chipps" on #debian #spectrwm
02:48-!-freshtube [~freshtube@] has joined #debian
02:48-!-freshtube is "realname" on #redditprivacy #debian
03:01-!-hdh [~hmgm@2405:4802:11e:7e00:ffff:ffff:ffff:ffe3] has joined #debian
03:01-!-hdh is "realname" on #debian
03:02-!-tnewman [] has quit [Quit: Ping timeout (120 seconds)]
03:03-!-hdh [~hmgm@2405:4802:11e:7e00:ffff:ffff:ffff:ffe3] has quit []
03:04-!-tnewman [] has joined #debian
03:04-!-tnewman is "Travis Newman" on #debian
03:12-!-diogenes_oftc [~diogenes_@] has quit [Quit: vergissmeinnicht]
03:13-!-texou [] has joined #debian
03:13-!-texou is "Stoicien" on #debian-nonupload #debian-i18n #bitlbee #debian-next #debian #debian-es #debian-devel-es #debian-devel-it #debian-l10n-fr #debian-a11y
03:18-!-pamaury [~pamaury@2a02:c7f:60fd:1100:8286:9881:abe9:3d42] has joined #debian
03:18-!-pamaury is "Amaury Pouly" on #oftc #debian-next #debian
03:21-!-nu-c [] has quit [Ping timeout: 480 seconds]
03:23-!-awal1 [] has joined #debian
03:23-!-awal1 is "realname" on #debian-devel-changes #debian-next #debian
03:23-!-imega [~coma@] has joined #debian
03:23-!-imega is "coma" on #fai #debian #ceph
03:23-!-TheRuralJuror [] has joined #debian
03:23-!-TheRuralJuror is "AP,,," on #security #debian-next #debian
03:24-!-Ericounet [~Eric@2a01:e0a:d0:3c20:6748:ef73:2cfa:50e7] has quit [Quit: Je m'en vais ...]
03:24-!-partlycloudy [] has joined #debian
03:24-!-partlycloudy is "partlycloudy" on #debian #ceph
03:26-!-partlycl- [] has quit [Ping timeout: 480 seconds]
03:38-!-imega [~coma@] has quit [Ping timeout: 480 seconds]
03:41-!-os_ [~Usama@] has quit [Ping timeout: 480 seconds]
03:44-!-mentor [] has quit [Ping timeout: 480 seconds]
03:45-!-ao2 [] has joined #debian
03:45-!-ao2 is "ao2" on #vcs-home #debian #cell
03:50-!-ianma [~ianma@] has joined #debian
03:50-!-ianma is "IanMa" on #poweradmin #debian
03:52-!-jipege [~quassel@2a01:cb19:85fa:2d00:c035:b7b9:acd4:1a3c] has quit [Remote host closed the connection]
03:53-!-tejr [] has quit [Remote host closed the connection]
03:54-!-jipege [~quassel@2a01:cb19:85fa:2d00:6c1e:c421:abac:5a77] has joined #debian
03:54-!-jipege is "jipege" on #debian #debian-l10n-fr
03:57-!-tejr [] has joined #debian
03:57-!-tejr is "Tom Ryder" on #perl #debian-vim #debian-perl #debian-lts #debian
04:08-!-Chitral_J [~Chitral_J@2401:4900:5239:cdf0:7f57:5b53:f386:c515] has joined #debian
04:08-!-Chitral_J is "realname" on #debian
04:08-!-Chitral_J [~Chitral_J@2401:4900:5239:cdf0:7f57:5b53:f386:c515] has quit []
04:12-!-czesmir_ [] has joined #debian
04:12-!-czesmir_ is "Stefan" on #debian-next #debian
04:17-!-pamaury [~pamaury@2a02:c7f:60fd:1100:8286:9881:abe9:3d42] has quit [Ping timeout: 480 seconds]
04:19-!-lunc [~omnd@] has quit [Ping timeout: 480 seconds]
04:19-!-czesmir [] has quit [Ping timeout: 480 seconds]
04:20-!-mcope [~mcope@] has joined #debian
04:20-!-mcope is "Matthew Cope" on #debian-kde #debian
04:25-!-os_ [~Usama@] has joined #debian
04:25-!-os_ is "realname" on #debian #debian-next
04:38-!-krauser [] has joined #debian
04:38-!-krauser is "krauser" on #debian
04:38-!-krauser is now known as krauser_
04:39-!-krauser_ is now known as krauser
04:39-!-krauser [] has quit []
04:39-!-diogenes_oftc [~diogenes_@] has joined #debian
04:39-!-diogenes_oftc is "Nicolas" on #debian
04:41-!-krauser [] has joined #debian
04:41-!-krauser is "krauser" on #debian
04:42-!-krauser is now known as krauserii
04:45-!-NomadJim [~Jim@] has joined #debian
04:45-!-NomadJim is "Nomad" on #linode #debian
04:45-!-NomadJim_ [~Jim@] has quit [Read error: Connection reset by peer]
04:52-!-vseva [] has joined #debian
04:52-!-vseva is "Your Name" on #debian
04:55-!-jgowdy [] has quit [Quit: ZNC -]
04:55-!-jgowdy [] has joined #debian
04:55-!-jgowdy is "jgd" on #debian
05:00-!-pwgen [~smuxi@] has joined #debian
05:00-!-pwgen is "Eric Weiss" on #debian
05:00-!-awal1 [] has quit [Quit: Leaving]
05:00-!-ianma_ [~ianma@] has joined #debian
05:00-!-ianma_ is "IanMa" on #poweradmin #debian
05:01-!-ianma [~ianma@] has quit [Ping timeout: 480 seconds]
05:05-!-krauserii [] has quit [Quit: Konversation terminated!]
05:06-!-czesmir_ is now known as czesmir
05:08-!-Brigo [] has joined #debian
05:08-!-Brigo is "realname" on #debian-offtopic #debian-next #debian-es #debian
05:10-!-jmux [~jan-marek@2a01:c22:6e28:7c00:4236:798:9871:3460] has joined #debian
05:10-!-jmux is "Jan-Marek Glogowski" on #debian
05:11-!-mimi89999 [] has left #debian [Error from remote client]
05:12-!-mimi89999 [] has joined #debian
05:12-!-mimi89999 is "mimi89999" on #debian
05:18-!-mode/#debian [+l 701] by debhelper
05:22-!-lft2496 [] has joined #debian
05:22-!-lft2496 is "lofty2496" on #debian
05:23-!-imega [~coma@] has joined #debian
05:23-!-imega is "coma" on #fai #debian #ceph
05:34-!-diogenes_oftc [~diogenes_@] has quit [Quit: vergissmeinnicht]
05:34-!-lft2496 [] has quit [Ping timeout: 480 seconds]
05:36-!-ianma [~ianma@] has joined #debian
05:36-!-ianma is "IanMa" on #poweradmin #debian
05:37-!-arnoldoree [] has quit [Ping timeout: 480 seconds]
05:37-!-ao2 [] has quit [Quit: Leaving]
05:39-!-ianma_ [~ianma@] has quit [Ping timeout: 480 seconds]
05:40<berto>does anyone know how to reset an NVMe hard drive that is protected with a password on the BIOS? I don't care about losing the data
05:42-!-cyphase [] has quit [Ping timeout: 480 seconds]
05:42-!-Argus [] has joined #debian
05:42-!-Argus is "Lou Poppler" on #debian #debian-next
05:42-!-lft2496 [] has joined #debian
05:42-!-lft2496 is "lofty2496" on #debian
05:45-!-testi [~quassel@2a02:120b:c3c5:7040:3ea8:2aff:fe9f:20b4] has quit [Quit: - Chat comfortably. Anywhere.]
05:47-!-alex_ [] has joined #debian
05:47-!-alex_ is "your worst nightmare" on #debian #debian-next #bitlbee
05:47<jm_>not sure how password may affect it, but you could try with the nvme tool, either sanitize or format
05:47<berto>tried that, no luck
05:48<berto>NVMe status: INVALID_OPCODE: The associated command opcode field is not valid(0x1)
05:48-!-ianma_ [~ianma@] has joined #debian
05:48-!-ianma_ is "IanMa" on #poweradmin #debian
05:48-!-Sqrt{not} [] has quit [Ping timeout: 480 seconds]
05:49<jm_>and it does support them?
05:49-!-ianma [~ianma@] has quit [Ping timeout: 480 seconds]
05:50-!-lunc [~omnd@] has joined #debian
05:50-!-lunc is "lunc" on #debian #oftc #help
05:51-!-sidmo__ [] has quit [Quit: Konversation terminated!]
05:52<berto>well they don't work, it seems that all access to the drive is locked, opening the device returns an I/O error
05:52-!-alex11 [] has quit [Ping timeout: 480 seconds]
05:52<jm_>ahh, sorry no idea then
05:53-!-imega [~coma@] has quit [Ping timeout: 480 seconds]
05:54-!-user [~user@] has joined #debian
05:54-!-user is "realname" on #debian
05:54-!-user [~user@] has quit []
05:54-!-sidmo__ [] has joined #debian
05:54-!-sidmo__ is "sidmo" on #debian-next #debian-offtopic #debian-kde #debian
05:57-!-gr_wity is now known as grawity
06:00-!-Brigo [] has quit [Ping timeout: 480 seconds]
06:02-!-gnugr [~gnugr@] has joined #debian
06:02-!-gnugr is "Vangelis Mouhtsis" on #debian-xfce #debian-owncloud #debian-devel-changes #debian #debian-ayatana
06:03-!-cyphase [] has joined #debian
06:03-!-cyphase is "Cyphase" on @#heroes #guardianproject #ceph #virt #debian #debian-next # @#PrisonBreak #quodlibet #qemu #ceph-devel @#lost @#p4xriddle
06:08-!-lft2497 [] has joined #debian
06:08-!-lft2497 is "lofty2496" on #debian
06:09-!-lft2496 [] has quit [Ping timeout: 480 seconds]
06:10-!-dselect [] has quit [Quit: ouch... that hurt]
06:11-!-dselect [] has joined #debian
06:11-!-dselect is "dpkg backup readonly db" on #debian
06:11-!-testi [~quassel@2a02:120b:c3c5:7040:3ea8:2aff:fe9f:20b4] has joined #debian
06:11-!-testi is "Dietrich Helexien" on @#docker #debian-next #debian @#hardware @#xrdp @#roccat
06:14-!-arsh [~quassel@] has joined #debian
06:14-!-arsh is "arsh,,," on #debian
06:16-!-ianma_ [~ianma@] has quit [Ping timeout: 480 seconds]
06:23-!-ianma [~ianma@] has joined #debian
06:23-!-ianma is "IanMa" on #poweradmin #debian
06:26-!-arsh [~quassel@] has quit [Ping timeout: 480 seconds]
06:30-!-Ericounet [~Eric@2a01:e0a:d0:3c20:6748:ef73:2cfa:50e7] has joined #debian
06:30-!-Ericounet is "realname" on #freedombox #debian
06:31-!-tnewman [] has quit [Quit: Ping timeout (120 seconds)]
06:31-!-tnewman [] has joined #debian
06:31-!-tnewman is "Travis Newman" on #debian
06:32-!-erle- [~stephan@2a04:ee41:3:3297:8540:6f69:4d3b:4b15] has joined #debian
06:32-!-erle- is "Stephan" on #mobian #debian #debian-raspberrypi
06:33-!-flappy [] has quit [Ping timeout: 480 seconds]
06:36-!-{4144}| [~{4144}@] has quit [Read error: Connection reset by peer]
06:40-!-diogenes_oftc [~diogenes_@] has joined #debian
06:40-!-diogenes_oftc is "Nicolas" on #debian
06:44-!-silver [] has quit [Remote host closed the connection]
06:44-!-silver [] has joined #debian
06:44-!-silver is "Jesse Lee Morgan" on #experimental #oftc #moocows #C #mm #linux #neurodebian #debian-offtopic #debian-nginx #debian-kde #debian-next #debian #debian-support #debian-devel-changes #minidebconf-online #debian-meeting #debconf-cambridge
06:45-!-pavlushka [] has joined #debian
06:45-!-pavlushka is "Pavel Sayekat" on #debian #oftc
06:45-!-andibmu [~andi@] has quit [Ping timeout: 480 seconds]
06:49-!-ianma [~ianma@] has quit [Ping timeout: 480 seconds]
06:49-!-tnewman [] has quit [Quit: Ping timeout (120 seconds)]
06:49-!-tnewman [] has joined #debian
06:49-!-tnewman is "Travis Newman" on #debian
06:50-!-gabriel1 [] has joined #debian
06:50-!-gabriel1 is "Gabx" on #security #retroshare #Qubes_OS #i2p #debian
06:51-!-gabriel1 [] has quit [Remote host closed the connection]
06:51-!-gabriel1 is "Gabx" on #security #retroshare #Qubes_OS #i2p #debian
06:51-!-gabriel1 [] has joined #debian
06:54-!-ianma [~ianma@] has joined #debian
06:54-!-ianma is "IanMa" on #poweradmin #debian
06:59-!-{4144}| [~{4144}@] has joined #debian
06:59-!-{4144}| is "KVIrc 5.0.0 Aria" on #qemu #tmw-br #debian-next #debian
07:01-!-nuc [] has quit [Read error: Connection reset by peer]
07:01-!-nuc [] has joined #debian
07:01-!-nuc is "realname" on #debian
07:04-!-ftobich [] has joined #debian
07:04-!-ftobich is "Fabio A. De Muzio Tobich" on #debian-cwb #debian-next #debian #debian-devel-br #debian-devel-changes #debian-br
07:05-!-dpkg [] has quit [Quit: buh bye!]
07:05-!-dpkg [] has joined #debian
07:05-!-dpkg is "apt backup" on #debian
07:06-!-freshtube [~freshtube@] has quit [Ping timeout: 480 seconds]
07:06-!-tnewman [] has quit [Quit: Ping timeout (120 seconds)]
07:09-!-ianma [~ianma@] has quit []
07:12-!-nuc [] has quit [Read error: Connection reset by peer]
07:13-!-nuc [] has joined #debian
07:13-!-nuc is "realname" on #debian
07:13-!-zebrag [] has joined #debian
07:13-!-zebrag is "inkbottle" on #oftc #debian-kde #debian-next #debian #kernelnewbies
07:20-!-otisolsen70 [] has joined #debian
07:20-!-otisolsen70 is "realname" on #debian-nordic #debian #packaging
07:28-!-Xinayder [] has quit [Remote host closed the connection]
07:29-!-Xinayder [~xinayder@] has joined #debian
07:29-!-Xinayder is "ZNC -" on #packaging #debian-br #debian
07:29-!-polymetric [] has quit [Ping timeout: 480 seconds]
07:50-!-ph0b0s [] has quit [Remote host closed the connection]
07:52-!-ph0b0s [] has joined #debian
07:52-!-ph0b0s is "ph0b0s" on #debian
07:55-!-zebrag [] has quit [Quit: Konversation terminated!]
07:58<Tas-sos>Hello Debian GNU/Linux community, I had a problem with a web app tha using MySQL database
07:59<Tas-sos>and in testing machine I got zero ( 0 ) values in some responses, finaly I found out the solution
07:59<Tas-sos>but I do not fully understand what really happened.. could you help me please?
08:00<Tas-sos>the solution is just to run the following command :
08:00<Tas-sos>mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql -u root -p mysql
08:00<Tas-sos>and after that to restart the mysql server
08:00<Tas-sos>and now all the queries works perfect!
08:01<Tas-sos>Could you help to undertand what happens now ?
08:02-!-kathenas [~kathenas@2a02:c7f:e512:a500:761b:dd83:9b43:bc40] has quit [Quit: Leaving]
08:04-!-dvs [] has joined #debian
08:04-!-dvs is "realname" on #debian
08:06-!-imega [~coma@] has joined #debian
08:06-!-imega is "coma" on #fai #debian #ceph
08:08-!-ddsys [] has joined #debian
08:08-!-ddsys is "ddsys" on #debian-offtopic #debian-next #debian
08:09-!-thiras [~thiras@] has joined #debian
08:09-!-thiras is "Ant Somers" on #debian
08:10-!-kathenas [~kathenas@2a02:c7f:e512:a500:761b:dd83:9b43:bc40] has joined #debian
08:10-!-kathenas is "Phil Wyett" on #packaging #debian #debian-ai #debian-next #debian-meeting
08:11-!-TheRuralJuror [] has quit []
08:25-!-andibmu [~andi@] has joined #debian
08:25-!-andibmu is "Andreas B. Mundt" on #debian-meeting #debian #debian-next #debian-offtopic #debian-edu #debian-lan
08:25-!-wololoer [] has joined #debian
08:25-!-wololoer is "user" on #qemu #kvm #virt #suckless #openjdk #debian-next #debian
08:26-!-zebrag [] has joined #debian
08:26-!-zebrag is "inkbottle" on #oftc #debian-kde #debian-next #debian #kernelnewbies
08:27-!-blue_penquin [] has joined #debian
08:27-!-blue_penquin is "blue_penquin" on #debian
08:28-!-mode/#debian [+l 708] by debhelper
08:29<petn-randall>Tas-sos: What queries gave you zero responses? And why is that surprising to you?
08:30<petn-randall>Tas-sos: That command does this:
08:30<petn-randall>But hard to say what your issue is if you left that part out.
08:31-!-chele [~chele@] has joined #debian
08:31-!-chele is "chele" on #debian-next #debian
08:33-!-igormuzetti [] has joined #debian
08:33-!-igormuzetti is "igor" on #debian
08:37-!-moldorcoder7 [~moldorcod@] has joined #debian
08:37-!-moldorcoder7 is "moldorcoder7" on #virt #qemu #openvas #llvm #debian-next #debian #C
08:38-!-dvs [] has quit [Remote host closed the connection]
08:46-!-chele [] has quit [Quit: Leaving]
08:49-!-wololoer [] has quit [Quit: WeeChat 3.0.1]
08:49-!-plaur [~laur@] has joined #debian
08:49-!-plaur is "laur" on #debian
08:50-!-wololoer [] has joined #debian
08:50-!-wololoer is "user" on #qemu #kvm #virt #suckless #openjdk #debian-next #debian
08:55-!-jm_ [] has quit [Quit: Disconnecting]
08:58-!-Granth [~Granth@] has joined #debian
08:58-!-Granth is "realname" on #debian
08:59-!-Granth [~Granth@] has quit []
09:02-!-Blacker47 [] has joined #debian
09:02-!-Blacker47 is "Blacker47" on #debian-next #debian
09:10-!-Haudegen [~quassel@] has joined #debian
09:10-!-Haudegen is "AP,,," on #security #debian-next #debian
09:12-!-miettine [] has joined #debian
09:12-!-miettine is "." on #debian #oftc #C #debian-next #debian-glibc #linux #tor-bots #virtualization #freedombox #msys2 #ceph
09:12-!-pavlushka [] has quit [Ping timeout: 480 seconds]
09:13-!-miettine [] has quit [Remote host closed the connection]
09:14-!-bstockwell87 [~ben@] has joined #debian
09:14-!-bstockwell87 is "Ben" on #debian
09:19-!-tarzeau_ [] has joined #debian
09:19-!-tarzeau_ is "Alex Myczko" on #debian #packaging #debian-init #debian-bsp-2021-szg #green-pears-eat-red-bananas-and-blue-oranges #objfw #bash #debian-privacy #debian-superh #minidebconf-online #debian-games #debian-go #debian-janitor #debian-perl #debian-ai #debian-netdata #meshlab #debian-rant #pkg-phototools #debian-java #debian-devel-changes #debian-fasttrack #debian-hpc #debian-bts #debian-next #debian-pl #debian-curiosa #debian-astro
09:20-!-plaur [~laur@] has quit [Quit: WeeChat 2.3]
09:22-!-imega [~coma@] has quit [Ping timeout: 480 seconds]
09:23-!-os__ [~Usama@] has joined #debian
09:23-!-os__ is "realname" on #debian #debian-next
09:28-!-pavlushka [] has joined #debian
09:28-!-pavlushka is "Pavel Sayekat" on #debian #oftc
09:29-!-os_ [~Usama@] has quit [Ping timeout: 480 seconds]
09:35-!-hoonetorg [~hoonetorg@] has quit [Ping timeout: 480 seconds]
09:38-!-f10 [] has joined #debian
09:38-!-f10 is "f10" on #debian-kde #debian
09:44-!-artur [~smuxi@] has joined #debian
09:44-!-artur is "Your Name" on #debian
09:45-!-hoonetorg [~hoonetorg@] has joined #debian
09:45-!-hoonetorg is "hoonetorg" on #ceph #ceph-ansible #debian #debian-installer #ovirt #debian-next
09:46-!-vseva [] has quit [Remote host closed the connection]
09:47-!-Alexer [] has joined #debian
09:47-!-Alexer is "Aleksi Torhamo" on #debian
09:52-!-bstockwell87 [~ben@] has quit [Quit: Lost terminal]
09:54-!-alex11 [] has joined #debian
09:54-!-alex11 is "your worst nightmare" on #debian #debian-next #bitlbee
09:57-!-towo^work [] has quit [Quit: Leaving]
09:57-!-dogsleg_ [~dogsleg@] has joined #debian
09:57-!-dogsleg_ is "Lev Lamberov" on #debian-social #debian-l10n-russian #debian-devel-changes #debian-meeting #debian
09:58-!-inkbottle[m] [~inkbottle@2001:470:1af1:101::8040] has joined #debian
09:58-!-inkbottle[m] is "org.matrix:inkbottle" on #debian
10:00-!-alex_ [] has quit [Ping timeout: 480 seconds]
10:04-!-dogsleg [] has quit [Ping timeout: 480 seconds]
10:05-!-uos_eric2023 [~quassel@] has quit [Remote host closed the connection]
10:05-!-Mohammad [] has joined #debian
10:05-!-Mohammad is "realname" on #debian
10:07-!-Mohammad [] has quit []
10:07-!-voyager1 [] has quit [Quit: ...]
10:11-!-voyager1 [] has joined #debian
10:11-!-voyager1 is "user" on #debian
10:23-!-andibmu [~andi@] has quit [Ping timeout: 480 seconds]
10:25-!-ax5623 [] has joined #debian
10:25-!-ax5623 is "realname" on #debian-next #debian #linux
10:26-!-Brainium [] has joined #debian
10:26-!-Brainium is "brainium" on #debian-social #linux #virt #qemu #C #tor-project #debian-br #debian-kde #debian
10:29-!-gabriel1 [] has quit [Ping timeout: 480 seconds]
10:29-!-mentor [] has joined #debian
10:29-!-mentor is "Matthew W.S. Bell" on #debian
10:31-!-ax562 [] has quit [Ping timeout: 480 seconds]
10:31-!-Ericounet [~Eric@2a01:e0a:d0:3c20:6748:ef73:2cfa:50e7] has quit [Read error: Connection reset by peer]
10:32-!-diogenes_oftc [~diogenes_@] has quit [Quit: vergissmeinnicht]
10:32-!-towo` [] has joined #debian
10:32-!-towo` is "Torsten -towo- Wohlfarth" on #qemu #kernelnewbies #siduction-admin #debian-offtopic #debian-next #debian #aptosid
10:39-!-lunc [~omnd@] has quit [Ping timeout: 480 seconds]
10:40-!-mlavrik [] has joined #debian
10:40-!-mlavrik is "mlavrik,,," on #debian-academy #debian
10:41-!-mlavrik [] has quit []
10:48-!-user2259847770 [~user22598@] has joined #debian
10:48-!-user2259847770 is "realname" on #tor-l10n #tor-south #tor-project #debian
10:48-!-nuc [] has quit [Read error: Connection reset by peer]
10:48-!-nuc [] has joined #debian
10:48-!-nuc is "realname" on #debian
10:50<user2259847770>linux is a meme os
10:51-!-jar-el [~jar-el@2a02:a466:2ea6:1:9c09:73cf:d178:9e42] has joined #debian
10:51-!-jar-el is "realname" on #debian-offtopic #debian-games #debian
10:52-!-user2259847770 [~user22598@] has quit []
10:58-!-qsx [] has quit [Quit: - Chat comfortably. Anywhere.]
10:58-!-qsx [] has joined #debian
10:58-!-qsx is "qsx" on #ceph #debian
10:59-!-hele [] has joined #debian
10:59-!-hele is "hele" on #debian-next #debian
11:01-!-lanoxx [] has joined #debian
11:01-!-lanoxx is "realname" on #debian
11:03-!-liquidsnake [] has joined #debian
11:03-!-liquidsnake is "realname" on #debian-offtopic #MXLinux #linux #debian #retroshare
11:06-!-lunc [~omnd@] has joined #debian
11:06-!-lunc is "lunc" on #debian #oftc #help
11:08-!-mode/#debian [+l 714] by debhelper
11:08-!-andibmu [~andi@] has joined #debian
11:08-!-andibmu is "Andreas B. Mundt" on #debian-meeting #debian #debian-next #debian-offtopic #debian-edu #debian-lan
11:09-!-zleap [] has joined #debian
11:09-!-zleap is "realname" on #minidebconf-online #debian-academy #debian-next #debian
11:10-!-filePeter [] has quit [Quit: Lost terminal]
11:10-!-ryzokuken [] has quit [Ping timeout: 480 seconds]
11:14-!-mcope [~mcope@] has quit [Quit: Konversation terminated!]
11:15-!-r4fkramer [] has joined #debian
11:15-!-r4fkramer is "realname" on #debian
11:16<r4fkramer>I saw on the Debian website in the 'Security Information' section, that this repository line is treated in a more particular way, as it is recommended primarily to be included in the Debian sources.list, for security purposes:
11:16<r4fkramer>deb buster/updates main contrib non-free
11:16<r4fkramer>However, there is also this line:
11:16<r4fkramer>deb buster / updates main contrib non-free
11:16<r4fkramer>My question is: Please, what is the difference between the two in relation to the item 'Security'?
11:17<petn-randall>r4fkramer: The bottom one should at least give you some error, as that isn't valid syntax.
11:17-!-gmelis [~gmelis@2a02:587:2912:4e05:f4b:50e0:fd37:3208] has joined #debian
11:17-!-gmelis is "Gerasimos Melissaratos" on #debian
11:17-!-gmelis [~gmelis@2a02:587:2912:4e05:f4b:50e0:fd37:3208] has quit []
11:17<r4fkramer>petn-randall, what is not a valid syntax
11:17-!-craigevil [] has joined #debian
11:17-!-craigevil is "craig" on #debian-raspberrypi #debian-next #debian-offtopic #debian
11:18<petn-randall>r4fkramer: Try the bottom line, you should get an error.
11:18<r4fkramer>I have both in my sources.list, and update hasn't generated any error log
11:18-!-gmelis [~gmelis@2a02:587:2912:4e05:f4b:50e0:fd37:3208] has joined #debian
11:18-!-gmelis is "Gerasimos Melissaratos" on #debian
11:19<petn-randall>r4fkramer: will tell you what it is.
11:19-!-Alexer [] has quit [Ping timeout: 480 seconds]
11:19<petn-randall>For all practical purposes both mirrors are the same.
11:20-!-liquidsnake [] has quit [Quit: Leaving]
11:20<petn-randall>r4fkramer: Err:4 buster Release 404 Not Found [IP: 2a04:4e42:62::644 80]
11:20-!-usernet [] has joined #debian
11:20-!-usernet is "realname" on #python #C #debian
11:20<r4fkramer>Doesn't make sense both lines refer to the same repo....
11:20<petn-randall>If you have "buster / updates" in there, it'll give you an error.
11:20<petn-randall>Note the spaces around the /.
11:21-!-wololoer [] has quit [Quit: WeeChat 3.0.1]
11:21<r4fkramer>Ok, I will check it now.
11:22<petn-randall>Why doesn't it make sense if both lines refer to the same repo?
11:22<r4fkramer>So, in this case, I can remove deb buster/updates main contrib non-free
11:22<dpkg>A suitable /etc/apt/sources.list for "Buster" has the lines: "deb buster main" "deb buster/updates main", and optionally "deb buster-updates main". See <deb-src> <contrib> <non-free> <buster/updates> <buster-updates> and "man sources.list".
11:22<petn-randall>r4fkramer: I'd go with those lines. ^^^
11:24<r4fkramer>I don't understand why two different lines should make sense, if they refer to the same function in sources.list If they don't do any difference during update && upgrade - just one is enough
11:24<petn-randall>r4fkramer: Well, you added one of them ...
11:24-!-usernet [] has quit []
11:25<r4fkramer>Yes, I have both them, but now, after your explanation, I will remove one of them; in this case, I will remove deb buster/updates main contrib non-free
11:25<r4fkramer>And mantain the other; I suppose your sources.list have just one of them.
11:26<cambrian_invader>what is the correct way to set the wireless regulatory domain on boot?
11:27-!-diogenes_oftc [~diogenes_@] has joined #debian
11:27-!-diogenes_oftc is "Nicolas" on #debian
11:27<r4fkramer>Fine, petn-randall, in fact, I haven't realized any error log during update here. But, I will remove one of them. Thank you very much for Attention and Great Support :)
11:28-!-blue_penquin [] has quit [Remote host closed the connection]
11:29-!-mbond [] has joined #debian
11:29-!-mbond is "mbond" on #debian
11:31-!-gothicserpent [] has quit [Quit: Leaving]
11:34-!-r4fkramer [] has quit [Quit: Leaving]
11:35-!-Blacker47 [] has quit [Quit: Life is short. Get a V.90 modem fast!]
11:38-!-ax5623 [] has quit [Quit: Leaving]
11:40-!-freshtube [~freshtube@] has joined #debian
11:40-!-freshtube is "realname" on #redditprivacy #debian
11:41-!-Blacker47 [] has joined #debian
11:41-!-Blacker47 is "Blacker47" on #debian-next #debian
11:44-!-ahso [] has joined #debian
11:44-!-ahso is "ahso" on #debian-next #debian #debian-wsl
11:44-!-Haudegen [~quassel@] has quit [Quit: Bin weg.]
11:45-!-drakonis [] has quit [Quit: WeeChat 3.1]
11:47-!-ax562 [] has joined #debian
11:47-!-ax562 is "realname" on #linux #debian #debian-next
11:48-!-drakonis [] has joined #debian
11:48-!-drakonis is "drakonis" on #debian-offtopic #debian
11:48-!-debabrata [~debabrata@2409:4052:228a:b1c2:dd21:b7dd:7793:8cf7] has joined #debian
11:48-!-debabrata is "realname" on #debian
11:49-!-ruppert1 [~ruppert@2a02:810c:200:195c:21c:25ff:fe95:8294] has joined #debian
11:49-!-ruppert1 is "ruppert" on #debian #oftc
11:49-!-pavlushka [] has quit [Ping timeout: 480 seconds]
11:51-!-freshtube [~freshtube@] has quit [Quit: Leaving]
11:52-!-debabrata [~debabrata@2409:4052:228a:b1c2:dd21:b7dd:7793:8cf7] has quit []
11:52-!-ax562 [] has quit [Quit: Leaving]
11:55-!-ax562 [] has joined #debian
11:55-!-ax562 is "realname" on #linux #debian #debian-next
11:56-!-kfvn_ [] has quit [Remote host closed the connection]
11:57-!-kfvn_ [] has joined #debian
11:57-!-kfvn_ is "weechat" on #debian
11:58<Tas-sos>petn-randall: I really thank you for you interest and try to help! I appreciate it! Thank you
11:58-!-pavlushka [] has joined #debian
11:58-!-pavlushka is "Pavel Sayekat" on #debian #oftc
11:58<Tas-sos>To be honest, I didn't know that this command exist for databases... I have never see a similar problem like this today with a web app for example that uses database..
11:59-!-sappheiros [~sappheiro@2603:9004:510:d155:ec99:552d:17c8:ddc2] has joined #debian
11:59-!-sappheiros is "realname" on ##Christian #debian
12:00<Tas-sos>With this command, what we will fix ?
12:00-!-_cr_ [] has quit [Read error: Connection reset by peer]
12:00<Tas-sos>In some cases its required ? When ? Why ?
12:00-!-_cr_ [] has joined #debian
12:00-!-_cr_ is "Carsten Rosenberg" on #debian @#clamav
12:01<Tas-sos>For example, this is my (today) case: with my friend we have a django web application - actualy a API
12:01<petn-randall>Tas-sos: ... you're still not explaining your problem. You're making vague statements to some MySQL database.
12:01<Tas-sos>and we have write many requests, that uses the database, but today, my friend push a part of code that
12:02<Tas-sos>only in your laptop works ( with SQLite first - but after also installs locally MySQL 5 and workS )
12:03<Tas-sos>your end point return results.. but in testing machine, it returns only zero (0) - nothing else
12:03-!-plains [] has quit [Quit: ZNC 1.8.2+deb1+focal2 -]
12:03-!-kevinniuwu [~kevin@] has quit [Remote host closed the connection]
12:04-!-plains [~plains@] has joined #debian
12:04-!-plains is "plains" on #redditprivacy #debian
12:04<petn-randall>Tas-sos: It seems to me like your best chance is asking #python, or django support what is actually happening, since that's also a layer in between.
12:05<petn-randall>(also, update your system, jessie LTS has been unsupported for nearly a year now.)
12:06-!-kevinniuwu [~kevin@] has joined #debian
12:06-!-kevinniuwu is "Kevin Wu" on #debian
12:06-!-kevinniuwu [~kevin@] has left #debian []
12:06-!-kevinniuwu is "Kevin Wu" on #debian
12:06-!-kevinniuwu [~kevin@] has joined #debian
12:07<Tas-sos>yes, I know.. and thank you for your kind help - and you do not immediately persecute me with the voices "get out of this channel" ^_^
12:07<petn-randall>We'd only do that if you're mean, which you are not ;)
12:08<Tas-sos>thank for the directions to another channels, I also try to ask here and find a way to figure out what's going on.. ( and of course I try to read and search about this )
12:10<Tas-sos>But I really think this is something intermediate - between the system and the application, thats why I also ask here to discuss with other people..
12:11<Tas-sos>xaxaax yes I know about the Debian GNU/Linux 8 ^_^ It's a litle bit "old", but for now But for now we can not go elsewhere.. thanks btw ^_^ )
12:11<petn-randall>Tas-sos: To be honest your problem is not well presented. It's unclear to me what that database contains. So it's unclear to me why you expect data being returned. And it's also unclear to me what data *is* being returned after the "fix".
12:12-!-mobian [~mobian@] has joined #debian
12:12-!-mobian is "mobian" on #debian
12:12-!-lft2497 [] has quit [Quit: ⠟⠥⠊⠞]
12:12-!-lft2496 [] has joined #debian
12:12-!-lft2496 is "lofty2496" on #debian
12:12-!-sig is now known as sig_9
12:13<Tas-sos>but - if it is a sample a sample - in CentOS 7 ( with the same version of MySQL ) we have exactly the same results... 0 in this requests :-/
12:13-!-mobian_ [~mobian@] has joined #debian
12:13-!-mobian_ is "mobian" on #debian
12:13-!-Redentor [~armando@2600:3c01:e000:20c:26a:b4b9:9a0e:e249] has joined #debian
12:13-!-Redentor is "realname" on #linode #debian-next #debian-es #debian-mx #debian
12:13<Tas-sos>hm... yes, you're right
12:14-!-mobian [~mobian@] has quit []
12:14-!-mobian_ [~mobian@] has quit []
12:16<Tas-sos>you aren't wrong! ^_^ I really, thank you! I try to search a litle more, and if I can to presend better what happens, I will tell you :-)
12:16<Tas-sos>Thank you my friend for your time :-)
12:17-!-gmelis [~gmelis@2a02:587:2912:4e05:f4b:50e0:fd37:3208] has quit [Quit: Konversation terminated!]
12:18-!-rojin [~rojin@2401:4900:507f:9fb3:825b:71f8:3527:928] has joined #debian
12:18-!-rojin is "realname" on #minidebconf-india-rex #minidebconf-india-buzz #kernelnewbies #minidebconf-online #minidebconf-india #debian #debian-india
12:18-!-ddsys [] has quit [Quit: Leaving]
12:24-!-ach [] has quit [Read error: Connection reset by peer]
12:24-!-gothicserpent [] has joined #debian
12:24-!-gothicserpent is "realname" on #scilab #publiclab #oftc #linux #debian #C
12:30-!-freshtube [~freshtube@] has joined #debian
12:30-!-freshtube is "realname" on #redditprivacy #debian
12:30-!-devlab [~AdminUser@2804:3b18:8001:1:794a:5306:800f:af63] has joined #debian
12:30-!-devlab is "Bruno,,," on #debian
12:30-!-devlab [~AdminUser@2804:3b18:8001:1:794a:5306:800f:af63] has quit []
12:32-!-RedSoxFan07 [] has joined #debian
12:32-!-RedSoxFan07 is "RedSoxFan07" on #debian-next #debian
12:32-!-artur [~smuxi@] has quit [Remote host closed the connection]
12:32-!-brnfra [~AdminUser@2804:3b18:8001:1:794a:5306:800f:af63] has joined #debian
12:32-!-brnfra is "Bruno" on #debian
12:33-!-brnfra [~AdminUser@2804:3b18:8001:1:794a:5306:800f:af63] has quit []
12:39-!-RedSoxFan07 [] has quit [Quit: RedSoxFan07]
12:50-!-texou [] has quit [Quit: WeeChat 3.0.1]
12:53-!-brunoramos_ [~brunoramo@] has joined #debian
12:53-!-brunoramos_ is "ZNC -" on #packaging #oftc #help #debian-xfce #debian-perl #debian-next #debian
12:54-!-texou [] has joined #debian
12:54-!-texou is "Stoicien" on #debian-nonupload #debian-i18n #bitlbee #debian-next #debian #debian-es #debian-devel-es #debian-devel-it #debian-l10n-fr #debian-a11y
12:55-!-Mister00X [] has joined #debian
12:55-!-Mister00X is "Mr. X" on #debian-de #debian #debian-next
12:55-!-Redentor [~armando@2600:3c01:e000:20c:26a:b4b9:9a0e:e249] has quit [Quit: Leaving]
12:56-!-brunoramos [~brunoramo@] has quit [Ping timeout: 480 seconds]
12:56-!-brunoramos_ is now known as brunoramos
12:56-!-expzak [~expzak@2001:4451:873a:3600:376f:e851:95ec:c7a3] has joined #debian
12:56-!-expzak is "realname" on #debian
12:57-!-towo` [] has quit [Quit: Leaving]
12:59-!-towo` [] has joined #debian
12:59-!-towo` is "Torsten -towo- Wohlfarth" on #qemu #kernelnewbies #siduction-admin #debian-offtopic #debian-next #debian #aptosid
13:00-!-mzajc [] has joined #debian
13:00-!-mzajc is "Marko Zajc" on #debian-next #debian-kde #debian
13:00-!-Argus is now known as Sqrt{Not}
13:01-!-expzak [~expzak@2001:4451:873a:3600:376f:e851:95ec:c7a3] has quit []
13:01-!-Mister00X [] has quit [Remote host closed the connection]
13:03-!-texou [] has quit [Quit: WeeChat 3.0.1]
13:04-!-ax56234 [] has joined #debian
13:04-!-ax56234 is "+" on #debian
13:07-!-Mister00X [] has joined #debian
13:07-!-Mister00X is "Mr. X" on #debian #debian-de #debian-next
13:08-!-gabuscus_ [~quassel@] has quit [Ping timeout: 480 seconds]
13:10-!-TheRuralJuror [] has joined #debian
13:10-!-TheRuralJuror is "AP,,," on #security #debian-next #debian
13:12-!-diogenes_oftc [~diogenes_@] has quit [Quit: vergissmeinnicht]
13:13-!-rojin [~rojin@2401:4900:507f:9fb3:825b:71f8:3527:928] has quit [Remote host closed the connection]
13:15-!-kathenas [~kathenas@2a02:c7f:e512:a500:761b:dd83:9b43:bc40] has quit [Quit: Leaving]
13:27-!-peter82 [~peter82@] has joined #debian
13:27-!-peter82 is "realname" on #debian
13:27-!-kathenas [~kathenas@2a02:c7f:e512:a500:761b:dd83:9b43:bc40] has joined #debian
13:27-!-kathenas is "Phil Wyett" on #packaging #debian #debian-ai #debian-next #debian-meeting
13:28-!-peter82 [~peter82@] has left #debian []
13:29-!-peregrine8 [~peregrine@] has joined #debian
13:29-!-peregrine8 is "realname" on #debian-xfce #linux #debian-next #debian
13:34-!-hele [] has quit [Ping timeout: 480 seconds]
13:36-!-ao2 [] has joined #debian
13:36-!-ao2 is "ao2" on #vcs-home #debian #cell
13:38-!-broadfjord [] has joined #debian
13:38-!-broadfjord is "Bradford Boyle" on #debian
13:39-!-diogenes_oftc [~diogenes_@] has joined #debian
13:39-!-diogenes_oftc is "Nicolas" on #debian
13:40-!-pwgen [~smuxi@] has quit [Ping timeout: 480 seconds]
13:54-!-cristiancamilo [~cristianc@] has joined #debian
13:54-!-cristiancamilo is "realname" on #debian
13:58-!-IPFreely [~wh0kares@2001:4ba0:fffe:5::] has joined #debian
13:58-!-IPFreely is "wh0kares" on #freedombox #debian #Qubes_OS
13:59-!-cristiancamilo [~cristianc@] has quit []
14:00-!-IPFreely [~wh0kares@2001:4ba0:fffe:5::] has quit [Remote host closed the connection]
14:01-!-IPFreely [~wh0kares@2001:4ba0:fffe:5::] has joined #debian
14:01-!-IPFreely is "wh0kares" on #Qubes_OS #debian #freedombox
14:07-!-marian [] has quit [Quit: WeeChat 3.0.1]
14:10-!-anandh [~anandh@] has joined #debian
14:10-!-anandh is "realname" on #debian
14:10-!-anandh [~anandh@] has quit []
14:12<unixbsd>sney: hi sney, on wiki, there are littlee infomration about initramfs, i am professional. what are you attempting to do? which help do you needÃ?
14:13<sney>unixbsd: if you look again, you will see that a) the initramfs discussion was in the other #debian on freenode, and 2) I was helping someone else, not asking the question.
14:13<unixbsd>ah okÂ. good
14:13<sney>but thanks for your contribution, I guess?
14:14-!-texou [] has joined #debian
14:14-!-texou is "Stoicien" on #debian-nonupload #debian-i18n #bitlbee #debian-next #debian #debian-es #debian-devel-es #debian-devel-it #debian-l10n-fr #debian-a11y
14:20-!-mzajc [] has quit [Ping timeout: 480 seconds]
14:26-!-jwest [~jwest@2601:18c:cd7f:63c0:216:3eff:fe2a:4bbe] has joined #debian
14:26-!-jwest is "realname" on #debian-next #debian-lts #debian
14:27-!-jstein [] has joined #debian
14:27-!-jstein is "Jonas Stein" on #kernelnewbies @#fsfe @#mint #debian
14:27<unixbsd>the initramfs lacks of documentation. anyhow.
14:28-!-freshtube [~freshtube@] has quit [Quit: Leaving]
14:29-!-texou [] has quit [Quit: WeeChat 3.0.1]
14:29-!-omenfiend [~damion@] has joined #debian
14:29-!-omenfiend is "realname" on #debian
14:29-!-texou [] has joined #debian
14:29-!-texou is "Stoicien" on #debian-nonupload #debian-i18n #bitlbee #debian-next #debian #debian-es #debian-devel-es #debian-devel-it #debian-l10n-fr #debian-a11y
14:30-!-dmm- [~dmm@] has joined #debian
14:30-!-dmm- is "snake" on #debian
14:33-!-Brainium [] has quit [Ping timeout: 480 seconds]
14:35-!-PoPpiLLs [~damion@2600:1700:8731:af50:4c22:2bb3:3f1f:4fb0] has quit [Ping timeout: 480 seconds]
14:36-!-mzajc [] has joined #debian
14:36-!-mzajc is "Marko Zajc" on #debian-next #debian-kde #debian
14:37-!-dmm [~dmm@] has quit [Ping timeout: 480 seconds]
14:37-!-polymetric [] has joined #debian
14:37-!-polymetric is "polymetric" on #debian
14:40-!-giraffy [~giraffy@2601:603:1301:7f60:476b:43a1:f007:5a5d] has joined #debian
14:40-!-giraffy is "Kyle" on #debian
14:40-!-giraffy [~giraffy@2601:603:1301:7f60:476b:43a1:f007:5a5d] has left #debian []
14:40-!-dmm [~dmm@] has joined #debian
14:40-!-dmm is "snake" on #debian
14:43-!-dmm- [~dmm@] has quit [Ping timeout: 480 seconds]
14:47-!-shreeya [] has joined #debian
14:47-!-shreeya is "Shreeya Patel" on #debian
14:48-!-AnonDragonFly_ [] has quit [Quit: - Chat comfortably. Anywhere.]
14:49<shreeya>Hello, is this the right place to discuss about the boot failure I'm observing on my machine which has debian installed. It's probably related to lvm UUID which got messed up when I was trying to add a partition to rootfs
14:52<unixbsd>sure we can help
14:52<Sqrt{Not}>shreeya, Sure, a good place to start anyway.
14:53<unixbsd>do u use GRUB?
14:53<shreeya>unixbsd: yes
14:53<unixbsd>do you have kernel panic?
14:54<shreeya>Let me give you some context for better understanding
14:54<unixbsd>vmlinuz kernel will start first, from grub, once kernel loaded, it will look for a root (given by root=/dev/sda2 or ... some uuid).
14:56<shreeya>I was trying to create a new partition on my rootfs but I think I didn't do it correctly. Now after my system got rebooted, it giving me error as debian-vg-root does not exist. I end up on initramfs console
14:57<unixbsd>sudo apt-get install fdisk ; sudo fdisk -l
14:57-!-dpanterdpanter [~dpanter@] has joined #debian
14:57-!-dpanterdpanter is "realname" on #debian #debian-next
14:57<unixbsd>do you have a second way to medkit your machine?
14:57-!-bodiccea [~bodiccea@] has quit [Ping timeout: 480 seconds]
14:58<unixbsd>you might use the live cdrom for instance, fine for your this live?
14:58<shreeya>I am not able to boot into the machine at all
14:58<unixbsd>do you have a second PC ?
14:58<shreeya>Yes but haven't used it for ages
14:58<unixbsd>windows ?
14:58<shreeya>It has linux Ubuntu
14:58<unixbsd>so it is fine
14:59<unixbsd>do you prefer to use my tools or the regular groovy live ?
14:59-!-jwest [~jwest@2601:18c:cd7f:63c0:216:3eff:fe2a:4bbe] has quit [Quit: Leaving]
14:59<shreeya>Anything is fine
14:59-!-weaponx [~weaponx@] has joined #debian
14:59-!-weaponx is "realname" on #debian
14:59<unixbsd>ok, just: wget -c --no-check-certificate ""
15:00-!-weaponx [~weaponx@] has left #debian []
15:00<shreeya>But I do not really know the procedure or anything. I'm solving this kind of problem for the first time
15:00<unixbsd>Once you have it: sudo su; cat "ubuntu-20.10-desktop-amd64.iso" > /dev/sdb <-- considere sdb is likely your usb memstick, find out with dmesg
15:00<unixbsd>shreeya: you are not alone, we are up there
15:02<shreeya>So I have to install this iso file on other PC right?
15:02<unixbsd>no no, I have all tools to fix it, even from ramdisk. first this iso hybrid, you can put it on memstick (usb).
15:03-!-dpanter [] has quit [Ping timeout: 480 seconds]
15:04<shreeya>Sorry, it's not really clear to me how we are going to fix this. Can you explain me in a little more detail so I can understand it
15:04<unixbsd>Sorry, I am far experienced, I will try.
15:04<unixbsd>so you boot up the ubuntu machine. PC, if you have or windows it is fine as well.
15:05<unixbsd>start Firefox or chromium and download first the image: by any favorite way you prefer, firefox is likely the easiest.
15:06-!-freshtube [~freshtube@] has joined #debian
15:06-!-freshtube is "realname" on #redditprivacy #debian
15:06-!-Linux-Fan [] has joined #debian
15:06-!-Linux-Fan is "Linux-Fan" on #debian
15:08<unixbsd>In the meantime, it is downloading, get a coffee to relax and you will need any memstick. Size greater than 2.7 GB.
15:08<unixbsd>the memstick will have linux system on it. so an old one you dont need.
15:09-!-trinbene [] has quit [Remote host closed the connection]
15:09<shreeya>Okay I understood this procedure. Thanks for explaining
15:09-!-trinbene [] has joined #debian
15:09-!-trinbene is "trinbene" on #packaging #kernelnewbies #iovisor #debian #brouter #bpftrace
15:11<shreeya>I want my debian system to be as it was. I have lots of stuff installed which would talk a week to set them up again :(
15:11<shreeya>So this memstick is just going to be for debugging right?
15:11-!-jumbogram[m] [~jumbogram@2001:470:1af1:101::7aa4] has quit [Quit: Client limit exceeded: 8192]
15:12<unixbsd>shreeya: fixing is surely possible. anything like fix is possible
15:12-!-towo` [] has quit [Quit: Leaving]
15:12<unixbsd>the memstick is a live system, with that you can fix all system or clone or whatsoever.
15:13<unixbsd>there is a well debian live, that do the same. Since ubuntu is debian, there is no difference.
15:13<unixbsd>*as well
15:13<shreeya>Okay got it
15:14<shreeya>Let me get this ready and I'll message back
15:14<kag>Linux-Fan: hey
15:15<unixbsd>by the way, in case you have a older machine, ubuntu with a cutting edge soft will run slower than debian. it depends how old if your hardware. i3 or hgiher will do fine with ubuntu
15:15<shreeya>It's i5
15:15<shreeya>Debian is on XPS 15 laptop
15:15-!-craigevil [] has quit [Quit: leaving]
15:16<shreeya>And Ubuntu is on some lenovo i5
15:16<kag>just wanted to tell you that I managed to figure out what to do to finalize boot and get a login prompt
15:17<shreeya>Hi kag
15:17<unixbsd>i5 will do fine, ubuntu is slight way ligther and faster than windows. i5 is a very good machine. ok. keep going
15:17<kag>I had to blacklist phy_mxs_usb
15:18<kag>I'll have to double check, but I think as soon as I modprobe it, then the system freezes
15:19-!-Konomi_ [] has joined #debian
15:19-!-Konomi_ is "Konomi" on #debian
15:19<kag>i don't know what I am losing by doing so, this sounds like the physical USB layer, so maybe i actually don't have USB at all right now :)
15:20<kag>shreeya: hi
15:20<somiaj>shreeya: you can use your debian install image (if you still have it) to recover as well.
15:21<somiaj>ubuntu is not debian, at the core it is quite different. Though when recovering the only thing that really matters is the linux kernel, not the distro on the live image you use (since you end up chrooting into your debian isntall anyways)
15:22<shreeya>somiaj: nope, I do not have it. Also, I remember facing issues with that image because xps 15 has quite new hardware and I had to manually add the wifi firmware for installation to work. ( Even though I used debian bullseye )
15:23<somiaj>shreeya: for that case you probably just used a free installer and not the non-free one that includes firmware. Debian does provide unoffical non-free images with firmware.
15:23<shreeya>Yes I did use non free one
15:24<shreeya>It still didn't work
15:24<somiaj>shreeya: Though here what is important is having a linux kernel that supports your hardware, and then use that to chroot into your actual install to fix.
15:24-!-ach [] has joined #debian
15:24-!-ach is "ZNC -" on @#spooky #debian
15:24<somiaj>shreeya: did you end up having to download the firmware from upstream (
15:24-!-Konomi [] has quit [Ping timeout: 480 seconds]
15:24-!-Konomi_ is now known as Konomi
15:25-!-marian [] has joined #debian
15:25-!-marian is "marian" on #debian
15:25<somiaj>shreeya: anyways, since you aren't isntalling and may not need wifi to fix your current issue, this maynot be a problem with recovery, but that explains it.
15:25<Linux-Fan>kag: Hey, glad to hear it worked in the end. I used to not have USB with my ARM SBC either, but I have not checked recently :)
15:25<kag>:) thanks for your time and support
15:26-!-ol [~quassel@2406:e003:852:ff01:8e89:a5ff:feca:57fe] has joined #debian
15:26-!-ol is "Ol" on #debian
15:26<Linux-Fan>kag: You're welcome
15:26<unixbsd>shreeya: back... playing ps2 on ubuntu. hwo is it progressming?
15:27<shreeya>unixbsd: still trying to boot my machine 😅
15:27<shreeya>I had custom kernel for this machine which has also broken lot of things 🙃
15:28-!-bodiccea [~bodiccea@2a01:e34:ed64:e140:4c0f:31b0:6af3:2b24] has joined #debian
15:28-!-bodiccea is "bodiccea" on #oftc #debian-next #debian #kernelnewbies
15:30<unixbsd>shreeya: ah.... It is not so easy to diagnose over irc. needs more time. I am sure I would fix that boot in real live with 3-4 min max.
15:30<unixbsd>if you have a grub, still, all is so easy.
15:31-!-imega [] has joined #debian
15:31-!-imega is "coma" on #fai #debian #ceph
15:31<shreeya>unixbsd: I wish I had that much experience to solve it in 3-4 mins 😅
15:32-!-dpanterdpanter [~dpanter@] has quit [Quit: Leaving]
15:33<unixbsd>shreeya: the documentation is usually missing. it was easy actually, best is to be shown by a friend to learn faster.
15:33<unixbsd>anyhow, do you have now linux debian or ubuntu live ?
15:33<unixbsd>once you have this live running on your broken machine, you can then fix.
15:33<shreeya>You mean the memstick ready?
15:34<shreeya>Not yet. It will take more 10 mins I guess depending on my download spead
15:34<unixbsd>ah, yeah this live is 2.7GB...
15:34<shreeya>I will ping you once it's ready
15:34<unixbsd>For that reason, I made a pcmedkit on 400 MB only.
15:34<shreeya>2.7gb. it's definitely going to take more time than 10 mins then
15:35<unixbsd>shreeya: mine, my live is just 400mb, for x86 processors.
15:35<shreeya>Okay let me get yours
15:35<unixbsd>people usually prefer to have a desktop
15:36<unixbsd>caution: mine is just command line...
15:36-!-craigevil [] has joined #debian
15:36-!-craigevil is "craig" on #debian-raspberrypi #debian-next #debian-offtopic #debian
15:36<shreeya>No problem. I'll get to learn something new then
15:37<unixbsd>I can only recommend the officials, groovy live, cuz here they will kill me to give any other help than ubuntu only.
15:37<unixbsd>anyhow, what works, you just need a terminal or console running
15:38<Linux-Fan>unixbsd: Is the source code for the PC MedKit online somewhere?
15:39<unixbsd>it is the debootstrap, yeah, it is based on debian. if you are experienced, you will see that I am not a kidding guy.
15:39<jmcnaught>I wouldn't use that.
15:39<unixbsd>of course, all is opensource and default usage.
15:39-!-amcclure [~anton@] has joined #debian
15:39-!-amcclure is "anton" on #debian
15:39<unixbsd>shreeya: you see. just use the groovy otherwise they will freak out.
15:39-!-RedSoxFan07 [] has joined #debian
15:39-!-RedSoxFan07 is "RedSoxFan07" on #debian-next #debian
15:40<Linux-Fan>unixbsd: I am not freaking out. Its just that building such environments is complicated and I like to learn from seeing how other people do it, hence my question for the source code :)
15:40-!-peregrine8 [~peregrine@] has quit []
15:40<unixbsd>Linux-Fan: I am not interested to argue with you. I know what I am doing with Linux.
15:40<Linux-Fan>unixbsd: Never mind then :)
15:44<unixbsd>shreeya: once you have your live running and up on a machine, the question is to prepare the live, i.e. to copy it to the memstick.
15:45-!-kag [] has quit [Quit: leaving]
15:45<unixbsd>So to copy on the memstick, it is important to target the right device. /dev/sda is usually the sata first disk. /dev/sdb will be the second device, so it could be fine. To check it: run: sudo dmesg
15:45<unixbsd>or: sudo blkid
15:46<unixbsd>or: apt-get install gparted <-- to make it GUI.
15:46-!-zleap [] has quit [Remote host closed the connection]
15:46<blast007>Gnome also has a disk image writer
15:47<unixbsd>blast007: thank you to help
15:48-!-zleap [] has joined #debian
15:48-!-zleap is "realname" on #minidebconf-online #debian-academy #debian-next #debian
15:49<shreeya>unixbsd: I got your source code. The image img.gz is the one right?
15:49-!-lft2496 [] has quit [Quit: ⠟⠥⠊⠞]
15:49-!-ibx [] has joined #debian
15:49-!-ibx is "realname" on #debian
15:51<unixbsd>I usually use this one:
15:52<unixbsd>Currenlty I try to make the same with a ubuntu system for fun.
15:52<blast007>shreeya: note that if you're just needing to edit your /etc/fstab with the new UUID, you could use a Debian Live image
15:52<unixbsd>I guess people would need a GUI or desktop to use a pc med kit easily. usually, people dont like much terminals
15:53<shreeya>blast007: I have an empty /etc/fstab file :(
15:53<shreeya>But instead crypttab has uuid
15:53<unixbsd>empty fstab IS ALLOWED !!!!
15:53<shreeya>But crypttab has the incorrect uuid I assume
15:53<unixbsd>modern linux kernel do not have a fast edited. They took ideas from BSD mostly.
15:54<shreeya>Because it doesn't match with the one in grub.cnf
15:54<unixbsd>you just need to know or tell me what you have into the directory /lib/modules ?
15:54<shreeya>There are modules
15:54<unixbsd>and which /dev/sdXXX do you use as your partition...
15:55-!-pavlushka [] has quit [Remote host closed the connection]
15:55<unixbsd>Or just press
15:55<shreeya>It's /dev/nvm...
15:55<unixbsd>'c' into grub2 to get console command line.
15:55<shreeya>I'm already into it
15:56<unixbsd>set root=( <-- press TAB key
15:56<blast007>hmm, the /etc/fstab on my encrypted Debian install has mount points for the root and swap
15:57<unixbsd>it will give you: 0 the first booted disk, and 1 the usually second one, ... and so on.
15:57<shreeya>unixbsd: nothing comes up on tab
15:57<unixbsd>set root= <-- should normally see a disk
15:57<shreeya>blast007: I was expecting the same
15:58<shreeya>If I do root=(hd0, gpt2) then tab
15:58<shreeya>I get 3 vmlinuz files
15:58<unixbsd>linux /boot/ <-- press tab
15:58<blast007>my /etc/crypttab has a single line for my LUKS partition
15:59-!-ibx [] has quit [Quit: Q]
15:59-!-ibx [] has joined #debian
15:59-!-ibx is "realname" on #debian #bash @##peertube @#disroot #linuxmint @##linuxmint
15:59-!-ddsys [] has joined #debian
15:59-!-ddsys is "ddsys" on #debian-offtopic #debian-next #debian
15:59<shreeya>Strangely I do not have any boot folder
15:59<unixbsd>do you "set root=(hd to the right disk?
16:00<unixbsd>likely you installed ext4 right?
16:00<shreeya>Ext4? For what?
16:00-!-amcclure [~anton@] has quit [Remote host closed the connection]
16:01<unixbsd>when you did format, it was ext4 linux.. just to be sure.
16:01<unixbsd>normally, grub2 is designed to work better with native ext partitions. (linux ext)
16:01<unixbsd>which one you selected during install?
16:01<shreeya>My root partition is ext2
16:01<shreeya>There is one more which is vfat
16:02<unixbsd>ahh.. this is surely seen. all linux even old can read ext2
16:02-!-Blacker47 [] has quit [Quit: Life is short. Get a V.90 modem fast!]
16:02<unixbsd>vfat is certainly sthg else, not the main rootfs <-- locatino of /boot /etc /.... /lib /var .
16:02<shreeya>blast007: yes there is only a single line for me as well
16:02<shreeya>Main rootfs is ext2
16:03<shreeya>When I run blkid
16:03<jmcnaught>It's more likely that /boot is ext2 and /boot/efi is vfat the UEFI ESP
16:03<unixbsd>so with playing around with : set root=( ... you need to get these: /boot /etc /.... /lib /var <-- that is your linux
16:03-!-zleap [] has quit [Quit: Leaving]
16:03-!-dac2496 [] has joined #debian
16:03-!-dac2496 is "realname" on #debian #bash ##peertube #disroot #linuxmint ##linuxmint
16:04<unixbsd>(u)efi are usually partitions ef which is actually just some fat or similar.
16:04<shreeya>Hmmm I do not get those though
16:04<shreeya>But let me try
16:04<shreeya>jmcnaught: yes, that's right
16:05<unixbsd>ahh... normally it installed in legacy, but maybe some uefi plays around.-
16:05-!-dac2496 [] has quit []
16:05-!-dac2496 [] has joined #debian
16:05-!-dac2496 is "realname" on #debian #bash ##peertube #disroot #linuxmint ##linuxmint
16:06<unixbsd>also modifying the BIOS, how the harddisk is set, can influence on your visibility of data.
16:06<somiaj>shreeya: to determine the file system are you reading the partition flag or looking at the actual file system?
16:06-!-mzajc [] has quit [Ping timeout: 480 seconds]
16:06<somiaj>unixbsd: debian installs in what ever mode it was booted in, there is no normally, totally depends on the hardware and how the user choose to boot the installer
16:07-!-srgrint [] has joined #debian
16:07-!-srgrint is "Simon Richard Grint" on #debian
16:07<somiaj>and since most hardware defaults to uefi these days, modern hardware is most likely uefi unless the admin specifically chose legacy
16:07-!-dac2496 [] has quit []
16:07<shreeya>This is what my set looks like
16:07-!-dac2496 [] has joined #debian
16:07-!-dac2496 is "realname" on #linuxmint #disroot ##peertube #bash #debian
16:08<shreeya>Sorry about the font size. It's really small
16:08<somiaj>shreeya: why not just boot into the live system and debug from there?
16:08-!-dac2496 [] has quit []
16:09-!-dac2496 [] has joined #debian
16:09-!-dac2496 is "realname" on #linuxmint #disroot ##peertube #bash #debian
16:09<unixbsd>nice ...
16:09<unixbsd>the efi boot is up there. you have uefi
16:09<shreeya>If you see that config_file is under (hd0, gpt1) whereas prefix is (hd0,gpt2)
16:09-!-ibx [] has quit [Ping timeout: 480 seconds]
16:10<unixbsd>cool, so you have the default amd64 5.10 kernel, likely from ubuntu, this is readily working with most harddware.
16:10<blast007>unixbsd: you do realize this is #debian, right?
16:10<unixbsd>maybe you have a (hd0, gpt3) ?
16:10<somiaj>the uefi seems to suggest it is from debian, and 5.10 is what bullseye runs
16:10-!-dac2496 [] has quit []
16:11<unixbsd>question where is hte rootfs
16:11-!-ibx [] has joined #debian
16:11-!-ibx is "realname" on @#disroot #linuxmint @#peertube #bash #debian
16:11<shreeya>Yes, it's debian bullseye
16:11<somiaj>shreeya: anyways if it was me, I would boot into the live system (being ubuntu doesn't matter), and debug from there, not from the limited grub console
16:11<unixbsd>I am pondered where is your rootfs. I dont not see your system in the gpt
16:12<unixbsd>yeah ok, try devuan-live, that would fix it.
16:12<unixbsd>whatever live, is
16:13<blast007>are you just going to suggest everything except Debian? :)
16:13<unixbsd>is there a good debian live? no idea
16:13<dpkg>The Debian Live project provides pre-built Debian live system images and allows creation of your own. These can be used to install a Debian system (although the installer is better to use). Live images are available from . #debian-live on See also <live firmware>. <UEFI> mode is supported by Debian Live images.
16:13<somiaj>you don't even need a live image for this issue, but yes debian provides various live images, a debian installer image would also work just fine.
16:14-!-gabuscus [~quassel@] has joined #debian
16:14-!-gabuscus is "gabuscus" on #debian #debian-puppet
16:14<unixbsd>I gave you the live to current live of debian. I guess it might work, I had observation of numerous bugs with the installer of debian. devuan-live is very likely more stable.
16:14<somiaj>though at this point it doesn't matter, If I were shreeya I would boot into the live system, find the filesystems, mount them and chroot into the debian install, then fix it from there. Likely something along the lines of
16:14<dpkg>To reinstall <GRUB> boot to your Debian install disk/live CD, switch to the other console (Alt-F2), mount your root filesystem (mount -t ext4 /dev/whatever /target ; mount --bind /dev /target/dev ; mount -t proc none /target/proc ; mount -t sysfs none /target/sys), chroot into it (chroot /target), run "mount /boot/efi" on EFI and "update-grub && grub-install /dev/whatever". See also <rescue mode>, <dual boot guide>, <supergrub>.
16:15<unixbsd> with : fdisk -l
16:15<unixbsd>not sure that debian live still give fdisk. debian is bit like ubuntu. nothing to fix a machine.
16:15<blast007>there's also a recovery mode on the installer images:
16:15<blast007>rescue mode*
16:16<shreeya>I am not able to do ls on (hd0,gpt3)
16:16<unixbsd>rescue wont help much, anyhow, best is likely a live, with fdisk.
16:16<shreeya>It gives unknown filesystem
16:17<unixbsd>Into grub, you havent much features.
16:17-!-dpanter [] has joined #debian
16:17-!-dpanter is "realname" on #debian-kde #debian-offtopic #debian-next #debian
16:17<somiaj>resuce mode would most likely help with this issue, since they just need to chroot into their system and fix the UUID issue they have.
16:17<unixbsd>I guess I have a 14MB live memstick ... somewhere.
16:18<unixbsd>this is minirescue: "" (based on a debian/devuan).
16:20<shreeya>So do I need to do cat image > usb-drive
16:20<unixbsd>not cat! zcat
16:20<shreeya>For this minirescue image?
16:20<unixbsd> example: zcat Defunc CMD: /usr/bin/wget -c "" >
16:21-!-ibx [] has quit [Quit: Q]
16:21<unixbsd>zcat minirescue-linux-bsd-v1.img.gz > /dev/XXX <-- device
16:21<unixbsd>(sorry my mouse clicked too fast).
16:21-!-ibx [] has joined #debian
16:21-!-ibx is "realname" on @#disroot #linuxmint @#peertube #bash #debian
16:21<somiaj>shreeya: I would suggest not downloading more images, did the ubuntu image you downloaded not boot?
16:22<jmcnaught>Honestly in #debian I think we should be recommending official tools from trusted sources like not some stranger's random binary image.
16:22<somiaj>and focus on the actual issue, which unixbsd is putting lots of bias they have against debian for.
16:22<unixbsd>jmcnaught: I cannot recommend my images. I can only recommend debian or ubuntu, they are trusted.
16:23<unixbsd>jmcnaught: but ... likely my images work better, because I am experienced in this field.
16:25<shreeya>unixbsd: it's fine. Let's just use official image. Then you all can help and work together :)
16:25-!-dmm [~dmm@] has quit [Remote host closed the connection]
16:26<shreeya>Can you recommend me any official image?
16:26<somiaj>shreeya: Does that ubuntu image you downloaded not boot on your hardware?
16:26-!-f10 [] has quit [Read error: No route to host]
16:27<unixbsd>I trust more devuan than debian for live images.
16:27-!-f10 [] has joined #debian
16:27-!-f10 is "f10" on #debian-kde #debian
16:27<shreeya>somiaj: I haven't downloaded any ubuntu or debian image yet
16:27<somiaj>unixbsd: please try to support the actual issue, and stop sharing non sequlators.
16:27<shreeya>I downloaded nwhat unixbsd suggested previously
16:27<unixbsd>or this one:
16:28<jmcnaught> is small and has a rescue mode that will give you a chroot of the target system
16:28<somiaj>shreeya: I would personally suggest just installing the install image you know works.
16:28<unixbsd>the above one is the official debian. xfce works bit better.
16:28<somiaj>Here I think theyir hardware is new enough (or at least wifi) they might need the bullseye image.
16:29<unixbsd>In case, it is very new, and you need a 5.x kernel, the ubuntu live have the most recent kernels.
16:29<shreeya>Yes I think it would be good idea to go with ubuntu image
16:30<shreeya>Because I remember, on my machine ubuntu was installed without any issues but debian had some firmware issues
16:30-!-mzajc [] has joined #debian
16:30-!-mzajc is "Marko Zajc" on #debian-next #debian-kde #debian
16:30<unixbsd>the groovy has a 5.x something kernel, I use this one:
16:30<somiaj>shreeya: firmware most likely won't be an issue here, it was just for wifi and you won't need it.
16:31<somiaj>shreeya: would be my suggestion, and just use its rescue mode to get into your install, from there you can fix your UUID issue, update-grub and be booting again.
16:31<unixbsd>debian has better wifi, ubuntu is not that good with wireless, devuan is older system (sysv) which is more realiable. but this is systemd war.
16:32<shreeya>unixbsd: somiaj I am installing this image for now
16:32<unixbsd>what is the most most recent ubuntu today? maybe I think about making a better live for me.
16:33<shreeya>So I have to burn it to my sd card right?
16:33<unixbsd> cat live.iso > /dev/XXXXX
16:33<shreeya>Okay okay got it
16:33-!-Hackintech [] has quit [Ping timeout: 480 seconds]
16:34<unixbsd>I will make a new minirescue, efi, with live to ramdisk and a better, newer kernel, based on ubuntu. let's see if 20 mb is possible.
16:36-!-RedSoxFan07 [] has quit [Quit: RedSoxFan07]
16:36-!-Ivysalt [] has quit []
16:37-!-ol [~quassel@2406:e003:852:ff01:8e89:a5ff:feca:57fe] has quit [Ping timeout: 480 seconds]
16:39-!-cheapie [] has joined #debian
16:39-!-cheapie is "cheapie" on #debian #moocows #oftc
16:43-!-Ivy [] has joined #debian
16:43-!-Ivy is "" on #linux #freedombox #debian #alpine-linux #Qubes_OS #
16:43-!-localhorst [] has joined #debian
16:43-!-localhorst is "localhorst" on #debian
16:44<unixbsd>fsck.ext2 ... might help. blkid might help. fdisk -l might help. And once all up: grub-install --no-floppy --root-directory=/media/sdXXX /dev/XXX and edit the grub config.
16:45-!-stephanlachnit [~Thunderbi@2a02:8071:b94:ab00:133c:15cb:1528:9c9e] has joined #debian
16:45-!-stephanlachnit is "Stephan Lachnit" on #debian-games #debian
16:45-!-dmm [~dmm@] has joined #debian
16:45-!-dmm is "snake" on #debian
16:48<shreeya>fsck.ext2 won't wipe anything right?
16:48<shreeya>Btw I'm done with cat command
16:49<shreeya>What's the next step?
16:50<somiaj>shreeya: boot from the image, then select rescue mode, from there give it info about your root filesystem.
16:52<unixbsd>fsck.ext2 is to fix the disk, but it can damage in case you have another fs
16:52<unixbsd>boot using F12 or F8 in case it does not want to see the UEFI boot memstick. somethinmes try 2x x3 times in case bios didnt see it well.
16:53<unixbsd>just power on witht eh memstick in it (before) and let it boot
16:53<shreeya>I'm got grub command line after booting
16:53<shreeya>Into the new image
16:55<shreeya>I do not understand. How is this different than the debian grub command line?
16:55<shreeya>I hope I'm not doing something wrong
16:55<somiaj>shreeya: hmm, must need to boot into the installer, open up a console and from there try to recover your volume group.
16:55<unixbsd>it will just run on the live (memory, ramdisk so called live-boot) and you have all functionalities to fix.
16:56<unixbsd>well, you will likely need apt-get maybe. who knows.
16:57<shreeya>Okay so I need to set the root for this new debian system
16:57<shreeya>And then install it
16:57-!-IPFreely [~wh0kares@2001:4ba0:fffe:5::] has quit []
16:57-!-Hackintech [] has joined #debian
16:57-!-Hackintech is "hackintech" on #qemu #debian #virt #tor-dev
16:57<unixbsd>install will erase !
16:57<shreeya>Sorry, I haven't used live-cd before for debugging 🙁
16:57<somiaj>shreeya: the installer does contain a small shell you can use to try to recover your old install, but it appears you have deleted your lvm volume group and it coudl take some work to try to recover it
16:58<unixbsd>there is always for each of us a first time. so no worry, we all understand and welcome new linux
16:58<shreeya>So from bios, I selected new debian to boot
16:59<shreeya>I ended up on a grub console
16:59<unixbsd>deleted is bit hardder. Ãsometime a sort of low endnew fdisk (low end one) will show up back the parititon. in case of big disaster, first is to image it with dd.
16:59-!-TheRuralJuror [] has quit []
17:00<shreeya>Now what I'm assuming is that I have to set prefix, root, to new debian image
17:00<unixbsd>basically, you need a EFI, grub, and 5.x kernel, with linux live maybe a GUI for gparted and fix tools, right?
17:01-!-TheRuralJuror [] has joined #debian
17:01-!-TheRuralJuror is "AP,,," on #security #debian-next #debian
17:02-!-towo` [] has joined #debian
17:02-!-towo` is "Torsten -towo- Wohlfarth" on #qemu #kernelnewbies #siduction-admin #debian-offtopic #debian-next #debian #aptosid
17:02<unixbsd>shreeya: first thing, fdisk -l to see which disks you have.
17:02<Linux-Fan>shreeya: If it went from BIOS to GRUB to a commandline it has most likely not booted the live system/installer because that one should always display a menu.
17:03<shreeya>Linux-Fan: right, I think the same
17:04-!-dac2496 [] has joined #debian
17:04-!-dac2496 is "realname" on #debian #bash #peertube #linuxmint #disroot #pinephone #backups #homelab #mumble #bakslak
17:04<shreeya>I haven't got any command line
17:04<unixbsd>yeah, i told you
17:04<unixbsd>you choosed the debian rescue (officials) ;)
17:04<unixbsd>try : alt + F2
17:05<unixbsd>alt + F2 will give you a busybox, there isnt much you can do with that.
17:05-!-dvs [] has joined #debian
17:05-!-dvs is "realname" on #debian
17:06<shreeya>Okay finally
17:06<unixbsd>On some modern debian distributions, they are capable to give a system without "fdisk".
17:06<shreeya>I am in the installer
17:07-!-os__ [~Usama@] has quit [Remote host closed the connection]
17:07<shreeya>But I dont have to install
17:07<unixbsd>installer means you are ready to erase
17:07<Linux-Fan>shreeya: If you chose the rescue mode, it will ask you some of the regular installer questions first before allowing you to drop to a shell.
17:07<unixbsd>let me give you a full desktop ... large but fullly equipped ...
17:07<shreeya>Haha yeah I'm no way ready to erase
17:07<somiaj>shreeya: that is fine, the installer will let you drop to a rescue shell that you can try to recover y our volume group with.
17:08-!-mode/#debian [+l 721] by debhelper
17:08<somiaj>shreeya: I was hoping you could just use it to boot into your system, but it appears since you have messed up/deleted your volume group, you'll have to drop into the shell, then see about recovering the volume group with your install.
17:08<unixbsd>Ok, I will make a mini ubuntu with desktop... it will take 1 or 2 hours. maybe wait till 2morrow. if you have data, keep it calm
17:09<unixbsd>the groovy above live iso, has good kernel, and it runs on live with commanmd line.
17:09<somiaj>shreeya: under advanced options
17:09<shreeya>Okay there it is
17:09<unixbsd>this is meaning installer :=> erase
17:09<shreeya>Rescue more
17:09<somiaj>unixbsd: that is false, please stop proving false information.
17:10<somiaj>the installer also contains rescue tools
17:10<unixbsd>somiaj: you see how much complicated are those images?
17:10-!-ibx [] has quit [Ping timeout: 480 seconds]
17:10<unixbsd>somiaj: the debian installer is just a junk, you have access to nothing.
17:11<shreeya>I get initramfs console
17:11<shreeya>When boot fails
17:11<unixbsd>initramfs is quite limited.
17:11<shreeya>Yes, it's very limited. Was not able to do anything useful
17:12<unixbsd>what debian believe? magic? with busybox without access to /dev/? man...
17:13-!-andibmu [~andi@] has quit [Ping timeout: 480 seconds]
17:13<somiaj>shreeya: after you choose rescue mode, what did you select next?
17:14<shreeya>One min, should I go with graphical one or just the rescue mode?
17:14<somiaj>just rescue
17:15<shreeya>Now I get installer like questions
17:15<somiaj>that is fine, it is just setting some stuff up for you
17:17<Linux-Fan>shreeya: Chose no. Internet access will not be needed :)
17:18<somiaj>just say no, you don't need inetrnet acces, also just skip the setup the network part, you syould eventally get to a point where it says [!!] enter rescue mode, and gives you a list of devices, send us the screenshot of that.
17:18<unixbsd>yeahh ... soon or later, new installatino and erase all.
17:18-!-Talkless [] has joined #debian
17:18-!-Talkless is "Talkless" on #debian-next #debian
17:18<somiaj>unixbsd: no, the rescue mode is not an install, try to provide actual support.
17:20<shreeya>It actually got connected to internet in the next step
17:20<shreeya>So should be fine
17:20<somiaj>cool, that gives you internet if you need it, but most likely won't
17:21<somiaj>sounds like bullseye has the firmware you need for your network (was it wifi?)
17:22<otisolsen70>In #virt I just got the following advice on KVM: "/dev/kvm must exist, and must be readable/writable by any uid (permission 666; no this isn't a security problem!)" Is this really true on Debian? If so, why doesn't Debian set the correct perms on /dev/kvm?
17:22<otisolsen70>Default perms seem to be 0660 on Debian.
17:22<unixbsd>somiaj: ok, i am reading and looking up until wehre it goes, or if fixing with it will succeed.
17:23<otisolsen70>Ownership is root:kvm. So maybe the right solution is to add users who will use kvm to the kvm group? If so, the advice on #virt is incorrect.
17:23<somiaj>yea, your lvm volume group was deleted, otherwise it would ahve been listed there, okay choose no root filesystem, from there it will drop you into a shell
17:23<somiaj>otisolsen70: are you using libvirt and tools like virt-manager or virsh?
17:24<otisolsen70>somiaj, yes
17:24<Linux-Fan>otisolsen70: It works with the 0660 here just fine. I am not using KVM directly though and just are only member of group "libvirt".
17:24<otisolsen70>Linux-Fan, I am member of libvirt also
17:24<somiaj>otisolsen70: on debian you don't need direct access to /dev/kvm, the libvirt daemon handels this for you, you should only need to be in the libvirt group.
17:24-!-choozy [] has joined #debian
17:24-!-choozy is "Choozy VAHFG" on #mobian #debian
17:24<shreeya>Execute a shell in the installer environment option to be selected right?
17:24<somiaj>otisolsen70: once you are in the libvirt group, you can tell the daemon via virsh or virt-manager to manage virtual machines. What was your issue?
17:25<otisolsen70>somiaj, I am in libvirt group. But problem is that VMs does not seem to use kvm even though specified.
17:25<otisolsen70>somiaj, and kvm module is loaded.
17:25<somiaj>shreeya: yes, though this is a fairly minimial shell, I was hoping we could easily find your volumegroup, here I'm unsure the if/how we can recover it (it might be a bit difficult to recover)
17:26-!-}ls{ [] has quit [Quit: real life interrupt]
17:27<shreeya>Hmmm so what should be our next step then?
17:27<unixbsd>somiaj: I am obversing,... very curious what you can do... hopefully for the best, let's hope.
17:27<somiaj>otisolsen70: How are you creating the vms? My vms use kvm here just fine and I'm only in the libvirt group.
17:27<Linux-Fan>otisolsen70: It used to be needed to explicitly install the user space program for it IIRC. But `aptitude show qemu-kvm` tells me it is just a wrapper script for backwards compatibility now. Not sure if it would help to install it.
17:30<somiaj>shreeya: what is the output of blkid
17:31<somiaj>unixbsd: unsure how much can be done if the volume group was deleted
17:31-!-ax5623 [] has joined #debian
17:31-!-ax5623 is "realname" on #debian-next #debian #linux
17:32<unixbsd>somiaj: fdisk alike can bring it back
17:32<unixbsd>but not fdisk.
17:32-!-ao2 [] has quit [Quit: Leaving]
17:32<somiaj>fdisk is not for lvm volume groups
17:32<unixbsd>if he removed it with 'd', then the data are up there still.
17:32<unixbsd>less -f ???? I use that often to read and fix
17:33<unixbsd>less -f /dev/XXXX
17:33<otisolsen70>virt-install --virt-type qemu --name myvm --cdrom /data/tmp/debian-10.7.0-amd64-netinst.iso --os-variant debian10 --disk size=10 --memory=2048
17:33<otisolsen70>somiaj, ^
17:34<otisolsen70>Linux-Fan, qemu-kvm is already the newest version (1:3.1+dfsg-8+deb10u8).
17:34<shreeya>There is no less command
17:34<somiaj>shreeya: Lets see what is on /dev/nvme0n1p2, if you 'mount /dev/nvme0n1p2 /mnt' does that work?
17:34<unixbsd>the rescue is for rescue, it has not much into it.
17:35<shreeya>Yeah I'm able to mount
17:35<somiaj>shreeya: ls /mnt (what do you see?)
17:35<shreeya>And it has same vmlinuz files
17:35<otisolsen70>shreeya, what is your problem here? I have done a fair bit of rescuing
17:35<somiaj>otisolsen70: they seem to have lost their debian-vg for their lvm
17:36<otisolsen70>somiaj, oh.
17:36-!-epoll [] has quit []
17:36<somiaj>shreeya: okay that is your /boot, which is what I thought, your /dev/nvme0n1p3 is your lvm, though unsure why it is calling it filesystem type 'dos'
17:37<somiaj>here Im' unsure how we can recover your lvm volume group, but at least we know now you put it on the third partition on your nvme
17:37-!-ax56234 [] has quit [Ping timeout: 480 seconds]
17:37<otisolsen70>Have not done too much with lvm. But have you done pvscan, lvscan, vgscan, etc?
17:37-!-ax562 [] has quit [Ping timeout: 480 seconds]
17:37<otisolsen70>shreeya, how was it lost?
17:38<Linux-Fan>otisolsen70: Trying out your commandline (with 10.5 instead of 10.7 and paths amended), I get `Error: --disk size=10: pool 'default' must be active.` It works when I run it as root.
17:38-!-epoll [] has joined #debian
17:38-!-epoll is "epoll" on #debian #kernelnewbies
17:38<otisolsen70>Linux-Fan, it works just fine here also. But the vm ends up running qemu , not kvm
17:38<shreeya>otisolsen70: God knows :(
17:38<shreeya>I was trying to add new partition in rootfs
17:38<shreeya>Maybe I messed up at that time
17:39<otisolsen70>Linux-Fan, virt-host-validate: unsupported hypervisor name myvm
17:39<Linux-Fan>otisolsen70: TBH the commandline has always only worked as root here. `virsh list` produces an empty result for regular user here.
17:39<otisolsen70>shreeya, how did you add it? Using what tool/command?
17:39<otisolsen70>Linux-Fan, I am running the vm as root. And still kvm is not utilized
17:39<shreeya>i think fdisk
17:39<somiaj>Linux-Fan: virsh has both qemu://system and one for user, by default it uses the user, you ahve to tell it to look/use the system list to get that
17:40<shreeya>Don't remember exactly but yeah those n, p, e options
17:40<somiaj>shreeya: I don't think fdisk is going to help, well lets umount /mnt, but I'm unsure how (or if it is even possible) to rebuild the lvm data for your partition. I'm doing some research
17:40<somiaj>shreeya: did you use fdisk to try to create this new partition?
17:40<somiaj>shreeya: and did you try to create a dos partition?
17:41<otisolsen70>shreeya, did you at any point use the 'd' command in fdisk?
17:41<shreeya>I don't think so it was dos
17:41<shreeya>But I cannot say anything
17:41<Linux-Fan>otisolsen70: Thanks for the hint, I shall try it out :) In the meantime, you could try `virt-host-validate qemu`, that outputs a nice list of "pass" lines here.
17:41<otisolsen70>shreeya, it would be either dos or gpt
17:41<shreeya>I used gpt most probably
17:41<somiaj>shreeya: you might have deleted your lvm volume group, and your data might be lost (without doing a disk scan for recvery)
17:42<otisolsen70>Linux-Fan, the last check failed: QEMU: Checking if IOMMU is enabled by kernel : WARN (IOMMU appears to be disabled in kernel. Add intel_iommu=on to kernel cmdline arguments)
17:42<somiaj>otisolsen70: see they have three partitions, one is vfat which is probably the efi partition, the ext2 partition is their /boot, and thei third partition, this was their lvm volume group, but it appears they messed it up using fdisk
17:42<Linux-Fan>otisolsen70: Well, TBH I do not thinkt hat one is the issue. AFAIK intel_iommu=on is only needed if you want to virtualize GPUs or such.
17:43<otisolsen70>Linux-Fan, ok. Any other checks I can do?
17:43<somiaj>otisolsen70: why are you using --virt-type qemu instead of --virt-type kvm?
17:43<shreeya>There was swap partition as well
17:43<shreeya>I wonder where it went
17:43-!-julienth37 [] has joined #debian
17:43-!-julienth37 is "julienth37" on #debian
17:43<somiaj>oh wait, I guess that will use kvm if it is avialable
17:43<otisolsen70>Linux-Fan, if I run just virt-host-validate, I get this:
17:44<somiaj>shreeya: well in a lvm, all partition are stored in a single physical partition
17:44-!-julienth37_ [] has quit [Read error: No route to host]
17:44<otisolsen70>somiaj, d'oh! That's an error.
17:44<somiaj>shreeya: so your /dev/nvme0n1p3 was your lvm partition, and inside that one physical parititoin, the lvm created virtual partitions inside the lvm volume group
17:44<otisolsen70>somiaj, I am pretty sure I actually did the install with kvm though. But now I doubt it a little. Is there any way I can change it from qemu to kvm on an existing vm?
17:45<somiaj>shreeya: and your error was you were using fdisk (wich works with physical parititons) insteald of lvm tools with works with the virutal partitions inside your volume group.
17:45<shreeya>Oh no
17:45<somiaj>otisolsen70: well I'm not quite sure here, it does appear that the qemu type will use kvm if availabe, so maybe this isn't the issue as to why kvm isn't being used.
17:45<shreeya>This means I'm never going to be able to recover my data
17:45<somiaj>shreeya: I don't know if it is recoverable since you bsiacllly overwrote your lvm volume group from the start
17:45<otisolsen70>somiaj, did you try changein your part type to lvm?
17:46<somiaj>shreeya: it doens't mean never, it does mean it is going to be way harder.
17:46<Linux-Fan>otisolsen70: Output on my machine looks very similar. Notable difference is that I have the IOMMU turned on (I, too get the error in the last line). Still, given that it says "hardware virtualization: pass" in the first line, I still believe it should be able to accellerate virtualization with KVM without issue.
17:46<shreeya>somiaj: can we try it?
17:46<somiaj>otisolsen70: I'm unsure here, my lvm knowledge is a bit low, I personally don't use it due to it adds an extra layer, but I don't think just changing the partition type will do that
17:47<otisolsen70>shreeya, did you try changein your part type to lvm?
17:47<somiaj>shreeya: Here i'm unsure exactly what tools are best for this, now one recovery will be read the partition raw data and try to guess/recover files, this can be done but is a painful process. This also won't recover your install but recover your data. Otuside of spending a week trying to cofnigure everything, is there any actual data you need?
17:47<otisolsen70>shreeya, do you have some medium with enough free space to image your disk?
17:48<somiaj>otisolsen70: do you think that will work, usually the type is a very pointless setting, wouldn't it be better to see if you can point lvm tools at that partition to see what it sees?
17:48<somiaj>but I think with using fdisk, all lvm metadata might have been lost which makes revering the actual lvm group very unlikely (though here my knowledge is limited)
17:49<otisolsen70>shreeya, I would do that. Go download sysrecuelinux and boot up on an usb. Then you do "pv /dev/nvme0n1 -B 4M | pigz -1 | mbuffer -m 5% -q > /net/disk.img.gz" where /net is a mounted NFS share on some other system with enough space.
17:49<shreeya>somiaj: I had some images which I was using with qemu. I was also using custom kernel with qemu
17:49<unixbsd>this is just the disk table thta is missing.
17:50<otisolsen70>somiaj, I agree. Right now I just want them to image the disk if at all possible before changing anything
17:50<unixbsd>usually I run a dd to save the disk table on my harddisks.
17:50<unixbsd>you might have a luck with testdisk
17:50<unixbsd>testdisk will restore it
17:50<somiaj>shreeya: data revoery might have trouble recvering full disk images.
17:50-!-mangix [] has joined #debian
17:50-!-mangix is "Rosen Penev" on #msys2 #debian #llvm
17:50<otisolsen70>somiaj, do you have valuable stuff on the disk? How much do you lose if you just reinstall and recover from latest backup?
17:51-!-diogenes_oftc [~diogenes_@] has quit [Quit: vergissmeinnicht]
17:51<unixbsd>but now it is time to dd your disk. Backup! dd if=/dev/XXX of=image.mydisk.img
17:51<somiaj>shreeya: anyways, otisolsen70 suggestion is standard, you need another disk the size of this physical partition, you can then make a direct copy of this physical partition to that disk and from there start to manually scan it. In the best case scenrio you could recover the metadata for your lvm from that scan, but this is going to require a lot of low level detailed work.
17:52<unixbsd> testdisk - Partition scanner and disk recovery tool, and PhotoRec file recovery tool
17:52<somiaj>shreeya: depending on your experience this is going to be a difficult thing to manually walk someone through on trying to recover the metadata, depending on what you loose a fresh install might be easiest at this point.
17:52<otisolsen70>shreeya, when you have the image you can try stuff out. You might even mine the image for stuff with scalpel or similar tools.
17:53<otisolsen70>shreeya, IF you have valuable data on the disk you should image the disk before doing anything else.
17:53<somiaj>shreeya: so recovery at this point would require you have another disk you can put a full image of your broken partition on, after that you can using that image to try to recover stuff, but this is a lot of work, so you have to decide how much it is worth trying to get that lost data due to using fdisk to overwrite the partition headers with your lvm metadata.
17:53<Linux-Fan>otisolsen70: Wrt. the ability to change emulation<->virtualization after creating the VM: My VMs have an `<emulator>/usr/bin/kvm</emulator>` line in their XMLs. You cold have a look at yours `virsh edit myvm`.
17:54<shreeya>If it's going to be lot of work then I'll probably do a fresh install
17:54-!-mangix_ [] has quit [Ping timeout: 480 seconds]
17:54<somiaj>shreeya: sorry it took so long for us to get actual information about what happened here, but until we actually saw your setup from those screenshots it was hard to guess what state your system was in.
17:54-!-dvs [] has quit [Remote host closed the connection]
17:55<shreeya>somiaj: it's totally fine. I'm so happy to atleast know what's wrong here and I can stop wasting more time on it
17:55<otisolsen70>Linux-Fan, I just did virsh edit. It has qemu mentioned multiple places: <domain type='qemu'>, emulator>/usr/bin/qemu-system-x86_64</emulator>, <driver name='qemu' type='qcow2'/>, and more
17:55<somiaj>shreeya: note lvm is a nice tool, but it does add an extra layer which makes recovery a bit harder if all the lvm metadata info is lost (as what happened here), and in the future if you use lvm, you need to use lvm tools (not fdisk) to resize/create new partitions inside the lvm.
17:56<unixbsd>otisolsen70: we might all recommend, backup now, first before it is fully gone.
17:56<shreeya>somiaj: yes, I wasn't aware that we cannot use fdisk for lvm
17:56-!-ahso1 [] has joined #debian
17:56-!-ahso1 is "ahso" on #debian-next #debian #debian-wsl
17:56<otisolsen70>shreeya, you should generally *never* use fdisk unless you really really have to. Most of the time you will be better off using gparted. And if that fails, use cfdisk. fdisk only if you need to do very low level stuff
17:56<somiaj>otisolsen70: on my system I have <domain type='kvm'>, so that appears to be why it isn't using kvm, though that is th only methion of kvm I have, I wonder if just chaning the domain type is enough
17:57<otisolsen70>somiaj, do you have mentions of qemu in yours?
17:57<somiaj>otisolsen70: You will have other things being emulated via qemu
17:57<Linux-Fan>otisolsen70: It's a long shot, but you might try to change the emulator line to /usr/bin/kvm. In fact, this should boild down to adding an `-enable-kvm` flag to the qemu invocation. In fact, my XML also has domain type='kvm'!
17:57-!-srgrint [] has quit [Quit: srgrint]
17:58<somiaj>otisolsen70: yes, I do have <emulator>/usr/bin/qemu-system-x86_64</emulator> and various metniones of qemu, since kvm is only part of a vm for cpu hardware support
17:58<somiaj>otisolsen70: the only pacce I have kvm mentioned is in the domain type
17:58-!-polymetric [] has quit [Ping timeout: 480 seconds]
17:59-!-Talkless [] has quit [Quit: Konversation terminated!]
17:59<Linux-Fan>Btw. regarding the ongoing LVM discussion: I am pretty sure that like file systems, LVM keeps some backups of its metadata (see e.g. I have too little experience with LVM to determine if/how it actually works, though :(
18:00<otisolsen70>somiaj, I changed domain type to kvm. Now it seems much faster. How do I check if it is actually using kvm?
18:00<otisolsen70>Linux-Fan, I also think it might be recoverable. But I wouldnt even try getting into that before having an image.
18:01<unixbsd>somiaj: congrats, you did great job.
18:01<somiaj>otisolsen70: a bit unsure here, but if the speed is there that is a good sign.
18:01<somiaj>unixbsd: coulnd't actually fix the problem, but at least identify what the actual issue is.
18:01<unixbsd>somiaj: no no, not about technicall... way more important
18:02<otisolsen70>somiaj, but the host still has two processes called /usr/bin/qemu-system-x86_64 running both at 100 % CPU all the time
18:02<unixbsd>somiaj: you are honest. superbe
18:02<somiaj>shreeya: anyways, this is a tough spot to be in, recovery is possible but does erquire a lot of patience and low level tools, you have to make that call, but follow otisolsen70 advice about making an image of your lvm partition if youw ant to attempt recovery.
18:03-!-ahso [] has quit [Ping timeout: 480 seconds]
18:03-!-ahso1 is now known as ahso
18:03-!-zebrag [] has quit [Quit: Konversation terminated!]
18:03<otisolsen70>shreeya, how big is the disk? It seems to be an nvme ssd, so I am betting it is much smaller than what a cheap SATA disk goes for. So I would buy a cheap X TB SATA disk, put it in and image your nvme disk onto that.
18:03-!-erle- [~stephan@2a04:ee41:3:3297:8540:6f69:4d3b:4b15] has quit [Remote host closed the connection]
18:03-!-dac2496 [] has quit [Remote host closed the connection]
18:03<somiaj>otisolsen70: yea, I'm not getting 100% ussage on qemu-system-x86_64 but it is running on my system. Is your vm doing a lot of work or in an idel state?
18:04<otisolsen70>somiaj, idle
18:04<otisolsen70>somiaj, that is why I think something it now right :)
18:04<somiaj>otisolsen70: what does your xml say about your <cpu> settings?
18:04<otisolsen70> <vcpu placement='static'>1</vcpu>
18:04<shreeya>Okay just one basic question here
18:05<somiaj>otisolsen70: did you stop all your vms that weren't using kvm? Here i'm a bit out of my experience to verify that kvm is actually being used, but it appears that for some reason kvm wan'st being set as an option in your install
18:05<shreeya>Why don't I see boot folder here
18:05<otisolsen70>somiaj, I only have one vm
18:05<shreeya>Also, in initramfs console there was no boot folder
18:05<somiaj>shreeya: is this another machine?
18:05<otisolsen70>shreeya, you are booting to an usb, right?
18:05<somiaj>otisolsen70: or is this when booted on your live image?
18:06<shreeya>Right now I'm in rescue mode
18:06<Linux-Fan>otisolsen70: Is it idle at 100% running a proper (Debian!) OS or is it e.g. at a GRUB/ISOLINUX or other low-level styl escreen? I am asking, because here, it takes 100% in the boot menu but gets less once the actual OS is loaded.
18:06<otisolsen70>shreeya, /boot is not there because you did not mount it?
18:06<somiaj>shreeya: that is the os running on the live image, it dones't need a /boot (the installer image is setup slightly different than say an actual install would be)
18:07<unixbsd>mount grep overlay will show you that it is running out of ram.
18:07<somiaj>here the installer rescue mode that is running in memeory doens't need to have a /boot, and loading that into memory would just be extra stuff not needed, so it isn't loaded
18:07<shreeya>It was the same case with initramfs console
18:07-!-jstein [] has quit [Quit: quit]
18:08-!-mode/#debian [+l 709] by debhelper
18:08<somiaj>shreeya: a live system or in this case rescue system (or even initrd console) is running only in memeory, and won't include a full os, and /boot is not something either of those need.
18:08<shreeya>There is no overlay filesystem here
18:08<otisolsen70>somiaj, it was in the bootup process actually, sorry. It is idle now and not going at 100 % CPU on the host. My mistake
18:08<shreeya>somiaj: okay got it
18:08<unixbsd>yeah rescue is smaller, overlay is with live-boot system, /live
18:09<otisolsen70>somiaj, when I go to virt-manager and open details for the vm, it says under Hypervisor details: Hypervisor: KVM
18:09<otisolsen70>Emulator: /usr/bin/qemu-system-x86_64
18:10<somiaj>otisolsen70: yea you'll still use qemu, along with kvm, both are needed (from my understanding, kvm is just adding some hardware acceleration but qemu is still emulated some stuff)
18:10<otisolsen70>somiaj, so the state I am in now is actually what is "best" performance?
18:11<otisolsen70>somiaj, I mean: does it mean that it does utilize kvm now. And this is the performance I should expect from kvm?
18:11<somiaj>otisolsen70: I belive so. I don't have virt-manager on my server, but under virsh dumpxml domain, I do see <emulator>/usr/bin/qemu-system-x86_64</emulator>, and as far as I know my vms are using kvm (they all seem to have good preformance)
18:12<otisolsen70>somiaj, it is noticably faster.
18:12<otisolsen70>somiaj, performance is actually quite good imo for what it is supposed to do
18:12<otisolsen70>somiaj, I was hoping the debian wiki entry on kvm would be better ...
18:13<otisolsen70>shreeya, are you also unixbsd ?
18:14<shreeya>I'm shreeya only
18:14<unixbsd>unixbsd is a bsd guy, we arent same.
18:14<somiaj>otisolsen70: if you ssh into your guest, do you see any useful info with 'lscpu', I see Hypervisor vendor: KVM
18:14<otisolsen70>Was just confused by the link to a unixbsd quote
18:15-!-rcf [] has joined #debian
18:15-!-rcf is "rcf" on #debian
18:15<Linux-Fan>otisolsen70: Performance tuning of VMs has many aspects but having it actually virtualized (KVM) rather than emulated (QEMU only) is the largest difference performance-wise.
18:15<unixbsd>unixbsd is trying to make a ubuntu live currently, with newest kernel
18:15<otisolsen70>somiaj, Hypervisor vendor: KVM
18:15<otisolsen70>somiaj, Model name: QEMU Virtual CPU version 2.5+
18:15<somiaj>otisolsen70: okay, it is using kvm now
18:16<shreeya>unixbsd: somiaj otisolsen70 Linux-Fan thank you so much for all your help. It's pretty late in India so I'm dropping off. I'm just going to do a fresh install mostly
18:16-!-NomadJim [~Jim@] has quit [Read error: Connection reset by peer]
18:16<somiaj>hmm, I actually see Intel Core Processor (Skylake, IBRS) in my guess (though it is on a xeon, so sure that is being emulated)
18:16<otisolsen70>shreeya, good luck
18:16<somiaj>shreeya: wella t least we got ot the bottom of your issue, sorry about your data.
18:16<unixbsd>shreeya: just install on a fresh memestick
18:16<otisolsen70>somiaj, I am on xeon as well
18:17-!-NomadJim [~Jim@] has joined #debian
18:17-!-NomadJim is "Nomad" on #debian #linode
18:17<Linux-Fan>shreeya: You're welcome (although I could not contribute much given my lack of LVM knowledge)
18:17<unixbsd>you can put debian or ubuntu runnong on the memstick, like 15GB, you will fix it later.
18:17-!-foka [] has quit [Read error: Connection reset by peer]
18:17<shreeya>unixbsd: Okay
18:17<somiaj>shreeya: in the future make sure to do backups in the future before messing with partitions, and create an image of your lvm partition if you want to play around with data recovery before you install.
18:18<shreeya>somiaj: yeah I got a good lesson today
18:18<unixbsd>shreeya: as somiaj said lvm is not easy to fix at all. I am looking about my lives how it might fix. testdisk, I dont even know if it has lvm
18:19<somiaj>unixbsd: you might be able to pull the metadata off the lvm partition if you manually scan it using data recovery tools, from there you can hope that only the headers were messed with and rewrite teh meta data to the lvm partition hoping to get it back.
18:19<shreeya>unixbsd: let me know if you find out something or wanna still try something. Anyway I'm losing my data now.
18:19<unixbsd>shreeya: for modern hardware like yours, this would fit most today use. ""
18:19-!-foka [] has joined #debian
18:19-!-foka is "Anthony Fok" on #debian-i18n #debian-glibc #debian-eeepc #debian-edu #debian-devel-changes #debian-ci #debian-ayatana #debian #debconf18-taiwan #autodeb
18:20<shreeya>I have to use Debian
18:20<unixbsd>somiaj: yeah, that way.
18:20<somiaj>again this is a debian support channel, we should stick to suggesting debian tools/images. If shreeya wants to choose another distro they are free to, but it isn't supported here.
18:20<shreeya>Cannot go with Ubuntu
18:20<unixbsd>dont know which debian maybe SID has good modern kernel?
18:20<somiaj>shreeya: and you already have a bullseye installer that you know works with your wifi, so you should be goo.
18:21<unixbsd>I have issues, many with testing and sid debians, moslty with the networking layer
18:21<somiaj>shreeya: note bullseye won't be released for another month or two, but it is frozen and mostly ready, just a bit slow on security support until the release.
18:21<otisolsen70>unixbsd, shreeya: there is a #ubuntu channel on freenode
18:22<unixbsd>hey guys, what is the available kernel into debian testing now? backports?
18:24<Linux-Fan>i.e. stable: 4.19, backports: 5.10.24, testing: 5.10.28, sid: 5.10.28
18:24-!-lavamind [] has left #debian []
18:26<otisolsen70>somiaj, Linux-Fan : thank you for your help!
18:26<Linux-Fan>otisolsen70: You're welcome :)
18:28<somiaj>unixbsd: 5.10 is going to be the bullseye kernel and is also the one in buster-backports
18:28-!-user [~user@] has joined #debian
18:28-!-user is "realname" on #debian
18:28-!-otisolsen70 [] has quit [Quit: Leaving]
18:28-!-user is now known as Guest3773
18:29<unixbsd>somiaj: that's already a pretty one.
18:29<unixbsd>this would like work on the above i5, mentioned lvm#Ã.
18:29<Guest3773>Hello, are some kernel experts here?
18:29<unixbsd>##linux are
18:30<somiaj>Guest3773: best to just ask your question, though this is more for debian support
18:30<somiaj>unixbsd: that channel isn't #kernel
18:30<somiaj>unixbsd: and it is not on this network
18:30<somiaj>Guest3773: what is your question, is it about kernels on debin?
18:30<kingsley>Can you suggest a nice, user friendly tool, with a GUI, that reveals the contents of all sessions recorded to a multisession DVD?
18:30<unixbsd>##linux is fine for kernel talk as well
18:31<Guest3773>i guess im to dumb to even ask the question properly :D
18:31<unixbsd>k3b maybe??
18:31<Guest3773> if (!psi_to_return) {
18:31<Guest3773> rcu_read_unlock();
18:31<Guest3773> pr_err("douane(%u):%d:%s: Failed to allocate new process_socket_inode.\n", packet_id, __LINE__, __FUNCTION__);
18:31<Guest3773> return NULL;
18:31<Guest3773> }
18:31-!-Guest3773 was kicked from #debian by debhelper [flood]
18:31-!-NikopolSohru [] has joined #debian
18:31-!-NikopolSohru is "user" on #biz #cryptoparty #debian-raspberrypi #openstreetmap #moocows #dogecoin #debian #i2p #zcash
18:31-!-Guest3773 [~user@] has joined #debian
18:31-!-Guest3773 is "realname" on #debian ##linux
18:31<Guest3773>got kicked ^
18:32<Guest3773>flood attack :'( sure
18:32-!-ahso [] has quit [Quit: bye]
18:32-!-cyphase [] has quit [Ping timeout: 480 seconds]
18:33<somiaj>Guest3773: yea please use a pastebing like, but what is your question, what is it you are trying to do?
18:34<Guest3773>ls -al /var/crash/ is always empty but the system is freezing, i installed the dbg kernel version and confirmed both with yes after installing kdump-tools
18:34<somiaj>Guest3773: so your issue is the system is freezing and you are trying to debug why?
18:35<Guest3773>i try to get some type of log because im working on a "patch" for a dkms module
18:35-!-towo` [] has quit [Quit: Leaving]
18:36<somiaj>Guest3773: oh so it is freezing due to some thrid party module. This is a bit out of my experience, but maybe #kernel on can help
18:36-!-v3xtra [] has joined #debian
18:36-!-v3xtra is "v3xtra" on #debian
18:36<somiaj>Guest3773: actually it is ##kernel
18:37<somiaj>Guest3773: there is also #debian-kernel on this network, though more focused on the kernel, might be able to help you with a dkms module
18:38-!-stephanlachnit [~Thunderbi@2a02:8071:b94:ab00:133c:15cb:1528:9c9e] has quit [Quit: stephanlachnit]
18:38<Guest3773>okay thank you, i will try my luck.
18:39<TimMc>Is there a relatively straightforward way to install Debian into an existing LUKS + LVM volume?
18:40<TimMc>I've tried (with stable) and I get an unbootable system...
18:40<somiaj>TimMc: is your /boot inside the luks+lvm?
18:40-!-v3xtra [] has quit []
18:40<TimMc>Nope, outside.
18:40<TimMc>MBR + unencrypted /boot because it seemed like the alternative was more trouble.
18:40<somiaj>so your install works fine, but installing grub and booting isn't?
18:41<somiaj>TimMc: yea, that was what I was going to suggest to put /boot outside the lvm
18:41<TimMc>The install "works", but when I boot I land in initramfs and it can't find the LVM volume (because it never prompts for LUKS pw.)
18:41<Guest3773>Cannot join #kernel (Channel is invite only) hm..
18:41<somiaj>Guest3773: ##kernel, and it is a different network
18:42-!-cyphase [] has joined #debian
18:42-!-cyphase is "Cyphase" on @#heroes #guardianproject #ceph #virt #debian #debian-next # @#PrisonBreak #quodlibet #qemu #ceph-devel @#lost @#p4xriddle
18:42<Guest3773>@timmc use chroot
18:42<TimMc>I *think* it's just missing the unlock-LUKS step from the... what, Plymouth scripts, I think? But I've tried several ways to tell it to include that (via a chroot) and no luck.
18:42-!-silver [] has quit [Quit: One for all, all for One (2 Corinthians 5)]
18:42<Guest3773>unlock volume before doing chroot :D
18:42-!-thomasross [] has joined #debian
18:42-!-thomasross is "thomasross" on #debian-next #debian #debian-kde #debian-offtopic #packaging
18:42<somiaj>TimMc: that should be a part of the initrd image, wonder why it isn't getting setup correctly.
18:43-!-Guest3773 is now known as korder
18:43<TimMc>Well, I unlocked everything and in a chroot I made sure cryptfs-initramfs was installed (it was) and even set CRYPTSETUP=Y in the /etc/cryptsetup-initramfs/conf-hook before running update-initramfs.
18:44<TimMc>(I also had to edit /etc/crypttab with the right details, because the installer assumed it would use a keyfile.)
18:45<korder> maybe this is somehow usefull
18:45-!-Linux-Fan [] has left #debian [Good Bye all]
18:46<korder>because its quite similar than what you are trying
18:48<TimMc>The root + cryptdevice for cmdline.txt looks like a good thing to investigate...
18:48<somiaj>TimMc: did you say you had cryptsetup-initramfs installed?
18:49<korder>or i don't got your intention right. the commands in there are outdated for modern debian / kali but still quite okay guide to follow with few changes
18:49<somiaj>and after you updated things you rebuilt the initramfs image?
18:50<TimMc>Tried to: update-initramfs -k all -c
18:50<TimMc>But some guides say to use -u
18:51<TimMc>I don't know how to check if it worked other than just trying to boot.
18:51<somiaj>hmm, yea unsure exactly what hook is needed to make the initramfs ask for the passphrase to decrypt the fs
18:51<korder>i always used -u until now
18:51<TimMc>Getting into the chroot is such a pain.
18:51<somiaj>TimMc: there is lsinitrd you can use to check out the contents of the image, this can help you at least poke around
18:54<korder>"when I boot I land in initramfs" wait what, thats something u messed up with your install
18:55<korder>u only get prompted for luks pw once u setup the dropbear ssh server correctly
18:55<korder>u cant unlock the disk with initramfs
18:55<korder>at least i never could :D
18:55<TimMc>Dropbear would only be relevant for that Kali rpi thing, right?
18:55<korder>its debian / linux universal
18:55<TimMc>I'm logging in from the keyboard of the laptop.
18:56-!-f10 [] has quit [Read error: No route to host]
18:56<TimMc>I don't think SSH is relevant here.
18:56-!-f10 [] has joined #debian
18:56-!-f10 is "f10" on #debian-kde #debian
18:58<korder>xD i guess u need like almost exactly what i called with that guide. because u cant unlock the disc otherwise. the dropbear, boots before the luks get decrypted, you either get prompted for you password once u followed the guide the correct way and either put in your password which gets parsed to the back-end that decrypt your disk
18:59<korder>or u login into the "rpi" over network ssh, thats your choice, i dont know if the unlock depends on dropbear, i dont think so as well
18:59<korder>but that u land in initramfs means 99.99% u screwed up the installation
19:00<TimMc>I think that has been established. :-)
19:00-!-_cr_ [] has quit [Read error: Connection reset by peer]
19:00-!-coruja [] has quit [Quit: ZNC 1.8.2 -]
19:00<korder>i think your right and dropbear was optional in the guide
19:00-!-_cr_ [] has joined #debian
19:00-!-_cr_ is "Carsten Rosenberg" on #debian @#clamav
19:00<TimMc>Process was: Start Debian Live, unlock LUKS, open LVM, start installer; choose existing LUKS and LVM; reboot.
19:01<TimMc>That's what landed me in initramfs complaining about "Gave up waiting for root device" even after each of the attempts above.
19:01<korder>okay :d yeah how to unlock the drive mahalo :D
19:01-!-me [] has joined #debian
19:01-!-me is "realname" on #debian
19:01-!-jmux [~jan-marek@2a01:c22:6e28:7c00:4236:798:9871:3460] has quit [Quit: Konversation terminated!]
19:01<TimMc>However! I have discovered that lsinitramfs says it can't find the initramfs image... aaaaand it turns out I didn't mount /boot for that chroot. -.-
19:03<korder>okay but u did "/etc/cryptsetup-initramfs/conf-hook" correctly ? i guess u can unlock out of initramfs, sry has been years since i have done that, but u have to setup the cryptsetup within the initramfs image before, without u cant unlock
19:06<TimMc>Yep, did the conf-hook, even though it shouldn't be required.
19:06<TimMc>I'm going to try removing that again *after* I get things working.
19:06<korder>its 100% never saw initramfs being capable of unlocking without it
19:07<korder>my advice (im noob) would be try to follow the guide i provided and change every outdated and not matching command
19:08<korder>i got it working so, im sure u can do as well. if you fail no wonders its a messy process and is supposed to drive u crazy :D
19:09-!-coruja [~coruja@] has joined #debian
19:09-!-coruja is "Markus Meyer" on #blobot #debian-next #debian #oftc #frickelplatz
19:09-!-choozy [] has quit [Quit: - Chat comfortably. Anywhere.]
19:09<TimMc>There isn't even a /boot/cmdline.txt so I don't know that that guide is applicable.
19:09-!-Cienisty [] has quit [Quit: Ping timeout (120 seconds)]
19:09<TimMc>(My existing Debian system doesn't have one either.)
19:09-!-Cienisty [] has joined #debian
19:09-!-Cienisty is "Cienisty" on #debian #osm-pl #cyclosm
19:09-!-Brigo [] has joined #debian
19:09-!-Brigo is "realname" on #debian #debian-es #debian-next #debian-offtopic
19:11-!-korder [~user@] has quit [Remote host closed the connection]
19:11-!-user2259847770 [~user22598@] has joined #debian
19:11-!-user2259847770 is "realname" on #tor-l10n #tor-south #tor-project #debian
19:12-!-me [] has quit [Quit: Leaving]
19:13<TimMc>Oho, if I remove CRYPTSETUP=Y then update-initramfs gives warnings about omitting crypto modules!
19:16<TimMc>"Target 'samsung' not found in /etc/crypttab" is another warning. I have it in there under a UUID instead.
19:26-!-Mister00X [] has quit [Quit: - Komfortabler Chat. Überall. ]
19:28-!-dvs [] has joined #debian
19:28-!-dvs is "realname" on #debian
19:28<TimMc>OK, apparently the *name* I unlock with has to match crypttab.
19:29<TimMc>I was doing `cryptsetup luksOpen /dev/sdb2 samsung` but the crypttab says cmencr instead of samsung, and apparently update-initramfs thinks that's horrible.
19:30<TimMc>But... if I fix that I get a bunch of other issues relating to the _dif volume, so I'm going to give up on using the --integrity LUKS option. -.-
19:31<TimMc>Maybe the right answer is to do a standard install, then shrink LVM and make a new LVM next to it with the thinpool I want, move stuff into it, remove the first one.
19:33<TimMc>Too many landmines I'm leaving for myself, I think.
19:42-!-jikkil [~jikkil@] has joined #debian
19:42-!-jikkil is "realname" on #debian
19:45-!-polymetric [] has joined #debian
19:45-!-polymetric is "polymetric" on #debian
19:46-!-jikkil [~jikkil@] has quit []
19:53-!-imega [] has quit [Ping timeout: 480 seconds]
19:55-!-ol [~quassel@2406:e003:852:ff01:8e89:a5ff:feca:57fe] has joined #debian
19:55-!-ol is "Ol" on #debian
19:57-!-lunc [~omnd@] has quit [Ping timeout: 480 seconds]
19:59<TimMc>I had been hoping to have an LVM with thinpool so that I could make a copy-on-write snapshot every time I took a backup and not have to reserve extra space for it... but I'm not sure it's worth the effort. This new drive is larger. -.-
19:59-!-xnaas is now known as Guest3774
19:59-!-xnaas [] has joined #debian
19:59-!-xnaas is "xnaas" on #debian
20:01-!-f10 [] has quit [Read error: No route to host]
20:02-!-ax5623 [] has quit [Quit: Leaving]
20:02-!-f10 [] has joined #debian
20:02-!-f10 is "f10" on #debian-kde #debian
20:04-!-ax5623 [] has joined #debian
20:04-!-ax5623 is "+" on #linux #debian-next #debian
20:06-!-Guest3774 [] has quit [Ping timeout: 480 seconds]
20:07-!-ax562 [] has joined #debian
20:07-!-ax562 is "realname" on #linux #debian #debian-next
20:09-!-voyager1 [] has quit [Quit: ...]
20:11-!-awal1 [] has joined #debian
20:11-!-awal1 is "realname" on #debian-devel-changes #debian-next #debian
20:13-!-polymetric [] has quit [Ping timeout: 480 seconds]
20:20<TimMc>I wonder why Debian's installer still creates a 1 GB swap by default. Not enough to hibernate in.
20:21-!-mbond [] has quit [Quit: mbond]
20:22-!-nuc [] has quit [Ping timeout: 480 seconds]
20:24-!-monkries [~monkries@] has joined #debian
20:24-!-monkries is "monkries [OpenComputers]" on #debian #debain
20:25-!-monkries [~monkries@] has quit []
20:28-!-mode/#debian [+l 703] by debhelper
20:28-!-nuc [] has joined #debian
20:28-!-nuc is "realname" on #debian
20:36-!-user2259847770 [~user22598@] has quit [Remote host closed the connection]
20:37-!-thiras [~thiras@] has quit [Ping timeout: 480 seconds]
20:43-!-craigevil [] has quit [Quit: Lost terminal]
20:45-!-julienth37_ [] has joined #debian
20:45-!-julienth37_ is "julienth37" on #debian
20:45-!-julienth37 [] has quit [Read error: No route to host]
20:55-!-dvs [] has quit [Remote host closed the connection]
20:55-!-polymetric [] has joined #debian
20:55-!-polymetric is "polymetric" on #debian
20:59-!-NikopolSohru [] has quit []
21:00-!-nuc [] has quit [Read error: Connection reset by peer]
21:01-!-julienth37 [] has joined #debian
21:01-!-julienth37 is "julienth37" on #debian
21:01-!-nuc [] has joined #debian
21:01-!-nuc is "realname" on #debian
21:02-!-julienth37_ [] has quit [Ping timeout: 480 seconds]
21:03-!-craigevil [] has joined #debian
21:03-!-craigevil is "craig" on #debian-raspberrypi #debian-next #debian-offtopic #debian
21:04-!-nuc [] has quit [Read error: Connection reset by peer]
21:04-!-ax562 [] has quit [Quit: Leaving]
21:05-!-nuc [] has joined #debian
21:05-!-nuc is "realname" on #debian
21:09-!-ax562 [] has joined #debian
21:09-!-ax562 is "realname" on #linux #debian #debian-next
21:11-!-voyager1 [] has joined #debian
21:11-!-voyager1 is "user" on #debian
21:11-!-radio_nowhere [] has joined #debian
21:11-!-radio_nowhere is "realname" on #debian-raspberrypi #debian-next #debian
21:12-!-shreeya [] has quit [Quit: Connection closed for inactivity]
21:14-!-polymetric [] has quit [Ping timeout: 480 seconds]
21:15-!-j_f-f [] has quit [Remote host closed the connection]
21:15-!-sidmo_ [] has joined #debian
21:15-!-sidmo_ is "sidmo" on #debian-next #debian
21:16-!-silver [] has joined #debian
21:16-!-silver is "Jesse Lee Morgan" on @#experimental #oftc #moocows #C #mm #linux #neurodebian #debian-offtopic #debian-nginx #debian-kde #debian-next #debian #debian-support #debian-devel-changes #minidebconf-online #debian-meeting #debconf-cambridge
21:16-!-TheRuralJuror [] has quit [Ping timeout: 480 seconds]
21:18-!-j_f-f [] has joined #debian
21:18-!-j_f-f is "J\xF6rg Frings-F\xFCrst" on #debian #debconf-miniauditorio #debian-games #debian-xfce #debian-ubuntu #debconf18-taiwan
21:18-!-sidmo__ [] has quit [Ping timeout: 480 seconds]
21:19-!-epoll is now known as Strom
21:21-!-shiki [] has joined #debian
21:21-!-shiki is "realname" on #moocows #debian
21:22-!-craigevil [] has quit [Quit: leaving]
21:22-!-sappheiros [] has quit [Quit: please pray for me]
21:25-!-sevu [] has quit [Ping timeout: 480 seconds]
21:26-!-M4he [] has joined #debian
21:26-!-M4he is "Mahe" on #debian
21:28-!-nuc [] has quit [Read error: Connection reset by peer]
21:28-!-nuc [] has joined #debian
21:28-!-nuc is "realname" on #debian
21:29-!-Strom [] has left #debian []
21:29-!-mahe [] has quit [Ping timeout: 480 seconds]
21:29-!-M4he is now known as mahe
21:30-!-craigevil [] has joined #debian
21:30-!-craigevil is "craig" on #debian-raspberrypi #debian-next #debian-offtopic #debian
21:31-!-ddsys [] has quit [Quit: Leaving]
21:32-!-ddsys [] has joined #debian
21:32-!-ddsys is "ddsys" on #debian-offtopic #debian-next #debian
21:37-!-nyov is now known as Guest3776
21:37-!-nyov [] has joined #debian
21:37-!-nyov is "nyov" on #debian-offtopic #oftc #debian #luakit
21:41-!-nuc [] has quit [Read error: Connection reset by peer]
21:41-!-nuc [] has joined #debian
21:41-!-nuc is "realname" on #debian
21:41-!-Strom [] has joined #debian
21:41-!-Strom is "Strom" on #debian
21:42-!-Brigo [] has quit [Ping timeout: 480 seconds]
21:43-!-nuc [] has quit [Read error: Connection reset by peer]
21:43-!-nuc [] has joined #debian
21:43-!-nuc is "realname" on #debian
21:44-!-Guest3776 [] has quit [Ping timeout: 480 seconds]
21:55-!-mzajc [] has quit [Quit: SIGTERM'd]
21:57-!-Strongstan [] has quit [Remote host closed the connection]
21:58-!-mode/#debian [+l 697] by debhelper
21:58-!-Strongstan [] has joined #debian
21:58-!-Strongstan is "Strongstan" on #alpine-linux #debian #ovirt #qemu #virt
22:01-!-user2259847770 [~user22598@] has joined #debian
22:01-!-user2259847770 is "realname" on #tor-l10n #tor-south #tor-project #debian
22:03-!-ol [~quassel@2406:e003:852:ff01:8e89:a5ff:feca:57fe] has quit [Ping timeout: 480 seconds]
22:04-!-craigevil [] has quit [Remote host closed the connection]
22:04-!-craigevil [] has joined #debian
22:04-!-craigevil is "craig" on #debian-raspberrypi #debian-next #debian-offtopic #debian
22:04-!-radio_nowhere [] has quit [Quit: Leaving]
22:05-!-dvs [] has joined #debian
22:05-!-dvs is "realname" on #debian
22:24-!-Roman3349 [] has quit [Ping timeout: 480 seconds]
22:27-!-thomasm [] has joined #debian
22:27-!-thomasm is "tm" on #debian #ceph
22:28-!-tm [] has quit [Ping timeout: 480 seconds]
22:29-!-nuc [] has quit [Read error: Connection reset by peer]
22:29-!-nuc [] has joined #debian
22:29-!-nuc is "realname" on #debian
22:33-!-chrisgt [~rusty@] has quit [Remote host closed the connection]
22:34-!-julienth37_ [] has joined #debian
22:34-!-julienth37_ is "julienth37" on #debian
22:36-!-julienth37 [] has quit [Read error: No route to host]
22:39-!-nuc [] has quit [Read error: Connection reset by peer]
22:39-!-nuc [] has joined #debian
22:39-!-nuc is "realname" on #debian
22:42-!-nuc [] has quit [Read error: Connection reset by peer]
22:43-!-nuc [] has joined #debian
22:43-!-nuc is "realname" on #debian
22:46-!-nuc_ [] has joined #debian
22:46-!-nuc_ is "realname" on #debian
22:52-!-nuc [] has quit [Ping timeout: 480 seconds]
22:53-!-nuc_ [] has quit [Read error: Connection reset by peer]
22:54-!-CeBe [~cebe@2a02:560:4a88:d800:884:e3e8:47c7:a4b3] has quit [Ping timeout: 480 seconds]
22:54-!-nuc [] has joined #debian
22:54-!-nuc is "realname" on #debian
22:55-!-Surfer2011_ [~quassel@] has joined #debian
22:55-!-Surfer2011_ is "Surfer2011" on #debian
22:57-!-ddsys [] has quit [Quit: Leaving]
23:03-!-Surfer2011 [] has quit [Ping timeout: 480 seconds]
23:03-!-CeBe [~cebe@2a02:560:4a8b:b300:6df3:c0f4:fa56:7ad5] has joined #debian
23:03-!-CeBe is "Carsten Brandt" on #debian #packaging
23:04-!-nuc [] has quit [Ping timeout: 480 seconds]
23:05-!-nuc [] has joined #debian
23:05-!-nuc is "realname" on #debian
23:07-!-NomadJim [~Jim@] has quit [Read error: Connection reset by peer]
23:07-!-NomadJim [~Jim@] has joined #debian
23:07-!-NomadJim is "Nomad" on #debian #linode
23:22-!-}ls{ [] has joined #debian
23:22-!-}ls{ is "nobody" on #kvm #qemu #debian-nginx #debian-lan #debian-kde #debian-django #debian
23:26-!-richard_h [~richard@2406:e001:8:a900:6e62:6dff:fe05:ae29] has joined #debian
23:26-!-richard_h is "purple" on #debian
23:30-!-shreeya [] has joined #debian
23:30-!-shreeya is "Shreeya Patel" on #debian
23:36-!-polymetric [] has joined #debian
23:36-!-polymetric is "polymetric" on #debian
23:37-!-nu-c [] has joined #debian
23:37-!-nu-c is "realname" on #debian
23:45-!-user2259847770 [~user22598@] has quit [Quit: going off the grid]
23:53-!-ftobich [] has quit [Quit: Leaving]
23:54-!-f10 [] has quit [Read error: No route to host]
23:55-!-f10 [] has joined #debian
23:55-!-f10 is "f10" on #debian-kde #debian
---Logclosed Sat May 15 00:00:45 2021