suavedandy | What is asynchronous discard? | 00:48 |
---|---|---|
suavedandy | Is it continuous discard or…? | 00:48 |
suavedandy | I mean, continuous TRIM. | 00:48 |
gnarface | i think the discard mount option enables continuous TRIM, yes, correct | 00:51 |
gnarface | according to my sources though, whether it is synchronous or asynchronous TRIM is a hardware thing | 00:51 |
gnarface | some brands do one, some brands do another | 00:51 |
gnarface | different performance impacts for both | 00:51 |
gnarface | the generally accepted advice i've heard though in either case is not to use it | 00:52 |
gnarface | and to cron fstrim instead | 00:52 |
gnarface | i think that the less that gets written to the disk the less it matters though too | 00:54 |
gnarface | (the advice not to use discard is based on both the higher load impact and the higher wear impact) | 00:55 |
suavedandy | "…we did not add discard to the crypttab. This is due to the fact that Btrfs async discard support is quite new, but [Ubuntu] 20.04 still runs kernel 5.4…" | 00:56 |
gnarface | so presumably that means you have to fstrim | 01:05 |
gnarface | i guess? | 01:05 |
gnarface | cron this weekly: /sbin/fstrim -a -v | 01:05 |
gnarface | or, i guess probably not -v if it's a cron | 01:06 |
gnarface | unless you want it mailing you the status | 01:06 |
gnarface | probably something more like: /sbin/fstrim -a >/dev/null 2>&1 | 01:06 |
gnarface | if it never gets written to, it might not cause problems | 01:07 |
gnarface | or at least not for many years | 01:07 |
gnarface | that would be my guess anyway | 01:07 |
suavedandy | Guys? | 01:15 |
suavedandy | I have a kernel panic, guys. | 01:15 |
gnarface | what'd you do? | 01:15 |
gnarface | it usually only panics when it can't find the rootfs | 01:15 |
suavedandy | Well… boot the system. | 01:15 |
gnarface | would have had to be something you changed before the last shutdown | 01:16 |
gnarface | either that or disk failure | 01:16 |
gnarface | did you build a new kernel? | 01:16 |
gnarface | a common trip-up is to fail to load the initrd.img or compile the harddrive controller driver in statically | 01:16 |
suavedandy | No. I was installing on BtrFS, following the instructions on the forum. | 01:16 |
gnarface | hmmm | 01:17 |
suavedandy | Do I hard reset or something? | 01:17 |
suavedandy | It's stuck. | 01:17 |
suavedandy | Isn't that streinous on my hardware to be stuck in kernel panic? | 01:18 |
suavedandy | Guys? | 01:19 |
suavedandy | Guys, what do I do? | 01:19 |
suavedandy | I don't want my PC to turn into a potato. | 01:20 |
gnarface | you can only power cycle at this point, yes | 01:20 |
gnarface | check the cable connections | 01:20 |
gnarface | (not while it's on) | 01:20 |
gnarface | it's not strenuous probably | 01:20 |
gnarface | but it's also not useful anymore in that state either. | 01:20 |
gnarface | power it down, let it cool off, check every plug and cable, then try again. if it panics again you'll have to try to boot a live image or something | 01:21 |
gnarface | or pull the drive and plug it into a working machine to examine it | 01:21 |
gnarface | like i said, could be hardware failure, but usually it's something you did wrong with the kernel or boot config | 01:22 |
suavedandy | Or I could just install Devuan on encrypted Ext4 instead of encrypted BtrFS. | 01:22 |
gnarface | yea or btrfs is not ready, that's very possible | 01:22 |
gnarface | i don't know either way | 01:22 |
fsmithred | if the filesystems are not mounted, poweroff should not hurt anything | 01:22 |
fsmithred | and you can also enable all the magic sysrq keys and reboot with that. | 01:23 |
fsmithred | in /etc/sysctl.conf | 01:24 |
fsmithred | kernel.sysrq=1 (I think that's right) | 01:24 |
gnarface | i thought it was on by default in the stock install | 01:24 |
gnarface | wasn't aware it could listen after a panic though | 01:25 |
fsmithred | it's limited | 01:26 |
fsmithred | oh | 01:26 |
fsmithred | maybe not | 01:26 |
fsmithred | last few releases of debian they only enabled some of the keys. default is 438 which I don't remember what that means. | 01:27 |
onefang | I thought a kernel panic was "things are too fubared for the kernel to continue, dump core and stack trace, halt everything". | 01:28 |
fsmithred | >1 is bitmask of all sysrq functions | 01:28 |
onefang | OK, not dump core, coz file systems are now halted as well. | 01:30 |
suavedandy | Nevermind. | 01:34 |
suavedandy | Just upgraded from chroot. | 01:34 |
suavedandy | Works fine now. | 01:34 |
suavedandy | Just needed to apt upgrade. Eh. | 01:34 |
suavedandy | https://youtu.be/Zmvt7yFTtt8 | 01:35 |
suavedandy | Uh-oh. | 01:37 |
suavedandy | Home subvolume has no user directory. | 01:38 |
suavedandy | WTF? | 01:38 |
suavedandy | It only has "devuan." | 01:38 |
suavedandy | fsmithred: Is that intended behavior? | 01:39 |
fsmithred | is what intended? | 01:39 |
fsmithred | what did you use to install? | 01:39 |
suavedandy | There's no user directory after the installation. | 01:40 |
fsmithred | what iso | 01:40 |
suavedandy | Your script. | 01:40 |
fsmithred | what iso | 01:40 |
suavedandy | Minimal. | 01:40 |
suavedandy | Minimal Devuan. | 01:40 |
fsmithred | the user directory is named after the primary user | 01:40 |
fsmithred | devuan | 01:40 |
fsmithred | /home/devuan | 01:40 |
fsmithred | as root, run: id devuan | 01:40 |
suavedandy | But mine's supposed to be /home/suavedandy | 01:40 |
fsmithred | and it will give you some relevant information | 01:40 |
fsmithred | you changed it during the install? | 01:41 |
suavedandy | No. | 01:41 |
suavedandy | I mean, I changed the username. | 01:41 |
fsmithred | when, where? | 01:41 |
suavedandy | When it asked me. | 01:41 |
fsmithred | and how? | 01:41 |
fsmithred | I'm confused | 01:41 |
fsmithred | it does ask that during the install, but you said "No" to that. | 01:42 |
fsmithred | to my quesiton about that | 01:42 |
fsmithred | you changed it during the install? | 01:42 |
suavedandy | It asked "Do you want to change the username?" And I've typed my new username. | 01:42 |
fsmithred | check the log to see what happened. It should change the username, the home directory and something else. Three usermod commands in the script, I think. | 01:43 |
fsmithred | oh yeah, user's primary group gets changed | 01:43 |
suavedandy | The log… where? | 01:43 |
fsmithred | so | 01:43 |
fsmithred | var/log/refractainstaller or | 01:44 |
fsmithred | well, nm | 01:44 |
fsmithred | /home/devuan/refractainstaller.log | 01:44 |
fsmithred | maybe it's there | 01:44 |
fsmithred | id devuan | 01:44 |
fsmithred | id suavedandy | 01:44 |
fsmithred | or look in /etc/passwd to see who exists | 01:44 |
suavedandy | Devuan does not exist. | 01:44 |
suavedandy | suavedandy, however. | 01:45 |
onefang | Or maybe just "adduser suavedandy" and move on with your life. | 01:45 |
fsmithred | id suavedandy | 01:45 |
suavedandy | suavedandy does exist. | 01:45 |
fsmithred | what's your user id | 01:45 |
fsmithred | 1000 | 01:45 |
suavedandy | It's just the folder that does not. | 01:45 |
fsmithred | so change it | 01:45 |
fsmithred | um | 01:45 |
fsmithred | no | 01:46 |
suavedandy | 1000, yes. | 01:46 |
fsmithred | figure out what's going on | 01:46 |
fsmithred | who owns the files in /home/devuan? | 01:46 |
suavedandy | How do I check it? | 01:46 |
fsmithred | ls -l /home/devuan | 01:46 |
fsmithred | ls -l /home/devuan/ | 01:46 |
suavedandy | There's only one file. | 01:47 |
suavedandy | package_list | 01:47 |
suavedandy | And it's owned by root. | 01:47 |
fsmithred | ls -la | 01:47 |
fsmithred | there are some hidden files | 01:47 |
fsmithred | ls -l /home | 01:48 |
suavedandy | .bash_logout, .bashrc, .kde, .profile. | 01:48 |
suavedandy | All owned by me. | 01:49 |
fsmithred | that's weird | 01:49 |
gnarface | this is still btrfs? | 01:49 |
fsmithred | I guess you can just change the name of the directory | 01:49 |
fsmithred | yeah | 01:49 |
suavedandy | gnarface: Indeed. | 01:49 |
suavedandy | fsmithred: Think so? | 01:50 |
gnarface | something seems weird, maybe the installer missed a step because of tool differences? | 01:50 |
fsmithred | maybe | 01:50 |
fsmithred | I suggested looking at the error log, but it probably doesn't say much | 01:50 |
fsmithred | unless it was run with -d|--debug | 01:50 |
suavedandy | Installing on BtrFS with Refracta's installer is… funny. | 01:50 |
suavedandy | To say the least. | 01:50 |
fsmithred | other option is to delete the whole thing and remove your user | 01:51 |
fsmithred | then create a new user | 01:51 |
fsmithred | the whole thing = /home/devuan | 01:51 |
fsmithred | rm -r /home/devuan | 01:51 |
fsmithred | deluser suavedandy | 01:52 |
fsmithred | adduser suavedandy | 01:52 |
suavedandy | If only I had root active… | 01:52 |
fsmithred | what? | 01:52 |
suavedandy | I have single-user sudo. | 01:52 |
suavedandy | Root turned off. | 01:53 |
fsmithred | ok, I don't know what you can do | 01:53 |
gnarface | fix it from another machine? | 01:53 |
gnarface | or boot in single user mode | 01:54 |
fsmithred | oh yeah, he was working in a chroot earlier | 01:54 |
fsmithred | that would work | 01:54 |
fsmithred | boot live media | 01:54 |
gnarface | i would just rename the directory | 01:54 |
fsmithred | worth a try | 01:54 |
suavedandy | Ah, okay. | 01:54 |
suavedandy | Damn, forgot to install cryptsetup-modified-functions. | 01:56 |
suavedandy | Renamed the folder. No more errors, that's for sure. | 01:58 |
suavedandy | fsmithred: Maybe the script just "forgot" to rename the folder. | 02:01 |
fsmithred | the command might have failed for some reason, but it wouldn't just skip that line in the script. | 02:02 |
suavedandy | Hm… | 02:02 |
suavedandy | Maybe I needed to upgrade everything before doing anything. | 02:04 |
fsmithred | `? | 02:04 |
suavedandy | I mean, it worked against the kernel panic. | 02:04 |
suavedandy | Might as well fix whatever your script was struggling with. | 02:05 |
suavedandy | I can upgrade before continuing with installing the bootloader and setting up the user. | 02:05 |
fsmithred | that sounds like a bad idea | 02:06 |
suavedandy | You think? | 02:06 |
fsmithred | the installer copies the live system to hard disk | 02:06 |
fsmithred | all the versions in the live system go together | 02:06 |
fsmithred | anything you pull from repo might be newer | 02:06 |
fsmithred | finish the install then upgrade after you reboot | 02:06 |
fsmithred | I thought you already finished the install | 02:07 |
suavedandy | I thought about doing it again just in case. | 02:07 |
fsmithred | if you do, please run 'refractainstaller -d' | 02:08 |
fsmithred | that'll make a bigger log | 02:08 |
suavedandy | But if it won't work then… | 02:08 |
fsmithred | will look a little weird on your screen because it echoes all the commands | 02:08 |
fsmithred | why wouldn't it work? | 02:09 |
fsmithred | oh, you said But | 02:09 |
fsmithred | well, that's the point of the log. If the install fails, there will be some evidence of what did or didn't happen. | 02:09 |
suavedandy | Talking about upgrading before proceeding with installing the bootloader. | 02:09 |
suavedandy | In the script. | 02:09 |
fsmithred | upgrade in chroot? | 02:10 |
suavedandy | You know, that step where it suggests you to chroot. | 02:10 |
fsmithred | might work and might cause a conflict | 02:10 |
suavedandy | Yeah. | 02:10 |
fsmithred | don't try to upgrade the running system | 02:10 |
suavedandy | chroot into /target. | 02:11 |
suavedandy | After you type 2 into the prompt, the script proceeds with installing the bootloader. | 02:12 |
suavedandy | But before you do that it suggests you to chroot into /target. | 02:12 |
fsmithred | not if you choose chroot from the menu | 02:12 |
fsmithred | if you choose chroot from that menu, you will have to install grub manually | 02:12 |
suavedandy | There's no "chroot" in the menu. | 02:12 |
suavedandy | There's either "Install the bootloader," "Proceed without the bootloader" or "Abort the installation." | 02:13 |
fsmithred | yeah, I'm looking at the code now | 02:13 |
fsmithred | the graphical installer has a chroot button. I assumed it was in the list in the cli installer, but instead, I expect you to alt-Fn to another virtual console | 02:14 |
fsmithred | if you want to do that | 02:14 |
suavedandy | Indeed. | 02:14 |
fsmithred | so yes, you could leave that screen up, go to tty2 and chroot, go back and tell it to install the bootloader | 02:15 |
suavedandy | I did chroot in the second TTY and prepare everything for BtrFS to work. I didn't upgrade tho. | 02:15 |
fsmithred | just be mindful of where you get your grub packages | 02:16 |
fsmithred | if you pull in grub packages in chroot, then go back to the installer and say 'install bootloader' | 02:16 |
fsmithred | it'll work if the grub versions are the same | 02:16 |
fsmithred | the installer copies the live system to hard disk | 02:17 |
fsmithred | the installer copies the live system to hard disk | 02:17 |
suavedandy | I upgraded after rebooting into the system, getting the kernel panic, getting back to the live environment, chrooting into the installation and upgrading it from there. | 02:17 |
suavedandy | Then kernel panic gone. | 02:17 |
fsmithred | and you're upgrading the target before the installer is finished | 02:17 |
fsmithred | probably because it remade the initramfs | 02:18 |
suavedandy | Maybe. | 02:18 |
suavedandy | Doesn't the installer remake initramfs? | 02:18 |
fsmithred | yes | 02:19 |
suavedandy | Oof. | 02:19 |
suavedandy | Well, I dunno. | 02:19 |
fsmithred | and that's why the graphical installer uses --debug by default. | 02:19 |
suavedandy | I guess it would have been easier if there was a more native way to install on BtrFS like on OpenSUSE. | 02:20 |
fsmithred | I was nice to the user by not doing that with the cli script | 02:20 |
suavedandy | Unfortunately, OpenSUSE runs like a dying whale on my laptop even without GUI and has a very hard time when it comes to switching fonts. | 02:22 |
suavedandy | Console fonts, I mean. | 02:23 |
suavedandy | I don't know why OpenSUSE runs so terrible on my laptop. It just does. | 02:26 |
fsmithred | have you seen it run fast on anything? | 02:28 |
suavedandy | No? | 02:29 |
suavedandy | But, like, it's so slow I can't even type precisely. When I type my password too fast it just blocks me. | 02:30 |
mason | Depends on what you have it running. It's run fine for me in the past, but it's the same software I run now. | 02:30 |
suavedandy | I have to try, like, 3 times and place my fingers precisely on every key. | 02:31 |
suavedandy | One of the bizarre things with YaST (with the TUI version, at least) is that the only way of changing the console font is through the sysconfig editor. | 02:35 |
suavedandy | And /etc/sysconfig/console is deprecated. | 02:35 |
suavedandy | I'm like: "What? Why is it here then?" | 02:35 |
suavedandy | I mean changing the console font, not the whole file. | 02:36 |
suavedandy | Apparently you change the font in /etc/vconsole.conf, which kinda unnecessarily seperates /etc/sysconfig/console and /etc/vconsole.conf and makes it all scrambled and stuff. | 02:40 |
fsmithred | yeah, that's not relevant here | 02:41 |
suavedandy | Anyway. | 02:41 |
suavedandy | The system seems to be working fine now. I don't know what happened to that folder. I guess it's nothing critical, maybe? | 02:42 |
suavedandy | Will finish with creating a keyfile and snapshots after I'll get some sleep. | 02:44 |
fsmithred | sounds like a plan | 02:45 |
suavedandy | Bye. | 02:46 |
fsmithred | good night | 02:46 |
stevelitt | I'm using the Beowulf live CD. What is the root password? Also, is apt-get still the way to install stuff? | 04:31 |
golinux | either root or toor iirc | 04:32 |
stevelitt | Is apt-get stil the way you install stuff golinux? | 04:32 |
golinux | I think so. Haven't installed anything in a year or two | 04:33 |
golinux | I update mostly with synaptic. | 04:33 |
stevelitt | Well, if Devuan runs Chromium+Jitsi well, I'm gonna install it, so wish me luck. And thanks for your help. | 04:33 |
stevelitt | Is synaptic confusing? | 04:33 |
golinux | Everything is confusing at my age | 04:34 |
stevelitt | lol | 04:35 |
golinux | I'm used to it. The hardest part is remembering | 04:35 |
stevelitt | I'll try apt-get first. I kinda sorta remember that from 2014. | 04:35 |
stevelitt | Thanks!!! | 04:35 |
golinux | Happy installing, Steve! | 04:37 |
Xenguy | stevelitt: All the cool kidz use 'apt' these days, and save themselves typing 4 characters 8 -) | 04:40 |
Xenguy | Me? I go with the tried and true: apt-get FTW ! | 04:41 |
golinux | +1 | 04:43 |
tuxd3v | +1 | 04:49 |
onefang | apt-get has a FTW command now? | 05:00 |
Xenguy | Now there's an idea onefang ; -) | 06:24 |
mason | dselect is the one true interface. | 06:58 |
* enyc meows | 12:05 | |
mrjayviper1 | hello, 2 questions please. 1 - Is raspberry pi3b supported in versions 3.x? I cannot find a ready made image for it. | 2 - Is ZFS supported? I cannot find any discussion on this one when doing a net search. | Thank you. | 14:53 |
Joril | mrjayviper1: to install Beowulf on a 3B I installed Devuan Ascii and then dist-upgraded to Beowulf | 14:55 |
Xenguy | mason: I confess I used to use dselect back in the day. People always complained about it then, but it didn't seem that bad to me. Why I stopped using it, I now don't recall. | 14:55 |
Joril | mrjayviper1: you end up with Beowulf on a Ascii kernel though, if you want a newer one you have to recompile it yourself | 14:56 |
mrjayviper1 | is the built-in wireless working with the ascii kernel? | 15:00 |
Joril | mrjayviper1: well I haven't tried yet, but I will, in the next few days :D I'm using just eth0 at the moment | 15:06 |
flrn_ | Good evening! | 23:18 |
flrn_ | beowulf-proposed-update brought me a strange issue with lighdm. | 23:19 |
flrn_ | when switching tty, on return to X, the screen is locked. | 23:20 |
flrn_ | that's new | 23:20 |
flrn_ | and there's an identical xsession on tty8, unlocked. | 23:25 |
flrn_ | when switching to a console and back again to tty7 a second time, this session is gone | 23:26 |
flrn_ | (switch after login) | 23:27 |
flrn_ | but the session on tty8 runs stable and survives any further tty-hopping | 23:27 |
flrn_ | downgrading back to 1.26.0-4 (from 1.26.0-4+devuan1) returns everything to normal | 23:29 |
xrogaan | > when switching tty, on return to X, the screen is locked. | 23:36 |
xrogaan | I believe it's working as designed. | 23:36 |
flrn_ | couldn't find a config option, only for suspend | 23:37 |
flrn_ | and it came just with this update, probably no coincidence (at least worth mentioning;) | 23:38 |
xrogaan | What locks the screen should be the screensaver. | 23:43 |
fsmithred | xfce-power-manager also has a lock option | 23:46 |
fsmithred | I think that's just on suspend | 23:46 |
flrn_ | oh, it's lxqt, but I | 23:47 |
flrn_ | but I looked under /etc | 23:47 |
fsmithred | I don't remember what lxqt uses for that. Is xscreensaver running? | 23:48 |
fsmithred | light-locker with lightdm? | 23:48 |
fsmithred | I'm going to test with xfce on my laptop in a few minutes. | 23:49 |
fsmithred | huh. You have lightdm with lxqt, and I have lxdm with xfce. | 23:49 |
fsmithred | weird symmetry | 23:50 |
xrogaan | might be interacting with https://github.com/the-cavalry/light-locker/ | 23:50 |
xrogaan | > This will redirect you to VT8 (assuming that your open session was on VT7 and is now kept safe by light-locker) and present LightDM's greeter for unlocking your session again. On suspend/resume light-locker will lock the active session and redirect to the LightDM's greeter for unlocking the session again. | 23:51 |
xrogaan | oh, already stated. I'm a bit late :) | 23:52 |
flrn_ | light-locker is not involved | 23:57 |
flrn_ | didn't even have it installed and just apt-got it. | 23:57 |
flrn_ | no difference | 23:58 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!