You are not logged in.
When you install runit, live-config-sysvinit will be removed if it's installed. So will live-config and refractasnapshot and maybe a few other things. Install live-config-runit and then you can install live-config and refractasnapshot-base and -gui. The package is here:
http://distro.ibiblio.org/refracta/file … u1_all.deb
I made it for beowulf, but it should work on chimaera, too. I have not tried runit on chimaera, but I know someone who is using runit on ceres and also that same live-config-runit package and refracta tools.
HoaS: I was referring to this part of the man page:
At allows fairly complex time specifications, extending the POSIX.2 standard. It accepts times
of the form HH:MM to run a job at a specific time of day.
Your example worked. I was not putting the command inside a file. Isn't there a way to run the command from the command line?
This works:
at now + 1 minute -f testfile
This does not work:
at now + 1 minute echo "hello"
It's not you, and it's not just chimaera. I tried it in beowulf, and I can't get it to work. When I tried 'at' around 10 years ago, it was simple to figure out and it worked as expected. I'm not sure what changed.
The man page states that HH:MM is the correct format for time, but apparently 09:21 or similar is not the correct time format. So I no longer know how to do HH:MM. I tried it around two dozen different ways. (Can you tell that I'm angry?)
Sorry I have nothing useful to offer. Oh wait, yes I do. Screw at, make a cron job. Last time I did that it worked as expected.
I think the card uses the legacy driver so
Maybe. I just did 'apt-cache search IWL4965' and it showed firmware-iwlwifi.
grep for just 'iwl' and they can all show up.
I'd like to rule out eudev as the source of the problem before anything else is changed. If so, there's a fix in beowulf-proposed-updates. https://bugs.devuan.org/cgi/bugreport.cgi?bug=483
Try grep iwlwifi /var/log/syslog and see if there are any error messages.
And please do the following for me. lsmod | wc -l and compare the numbers you get when the wireless does and does not connect after a reboot. Let me know if they are different. Thanks. You could also do lsmod |grep iwlwifi to see if the wireless module is loaded.
4.19.118-2
That version is no longer in the repo. Run apt update to update your package cache and try again. You should see linux-libc-dev_4.19.160-2
The problem is with the installer. If you don't want to download a new iso, you could just upgrade the installer. The new version is currently in beowulf-proposed-updates and will be moved to the main beowulf repository very soon. You could install it from there in the live session and then do the installation.
If you don't want to mess around with editing sources.list, you could download the packages directly and install them with dpkg or gdebi. These are the same packages that are in the repo, but the links are a little shorter and easier to type.
https://sourceforge.net/projects/refrac … .6_all.deb
https://sourceforge.net/projects/refrac … .6_all.deb
fsmithred wrote:It used to ask where to put the bootloader when you installed the deb package, but it no longer asks.
The non-UEFI version (grub-pc) still asks for a target drive but the UEFI version does not because the question is meaningless for a UEFI system.
Yes, that's what I remember, and it stopped doing that for me earlier this year. I modified refractainstaller to account for that. The modification involved uncommenting one line which I had commented out in the past because the user was being asked twice where to put the bootloader. Today, it's asking me again.
The problem with the 3.0.0 iso is that the boot partition isn't getting mounted correctly for grub-install. I was able to get it to work by manually mounting it right before installing the grub-pc package. But that does not explain why the attempts to fix it in chroot didn't work for OP. Everything was mounted correctly there. I'd have to go back and read everything again to be sure, but maybe there was a problem with mis-match of grub packages between the iso and the repo.
I just did a successful install with a preliminary 3.1.0 iso I made for testing before actual point-release. It works. I do get asked twice where to put the bootloader. I also get a warning before the boot menu, because it can't find the theme. Press any key to continue, and it works.
Here's the link for the test iso.
https://get.refracta.org/files/experime … p-live.iso
sha256sum: bf477a3c0dc27866509407fde670d8fa0b903296effef7f67c2222a48fd9eb2a
I just noticed that the command, grub-install, does not appear anywhere in this thread. You might need to run that or 'dpkg-reconfigure grub' before you run update-grub. It used to ask where to put the bootloader when you installed the deb package, but it no longer asks.
I: update-initramfs is disabled (live system is running without media mount on /lib/live/mount/medium).
You can either remove the live-tools package or use the modified name for the command.
update-initramfs.orig.initramfs-tools -u -k all
Quick answer on compressing initrd. Look at extract_initrd() rebuild_initrd() starting at lines 316 and 385.
https://git.devuan.org/devuan/refractas … tasnapshot
There's extra code if the cpu microcode is installed.
If you're doing this on a usb, you can mount the usb, copy the modified initrd to the /live folder and edit the boot menu. This won't work if you used dd to put the isohybrid image on the usb. It needs to be a real first partition.
Instead of mkinitramfs, you can use update-initramfs -u in the chroot. It will rebuild the initrd.img for the running kernel. If you want to build for a different kernel, use update-initramfs -u -k <kernel-version> or update-initramfs -u -k all
If you try patching 9990-misc-helpers.sh please let me know how it goes. That file already gets patched for refracta2usb, and I could add the ntfs support next time I touch that package.
I think this post has the magic sauce: https://lists.debian.org/debian-live/20 … 00038.html
live-boot's function 'is_supported_fs' should add one statement,'if test "$fstype" = "ntfs" -a -e /sbin/mount.ntfs -a -e /bin/ntfs-3g;then return 0;fi '.
ntfs-3g's command is /bin/ntfs-3g,and /sbin/mount.ntfs (also /sbin/mount.ntfs-3g) is a soft link to /bin/ntfs-3g.when user installed ntfs-3g,it's /var/lib/dpkg/ntfs-3g.postinst will auto remake initrd.img (call update-initramfs),include live-boot'script in new initrd.img,but,when live-boot not change it's code of function 'is_supported_fs',new initrd.img will boot failed on ntfs.All live-boot need to do is add one statement to it.
That function, is_supported_fs is in /lib/live/boot/9990-misc-helpers.sh
But I'm not sure where that test goes. Maybe early in the function to avoid some of the other tests.
I can confirm that the ntfs kernel modules are not in the beowulf iso's initramfs, and that they are in the ascii iso's initramfs.
3.1
# lsinitramfs mnt/live/initrd.img |grep ntfs
scripts/local-bottom/ntfs_3g
scripts/local-premount/ntfs_3g
usr/bin/ntfs-3g
usr/lib/x86_64-linux-gnu/libntfs-3g.so.883
usr/lib/x86_64-linux-gnu/libntfs-3g.so.883.0.0
usr/sbin/mount.ntfs
usr/sbin/mount.ntfs-3g
2.1
# lsinitramfs mnt/live/initrd.img |grep ntfs
bin/ntfs-3g
sbin/mount.ntfs-3g
sbin/mount.ntfs
scripts/local-premount/ntfs_3g
scripts/local-bottom/ntfs_3g
lib/x86_64-linux-gnu/libntfs-3g.so.871
lib/x86_64-linux-gnu/libntfs-3g.so.871.0.0
lib/modules/4.9.0-11-amd64/kernel/fs/ntfs
lib/modules/4.9.0-11-amd64/kernel/fs/ntfs/ntfs.ko
Where the hell did ntfs.ko go? On my installed beowulf system, it's missing. Same ntfs packages are installed as in my ascii, which does have ntfs.ko. In ascii, apt-file shows that it comes with the kernel. In beowulf, apt-file doesn't find ntfs.ko.
dpkg -l |grep ntfs
ii libntfs-3g883 1:2017.3.23AR.3-3 amd64 read/write NTFS driver for FUSE (runtime library)
ii ntfs-3g 1:2017.3.23AR.3-3 amd64 read/write NTFS driver for FUSE
# find /lib/modules/4.19.0-13-amd64/ -name "*ntfs*"
#
# locate ntfs.ko
#
Thanks for the detailed report. I don't know what decisions went into using start-stop-daemon. There were a few iterations of the patch, and they all seemed to work.
NTFS: If something is missing, I have no idea what it is. I did not remove any packages and ntfs-3g is installed in the live system. Do you maybe need to load a grub module before loading the kernel?
acpi-fakekey is still there because I didn't think to remove it. I will do so in the rebuild.
The instructions say to use
deb http://deb.devuan.org/devuan beowulf-proposed-updates main
but I used
deb http://deb.devuan.org/merged beowulf-proposed-updates main
which explains why I got more than our own forked packages.
I made some preliminary desktop-live isos with the updates. Please test.
https://get.refracta.org/files/experime … p-live.iso
https://get.refracta.org/files/experime … p-live.iso
sha256sums:
bf477a3c0dc27866509407fde670d8fa0b903296effef7f67c2222a48fd9eb2a devuan_beowulf_3.1.0_2020-11-30_amd64_desktop-live.iso
6b5a47918d983850500829d008ea0b96daba8b2fae45f26456b28a4fedba926f devuan_beowulf_3.1.0_2020-11-30_i386_desktop-live.iso
Message copied from dng mailing list:
The Devuan Developers are preparing for a beowulf point release (3.1). It would be very helpful to have the new versions of packages tested more widely. If you feel able to help with that and are prepared to debug any breakage with us, please
- add beowulf-proposed-updates to apt sources.list:
deb http://deb.devuan.org/devuan beowulf-proposed-updates main
Run:
apt update apt upgrade
beowulf-proposed-updates contains packages built from the following updated source versions.
base-files | 10.3+devuan3.5
choose-init | 0.3
cryptsetup-modified-functions | 19.09.02+devuan1
dbus | 1.12.20-0+deb10u1+devuan1
eudev | 3.2.9-8~beowulf1
init-system-helpers | 1.56+nmu1+devuan3
lightdm | 1.26.0-4+devuan1
refractainstaller-base | 9.5.6
refractainstaller-gui | 9.5.6
tomcat9 | 9.0.31-1~deb10u2+devuan1
udev | 1:3.2.9+devuan4Depending on your setup, you will get some, but not necessarily all of those.
If you encounter problems, please use reportbug to send a report to Devuan BTS.
Note: If you do it wrong like I did, you may also get some updates from debian package we do not fork. (See later post for explanation.) One example is Thunderbird. I wish I'd kept that one back. - fsmithred
Who are the developers of devuan in this forum?
I'm one. I make the live isos and maintain a few packages. Why do you ask?
Devuan does not boot with Secure Boot enabled on my system. Despite the presence of shim packages. But another systemd-free distro, antiX, boots. Without any shim packages at all. How can Devuan be made to boot the same way as antiX when Secure Boot is enabled ?
It works on my system. I have no idea how it works on MX, but in devuan, it works exactly the same way it works in debian, because we don't fork any of the packages necessary for secure boot. Make sure grub-efi-amd64-signed is installed. The bootloader directory in /boot/efi/EFI/ will be named 'debian'. You'll probably see that name in the boot menu, too. Rest assured, it's still really devuan.
With some troubleshooting, it might work on your system, too. Or maybe not. UEFI implementations vary widely and don't necessarily conform to any actual uefi standards.
The amd64 desktop-live iso already has the signed grub package and the shim packages.
I like seeing the individual core temps. Here's the line I'm using:
${execi 8 sensors | awk '/Core/ { printf substr($3,2,2)" " }'}
and the output looks like this:
CPU: 42 36 40 41
You can uninstall the non-pae kernel after you reboot into the new one.
Install linux-image-686-pae if you want the metapackage (so you get updated kernels with your regular package upgrades). Or else you could install linux-image-<version>-686-pae for a specific kernel.
An alternative to solving the problem would be to set up autofs for the nfs mounts. Then they'll mount automatically when you use them.