22:06:33 <Harzilein> uiui, prechteln, du warst offenbar wirklich angegriffen :D

22:06:34 <Harzilein> ewin

06:37:00 <systemdlete> would it be advisable, during a dist upgrade, to reboot between the apt upgrade and apt dist-upgrade steps, as instructed in https://www.devuan.org/os/documentation/install-guides/chimaera/upgrade-to-chimaera ?

06:37:49 <systemdlete> my upgrade is (finally!) finishing up the apt upgrade part of the beowulf->chimaera portion on its way to daedalus (I hope to get to daedalus)

06:40:42 <systemdlete> oh wait... I am upgrading a VM! So I can snapshot it and try, although I am not sure if other than a successful mid-effort reboot if the system would be stable at that point?

06:43:29 <debdog> systemdlete: depends on kernel package you're using. in case a meta package is used, a reboot makes senses

06:43:53 <systemdlete> whatever the default is

06:44:19 <systemdlete> I haven't selected any specific kernel package that I am aware of

06:44:29 <systemdlete> so whatever it was when it was installed

06:44:44 <systemdlete> sorry I can't seem to be more specific

06:45:20 <systemdlete> I tend to use the generic package rather than a specific release so that kernels will get upgraded without trouble

06:45:45 <systemdlete> if you "get" what I mean... not sure of the correct nomenclature for this

06:46:03 <systemdlete> so, I install linux-kernel-amd (or whatever it is)

06:46:18 <systemdlete> rather than linux-kernel-amd-blahblahblahversion

06:46:38 <debdog> default is meta pckage

06:46:41 <systemdlete> I guess that is a meta package

06:46:43 <systemdlete> ok

06:46:51 <systemdlete> so a reboot makes sense

06:47:15 <debdog> makes sense, but not required

06:47:44 <systemdlete> well, it just took a day to do that one apt upgrade and I am wondering about ongoing stability

06:48:03 <systemdlete> I mean, I am not too worried, but I'd hate to lose another day upgrading 868 packages

06:48:07 <systemdlete> again

06:48:14 <debdog> but then there are kernel dependend drivers, like nvidia stuff. so, in those cases you will prolly like to reboot

06:48:45 <systemdlete> OK, well I have snapshotted the whole business, so if there is a problem I can get "back"

06:48:59 <debdog> but until you reboot, the older modules will be used

06:49:09 <systemdlete> After the apt upgrade completed, I saw some mtp-probe errors on the console

06:49:22 <systemdlete> that's for, like, android, right?

06:49:30 <systemdlete> (mtp)

06:49:40 <systemdlete> so maybe I don't need to worry about those

06:50:35 <debdog> hmm, IIRC, yes. some smart phone media transfer protocol or such

06:50:51 <systemdlete> also, debdog, I have needrestart installed, and at the end of the apt upgrade, it is saying that a whole bunch of stuff is out of date

06:50:58 <systemdlete> so I think rebooting makes a lot of sense

06:52:03 <systemdlete> I'm going to cold reboot just to ensure that the VM starts clean

07:04:24 <systemdlete> starting apt dist-upgrade to chimaera...

07:04:36 <systemdlete> thanks, debdog

07:13:13 <debdog> hehe, no clue about needrestart. but purely judge by its name, isn't that what it's supposed to report

07:13:53 <systemdlete> yeah. Anyway, I cold booted and everything looks clean and is proceeding without incident (so far, anyway)

07:14:32 <systemdlete> this is actually an upgrade from starlinux kirk (which is beowulf, as indicated by os-release) not from an actual beowulf

07:14:58 <systemdlete> The only thing I see is that, at some point, I will want to change the grub splash to something more devuan mainline

08:22:32 <onefang> needsrestart tells you at the end of updating what needs to be restarted, and offers to restart services for you. It includes non service things running that depend on any library you just updated as well.

08:24:32 <onefang> You can even decide at the time to NOT restart some specific service, if it needs to be running right now and you prefer to restart it later.

08:25:07 <onefang> Naturally for something like a new kernel, it'll tell you about that to.

08:38:44 <bgstack15> alright team, I'm lost. I have a EFI-boot-only system and I just installed Devuan daedalus 5.0.1 from netinstall. When I boot to the ssd I just installed Devuan on, I only get a cursor. I think the EFI boot is somehow not finding the right stuff. I confess I don't understand EFI yet and I've tried searching the Internet. I can chroot into the system from the boot iso's rescue mode.

08:39:05 <bgstack15> I've tried reinstalling grub-efi-amd64 but that hasn't made a difference. What do I need to check/do?!

08:41:14 <fsmithred> you could try dpkg-reconfigure grub

08:41:15 <onefang> Compare the EFI partitions of the install ISO and what you installed. Might give a clue. For EFI and grub that's all the clue I can provide.

08:42:55 <fsmithred> check efibootmgr to make sure the right bootloader is first.

08:45:46 <bgstack15> will try those things. stand by.