The officially official Devuan Forum!

You are not logged in.

#1 Devuan Derivatives » Refracta beowulf no-X isos » 2019-12-13 21:23:10

Replies: 2

No X. Plenty of extra command-line software, especially stuff for rescue and repair.

I'm calling them beta because beowulf is still undergoing some changes. These were built with live-sdk, and I don't think I need to change anything in the build process. I'll probably make new isos when beowulf goes stable.

Xfce isos coming soon. (Weeks, not days.)

New versions of installer and snapshot also coming soon. (Days, not weeks. They're already in the new isos, just have to get them into the repo.)

#3 Re: Hardware & System Configuration » Eudev broke down after upgrade. » 2019-12-11 22:57:40

Thanks for finding that!

There's a new version in ascii-proposed with the fix. (3.2.2-17)  Please test and report.

#4 Re: Off-topic » This should be fun... » 2019-12-11 16:37:01

OK, I read A.6 and if I read it again, I'm sure I'll get a headache.

I think we're screwed. As I see it, there should only be two options on this vote:
1. systemd only
2. some kind of support for other inits.

Then if 2 wins, figure out the details.

#5 Re: Off-topic » This should be fun... » 2019-12-11 13:00:10

I'm not clear on what this means:

Majority Requirement

The proposals need a simple majority

#6 Re: Hardware & System Configuration » Eudev broke down after upgrade. » 2019-12-11 01:18:10

Oops! I gave you the option that goes with dpkg, not apt. Sorry about that.

You could try downloading the packages and installing with dpkg --force-downgrade -i <packages>.
Or maybe install an older package from /var/cache/apt/archives/

I'm not exactly sure what the problem is. If you're ambitious, you could unpack the deb, add a 'set -x' to the preinst script(s) and then repack. That might give useful information.

Not sure if this is relevant, but I recently had trouble upgrading  eudev to a lower package version (220:something from when ascii was in testing to 3.2.2-something). I had to comment out a couple lines in /var/lib/dpkg/info/libeudev1:amd64.list and .md5sums to nullify a dependency that was getting in the way.

These two:

#7 Re: Hardware & System Configuration » Eudev broke down after upgrade. » 2019-12-10 19:58:51

Geoff 42 wrote:

I have tried reinstalling with the version 13 :-

apt install --reinstall  eudev=3.2.2-13 libeudev1=3.2.2-13 libeudev-dev=3.2.2-13

but is fails with <snip>


Try adding --force-downgrade

#8 Re: Installation » sources.list for bloody germans » 2019-12-10 13:08:23

You can drop the country code altogether. It doesn't really do anything - you just get redirected to a nearby mirror. (e.g. I'm in the US and I frequently get Italian or German mirrors. There is no US mirror.)

If you want to use a specific mirror, choose one from the list here:

#9 Re: Installation » Refracta Snapshot VM mount points question. » 2019-12-07 12:46:56

I use optical media, too. Any directories under /media that are needed get created automatically. I think udev takes care of that.

To preserve any directories you made under /media, take a look at the rsync excludes list (/usr/lib/refractasnapshot/snapshot_exclude.list) and comment out one or more of the following lines, as needed.
Like this:

#- /cdrom/*
#- /media/*

Do the same with /usr/lib/refractainstaller/installer_exclude.list

To add a line to fstab in the installer, you just need to add this line:

echo -e "/dev/sr0\t/media/cdrom\tauto\tnoauto,owner,ro,users\t0\t0" >> /target/etc/fstab

You can put it right after the section that adds the swap line to fstab. That section starts around line 1430 in /usr/bin/refractainstaller and around line 1570 in /usr/bin/refractainstaller-yad. The last two lines in the following code block are what you need to add.

# add entry for swap to fstab if needed
if [[ $use_existing_swap = "yes" ]] ; then
        if [[ $use_uuid = yes ]]; then
                swap_part="$(/sbin/blkid -s UUID $swap_dev | awk '{ print $2 }' | sed 's/\"//g')"
        echo -e $"\n Adding swap entry to fstab...\n"
        echo -e "$swap_part\tswap\tswap\tdefaults\t0\t0" >> /target/etc/fstab
        echo -e "/swapfile\tswap\tswap\tdefaults\t0\t0" >> /target/etc/fstab

# Make entry for cdrom in fstab
echo -e "/dev/sr0\t/media/cdrom\tauto\tnoauto,owner,ro,users\t0\t0" >> /target/etc/fstab

#10 Re: Installation » Refracta Snapshot VM mount points question. » 2019-12-06 21:52:01

fstab is excluded in the rsync copy when you make a snapshot.
fstab gets created when you install with refractainstaller. There's no entry for cdrom. I haven't needed that in years. If you do need it, I think you'd need to add a line of code to refractasnapshot.

#11 Re: Installation » Xfe + isomount question » 2019-12-05 02:49:44

Excuse my ignorance, but how do I set that up in a live *.iso when I don't know what drives will be in the box when I use it?

Oh yeah, I didn't think of that. Once you get everthing set up, you could make a hookscript that will run when you boot the live iso and inject the necessary lines into /etc/fstab. But that won't work for a rescue usb that you're booting on some other box. For that, you might be better off doing it manually in a root terminal. Then you can run fdisk, df and blkid to get information about the partitions and figure out which one you want to mount.  That's my preferred method, even on a box that will let me mount partitions from the desktop.

#12 Re: Installation » Xfe + isomount question » 2019-12-04 20:16:31

Right, you can set up the boot menu before or when you make the snapshot.

If you set up the extra partitions in fstab with 'noauto,user' options, then you can mount/unmount by right-clicking on the mountpoint. I just tested this in jessie and it works. That's the version before the custom mount/unmount commands were added.

If xfe won't do what you want, take a look at spacefm or pcmanfm.

#13 Re: Installation » Xfe + isomount question » 2019-12-04 15:20:03

If you recall, this live Devuan ascii *.iso will live inside my box in a small capacity USB plugged into a motherboard USB port and will be used as a sort of rescue installation.
The drive will also have one or maybe two separate logical partitions inside an extended partition to hold a few *.iso files which I may need.

This is why I consider it important to be able to mount an *.iso image from within the live installation.
eg: imagine a rig with disabled boot drive and a failing CD/DVD unit with the backups/images in another drive in the box or on a portable external drive.

I can understand why you want to be able to boot an iso for rescue/repair, and I can understand why you want to be able to mount your installed partitions from that live system, but I still don't understand why you need to mount the isos. Are you planning to do frequent editing of the iso's boot menu?

According to the xfe docs here:
You can mount filesystems with ctrl-M and unmount with ctrl-U. What I can't figure out is how/where you find these unmounted filesystems. I don't see anything in the preferences about volume management or devices. I can only see mounted filesystems.

Edit: Oh, I'm looking at an older version in jessie. I see this for 1.42, which is the version in ascii:

This release fixes several bugs and regressions and adds custom mount / unmount commands to the Preferences dialog.

#14 Re: Installation » Xfe + isomount question » 2019-12-04 00:11:34

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/mountpoint

Why do you want to mount the isos?

#15 Re: Installation » Updating ASCII to ASCII 2.1 point release » 2019-12-03 18:05:28

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.)

#16 Re: Installation » Problem with *.iso file » 2019-11-30 23:35:40

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.

#17 Re: DIY » ascii VM to ascii live *.iso » 2019-11-30 02:58:33

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?

#19 Re: Installation » lsb-release » 2019-11-29 03:44:48

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
  Installed: 4.1+devuan2
  Candidate: 4.1+devuan2
  Version table:
 *** 4.1+devuan2 500
        500 ascii/main amd64 Packages
        500 ascii/main amd64 Packages
        100 /var/lib/dpkg/status
user@ascii:~$ apt-cache policy distro-info-data
  Installed: (none)
  Candidate: 0.36
  Version table:
     0.36 500
        500 ascii/main amd64 Packages
        500 ascii/main amd64 Packages
user@ascii:~$ apt-cache depends lsb-release
  Depends: python
  Depends: python
  Recommends: apt
  Suggests: lsb

#20 Re: Installation » Thinning down the ascii installation » 2019-11-27 19:33:54

If 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.

#21 Re: Installation » Thinning down the ascii installation » 2019-11-27 17:44:12

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. … 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.

#22 Re: Installation » Strange Synaptic issue » 2019-11-26 14:53:42

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 - ) 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.)

#23 Re: Installation » Problems configuring persistence » 2019-11-23 19:25:21

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.)

#24 Re: Installation » Problems configuring persistence » 2019-11-23 00:56:24

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.

#25 Re: Installation » Problems configuring persistence » 2019-11-22 22:26:11

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?

Board footer

Forum Software