You are not logged in.
Why don’t you tell me?
"I'm sorry, Dave. I'm afraid I can't do that."
I read through this thread quickly and may have missed something, but it sounds like you're trying to make changes in a running live session. Or maybe you're surgically modifying the iso file and then booting the result. Those ways sound difficult to me. Easier is to install devuan into a spare partition or into a virtual machine, configure it the way you want, and then run refractasnapshot.
To boot the live isos without autologin, add the word noautologin to the boot command.
To boot the live isos without sudo, add nocomponents=sudo to the boot command.
Read man live-config for more.
You'll also need to recompile the kernel to support aufs. (or use one that does support it)
Maybe I'm dense, but I don't understand what you're trying to do.
I was wrong. That package is gone and consolekit was rebuilt without the dep on libcgmanager0.
If you refuse aptitude's first suggestion, it should give you other possible solutions.
Edit: if that doesn't work, whatever is wrong will get fixed tomorrow or so.
This post intentionally left blank.
After update, it's gone.
$ apt policy libcgmanager0
libcgmanager0:
Installed: (none)
Candidate: (none)
Look:
empty@P14s:~ $ pgrep -a dbus 1|empty@P14s:~ $
^ This is not possible with the other init systems.
I guess I'm not understanding what you're saying here. It is possible to run sysvinit without dbus. This is in a daedalus live-iso made last May.
user@refracta-nodbus:~$ pgrep -a dbus
user@refracta-nodbus:~$
user@refracta-nodbus:~$ dpkg -l |grep sysvinit
ii live-config-sysvinit 11.0.3+devuan2 all Live System Configuration Components (sysvinit backend)
ii sysvinit-core 3.03-1devuan1 amd64 System-V-like init
ii sysvinit-utils 3.03-1devuan1 amd64 System-V-like utilities
1. During installation, formatting is mandatory for the "/" partition and is not allowed without a direct user selection for the /home partition.
I don't understand what you are saying here, but it sounds wrong.
It is not mandatory for the installer to format the chosen partition(s) but it is mandatory for them to have a filesystem if you want them to contain files, and formatting is the default setting.
You can partition and format before running the installer and tell the installer not to format. That's a checkbox in the options menu of the graphical installer and it's a config file setting in the cli installer.
You have the choice to install the entire system to one partition, or you could optionally have separate partitions for /boot and/or /home.
The installer doesn't know what to do with your old home or the user configs it contains. It's up to you to figure out any conflicts caused by mismatched or missing config files caused by sharing a home between two different operating systems.
deepforest, I would like to see the installation log (refractainstaller.log) that should be in the user's home directory. You can post it here or paste.debian.net or email it to me through the forum. Thanks.
It shouldn't matter that your partition was mounted, because you should not be selecting that pre-existing home partition during the installation. Please be aware that the default action is to format any partitions you select. If you select a partition with data you want to keep, you will lose it.
Camtaf's diagnosis is probably correct. I've sometimes seen remnant /target_home and /target_boot directories that didn't get cleaned up correctly, but they are just mountpoints and are always empty on reboot.
Also, that first option in the live installer, "Create new, separate /home partition" is not the same thing as "Re-use an existing /home partition that already has files on it." That latter option doesn't exist. If you want to re-use an existing home, just let the installer put /home in the root partition and edit your fstab afterward. I recommend keeping the user configs from the live install in case you need to use them. Just rename /home to /home.live or something like that.
I built live-boot packages with the fix and put them here for people to use until debian builds them. I really hope we don't have to fork live-boot for this.
https://sourceforge.net/projects/refracta/files/tools/
live-boot, live-boot-initramfs-tools and live-boot doc all from 2022-12-16.
Fluxbox-1.4 is not in sid/ceres yet, so I guess you'd have to compile it yourself. That might be easy or not. I don't know. It may not make it into sid in time for bookworm/daedalus.
You might have older deb packages in /var/cache/apt/archives but if they're from beowulf, they're a lot less likely to work than if they are previous versions from chimaera.
I tested on a T450s, running amd64.
If I use lxrandr in xfce to change the resolution as described in my previous post, it does not cause the problem with firefox. It only happens in fluxbox.
Is this an issue with client-side decorations? If so, make sure gtk3-nocsd is installed.
For the live isos, root password is toor, user name is devuan and user's password is devuan.
Edit: It's not a CSD problem. I just got the same behavior. I added fluxbox, logged out and into fluxbox, changed the display with lxrandr from 1600x900 to 1360x768. Firefox lost its window border and controls. I changed back to 1600x900 using lxrandr and the window borders did not return.
I'm back in xfce now and everything is normal.
I just tested this, and yes, there's a delay on reboot if the nfs server goes down while the share is mounted. The delay was less than 10 seconds on an old thinkpad with an i5 cpu. To avoid the delay before attempting reboot, you can unmount the share with
umount -l <nfs-share-mountpoint>
There might be a way to shorten the timeout on the delay, but I don't know where that would be.
The version of live-boot in daedalus/ceres is still broken. Use the deb packages for live-boot and live-boot-initramfs-tools in the same sourceforge directory I linked in my last post.
Make sure you dd the iso to the whole device, not to a partition. ( to /dev/sdb and not to /dev/sdb1 for example.)
Hello
I wish all people a merry new year 2023!
Gnuinos for i686: the new release of refracta snapshot causes that the USB stick can't be found to start linux starting the snapshot from USB.
can someone having a good working version upload a snapshot INCLUDING refracta tools?
I don't understand what problem you are having or what you are asking for. If you want the previous version of refracasnapshot or any older version, they are here: https://sourceforge.net/projects/refracta/files/tools
What version of gnuinos/devuan are you using and how did you prepare the usb stick?
Why don't I have /var/log/messages anymore,
not because I have noatime in fstab, and rsync installed.
I hope it's not a new feature.
tail -f /var/log/messages is handy.
I have a minimal console install, I'm being extremely careful, I havn't broken anything, I do that in a RefractaSS.
You might be running into this problem:
https://dev1galaxy.org/viewtopic.php?id=5096
https://sourceforge.net/projects/refracta/files/tools/
I just uploaded fixed live-boot deb packages I made for myself in October. These have a newer version number than what's in the repo, so they will replace the broken live-boot packages. I used these to make the daedalus live test isos.
Bug reports have been submitted for the live-boot-initramfs-tools problem.
https://bugs.debian.org/cgi-bin/bugrepo … ug=1010951
The fix is in git.
https://salsa.debian.org/live-team/live … 8678106523
Still waiting for the package to be built with the fix. I really don't want to fork live-boot for this.
Several years ago I discovered that the software that cycles through the USB ports looking for the non-free device drivers on a usb stick, only looks at USB-a and USB-b ports. It does not look beyond this to, say, USB-c (where I initially had the usb stick plugged in)... the code simply cycles back around and ask that a usb drive be inserted with the firmware on it
What software are you using that asks you to insert a usb with firmware? The only thing I know that asks that is the debian/devuan installer that's on the installer isos, not in the devuan live isos or any Refracta isos. That question comes up early in the installer and should usually be ignored. In most cases, the firmware will be installed automatically unless you do an expert install and tell it not to use non-free software. The main exceptions to this are certain broadcom devices that require an internet connection to get the wireless firmware - that poses a serious problem if someone is trying to install and doesn't have an ethernet connection.
If my guess is right, and you're talking about that early question in the debian/devuan installer, then I think the code is probably in the udeb package that asks for the firmware. I don't know that installer well enough to know which udeb that is.
If you install the firmware package while running the live iso on usb, it will be in the system memory only, so it won't survive a reboot. If you install the firmware then install the system to hard drive, the firmware will be in the installed system. It's also possible to install the system first, reboot into the installed system and then install the firmware package.
If you want a live-usb with your wifi driver, you need to set up a persistent volume (rw instead of ro) so your changes are saved. I use refracta2usb for that, but there are other ways.
https://sourceforge.net/projects/refracta/files/tools/refracta2usb-2.4.3.deb
Refracta xfce isos and the no-X isos do not have non-free firmware installed. There are firmware packages in the user's home directory that you can install with dpkg if you don't have a network connection. dpkg -i /home/user/firmware-iwlwifi*.deb
If you do have a network connection, you can add 'contrib' and 'non-free' to the deb lines in /etc/apt/sources.list then run apt update and apt install firmware-iwlwifi.
If you have to install without network, the desktop dvd (3G) is probably the easiest to deal with. But if the live iso worked, then the right firmware package should also be in the installer isos. What intel hardware is not recognized, and are you sure it's not recognized?
If you stopped at the very beginning because the installer told you that you needed to provide the drivers on a usb stick, then run the installer again and ignore that question and proceed. Hardly anyone needs to do that. (a few broadcom chips)