You are not logged in.
Your commands are correct for fuseiso and fusermount. I stopped using fuseiso a few years ago because it went away. I guess it's back, but I haven't tried it.
As root:
mount snapshot.iso /some/mountpoint
do stuff
umount /some/mountpointWhy do you want to mount the isos?
The reason for the point release is to release updated installer isos and live isos with newer software that's in the repo. If you regularly do 'apt update' and 'apt upgrade' or the equivalent, you're already there.
Note: If you're upgrading for the first time an ascii that was installed when ascii was still in testing (around two years ago), you might run into some trouble. (Happened to me last week.)
I think FM81 was showing the mkisofs command as an example. You don't need to run that command - it's used to make the .iso file, not to put it on a usb.
You can make an iso that boots uefi or bios with refractasnapshot. See the config file. See the xorriso command in the script itself. There are a couple of options needed for uefi. If you have questions, we can talk about it in a separate thread.
NAME_OF_ISO would be the name of the .iso file you are creating. With just the file name and no path, it would be created in the current working directory. Add a path if you want it to land someplace else.
ISO_ROOT_OF_FILES is the top-level directory of the file tree you want to put inside the iso. Typically, it contains an isolinux directory and a live directory.
I don't understand the error message. You shouldn't need 3D acceleration for synaptic. (And I've never gotten 3D to work in vbox.) How are you starting synaptic?
File the bug report against eudev.
I have that version of lsb-release and I don't have distro-info-data installed. You should be able to remove it. It's not listed as a Depends or even a Recommends for lsb-release. If that doesn't work, you can edit /etc/lsb-release to say whatever you want.
user@ascii:~$ apt-cache policy lsb-release
lsb-release:
Installed: 4.1+devuan2
Candidate: 4.1+devuan2
Version table:
*** 4.1+devuan2 500
500 http://deb.devuan.org/merged ascii/main amd64 Packages
500 http://auto.mirror.devuan.org/merged ascii/main amd64 Packages
100 /var/lib/dpkg/status
user@ascii:~$ apt-cache policy distro-info-data
distro-info-data:
Installed: (none)
Candidate: 0.36
Version table:
0.36 500
500 http://deb.devuan.org/merged ascii/main amd64 Packages
500 http://auto.mirror.devuan.org/merged ascii/main amd64 Packages
user@ascii:~$ apt-cache depends lsb-release
lsb-release
Depends: python
Depends: python
Recommends: apt
Suggests: lsb
lsb-compatIf you're not going to be upgrading, you can delete the theme directories that you don't use. They're in /usr/share/themes.
Search for posts by Mr. Greenjeans in the Devuan Derivatives section. He's the most radical minimalist I can think of. That should give you some good ideas.
If you can devote 1 GB of that usb stick to the rescue system, you shouldn't need to work hard to trim it down. The live system is compressed in a squashfs.
Have you seen this guide for minimal install? It's for jessie, but the basic procedure is valid for any suite.
https://devuan.org/os/documentation/dev … al-install
A debootstrap install will give you the leanest possible base to start with. I prefer to start with an installer iso and un-check all the boxes except 'Standard system utilities' in the tasksel window. Then install what I want, usually excluding Recommends. You might have better luck with the command-line tools (apt or apt-get) instead of synaptic. Getting rid of synaptic will free up a lot of space.
I think you can remove the locales package to get rid of all the extra internationalization files.
It's because I did something sneaky and you did something you don't remember.
1. There's no refractasnapshot-gui in ascii because yad uses gtk3 and some of the windows had their buttons off-screen. So I pulled it before the first release of ascii.
2. In beowulf/ceres I fixed refractasnapshot-gui so that you can see all the buttons in the windows. If you installed from the 2.1 desktop-live, you got a newer version of refractasnapshot-gui that's not in the ascii repo. (I slipped it in.)
3. If you didn't install from 2.1 desktop-live, then you got it from the same place you got refracta2usb, which is not in any devuan repo. (i.e. from my sourceforge site - https://sourceforge.net/projects/refracta/ ) You can use the latest versions from sourceforge or download the beowulf or ceres packages and use them in ascii. Use same version of -base and -gui. (note: 10.2.6 through 10.2.9 are the same. We had to keep incrementing the version due to a bug in the build system that wouldn't let us build the same version twice.)
When you ran the upgrade, did it include reinstalling grub? Is grub even installed in the live system? Does the computer boot without the usb stick?
Maybe the flash drive is dying.
Maybe the system is just randomly confused and a reboot will fix it. (I'd power off completely then restart.)
Maybe just pulling the stick out and plugging it back in will help. (It will probably be /dev/sdf if you do this.)
Yes, you must have the word 'persistence' in the boot command and the filesystem label on the persistent partition must also be 'persistence'.
You have enough space in the persistent partition to hold a big upgrade. As long as you boot with persistence when you make the snapshot, it will copy the upgraded (running) system.
What does your boot command look like? cat /proc/cmdline
What is in persistence.conf?
I don't know Alien-OS. I assume this is a debian-based distro and it uses live-boot and live-config. Is that correct?
Is the OS 32-bit or 64-bit?
Were the system directories on the persistent partition automatically created, or did you create them manually?
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.bin