You are not logged in.
python3.8 is also in chimaera (our next testing when beowulf goes stable).
ceres=sid=unstable
Fix your address.
That's really weird. I've installed refractasnapshot in beowulf a few times. And isolinux is a real package.
$ apt-cache policy isolinux
isolinux:
Installed: 3:6.04~git20190206.bf6db5b4+dfsg1-1
Candidate: 3:6.04~git20190206.bf6db5b4+dfsg1-1
Version table:
*** 3:6.04~git20190206.bf6db5b4+dfsg1-1 500
500 http://deb.devuan.org/merged beowulf/main amd64 Packages
100 /var/lib/dpkg/statusMake sure you have all three lines in /etc/apt/sources.list and run 'apt update'
deb http://deb.devuan.org/merged beowulf main
deb http://deb.devuan.org/merged beowulf-updates main
deb http://deb.devuan.org/merged beowulf-security mainIf that isn't the problem, try installing syslinux and isolinux first, then install refractasnapshot.
If there was more to the refractasnapshot message, I'd like to see it. The syslinux dependency is as follows:
syslinux (< 3:6.03) | syslinux (>= 3:6.03), syslinux (< 3:6.03) | isolinux (>= 3:6.03)It's been like that for a few years. (Translation: syslinux older than 6.03, which included isolinux, or both syslinux and isolinux at least version 6.03)
The non-pae kernel is default for those with old machines. The linux-headers package is in the iso, but it does not get installed by default. That's standard for debian and consequently for devuan.
You probably need to remove or purge the pavucontrol package to get rid of the .desktop file.
I burned the 3/25 iso to dvd, booted and got the udev warning. Pressing alt-F2 does nothing. Really nothing. I can't change to another tty. Pressinc ctrl-c seems to stop the warnings.
On another machine, I booted from a usb that has a regular install from a netinstall iso on it. When I got to the desktop, the keyboard was not working. Unplug/replug the keyboard fixed it.
Update: boot dvd on laptop, keyboard doesn't work, trackpad and trackpoint don't work. Can't unplug them.
You probably need to change a symlink or two - the one for /usr/bin/python and /usr/bin/python3 would be my best guess.
Here's what I have in ascii:
$ ls -l /usr/bin/python*
lrwxrwxrwx 1 root root 9 Jan 24 2017 /usr/bin/python -> python2.7
lrwxrwxrwx 1 root root 9 Jan 24 2017 /usr/bin/python2 -> python2.7
-rwxr-xr-x 1 root root 3779512 Sep 26 2018 /usr/bin/python2.7
lrwxrwxrwx 1 root root 9 Jan 20 2017 /usr/bin/python3 -> python3.5
-rwxr-xr-x 1 root root 4751184 Sep 27 2018 /usr/bin/python3.5
-rwxr-xr-x 1 root root 4751184 Sep 27 2018 /usr/bin/python3.5m
lrwxrwxrwx 1 root root 10 Jan 20 2017 /usr/bin/python3m -> python3.5mIt is safer to download the packages and then install them. Do not add debian repos to sources.list or you might break your system.
Fri Mar 27 00:35:43 2020: WARNING: Device /dev/sda not initialized in udev database even after waiting 10000000 microseconds.
Fri Mar 27 00:35:54 2020: WARNING: Device /dev/sda1 not initialized in udev database even after waiting 10000000 microseconds.
Fri Mar 27 00:36:04 2020: WARNING: Device /dev/sda2 not initialized in udev database even after waiting 10000000 microseconds.
I've been informed that when you get these repeating messages, you can make them stop by switching to tty2 and then back to tty1.
Press
alt-F2 and then alt-F1
fsmithred wrote:snip
apt purge pulseaudio avahi-daemon apt autoremoveis easy.
Hi
Won't that break wireless printing setup that uses avahi?
Maybe. If you're using avahi, you shouldn't remove it. Same goes for pulseaudio.
It's normal for everything to be upgraded when you dist-upgrade from one major release to the next. It's also normal for there to be some new packages. That happens because package dependencies or priorities sometime change, or a source package that creates several binaries might get split up differently, and you'll get new names. (e.g. cryptsetup-run is a new one)
You should update again after installing a new keyring. I didn't think it worked without doing that.
Thanks. It does help to know what won't fix it.
I made another desktop-live iso with changes that I hope will address the udev delays. If anyone who was getting messages like the one below could test the new iso, it would be a big help. Thanks.
"device /dev/sd<x> not available in udev database even after waiting for 1000000 microseconds.<another timeout>"
https://get.refracta.org/files/experime … p-live.iso
sha256sum
822ed7c7d3c456e60ba4041e8b2d43891c6853739b5fdcb16527eb041dbfe21e devuan_beowulf_3.0.0_beta_2020-03-25_amd64_desktop-live.iso
There's a ppc64el mini.iso for beowulf.
https://pkgmaster.devuan.org/devuan/dis … s/netboot/
You should be able to boot the dvd, go into rescue mode, get a network connection and install grub-efi-amd64. You don't need the -signed version unless you're using secure boot.
All the installation media (including desktop-live) boot with grub on uefi and boot with isolinux on bios. If you can't tell the difference by looking at them, you can test:
Press TAB to edit the boot command in isolinux.
Press e to edit the boot command in grub.
Press ESC to return to the boot menu - this one is the same for both.
If you're already booted into the system, check to see if /sys/firmware/efi exists. If it does, you booted in uefi mode.
Someone mentioned that grub-efi-amd64 is missing. I think that was on the netinstall iso. I'm downloading the dvd iso now to check it.
Did you install with or without a network mirror?
Gparted leaves 1MB free at the beginning by default. If that's not there, it could be the reason for grub failing. Open gparted in the live session to check that it's there.
The log is in the user's home directory on the hard disk.
mount /dev/sda3 /mnt
less /mnt/devuan/refractainstaller.logI don't know anything about zfs, but I can answer a few of your questions. I did ask someone who uses zfs to take a look at this thread, and he suggests using partitions instead of whole disk for zfs. There is no longer a performance hit for using partitions.
/home separate from the OS partition is a good idea for several reasons. You are less likely to fill up '/' if you keep your user's files separate. It can also make reinstall easier.
swapfile works fine in devuan.
I use the following to make a 256MiB swapfile:
dd if=/dev/zero of=/path/to/swapfile bs=1024 count=262144
mkswap /path/to/swapfileChange the count if you want a bigger swapfile. Add it to fstab to use it.
Swap is not necessary. You can boot and run the system without it as long as you have enough RAM. (You obviously do have enough.)
I recommend using a separate /boot partition. In ascii, it's possible to have the /boot directory as part of an encrypted root partition, but that doesn't work in beowulf. (Maybe it will by the time you want to upgrade, but that's a guess.)
Note: the /boot partition is not the same as the efi partition.
I've never used parted to make gpt partitions, but I think it should work. Gparted should also work. I usually do it with gdisk.
The desktop-live iso won't give you what you want. It installs a full XFCE desktop. Use one of the Installer isos. Netinstall iso, CD-1 or DVD will work.
Is there something unusual about your setup? How did you partition the drive? Gparted? Something else? Is there 1MB free space before the first partition? Does it use gpt partition table? What's in the log around the grub-install command?
Putting it in ~/.bash_profile didn't work for me. I suppose I have to log out of my desktop session and restart it. Putting it in ~/.bashrc works every time I open a new terminal on the desktop. If I put it in /root/.bashrc, it works every time I do 'su' or 'su -' in a terminal.
It sounds like you made the right choices for a legacy bios system with msdos partition table. The right place to put the bootloader is /dev/sda, so it should have worked.
What error message did you get? You can check the installation log by booting the live media, mounting the home partition and getting refractainstaller.log from the user's home. The grub section should be about three-quarters of the way down the log. Look for an error message about grub.
The other way to do the install would be to install the grub-pc package before running refractainstaller, but do not let it install the bootloader at that time. Run dpkg -i /grub-pc*.deb
After installing the package, you can install the system to hard disk, and you will be given a choice of where to put the bootloader. Choose MBR of /dev/sda. When the installer gets to the grub section, you will see a button that says 'Install bootloader' in the same place where you saw 'Copy files' the first time.
After doing some test runs, I think I know why you got a zero byte iso - if you use any of the build tasks other than "1. Create a snapshot" you have to edit the config file to set save_work=yes. Otherwise, there's nothing to re-squash or re-pack into an iso file.
These two lines from the log suggest that you stopped it in the middle of a previous run, and /tmp/extracted didn't get deleted. I was able to reproduce these errors, but I did not get any input/output errors, and I did get a normal sized iso.
mkdir: cannot create directory ‘/tmp/extracted’: File exists
cpio: kernel/x86/microcode/AuthenticAMD.bin not created: newer or same age version exists
62 blocks(Note to self: add /tmp/extracted to the cleanup function.)
I don't see any problems with the hard disk.
Run the head command again, but try '-n 2000'
See if you can get a few lines beyond the point where xorriso runs. (about 20 lines past it should be enough) Look for something like this to find it:
xorriso : UPDATE : 0.23% done
xorriso : UPDATE : 3.28% done
xorriso : UPDATE : 11.45% done
xorriso : UPDATE : 19.93% done, estimate finish Wed Dec 25 22:11:41 2019
xorriso : UPDATE : 28.85% done, estimate finish Wed Dec 25 22:11:40 2019
xorriso : UPDATE : 34.11% done, estimate finish Wed Dec 25 22:11:41 2019
xorriso : UPDATE : 36.97% done, estimate finish Wed Dec 25 22:11:42 2019
xorriso : UPDATE : 40.51% done, estimate finish Wed Dec 25 22:11:44 2019Check your hard disk health.
As root:
smartctl -a /dev/sda
(you may need to install smartmontools)
I have no idea how you managed to get an 18GB log file. Try this...
head -n 1000 /var/log/refractasnapshot.log > beginning.txt
tail -n 1000 /var/log/refractasnapshot.log > end.txtThat will put the first 1000 lines and last 1000 lines into text files.
Then try opening them with a text editor and see what's there.
A video of your file manager showing /var/log is not helpful.
Run
nc termbin.com 9999 < /var/log/refractainstaller.log
and then give me the link.
or send the log to me in email. (my screen name at gmail dot com)
That site isn't working for me. If I turn off noscript and allow all cookies, I see the name of a video file. I don't see a text file.