The officially official Devuan Forum!

You are not logged in.

#1126 Devuan Derivatives » Refracta no-X chimaera pre-beta isos » 2021-01-02 17:56:43

fsmithred
Replies: 0

Pre-Beta No-X isos for Refracta-11 (Chimaera)
https://get.refracta.org/files/testing/

I decided it's time to start making chimaera isos, so here are the preliminary refracta11 isos. They have all the usual command-line utilities and tweaks found in Refracta. No desktop (yet).

Full package list: https://get.refracta.org/files/testing/ … e_list.txt

You probably won't need these:
Login: user
Password: user
root password: root

Happy New Year!

Edit: Oh yeah, wicd is gone. For now, it's replaced with ceni. Run 'Ceni' (with the upper-case C) to set up network.

#1127 Re: Desktop and Multimedia » [Ceres] Xfce 4.16 » 2020-12-30 13:30:55

In English, the name changed from Preferred Applications to Default Applications, and in the Settings manager, it got moved from the Personal section to the System section.

I had to upgrade my ceres to get 4.16 and xfce4-settings was held back to 4.14. At that point, Preferred applications was missing, but I don't know if Default applications was there. I upgraded xfce4-settings to 4.16 and restarted the destkop before I noticed it.

#1128 Re: Devuan Derivatives » No networking on Refracta OS and then Refracta Snapshot issue on Mint » 2020-12-29 15:36:58

1. Try the iso with the backports kernel.

2. Show me the log.  /var/log/refractasnapshot.log  (email or paste.debian.net)
If you run the cli script, start it with the -d option (--debug) so that there's some useful information in the log. If you use the gui script, it will do that automatically.

#1129 Re: Devuan » Wifi and Ethernet not working in Devuan on newer AMD system » 2020-12-29 01:04:01

Here's one with backports kernel (kinda old one now) and wireless firmware already installed for testing new hardware. It's not the full mix - openbox, lxpanel, not a lot else.
https://get.refracta.org/files/experime … 5_1323.iso

Update: Here's a newer one with 5.9 kernel.
https://get.refracta.org/files/experime … 9_0205.iso

#1130 Re: Off-topic » dd command inside script. » 2020-12-28 18:03:32

It looks like it worked. The previous error is gone. Maybe loop1 is left from before? I think you can just delete it manually.

#1131 Re: Off-topic » dd command inside script. » 2020-12-28 14:56:13

You got this output for the line that says losetup ${LOOPDEV} $img but there's nothing for $LOOPDEV in the output. "No such device." The error also shows up in the first lines of the output where it shows that cat failed and LOOPDEV is empty.

+ losetup test.img
losetup: test.img: failed to use device: No such device

I think you need to define LOOPDEV after you run 'losetup -f'.

crypt_create () {
        losetup -f > /tmp/nextloop
        LOOPDEV=$(cat /tmp/nextloop)
        losetup ${LOOPDEV} $img
        cryptsetup luksFormat $img
        cryptsetup open $img cryptfs
        mkfs.ext4 /dev/mapper/cryptfs
}

#1132 Re: Off-topic » dd command inside script. » 2020-12-27 23:19:14

If you somehow end up with more than one loop device, you might use something like this:

losetup -f > /tmp/nextloop
LOOPDEV=$(cat /tmp/nextloop)

losetup ${LOOPDEV} ${LOOP_FILENAME}

That's taken from refracta2usb which can make an encrypted loopback filesystem for live-usb persistence.

#1133 Re: Off-topic » dd command inside script. » 2020-12-27 12:55:27

dd if=/dev/urandom of=$1 bs=$2 count=$3 iflag=fullblock value.img 100M 1

Thinking about how that will expand is making my head hurt. Wouldn't $1 = 'if=/dev/urandom'? And so on...

I like to redefine positional paramaters at the beginning of the script to give them meaningful names and to make sure I know what they really are.

outfile="$1"
blocksize="$2"
blockcount="$3"

dd if=/dev/urandom of=$outfile bs=$blocksize count=$blockcount iflag=fullblock

Then call the script with

myscript.sh value.img 100M 1

#1134 Re: News & Announcements » Testing for beowulf 3.1 point release » 2020-12-13 17:27:23

Andre,

Thanks for testing and reporting. What trouble did you have with grub? I've installed with and without a separate /boot partition. Other than installing the bootloader twice, it works correctly for me. Did you look at the error log? It should be in the user's home.

FYI: What we call "installer isos" refers to the isos with the debian(devuan)-installer. Not the live isos. Although either can be used to install devuan, as you know.

Bug#438 was fixed. You got the old lightdm because the fix is still in beowulf-proposed-updates, which is not in sources.list by default. We're working on another bug in lightdm, and it will get moved to the main beowulf repo when that one is fixed. Check this before you install the newer version:
https://bugs.devuan.org/cgi/bugreport.cgi?bug=529

I've been using that newer version since the package was put in the repo, and I didn't notice any problem until I tried to connect with vnc.

fsmithred

#1135 Re: Installation » Base install recent migration from ubuntu some concerns » 2020-12-13 12:00:47

You only need one line. There's no chimaera-updates or chimaera-security until it goes stable. Leave those commented out for now. Also comment the third-party repo for the upgrade. The deb-src lines are only needed if you want to rebuild source packages.

I did an upgrade from beowulf to chimaera back in July. There were a few tricky spots. I'll leave you my notes. You will probably run into some different tricky spots, so do not follow these directions exactly. They are only here as an example. Also, search this forum for other accounts of upgrading to chimaera.

Edit sources.list
apt update
apt upgrade
Took new versions of config files when asked.

apt full-upgrade fails d/t libc6-dev and libgcc-8-dev conflicts.
both before and after reboot into new kernel

apt remove build-essential
apt autoremove
apt remove libc6-dev
apt full-upgrade
apt autoremove

You may need to remove libgcc1 to get the next command to work.
apt install build-essential linux-headers-`uname -r` failed for same libgcc conflict.

apt install libgcc-8-dev=8.4.0-4
apt autoremove
apt full-upgrade --> sshfs has been kept back
apt install sshfs=3.7.0+repack-1

#1136 Re: Installation » Base install recent migration from ubuntu some concerns » 2020-12-12 20:46:08

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.

#1137 Re: Other Issues » at program » 2020-12-12 18:34:01

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"

#1138 Re: Other Issues » at program » 2020-12-12 14:38:13

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.

#1139 Re: Installation » Iwl4965 and HPdv6000 » 2020-12-11 20:57:31

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

#1140 Re: Installation » Iwl4965 and HPdv6000 » 2020-12-11 18:09:00

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.

#1141 Re: Other Issues » beowulf repositry update problem [SOLVED] » 2020-12-10 14:20:43

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

#1142 Re: Installation » Separate, non-encrypted /boot on BIOS/MBR » 2020-12-10 11:50:02

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

#1143 Re: Installation » Separate, non-encrypted /boot on BIOS/MBR » 2020-12-08 18:18:03

Head_on_a_Stick wrote:
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

#1144 Re: Installation » Separate, non-encrypted /boot on BIOS/MBR » 2020-12-08 14:45:09

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.

#1145 Re: Installation » Separate, non-encrypted /boot on BIOS/MBR » 2020-12-08 00:58:56

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

#1146 Re: News & Announcements » Testing for beowulf 3.1 point release » 2020-12-07 13:48:48

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.

#1147 Re: Installation » Separate, non-encrypted /boot on BIOS/MBR » 2020-12-07 13:40:10

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

#1148 Re: News & Announcements » Testing for beowulf 3.1 point release » 2020-12-07 13:31:00

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.

#1149 Re: News & Announcements » Testing for beowulf 3.1 point release » 2020-12-06 19:33:03

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.

#1150 Re: News & Announcements » Testing for beowulf 3.1 point release » 2020-12-06 18:22:10

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
#

Board footer

Forum Software