You are not logged in.
I've done it this way, without a loopback.cfg in the iso.
menuentry 'Live ISO Boot' {
insmod part_msdos
insmod part_gpt
insmod ext2
set isofile='(hd0,gpt13)/isos/refracta8_xfce_i386-20161014_1432.iso'
loopback loop "$isofile"
linux (loop)/live/vmlinuz boot=live findiso="$isofile" noeject
initrd (loop)/live/initrd.img
}It looks like the advantage of using the loopback.cfg is the ability to just drop the isos into a directory and get a list of them at the boot screen. But that requires the isodetect.lua script from Super GRUB2, which only works if grub is compiled with lua support. I don't know if debian's grub can use that.
Most times, I just boot isos in virtualbox or qemu, so I don't have to reboot.
I guess it will work in jessie or ascii. The devuan bug report is on ascii, and I tested it on ascii (with cryptsetup 1.7). The debian bug report is from 2013 and is for cryptsetup 1.6. You might need to apply it manually on jessie if the files aren't exactly the same in jessie and ascii.
I moved 70-persistent-net.rules and rebooted. It was not regenerated.
I don't know where that file came from. This system started out in June as a debootstrap install, then added openbox (without dbus). The one that doesn't have that file started out in April as a netinstall with standard system utilities only, then added parts of xfce. Neither were upgrades from jessie, so it can't be a leftover.
It's generated by udevd via /lib/udev/rules.d/75-persistent-net-generator.rules when net.ifnames!=1.
Huh. Other than when net.ifnames=1, when else would it not be generated? I have two ascii installs on the same computer; one has 70-persistent-net.rules and the other does not. Interfaces get the old names on both.
This situation made me realize some gaps in my knowledge:
1. What is the function of this file normally?
2. Why is the file absent/empty? It used to be generated automatically, but not anymore. Is something broken on these machines?
70-persistent-net.rules was used to make sure that each network interface kept the same name after reboot. Apparently, it still works if you create the file yourself. In ascii, you usually don't need it - eudev reverts to the old names.
The new method names them according to where they are plugged in on the motherboard. Some people believe that being able to predict the interface name is more important than being able to remember it. Longer, more complex names go along with the longer, more complex commands that have been created in recent years.
https://www.freedesktop.org/wiki/Softwa … faceNames/
A patch was submitted for the slow shutdowns. (Thanks, Jan!)
https://bugs.devuan.org//cgi/bugreport.cgi?bug=237
I just tested it and can shut down with no delay and no "failed" message.
It's not one of our packages, and upstream already has marked it "Wontfix".
https://bugs.debian.org/cgi-bin/bugrepo … bug=720340
------------------------patch------------------------------------------------------
--- /lib/cryptsetup/cryptdisks.functions.orig 2018-08-14 17:12:31.543227705 +0200
+++ /lib/cryptsetup/cryptdisks.functions 2018-08-23 16:36:23.849064962 +0200
@@ -763,9 +763,17 @@
# Removes all mappings in crypttab
do_stop () {
- local dst src key opts opencount major minor
+ local dst src key opts opencount major minor vgs vg
dmsetup mknodes
+ if [ -x /sbin/lvm ]; then
+ vgs="$(/sbin/lvm vgscan | sed -n '/"/s/^.*"\([^'\'']*\)".*$/\1/p')"
+ if [ -n "${vgs}" ]; then
+ for vg in ${vgs}; do
+ /sbin/lvm vgchange -a n ${vg} >/dev/null 2>&1
+ done
+ fi
+ fi
log_action_begin_msg "Stopping $INITSTATE crypto disks"
egrep -v "^[[:space:]]*(#|$)" "$TABFILE" | while read dst src key opts; do
------------------------patch/-----------------------------------------------------The templates for the .info and .mirrors files are part of python-apt-common. Here are a couple of sample devuan files you can test. This is my best guess based on the existing files for debian, ubuntu, gnewsense and tanglu. I only included ascii. Both of these go in /usr/share/python-apt/templates/
Devuan.info
ChangelogURI: http://packages.debian.org/changelogs/pool/%s/%s/%s/%s_%s/changelog
Suite: ascii
RepositoryType: deb
BaseURI: http://deb.devuan.org/merged
MatchURI: deb.devuan.org/merged
MirrorsFile: mirror_list.txt
Description: Devuan 2.0 'ascii'
Component: main
CompDescription: Officially supported
Component: contrib
CompDescription: DFSG-compatible Software with Non-Free Dependencies
Component: non-free
CompDescription: Non-DFSG-compatible Software
Suite: ascii-updates
RepositoryType: deb
ParentSuite: ascii
Description: Recommended updates
Suite: ascii-security
RepositoryType: deb
ParentSuite: ascii
Description: Security updatesDevuan.mirrors
#LOC:any
http://deb.devuan.org/mergedBut what I'd like to know is why the Devuan maintainers build the kernel with mei in it.
There are no devuan kernels. We use the debian kernels, unchanged. The only packages from debian that get changed are the ones that depend on systemd.
Sorry for the late reply. I didn't see this one until now.
If you chose 2 and 3, you got both. (but 3 gets 2 anyway).
2 adds the user to the sudo group
3 adds the user to the sudo group, disables the root password and edits a couple files in the user's home.
To re-enable the root account, run
sudo su
passwdYou might also need to change sudo-mode and super-user-command in these files if you have them. (It might also be safe to delete/move these. I've never tried that.)
~/.gconf/apps/gksu/%gconf.xml
~/.*/share/config/*desurc
RAID - LUKS - LVM
This method uses one encrypted raid array with lvm on top of it, so you only have to enter one password to unlock the encrypted volume.
Partition two disks, each with a small partition for boot and a large partition for the array.
If you use gpt with bios boot, add a third partition, greater than 1M, unformatted, with EF02 or bios_grub flag.
If you use uefi, add a third partition, 100-500M, fat32, EF00 or esp and boot flags.
This example uses the first partition for the boot array and the second partition for the system array.
(The second array for /boot is optional. See notes on full-disk encryption at the end of this post.)
Create the arrays.
Don't use names like /dev/md0, /dev/md1... If you do, cryptsetup will complain during update-initramfs. Use names like /dev/md/mdroot1 and /dev/md/mdboot1. (Note: the digit at the end is for refractainstaller, and it's really only needed on the unencrypted /boot. Any logical partitions in the lvm will have mapper names, and you can end those with a digit.)
mdadm --create -v /dev/md/mdroot1 -l1 -n2 /dev/sda2 /dev/sdb2
mdadm --create -v /dev/md/mdboot1 -l1 -n2 /dev/sda1 /dev/sdb1Encrypt the root array, /dev/md/mdroot1, then open it and give it a name, like crypt
cryptsetup luksFormat /dev/md/mdroot1
cryptsetup luksOpen /dev/md/mdroot1 cryptSet up LVM on the encrypted volume. The lv name sould end in a digit to make the installer happy.
pvcreate /dev/mapper/crypt
vgcreate vol0 /dev/mapper/crypt
lvcreate -L 5G vol0 -n lvroot1
lvcreate -l +100%FREE vol0 -n lvhome1Run refractainstaller.
Enter the following devices when the installer asks for the locations of /boot, operating system and /home.
/boot /dev/md/mdboot1
/ /dev/mapper/vol0-lvroot1
/home /dev/mapper/vol0-lvhome1
At the pause, switch to another console or terminal and do the following:
# save md detail to /etc/mdadm/mdadm.conf
mdadm --detail --scan /dev/md/mdboot1 >> /target/etc/mdadm/mdadm.conf
mdadm --detail --scan /dev/md/mdroot1 >> /target/etc/mdadm/mdadm.conf
# edit /target/etc/crypttab to add the following line:
crypt /dev/md/mdroot1 none luks
# edit /target/etc/cryptsetup-initramfs/conf-hook so it says:
CRYPTSETUP=y
# rebuild the initramfs:
chroot /target update-initramfs -uReturn to installer and proceed.
RAID1 - LUKS - LVM with FULL DISK ENCRYPTION (no separate unencrypted boot)
This is the same as the above,except for the following:
- don't make a separate array for /boot
- don't enter a partition for /boot in the installer
- at the pause, edit /target/etc/default/grub and add the following line:
GRUB_ENABLE_CRYPTODISK=yRun update-initramfs after you have edited all the files.
When you reboot, you should be asked for the password twice - once before you see the grub menu and once when the system is booting. Grub is slow to recognize the password. Be patient. Don't press ENTER a second time, or your boot menu will disappear too fast for you to select anything other than the default boot.
Slow Shutdown Fix
When you get tired of waiting for your encrypted system to shut down, see this post for a fix:
https://dev1galaxy.org/viewtopic.php?pid=8289#p8289
Yes, you may send me email.
LVM on RAID1
Partition disks as in the first post.
mdadm --create --verbose /dev/md0 --level=1 --raid-devices=2 /dev/sda1 /dev/sdb1
pvcreate /dev/md0
vgcreate vol0 /dev/md0
lvcreate -L 5G vol0 -n lvroot1
lvcreate -l +100%FREE vol0 -n lvhome2Run refractainstaller
Choose a partition for the operating system: /dev/mapper/vol0-lvroot1
Choose a partition for /home: /dev/mapper/vol0-lvhome2
At pause, before installing bootloader
go to another vt and run:
chroot /target
mdadm --detail --scan /dev/md0 >> /etc/mdadm/mdadm.conf
update-initramfs -u
exitProceed with installer. (install GRUB)
INSTALL TO LVM
Partition at least one disk with at least one partition. For this example, I'll use two disks with one partition and combine them into a single volume group.
Create the physical volume and volume group.
pvcreate /dev/sda1 /dev/sdb1
pvscan # or pvdisplay # This is just to see what you did.
vgcreate vol0 /dev/sda1 /dev/sdb1
vgscan # or vgdisplayCreate the logical volumes (the partition scheme for your filesystem).
WARNING: There's a test in refractainstaller that checks to make sure the partition you choose ends in a digit. The names you choose for your logical volumes must end in a digit. (or else comment out that test in the script.)
For this example, assume two disks of 4GB each. Since they are combined in a single volume group, we can make a partition that's bigger than 4GB. The next commands will create a 5G partition named lvroot1 and a second partition that uses the rest of the space, named lvhome2.
lvcreate -L 5G vol0 -n lvroot1
lvcreate -l +100%FREE vol0 -n lvhome2Run refractainstaller.
Choose a partition for the operating system: /dev/mapper/vol0-lvroot1
Choose a partition for /home: /dev/mapper/vol0-lvhome2
Note: When the installer asks if you want the partition encrypted, you could say yes, but you will have to enter a password for each encrypted partition. Also, the encrypted root and home partitions will be named /dev/mapper/root_fs and /dev/mapper/home_fs in /etc/fstab.
When the installer is finished, remove the live media and reboot.
NEXT: LVM on RAID1
The cli version of refractainstaller has a couple of characteristics that make it possible to use it in non-standard ways.
1. You have to type in the device name when choosing partitions.
2. The installer pauses before installing the bootloader. This allows you to chroot the installed system to make changes manually.
While lvm and raid are not explicitly supported by the installer, it is possible to do either or both. Here are some examples. These examples use /dev/sda and /dev/sdb. You must change that if you use different drives.
In all cases, I installed the grub bootloader to the mbr of /dev/sda.
Important note regarding encryption: If you encrypt a raid array or lvm and your root partition or home partition is contained within that volume, tell the installer "no" when it asks if you want to encrypt that partition.
INSTALL TO RAID1 (mirrored)
Partitioning
There are several ways to do this. You can create the array from whole disks (/dev/sda and /dev/sdb) or you can create it from two partitions (/dev/sda1 and /dev/sdb1). If you use whole disks, there will be no room at the beginning of the disk for grub, and you will need another disk for the bootloader. Also, if you use whole disks, you can then partition the array, and you will use partitions like /dev/md0p1, /dev/md0p2 during the installation.
For this example, partition two disks with at least one partition on each. Make them the same size. You can use either gpt or msdos partition tables. If you have uefi hardware, you need an efi partition somewhere. We'll install the whole system into one partition.
(Note: gpt with bios boot requires an unformatted partition, at least 1MB in size with bios_grub flag, or ef02)
(Note 2: refractainstaller can only recognize separate /boot, /home and / (root) partitions. There's a way to have more, but I haven't tested it with this. See /etc/refractainstaller.conf.)
(Note 3: refractainstaller asks for a partition and then tests to see that it ends in a non-zero digit. That means if you call your array /dev/md0 and try to use that as a single partition, it will fail. Call it /dev/md1 instead.
Create the raid (use the partitions, not the whole device.)
mdadm --create --verbose /dev/md1 --level=1 --raid-devices=2 /dev/sda1 /dev/sdb1
cat /proc/mdstat # this is just to let you see that it workedRun refractainstaller (please use the -d option for a better error log)
refractainstaller -dThe installer will ask where to put the operating system. Enter /dev/md1
(Note: we only made one partition, so don't enter anything for /boot or /home)
The installer will ask if you want the partition encrypted. You can say yes if you want, and it will work. (You don't need a separate /boot partition. See the notes on full-disk encryption at the end of this post.)
The installer will pause when the installed system is ready for chroot. That pause looks something like this:
The installed system is ready for chroot. (proc, sys, dev are mounted)
If you want, you may work in another virtual terminal.
Make a selection when you are ready to proceed.${bios_boot_warning}
Choices (enter number)
1 or 2) (Install bootloader or copy files and install bootloader)
3) Continue without a bootloader.
4) Abort the installation and exit.
Do not choose anything yet. Go to another console or another tab in your terminal and get root. Then run the following commands.
chroot /target
mdadm --detail --scan /dev/md1 >> /etc/mdadm/mdadm.conf
update-initramfs -u
exitReturn to the console or terminal where the installer is running, and make the appropriate choice. (usually, you want to install a bootloader.) Continue until the installer is finished. Reboot (remember to remove the live media).
References:
https://www.digitalocean.com/community/ … untu-16-04
https://dev1galaxy.org/viewtopic.php?pid=10954#p10954 (Thanks for trying it first, stroudmw.)
https://www.howtoforge.com/linux_lvm
https://wiki.archlinux.org/index.php/LVM
https://wiki.archlinux.org/index.php/Dm … VM_on_LUKS
Next: LVM
Thanks for the reply. Your English is good enough that I think I understand everything you said. And I agree with you.
a lot of software was created (mainly by freedesktop.org), in my opinion, very complicated and difficult to manage.
You're too polite! I won't put my version of that statment in print, because it's not safe for work.
I've spent a good part of the morning looking at dependencies of different display managers and session managers in jessie and ascii. It's a big rat's nest. It looks like the problem comes from a change in the dependencies of libpolkit-gobject-1-0 and libpolkit-backend-1-0.
I will discuss this with the appropriate devs, and we should be able to sort it out for beowulf.
A simple solution would be to move those dependencies to Recommends. Then anyone who wanted a minimalist xfce could install without recommends. (Many of them already do this.)
campus, can you list the functions that are lost by installing without consolekit?
Once you get your sources straightened out, just install kaffeine. You should not need to tell it to install vlc - the package manager will pull in any dependencies automatically.
Something from this list probably does what you want.
$ apt-cache search yandex
rclone - rsync for commercial cloud storage
translate-shell - Command-line translator using Google Translate, etc.
git-annex-remote-rclone - rclone-based git annex special remote
youtube-dl - downloader of videos from YouTube and other sitesThe devuanized versions of 0.105-15 are in jessie-security.
apt-get -t jessie-security install policykit-1As explained above, you need to fix your sources.list.
This is wrong:
deb http://gb.deb.devuan.org/merged/ ascii/non-free mainThis is right:
deb http://gb.deb.devuan.org/merged/ ascii main contrib non-freeMake similar changes in the other lines and update the cache again.
Edit: Ah, you posted while I was typing.
The microcode will be inserted into the initrd when you install the package. I think you can have both the amd and intel packages installed, but only the one for your processor will be in the initrd.
Gentoo can be completely no-dbus because you get to compile ALL your packages. (Anyone is welcome to recompile all the debian/devuan packages that require libdbus*)
The messages are letting you know that some of your hardware can use non-free firmware. You would need to enable contrib and non-free repos, update, and then install firmware-misc-nonfree if you wanted it. I don't know if it will make a difference in how your vid card performs.
Refracta-nodbus has libdbus-1-3 and libdbus-glib-1-2. I don't think they do anything except satisfy some package dependencies. A search for 'dbus' in /var/log/* shows some errors in the refractainstaller log and in Xorg.0.log.
refractainstaller_error.log:
D-Bus library appears to be incorrectly set up; failed to read machine uuid: Failed to open "/etc/machine-id": No such file or directory
See the manual page for dbus-uuidgen to correct this issue.Xorg.0.log:
(EE) dbus-core: error connecting to system bus: org.freedesktop.DBus.Error.FileNotFound (Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory)I'm not sure what question I'm supposed to answer from stevepusser's post.
This? libgtk-3-dev is installable in ascii. I tried to install it, but I already have the latest version.
Sorry about that. I did read all your posts, but I didn't re-read them every time I returned.
Anyway, I did get xfce running without any *kits and without xfce4-session in ascii. There may be better ways to do this, but this is mostly working. I doubt that there will be any changes in xfce4-session in ascii, but it might be possible for beowulf. If you start testing beowulf, you could file a bug report against xfce4-session to get things moving.
I started with a refracta-nox install in virtualbox. (standard system utilities plus some extras, no X)
Added the following packages (without Recommends):
xorg xinit xserver-xorg-legacy xfwm4 xfwm4-themes xfconf xfce4-panel xfce4-settings xfdesktop4 xfce4-terminal thunar thunar-volmanAdded needs_root_rights=yes to /etc/X11/Xwrapper.config
Put the following (exactly as posted) in /etc/X11/Xsession.d/31nokit
xfwm4 &
xfce4-panel &
xfdesktopStart the xsession as user with startx /etc/X11/Xsession
To end the xsession, I've been dropping to console and running 'init 1' as root. I'm sure there are better ways to do this, but this is convenient for testing.
rar/unrar is in non-free. You would need to add non-free to your sources.list to install it.