You are not logged in.
I'm instinctively concerned about loading my mounted and running system in a vm as a 'raw disk' even if only to access the boot menu. However:
Thanks to @tyder and @fsmithred, I finally worked out how to get persistence in qemu.
I tried a variation of fsmithred's usb method, having already a 'test' usb with grub(2) as bootloader. I shrunk it's fat32 partition, made a ext2 in the space, put 3x selectable persistence files there. Works, great potential for testing new stuff.
Booting as usb 'raw disk', in qemu, the unmounted usb device.
(convenience) 'devuan.iso' is 6.1.1 . One cmdline edit to select a different persistence-label=*
It's grub.cfg:
menuentry "Devuan Persistence" {
set isofile="(hd0,1)/devuan/devuan.iso"
loopback loop $isofile
linux (loop)/live/vmlinuz boot=live findiso=/devuan/devuan.iso username=devuan nottyautologin apparmor=0 keyboard-layouts=gb noeject persistence persistence-path=/devuan-pers persistence-label=pers0
initrd (loop)/live/initrd.img
}I got some fsck errors on the persistence partition later but no clue yet to the cause. Maybe ailing disk. But this one is expendable and at least my running system is not involved.
This is interesting, now I can investigate the live-config process more closely.
I was slow to switch from grub-legacy because grub2 was released only half baked. But grub2 later improved, has it's own basic cli, can loop mount ISO's and works well for a boot usb.
I see no evidence, so far, of a systemd issue here, Debian's live-boot/live-config support systemd but do not demand it.
btw @tyder: Why do you need to run kvm/qemu as root?
For the record:
Most people around here may not know the term 'PMI' (poor man's install). Far as I'm aware it originated from Knoppix. AntiX call it 'frugal install'. Klaus Knopper was the trailblazer of 'live' systems early 2000's whose work preceeded both Ubuntu's Casper and (later forked and evolved from casper) Debian's live-boot. Knoppix was where my journey into live ISO's began.
'PMI' simply means booting a live iso located on disk with a persistence overlay. Either directly or from the extracted squashfs, vmlinuz and initrd.
Well done @tyder, you got most of it if not quite all:
When that user is in place, the Debian default 'user' is harmless. May be added and removed without problems, it seems. The noautologin directive works.
And it is _not_ necessary to use the username=devuan parameter afterwards
When a different username is configured, the Debian default 'user' does not even exist, unless you created it manually.
The noautologin parameter is unavailable after first boot if using persistence because live-config is disabled.
The username=* parameter is unavailable after first boot if using persistence for the same reason.
BTW 'keyboard-layouts' is also unavailable for the same reason.
The persistence manual is actually in live-boot not live-config ..
/etc/sudoers.d/live does not exist in the squashfs. It is written dynamically on first boot by /lib/live/config/0040-sudoers .
I haven't done any modifications
@tyder, yes you have, at least inadvertantly. You have booted with incorrect cmdline parameters (omitting 'username=devuan') while using persistence.
If you boot with a new, clean persistence volume using the parameters as configured in the ISO's boot menus:
boot=live username=devuan nottyautologin apparmor=0username 'devuan' will be referenced in sudoers, will autologin.. and the system will work normally.
As I understand (and have observed) how persistence affects live-config:
Each live-config script writes a 'state' file to /var/lib/live/config/ . Each script is configured to exit doing nothing if it's own state file exists, meaning it has already run OR another script has written it's state file in order to disable it (example: slim writes a state file for xinit so xinit's script won't run and cause a conflict)
Therefore, live-config scripts should run only on the first persistence boot. They are then surely disabled because their state files remain in the RW overlay. They are certainly not in the squashfs.
This must also include 'noautologin' parameter, which the relevant live-config display manager script (slim) reads. But only once.
If I got that wrong, someone please enlighten me..
I see no mention in live-config manual about the need to specify a preconfigured live user if that live user is other than 'user', although I know it to be true from experience. Perhaps a documentation bug but no more than. A preconfigured user is valid, script 0030-user-setup checks and exits if found.
If future Devuan live images set the username in /etc/live/config.conf(.d/) of the squashfs there would be no need to use the cmdline.
the default user is not created. Without any user to serve, the display does not come up
But the cmdline you posted does not contain 'username=devuan' ..
Therefore live-config script /lib/live/config/0130-slim was not told to autologin the already system-configured user 'devuan'!
This is verifiable. Boot without 'username=devuan' and with 'sysv-rc=slim' (disable slim, show a shell login prompt) Autologin is then irrelevant.
cat /etc/slim.conf | lessshows that 'default user' set to 'user' (debian-live standard default) and autologin is set to 'default user'. There is no user 'user' on this system.
Here:
:~$ inxi -G
Graphics:
Device-1: Intel Core Processor Integrated Graphics driver: i915 v: kernel
Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: modesetting
unloaded: fbdev,vesa dri: crocus gpu: i915 resolution: 1366x768~60Hz
API: OpenGL v: 2.1 Mesa 22.3.6 renderer: Mesa Intel HD Graphics (ILK)What is yours?
Old toshiba laptop here, i3, 8gb ram.. 'devuan.iso' is a convenience relative symlink to devuan_excalibur_6.1.1_amd64_desktop-live.iso ..
Works:
qemu-system-x86_64 -enable-kvm -m 2048 devuan.iso(efi basic options) Boots to a black screen only. Lots of whirring fan noise:
qemu-system-x86_64 -enable-kvm -m 2048 -bios /usr/share/ovmf/OVMF.fd devuan.isoWorks:
$ qemu-system-x86_64 -enable-kvm -m 2048 -bios /usr/share/ovmf/OVMF.fd -boot d -cdrom devuan.isoWorks even better:
/usr/bin/qemu-system-x86_64 -k en-gb -machine accel=kvm -m 1924 -boot d -cdrom devuan.iso -bios /usr/share/ovmf/OVMF.fd -boot once=d,menu=off -nic user,hostfwd=tcp::8888-:22 -rtc base=localtime -smp cores=2,threads=1,sockets=1 -display gtk -name "devuan.iso"Those options are lifted from my own script, created because I never remember all the options and just want to drop a ISO in a directory and run it. They evolved over time, some maybe irrelevant, redundant or long forgotten what they even do.
Used TDE here since the beginning, ~2010. Main OS then was Debian Unstable (sidux) with KDE 3.5. The end for me with KDE and consequentially running testing/unstable on a production machine, was a routine dist-upgrade leaving a semi-functional DE with no way back, i.e. the premature release of KDE4.
Maintaining testing/unstable is nothing compared to such (yes, by design) nasty surprises.
@samhain, thanks for your contributions, I appreciate what you do and always give your latest ISO a spin.
I prefer to start with a full installation and then work my way back. Just mark all packages installed by tde-trinity as "manual". "tdm-trinity" should be pulled in automatically.
My approach is the minimalist opposite: Disable 'recommends', install tdebase-trinity and add what you want if/when needed. Wallpapers, games. stuff you will never use or prefer alternatives.. Why install in the first place?
Also, IMO, if unwanted stuff is apt-marked manual it gets difficult to track down and thin down.
Here is my basic, minimal TDE install list to feed apt with (adapt to suit). Other TDE essentials and deps (not all the cruft) are pulled automatically. I use this for the ExeGNU live images and (done usually from bootstrap) 'real' installations. Note, tdm is in the list, nothing else pulls it in.
tdebase-trinity
amarok-trinity
ark-trinity
gwenview-i18n-trinity
gwenview-trinity
k3b-i18n-trinity
k3b-trinity
kaffeine-trinity
kamera-trinity
karm-trinity
kate-plugins-trinity
kcalc-trinity
kcoloredit-trinity
kcron-trinity
kdf-trinity
kdiff3-trinity
kdirstat-trinity
kexi-trinity
kgamma-trinity
kget-trinity
kghostview-trinity
kicker-applets-trinity
kipi-plugins-trinity
kmix-trinity
knemo-trinity
knotes-trinity
konq-plugins-trinity
konversation-trinity
kpdf-trinity
kregexpeditor-trinity
ksnapshot-trinity
ksplash-engine-moodin-trinity
kspread-trinity
ksvg-trinity
ksysguardd-trinity
ktorrent-trinity
kuser-trinity
kword-data-trinity
kword-trinity
network-manager-tde
soundkonverter-trinity
tde-i18n-engb-trinity
tde-i18n-es-trinity
tde-style-qtcurve-trinity
tdeaddons-tdefile-plugins-trinity
tdeartwork-misc-trinity
tdeartwork-style-trinity
tdeartwork-theme-icon-trinity
tdeartwork-theme-window-trinity
tdebase-runtime-data-common-trinity
tdegraphics-tdefile-plugins-trinity
tdeio-locate-trinity
tdemultimedia-tdeio-plugins-trinity
tdepowersave-trinity
tdescreensaver-trinity
tdm-trinity
twin-style-crystal-trinityOpen /etc/default/grub in a root (or use sudo) text editor, e.g. nano and look ~line 17. Remove the "#" from this line:
#GRUB_DISABLE_OS_PROBER=falsethen (in a root terminal):
update-grubSame result for ceres. However.. I can connect (ceres) to other wireless networks! So my issue must be router configs not wicd itself. I can investigate that later.
Thanks metala! Confirmed working here for excalibur and ceres.
I would still like to know how wicd resource usage (size, deps, ram, cpu) compares to network-manager..
I did a bios install with grub-efi-amd64 installed and I rebooted to a grub rescue prompt
Maybe grub-pc-bin was absent? It doesn't conflict.
I'm confused about is grub. I changed one line in the bootloader module so that it would boot efi or bios, and I'm wondering how it does that. Is a network connection required for that to succeed? My iso has grub-efi-amd64 installed, but I did a bios install and it got grub-pc from somewhere. (either network or it found the deb package that I put in the root of the squashed filesystem)
Am I missing something, or are not all the required grub files in the grub2-common and grub*-bin packages (which can all co-exist on efi or bios systems)?
The currently-running laptop here is bios only.. grub-efi is a dummy, grub-pc is absent and I don't see why grub-efi-amd64 is of any use:
$ dpkg -l|grep grub
ii grub-common 2.06-13+deb12u1 amd64 GRand Unified Bootloader (common files)
ii grub-efi 2.06-13+deb12u1 amd64 GRand Unified Bootloader, version 2 (dummy package)
ii grub-efi-amd64 2.06-13+deb12u1 amd64 GRand Unified Bootloader, version 2 (EFI-AMD64 version)
ii grub-efi-amd64-bin 2.06-13+deb12u1 amd64 GRand Unified Bootloader, version 2 (EFI-AMD64 modules)
ii grub-efi-ia32-bin 2.06-13+deb12u1 amd64 GRand Unified Bootloader, version 2 (EFI-IA32 modules)
ii grub-pc-bin 2.06-13+deb12u1 amd64 GRand Unified Bootloader, version 2 (PC/BIOS modules)
ii grub2-common 2.06-13+deb12u1 amd64 GRand Unified Bootloader (common files for version 2)
$ dpkg -S /usr/sbin/grub-install
grub2-common: /usr/sbin/grub-install$ dpkg -S /usr/sbin/update-grub
grub2-common: /usr/sbin/update-grubGot a few "test" installs here.. wicd seems to work OK in excalibur. Not freia, it gets as far as 'connecting' 'obtaining ip address' then 'not connected' both in --tray and -curses. Same as root in -curses.
Double checked, of course, the key configs and restarted wicd (and the freia installation) numerous times.
I removed network-manager and installed the debs from chroot. There were some deps to install first (and apt-mark auto?):
python3-daemon
python3-lockfile
python3-dbus
python3-urwid
iwthen an order list to do dpkg -i:
python3-wicd_1.8.0~git20260213.19785e9f-1_all.deb
wicd-daemon_1.8.0~git20260213.19785e9f-1_all.deb
wicd-cli_1.8.0~git20260213.19785e9f-1_all.deb
wicd-curses_1.8.0~git20260213.19785e9f-1_all.deb
wicd-gtk_1.8.0~git20260213.19785e9f-1_all.deb
#meta:
#wicd_1.8.0~git20260213.19785e9f-1_all.debMaybe something required is missing in freia? I do have 'no-recommends' configured. Can try again in ceres later..
couldn't rule out the possibility the attacks are already known to the more advanced hackers, including those with government backing.
(quote from the linked article) hits the nail on the head for cloud-based or corporate-based solutions.
Keep it local.. a LUKS encrypted 'loopback' file is an option. Anyone got any mud on keepassxc?
ExeGNU and Refracta have similar resource usage. Trinity Desktop is not officially supported in Debian/Devuan, an issue for many although it has run well on Devuan for 10 years. Preference for style is a major factor.
Best option of course is a base debootstrap install and build what you want from there without "recommends" (that's how ExeGNU images are built).
Numerous lightweight options to choose from! But those live images give at least a preview of what is possible and are installable.
lxqt: Although qt-based it doesn't have the overheads of full-on kde plasma. One of many lxqt reviews:
https://itsfoss.gitlab.io/blog/lxqt-100 … ktop-ever/
i7 with 8GB ram? Definitely on my wishlist!
re browsers: The more marginal ones seem more prone to "fingerprinting". Using librewolf here currently (identifies as firefox but maybe a false sense of security).. just mind how many open tabs on a low-end machine.
$ apt-cache search firefox|grep "^firefox"
firefox-esr - Mozilla Firefox web browser - Extended Support Release (ESR)
firefox-esr-l10n-ach - Acoli language package for Firefox ESR
firefox-esr-l10n-af - Afrikaans language package for Firefox ESR
firefox-esr-l10n-all - All language packages for Firefox ESR (meta)
firefox-esr-l10n-an - Aragonese language package for Firefox ESR
firefox-esr-l10n-ar - Arabic language package for Firefox ESR
firefox-esr-l10n-ast - Asturian language package for Firefox ESR
firefox-esr-l10n-az - Azerbaijani language package for Firefox ESR
firefox-esr-l10n-be - Belarusian language package for Firefox ESR
firefox-esr-l10n-bg - Bulgarian language package for Firefox ESR
firefox-esr-l10n-bn - Bengali language package for Firefox ESR
firefox-esr-l10n-br - Breton language package for Firefox ESR
firefox-esr-l10n-bs - Bosnian language package for Firefox ESR
firefox-esr-l10n-ca - Catalan language package for Firefox ESR
firefox-esr-l10n-ca-valencia - Catalan (Valencia) language package for Firefox ESR
firefox-esr-l10n-cak - Kaqchikel language package for Firefox ESR
firefox-esr-l10n-cs - Czech language package for Firefox ESR
firefox-esr-l10n-cy - Welsh language package for Firefox ESR
firefox-esr-l10n-da - Danish language package for Firefox ESR
firefox-esr-l10n-de - German language package for Firefox ESR
firefox-esr-l10n-dsb - Lower Sorbian language package for Firefox ESR
firefox-esr-l10n-el - Modern Greek language package for Firefox ESR
firefox-esr-l10n-en-ca - English (Canada) language package for Firefox ESR
firefox-esr-l10n-en-gb - English (United Kingdom) language package for Firefox ESR
firefox-esr-l10n-eo - Esperanto language package for Firefox ESR
firefox-esr-l10n-es-ar - Spanish (Argentina) language package for Firefox ESR
firefox-esr-l10n-es-cl - Spanish (Chile) language package for Firefox ESR
firefox-esr-l10n-es-es - Spanish (Spain) language package for Firefox ESR
firefox-esr-l10n-es-mx - Spanish (Mexico) language package for Firefox ESR
firefox-esr-l10n-et - Estonian language package for Firefox ESR
firefox-esr-l10n-eu - Basque language package for Firefox ESR
firefox-esr-l10n-fa - Persian language package for Firefox ESR
firefox-esr-l10n-ff - Fulah language package for Firefox ESR
firefox-esr-l10n-fi - Finnish language package for Firefox ESR
firefox-esr-l10n-fr - French language package for Firefox ESR
firefox-esr-l10n-fur - Friulian language package for Firefox ESR
firefox-esr-l10n-fy-nl - Western Frisian (Netherlands) language package for Firefox ESR
firefox-esr-l10n-ga-ie - Irish (Ireland) language package for Firefox ESR
firefox-esr-l10n-gd - Scottish Gaelic language package for Firefox ESR
firefox-esr-l10n-gl - Galician language package for Firefox ESR
firefox-esr-l10n-gn - Guarani language package for Firefox ESR
firefox-esr-l10n-gu-in - Gujarati (India) language package for Firefox ESR
firefox-esr-l10n-he - Hebrew language package for Firefox ESR
firefox-esr-l10n-hi-in - Hindi (India) language package for Firefox ESR
firefox-esr-l10n-hr - Croatian language package for Firefox ESR
firefox-esr-l10n-hsb - Upper Sorbian language package for Firefox ESR
firefox-esr-l10n-hu - Hungarian language package for Firefox ESR
firefox-esr-l10n-hy-am - Armenian (Armenia) language package for Firefox ESR
firefox-esr-l10n-ia - Interlingua language package for Firefox ESR
firefox-esr-l10n-id - Indonesian language package for Firefox ESR
firefox-esr-l10n-is - Icelandic language package for Firefox ESR
firefox-esr-l10n-it - Italian language package for Firefox ESR
firefox-esr-l10n-ja - Japanese language package for Firefox ESR
firefox-esr-l10n-ka - Georgian language package for Firefox ESR
firefox-esr-l10n-kab - Kabyle language package for Firefox ESR
firefox-esr-l10n-kk - Kazakh language package for Firefox ESR
firefox-esr-l10n-km - Khmer language package for Firefox ESR
firefox-esr-l10n-kn - Kannada language package for Firefox ESR
firefox-esr-l10n-ko - Korean language package for Firefox ESR
firefox-esr-l10n-lij - Ligurian language package for Firefox ESR
firefox-esr-l10n-lt - Lithuanian language package for Firefox ESR
firefox-esr-l10n-lv - Latvian language package for Firefox ESR
firefox-esr-l10n-mk - Macedonian language package for Firefox ESR
firefox-esr-l10n-mr - Marathi language package for Firefox ESR
firefox-esr-l10n-ms - Malay language package for Firefox ESR
firefox-esr-l10n-my - Burmese language package for Firefox ESR
firefox-esr-l10n-nb-no - Norwegian Bokmål (Norway) language package for Firefox ESR
firefox-esr-l10n-ne-np - Nepali (Nepal) language package for Firefox ESR
firefox-esr-l10n-nl - Dutch language package for Firefox ESR
firefox-esr-l10n-nn-no - Norwegian Nynorsk (Norway) language package for Firefox ESR
firefox-esr-l10n-oc - Occitan language package for Firefox ESR
firefox-esr-l10n-pa-in - Panjabi (India) language package for Firefox ESR
firefox-esr-l10n-pl - Polish language package for Firefox ESR
firefox-esr-l10n-pt-br - Portuguese (Brazil) language package for Firefox ESR
firefox-esr-l10n-pt-pt - Portuguese (Portugal) language package for Firefox ESR
firefox-esr-l10n-rm - Romansh language package for Firefox ESR
firefox-esr-l10n-ro - Romanian language package for Firefox ESR
firefox-esr-l10n-ru - Russian language package for Firefox ESR
firefox-esr-l10n-sat - Santali language package for Firefox ESR
firefox-esr-l10n-sc - Sardinian language package for Firefox ESR
firefox-esr-l10n-sco - Scots language package for Firefox ESR
firefox-esr-l10n-si - Sinhala language package for Firefox ESR
firefox-esr-l10n-sk - Slovak language package for Firefox ESR
firefox-esr-l10n-skr - Saraiki language package for Firefox ESR
firefox-esr-l10n-sl - Slovenian language package for Firefox ESR
firefox-esr-l10n-son - Songhai languages language package for Firefox ESR
firefox-esr-l10n-sq - Albanian language package for Firefox ESR
firefox-esr-l10n-sr - Serbian language package for Firefox ESR
firefox-esr-l10n-sv-se - Swedish (Sweden) language package for Firefox ESR
firefox-esr-l10n-szl - Silesian language package for Firefox ESR
firefox-esr-l10n-ta - Tamil language package for Firefox ESR
firefox-esr-l10n-te - Telugu language package for Firefox ESR
firefox-esr-l10n-tg - Tajik language package for Firefox ESR
firefox-esr-l10n-th - Thai language package for Firefox ESR
firefox-esr-l10n-tl - Tagalog language package for Firefox ESR
firefox-esr-l10n-tr - Turkish language package for Firefox ESR
firefox-esr-l10n-trs - Chicahuaxtla Triqui language package for Firefox ESR
firefox-esr-l10n-uk - Ukrainian language package for Firefox ESR
firefox-esr-l10n-ur - Urdu language package for Firefox ESR
firefox-esr-l10n-uz - Uzbek language package for Firefox ESR
firefox-esr-l10n-vi - Vietnamese language package for Firefox ESR
firefox-esr-l10n-xh - Xhosa language package for Firefox ESR
firefox-esr-l10n-zh-cn - Chinese (China) language package for Firefox ESR
firefox-esr-l10n-zh-tw - Chinese (Taiwan) language package for Firefox ESR
firefox-esr-mobile-config - Default mobile-friendly configuration for Firefox ESRcasualty of the UK's Online Safety Act
Not the only one (bitchute was first) and coming your way fast wherever you are. And they're coming for the vpn's next..
On topic, point here is '|grep "^whatever"' picks only lines beginning with whatever. No use for synaptic here but,, whatever works for you.
refractasnapshot-base in arm64 requires syslinux 3:6.03
Wrong: syslinux (>= 3:6.03)
Apt-get complains because syslinux is not available at all for arm64. Until the official package gets updated, you have to recompile the source tarball yourself, having removed the syslinux dependency line in debian/control .. Not difficult. Only syslinux-common (all arches) is actually needed for refractasnapshot to function.
EDIT
There is a bit more to do, need to get efi files to work, read above.
The only solution is to use the evil that is Firefox
Librewolf is main browser here. But some sites don't work as expected.
It's no bug if a hardened browser, by default, blocks some remote elements from a known surveillance platform! Tried a separate profile, with uBlock Origin disabled? Or install Firefox, to be used for selected purposes only (as do I)..
We use cookies and other technologies that are essential to provide you our services and site functionality, as described in our Cookie Notice. If you agree and click 'Accept all', we will also allow 24 third-party companies, who we partner with, to store cookies on your device and use similar technologies to collect and use your personal data (e.g., IP address) for advertising personalisation, measurement and analytics, on and off our sites.
Mystery solved, thanks!
Most of us probably won't notice, except a few who use syslinux on usb and even then, depending on your local syslinux configuration.
EDIT: I'm guessing those modules are incompatible with current ldlinux.sys, which gets updated during syslinux installation to the drive.
https://files.devuan.org/devuan_excalib … l-live.iso
sha256:
392032e530b6c03b1e92431401de734fc7746342ae883df486d4a3a4fe403805
devuan_excalibur_6.1.1_amd64_minimal-live.iso
Firstly, thanks Devuan team for Excalibur. I have already Excalibur installs but still mostly run Daedalus, while I get Excalibur all configured how I want it.
Trying the new ISO in qemu I can't get it to boot from a syslinux USB in my usual way (using the
*.c32 modules from /isolinux). Although qemu does boot the ISO directly.
Undef symbol FAIL: init_fpu
Failed to load libcom32.c32
Failed to load COM32 file vesamenu.c32On investigation I found the md5sums of /isolinux/*.c32 are different from what is in the (system's) /usr/lib/syslinux/modules/bios ..
They also differ from my own /usr/lib/syslinux/modules/bios/ in both excalibur and daedalus.
If I replace those modules in my USB's /syslinux with the ones from the system, everything works as expected.
I already have verified the sha256sum of the ISO.
Where do /isolinux/*.c32 in the ISO originate from and why are they different?
@Berni: Please mark this thread [solved]!
Also, thanks for trying ExeGNU. Investigating this led to finding some other (minor) issues and solutions for the next version.
TDE is outside the mainstream for mostly conventional and political reasons. TDE has run almost flawlessly on a Devuan base since 2017, with no systemd dependencies and is still actively developed. ExeGNU is simply Devuan + TDE installable Live ISO.
EDIT: but with it's own potential flaws!
More info (please don't request support there if you don't run siduction):
https://forum.siduction.org/index.php?topic=9864.0
https://forum.siduction.org/index.php?topic=9854.0
I just did a new test install of exegnu64_excalibur-20251119.iso on real hardware (hp tower with UEFI) and booted it. All seems well.
The commands I posted earlier from the qemu live usb session returned exactly the same in the new install. A video clip opened in mpv plays without error.
apt update && apt install claws-mailgives me claws-mail in the menu which opens as expected.
So I'm in the dark what happened to you but still curious to know why..
EDIT: also, cuyo installs and opens here (although I don't understand how to use it), mpv still working after.