You are not logged in.
I find it easier to build a new system in a virtual machine, either with virtualbox or qemu. Give it around 10-12GB for a virtual disk, and that should be enough space to create a snapshot.
Your package selections, system configs and desktop configs will all be copied into the snapshot. You shouldn't need to change any of those once you have it the way you want. But there is a shortcut for that. (explained a little later)
If you just need to rebuild the iso to change things in the boot menu or anything else that's in the root of the iso instead of in the live filesystem there's a really short shortcut.
Make sure the config file is set to save_work="yes"
Run a snapshot.
If you need to change things in the root of the isos, edit whatever you want in /home/work/iso/
Then re-run refractasnapshot and select the option that says 4. Re-run xorriso only. (make iso, no-copy, no-squash)
This will re-run xorriso and only takes a minute or two.
If you want to change something in the system, you could edit config files in /home/work/myfs/ or even chroot that directory and add or remove packages with apt.
Then re-run refractasnapshot and select the option that says
2. Re-squash and make iso (no-copy)
This runs mksquashfs again and takes a little longer.
Then include instructions for replacing consolekit just how you did it, in case it's needed.
Try installing it with aptitude and see if it gives you any other options or information about the nature of the conflict.
What format for this system will you be offering? Live-iso, installer iso, disk image?
If you use live-sdk to make the iso, you can add consolekit to the purge_packages list. If you use refractasnapshot, you can remove consolekit before making the snapshot if it's installed. You should not add it to the excludes list - that wouldn't work right. If you're making a live iso that has the debian-installer, I probably can't help.
I can't say why it happened, but there's a good chance it wasn't anything that you did. Take a look at the section on Session management and policykit backends in the release notes. It's a rat's nest of dependencies.
http://files.devuan.org/devuan_ascii/Release_notes.txt
Head_on_a_Stick wrote:cipher wrote:Well ascii shows 24 hits for systemd
https://pkginfo.devuan.org/cgi-bin/d1pk … ease=asciiThe pattern is improving though: 14 results for beowulf and just 7 for ceres.
And please check the package descriptions: most of that stuff is for interacting with systemd and so will do *nothing* if it isn't installed.
Good point. But if these systemd components do nothing if systemd isn't installed (weird concept that) then why have them at all?
We include stuff called systemdthisorthat but unless realsystemd is installed they do nothing.
Why include things that do nothing?
Excluding packages with systemd in the name when they don't pull in systemd and their presence doesn't break anything would be a wasted effort, and in some cases, their removal would break things because of package dependencies.
Also note that some of the packages in the list you generated have '+devuan' in the version. That means we modified the package so that it will work without systemd. If we wanted to change the names of those packages, we'd have to modify any packages that depend on them to recognize the new names.
I think you need to remove consolekit. I'm not sure if you'll have problems doing that. You'll need to replace
libpolkit-backend-consolekit-1-0 libpolkit-gobject-consolekit-1-0with
libpolkit-backend-elogind-1-0 libpolkit-gobject-elogind-1-0which may or may not happen automatically.
Yell if you need help with it. (And post some terminal output if there are conflicts that you or aptitude can't resolve.)
Post the output of the following command. That will show which policykit related packages are installed. Something you need might be missing.
dpkg -l | egrep "consolekit|elogind|policykit|polkit|libpam"The 2.1 minimal-live isos both have the same isolinux.bin. The amd64 and i386 are both built using the same xorriso/mkisofs command. The desktop-live i386 and amd64 use slightly different commands, because the amd64 supports uefi. I'm a little bit surprised that the isolinux.bin in the 2.1 minimal-lives are the same as the 2.0.0 you posted.
f03d6ecc57dad4524a0cab76b7afab41I checked some Refracta isos and the i386 and amd64 are different (assuming for the same reason as the desktop-live) but the md5sums are consistent over time and only change occasionally. Possibly with new versions of isolinux or something else.
Getting back to the original post, I think the problem with installing software is not related to isolinux.bin. Sometimes the installer fails to get all the software and you need to repeat that step. This was more common with jessie isos, but I think it's happened with ascii, too.
Thanks, Ralph. I was planning to ask you about this, but I got delayed checking md5sums on more isos.
cancel that. If you read it, forget that I said it.
Sill looking...
I'm looking into this. Below are some collected md5sums on isolinux.bin that I have in various places. I checked the sha256sums on the netinstall isos and they are correct. Both were downloaded today. I don't know why i386 and amd64 made at or around the same day are different. The isolinux package is not arch-specific.
ascii-backports (2019-02-06 ~bpo9+2)
ea5013e737ba5ea49161a2b646312276 usr/lib/ISOLINUX/isolinux.bin
ascii (current 3:6.03+dfsg-14.1+deb9u1)
81d876d6234d3ca002390e7cb361bb61 /usr/lib/ISOLINUX/isolinux.bin
ascii (isolinux_3%3a6.03+dfsg-14.1_all.deb)
3e58f3f1a85d430556259f27f3b36d1a usr/lib/ISOLINUX/isolinux.bin
i386 2.1 netinstall iso
3b36f20bc14cf4ad0f046962c4414221 mnt/isolinux/isolinux.bin
amd64 2.1 netinstall iso
bdad948d65c1dea713e1698d04a4e75d mnt/isolinux/isolinux.bin
amd64 2.1 desktop-live iso (September 20)
bb8555ec5b6af5bebac5bfc08f88a543 mnt/isolinux/isolinux.bin
i386 2.1 desktop-live iso (September 20)
f03d6ecc57dad4524a0cab76b7afab41 mnt/isolinux/isolinux.bin
in live-sdk, possibly beowulf (Oct 18)
caaa9f76d534f8c710c78cef00388ed1 /home/phred/my-live-sdk/live-sdk/extra/syslinux/isolinux.bin
caaa9f76d534f8c710c78cef00388ed1 /home/phred/my-live-sdk/live-sdk/tmp/devuan-i386-build/binary/isolinux/isolinux.bin
beowulf
5424e654f2bb81acfb7726631a3a0c1b /usr/lib/ISOLINUX/isolinux.bin
refractasnapshot-base (this one is old)
a45f9b17d309273e3efa588611141b43
jessie
35c69b13a8771b012d6e86b323827d78 /usr/lib/ISOLINUX/isolinux.bin
wheezy
6b8de496c485f2a82ca5f51eb59887fd /usr/lib/syslinux/isolinux.binHead_on_a_Stick wrote:fsmithred wrote:Oh my, interesting read. I wonder what Charles Max Wood did to so offend the Foundation.
Apparently he used the word "whitehouse" when describing trump towers with a maga hat on. Damn racist nazi white supremacist if you ask me!
His real crime was to offer to mediate a civil discussion between two parties who were in an online battle. When you defend the target of an SJW attack, you become a target.
Dirk Gently might see everything in this discussion as interconnected and part of a bigger event.
fsmithred wrote:I'd be more worried about which projects MS contributes to.
Do you mean the Linux kernel?
https://www.linuxfoundation.org/membership/members/
Well, I wasn't thinking of that, but I'm worried about the linux foundation anyway...
https://blog.cleancoder.com/uncle-bob/2 … ation.html
Maybe just pining by origin is sufficient:
Package: dbus
Pin: release o=Devuan
Pin-Priority: -1
I tested this, and it doesn't work - dbus wanted to sneak in.
I don't trust them, and I assume that they're up to something. That said, I would expect most if not all devs have a local copy of their git repos. As long as that's the case, MS could burn github to the ground and it would be a minor inconvenience to move stuff to another location.
MS can control who has access to github or not, but if they want to dictate who can contribute to a project, they'll need to fork that project and maintain it themselves. I'd be more worried about which projects MS contributes to.
Above all else, confusion reigns
And though I ask, no one explains
- Procol Harum
Zephyr - Would you please re-post in a new thread or one of your older ones?
Avbox - Your review of Star Kirk belongs in Ozi's Star Linux thread. Star is not Crowz.
Thanks.
fsmithred wrote:It also helps to exclude Recommends.
are recommends still on by default? didnt debian change that after foisting systemd? (around 2014-2015?)
Yes, you still get Recommends by default.
It's not firefox that's pulling it in. Firefox-esr only suggests pulseaudio. It's getting pulled in due to Recommends in xfce. It's probably something similar in mate. Here's the command to check it:
$ aptitude why pulseaudio
i task-xfce-desktop Depends xfce4
i A xfce4 Depends xfce4-pulseaudio-plugin
i A xfce4-pulseaudio-plugin Recommends pulseaudio One good way to avoid pulling in packages you don't want is to only install the standard system utilitites and then add what you want after rebooting into the system. It also helps to exclude Recommends.
@steelpillow: you prefer a skirt? (or kilt)
You're right. The openrc package is not in the CD or DVD. It will only be installed if you selected a mirrorl.
You can still switch to openrc if you have an internet connection. Make sure sources.list points to devuan repos and install openrc. (See https://devuan.org/get-devuan for examples.)
I'm building beowulf isos with live-sdk without much trouble. I had to adjust a few things, and some of the adjustments are temporary. I don't want to push those changes to git until the temporary issues are solved. Meanwhile, here are the configs and blend file I'm using right now:
http://distro.ibiblio.org/refracta/file … end.tar.gz
Make a beowulf directory like the ascii directory here: https://git.devuan.org/sdk/live-sdk/tre … sktop-live
Replace devuan-desktop-live/config with config from the tarball. Replace the .blend file with the one in the tarball.
Copy config.beo from the tarball to beowulf/config
Or just compare the changes from the ascii files to the beowulf ones and use that as a guideline for modifying your own configs.
CAVEAT: I haven't looked at the instructions at the beginning of this thead in a long time. Some details have changed. If you follow the install directions on the git repo, it should work with minimal effort. https://git.devuan.org/sdk/live-sdk
(I have done that recently.)
Mine is greyed out in the list, too, and I still have a notification area in the panel. If you see a wicd (network) icon in the panel when the desktop starts, it's in the notification area. If I point the mouse at the correct stop, I can right-click and get the Properties box for the Notification area.
If I remove the notification area, it's no longer greyed out in the list, and I can add it to the panel. Apparently, you can only have one.
I tried it yesterday with the same iso you used. I ran the Graphical install and took all the defaults up to the point of choosing openrc. When it boots, openrc runs as expected. (Parts of sysvinit are still installed and are used by openrc.)
What did you do that's different?
Nixer's method still works. I just tried it today on a buster standard-system (no X).
First time, I rebooted before trying to install eudev, and I got the long hang on dbus.
Second time, I instlalled eudev before the reboot, the install failed, I rebooted and did not get the delay. I then installed eudev again, and it succeeded.
On both installs, when I tried to install elogind and libelogind0 it wants to install a bunch of desktop apps. I haven't figured out why that is.
Short version:
- boot buster, install sysvinit-core
- download and install devuan-keyring
- change sources to devuan, update, upgrade
- (optional) install eudev and let it fail. This might save some time on the first reboot.
- reboot and install eudev, remove or purge systemd if it doesn't get removed automatically. (possibly libnss-systemd also)
- (optional) install libelogind0 if you want to replace libsystemd0. Without elogind, it's not pulling in the desktop apps.