The officially official Devuan Forum!

You are not logged in.

#2101 Re: Other Issues » Devuan + paralleized OpenRC + KDE » 2018-03-20 21:06:46

I think kde is one of the choices for desktop environments in the ascii installer isos. If not, you can un-check the desktop options and install just the standard system utilities. When you reboot into the installed system, become root (or use sudo) and apt-get install task-plasma-desktop

For proprietary graphics drivers, see the debian wiki. The procedure for devuan is the same.

#2102 Re: Documentation » Make a live-CD with live-sdk » 2018-03-20 14:48:48

I don't know. Last time I built a heads iso was a year ago. Last time I built a plain devuan iso with live-sdk was a couple weeks ago.

Are you getting any error messages on-screen or in the logs? Is it creating an iso that doesn't work, or not making an iso at all? Is filesystem.squashfs getting created? (look in live-sdk/tmp/devuan-whatever/binary/live/)

#2103 Re: Other Issues » Devuan + paralleized OpenRC + KDE » 2018-03-20 14:11:21

ascii has kde 5:92 (I checked the version of kde-plasma-desktop). You don't need any PPA (and you should not use any PPA or non-devuan repositories.)

Installer isos are here -
https://files.devuan.org/devuan_ascii_b … aller-iso/

If you want to install openrc from the installer, choose Advanced Options from the boot menu and then choose Expert Install.
When you get to 'Load installer components from CD' choose the second item in that list, "Choose init". At some point, you will be given a chance to choose openrc. I don't know anything about parallelizing service startups in openrc. Isn't that what causes long delays in boot times with systemd?

Here's an installation guide for jessie. It will work with ascii, too.
https://git.devuan.org/dev1fanboy/Upgra … install.md

#2104 Re: Installation » Devuan Ascii Beta and repositories! » 2018-03-20 11:57:43

You have ascii and ascii-security in your sources. You could add ascii-updates.

The deb-src lines are for source packages. Unless you're planning on creating .deb packages, you can comment those lines.

The problem with synaptic (and gparted and just about anything else that requires root privileges) is that pkexec is broken. One workaround as mentioned above is to start it from a terminal as root. Another option is to edit the .desktop file so it runs a different command. Change the line that has 'Exec=synaptic-pkexec' to one of the following.

Exec=gksu synaptic
or
Exec=xterm -e 'su -c synaptic'

or replace xterm with your favorite terminal.

Note: you don't need to be in the sudo group to use gksu.
Note2: if you are in the sudo group, synaptic might work from the menu without editing the .desktop file. (It did for me in a test install.)

#2105 Re: Documentation » Make a live-CD with live-sdk » 2018-03-19 21:55:41

It needs to be in the base_packages or core_packages list to be included in the bootstrap tarball. You can add it to your blend config. Make sure you use "+=" and not just "=". You want to add to the main list, not replace it.

base_packages+=(
    build-essential
    bc
)

* `core_packages` 
  this array holds the core packages that will be installed in the bootstrap
  process.

* `base_packages` 
  this array holds the base packages that will be installed later in the
  bootstrap process.

#2106 Re: Hardware & System Configuration » Devuan and Secure Boot » 2018-03-19 21:35:11

You would need to create your own signing key. Search for 'secure boot self-signed' or something like that, and you'll find instructions.

#2107 Re: Documentation » Make a live-CD with live-sdk » 2018-03-18 10:43:14

Samhain, you need to install build-essential. Add it to one of the package lists so that it's installed before the kernel compile happens.

#2108 Re: Other Issues » Looking for recent Version of Inkscape » 2018-03-17 22:43:28

When the repos were new, backports had the wrong priority. That's been fixed. Twice. Once for packages.devuan.org and then once for pkgmaster.devuan.org. I don't know what the setting is in the repo, but apparently, it's possible to make a mistake. I like to keep backports pinned or disabled (commented out in sources.list), just in case.

If you want to check the priorities of whatever repos you have enabled, run

apt-cache policy

without any package name.

#2109 Re: Documentation » xserver-xorg-legacy in ascii » 2018-03-17 20:41:57

- tried it again after removing the packages I installed. It stopped working.
- tried if after removing dbus. Didn't work.

- installed libpam-elogind, which pulled in elogind, dbus, and something else, but not the libpolkit libraries. It works again.

#2110 Re: Documentation » xserver-xorg-legacy in ascii » 2018-03-17 13:17:12

Obviously, something has changed. I can confirm that it now works. I had to do a few things to get it to work...

- removed xserver-xorg-legacy
- disbled my display manager (lxdm)
- tried startx, it wouldn't start.

- added elogind
- still wouldn't start.

-tried it with lxdm. xorg and lxdm are running as root.

- added libpolkit-gobject-1-0-elogind and libpolkit-backend-1-0-elogind, which also pulled in libpam-elogind.
- startx works, and everything is running as user.

- tried it with lxdm again. xorg and lxdm run as root.
- tried it with lightdm. xorg and lightdm run as root.

#2111 Re: Devuan Derivatives » New Refracta Isos » 2018-03-16 15:41:56

I'm glad you bumped up this thread. This must be the one that fungus referred to, reminding me that I said I didn't know what was going on. (I say that a lot, anyway.) So here's my post-mortem on the situation:

I recently noticed that the Refracta isos that were used in this story contained some packages from ceres, and those isos were made from a system that was installed back in June. I wish I'd realized that at the time this thread was started. I would have fixed the isos and told fungus to start over. The fact that more packages from ceres were added makes the forensics more difficult.

So, bottom line - I don't know if there was something screwed up with the repo back in June or if I screwed up. I doubt that anyone will remember what was going on back then. That was right after jessie went stable and everyone in Europe went on vacation. To anyone dissatisfied with the results of installing my ascii isos, I say that I'm sorry about any inconvenience, but please keep in mind that it's called "Testing" for a reason.

#2112 Re: Devuan » ParrotSec OS, 'considered', switch to Devuan » 2018-03-16 14:05:52

Here's what I used for sources.list. No pinning, no defualt release defined. This should be enough.

deb http://pkgmaster.devuan.org/merged beowulf main contrib non-free

deb http://pkgmaster.devuan.org/merged ascii main contrib non-free
deb http://pkgmaster.devuan.org/merged ascii-updates main contrib non-free
deb http://pkgmaster.devuan.org/merged ascii-security main contrib non-free

Here are the only installed packages with 'power' in the name or description:

ii  pm-utils                          1.4.1-17                          all          utilities and scripts for power management
ii  powermgmt-base                    1.31+nmu1                         all          Common utils and configs for power management

"no kit" = no consolekit, policykit, libpolkit. I'm not relying on desktop menu entries for shutdown/reboot. I don't know if you lost any of those in the upgrade. Mine started as a debootstrap install, and I added enough to be able to function in a graphical environment. Similar to miyo or vuu-do, but not exactly the same. Compare your before and after package lists to see what you lost. Maybe something can be put back from ascii.

An easy way to keep a log of your changes is to tee the output to a file. Something like:

apt-get upgrade | tee upgrade-log

That way, if you run into some kind of dependency labyrinth, you can share the log to get some possibly useful help.

Things may change a lot over the next few weeks as some key packages in beowulf are rebuilt.

#2113 Re: Devuan » Question about devuan » 2018-03-16 12:53:36

Yes, the current stable version is based on debian jessie, which is around three years old.

Whether or not you need the latest version of something depends on your use case. Some people need the newest version of something, because that's the only version that does what they need it to do, or maybe they need the latest kernel for their new hardware. And some people are still on debian wheezy, which is five or six years old.

#2114 Re: Devuan » ParrotSec OS, 'considered', switch to Devuan » 2018-03-15 00:33:53

One important point on my smooth upgrade - I did not disable ascii repos, I just added the beowulf repo (singular) and ran an update, upgrade and dist-upgrade. At one point I had to use aptitude to give me some options. 46 out of almost 900 packages did not get upgraded.

That was on a small install with openbox, lxpanel and spacefm. No 'kits. I use sudo for shutdown and pmount for removable drives (with spacefm). Point is, if you don't have a bloated desktop environment, you should be pretty safe. Still, you should be prepared to hose the system and have to start over a few times. Each iteration will be better.

#2115 Re: Devuan Derivatives » Refracta Installer needs testers. » 2018-03-14 15:00:35

Thanks! Um, there's a new one coming soon, but I'll wait for you to report. I'm sure you'll see some things that have become invisible to me. Anyway, I just added support for full disk encryption. Only had to add four lines of code and change a couple of on-screen messages.

#2116 Re: Devuan Derivatives » Refracta Installer needs testers. » 2018-03-12 21:01:16

Here are some notes I made for a recent test iso with a newer version of the cli installer. Most of this information applies to the graphical installer, too. Options are mostly controlled in the options window instead of the config file. The parts that talk about which grub is installed and which grub packages are supplied in the iso will only apply if you have those versions of grub installed or available.

- The installer allows you to have separate /boot or /home partitions.

- The root and /home filesystems can be encrypted (without LVM).

- Other directories can be moved to separate partitions (see config file).

- Installer will create a 256MB swapfile. To change the size or to use
  a swap partition, edit the config file. (/etc/refractainstaller.conf)

- Installer uses ext filesystems by default. To use other fs types, edit
  the config file to turn on the no_format option, and format the
  partitions manually.

Partitioning the disk(s) can be done before running the installer or from
within the installer. If you are in a graphical environment, you can use
gparted. If you are not in a graphical environment, the installer will run
either cfdisk or gdisk. New feature: the installer will let you return to
the partitioner before proceeding, in case you want to change something.

For UEFI Install:
grub-efi-amd64 is installed. Near the end of the installation, you will be
given a choice to install the bootloader or not.

For BIOS Install:
grub-pc package is in the root of the filesystem, and the installer will
know what to do with it. Let the installer copy the package to /target
and install the bootloader. You can also skip the bootloader if you
plan to use another.

For 32-bit grub with 64-bit system:
grub-efi-ia32 package is in the root of the file system. Install the
package before you run refractainstaller or install it to /target in
a chroot. The installer will pause to let you do this before it installs
the bootloader. It may also work if you let the installer copy the package
to /target during the installation.

For BIOS install with GPT partition table:
You will need to create a small partition (>1M), unformatted, with
bios_grub flag in parted/gparted or EF02 in gdisk. Otherwise, you will
need to boot from a disk that has dos partition table.
More info: http://www.rodsbooks.com/gdisk/bios.html"

#2117 Devuan Derivatives » Refracta Installer needs testers. » 2018-03-12 13:15:50

fsmithred
Replies: 3

I merged the two gui scripts into one - refractainstaller-yad and refractainstaller-uefi are now refractainstaller-gui. It's not packaged yet. I moved a bunch of stuff around and shook up the code a bit, so there could be some new bugs. I've run through the install many times (scores of times) and it seems to be pretty good. But I want more guinea pigs to try it before I put it in the repo.

Copy the script from here and save it as refractainstaller-gui
https://gist.github.com/fsmithred/86594 … 07ebd41e58
You can run it from the current directory with

sudo refractainstaller-gui -d

(or be root)

You should have the latest refractainstaller-base installed from ascii repo (or newer from sourceforge.)

Changes:

refractainstaller-gui (9.3.4) unstable; urgency=low

  * Use LC_ALL=C for fdisk -l to accommodate other locales.
  * Test for gpt and for BIOS boot partition and warn if it's needed.
  * Allow re-run partitioner within the installer.
  * Improved test_hostname() to play nice with xgettext. (Blinkdog)
  * Add '-k all' to update-initramfs for cryptsetup.
  * Select EFI partition from list if there are more than one.
 
-- fsmithred <fsmithred@gmail.com>

refractainstaller-gui (9.3.3) unstable; urgency=low

  * Run grub-install after copy debs in case debconf does not run.
  * select_grub_dev if grub-pc is copied to /target and installed.
  * Use default reserved blocks with new ext filesystems.
  * Test for unformatted EFI partition.
  * Merged uefi and bios installer scripts.

-- fsmithred <fsmithred@gmail.com>

Known (very weird) bug:

If you're running in virtualbox, and you let the installer format the partitions, which it does by default, some yad windows might be malformed. This occurs in ascii, with yad-0.38. It's not a gtk3 problem, because I tried it with gtk2 versions of yad-0.38 and yad-0.40. It does not occur with yad-0.27.

It also does not occur if you select the 'Do not format' option, and you format the partitions in gparted (from within the installer or before running the installer. Doesn't matter.)

Even weirder...
If you select to install on encrypted filesystem and select 'Do not format', it won't format your /boot partition, but it must format the encrypted partition, but the bug does not manifest in this situation.

The window that's almost exclusively affected only comes up if you have the wrong grub installed. It's the window at the Pause, right before installing the bootloader, and it has buttons for Chroot, Continue, Abort and either Install Bootloader or Copy files. It may appear as a vertical line, probably 1 pixel wide, and if you grap the edge to expand the window, it will be distorted, and the title bar will say "Unnamed window". Easiest thing to do in this case is reboot (otherwise, you need to unmount /proc, /sys and /dev from /target, unmount /target/boot/efi and /target/boot if they are mounted, and then unmount /target.)

I did not see the bug when I installed on hardware, and I haven't tried installing in qemu. I've also seen it happen with the first greeting window, if I've run the installer more than once in a session.

So...  format your partitions first, and select 'Do not format' if you're in virtualbox. Install it in different ways to test all the parts. Let me know what breaks. Make some deliberate errors to see if the script is smart enough to stop you from shooting yourself in the foot. Don't test this on a production system.

Thanks,
fsmithred

#2118 Re: Devuan » ParrotSec OS, 'considered', switch to Devuan » 2018-03-12 11:57:15

You could start with a minimal install and add packages from the parrot package list, configure everything the way you want. It won't be parrotsec, it would be stanzsec. Or, you could do a minimal install and then use 'dpkg --set-selections...' on the parrot package list to reproduce the system. You'd need to remove any unavailable or unwanted packages from the list first.

It might be possible to convert a parrot install to devuan once beowulf is usable. I just checked the package list, and almost everything seems to be in the devuan repositories. Here's a list of packages in parrot that are not in the devuan repos. Some of them you don't want (systemd) and some of them are replaced by other packages (firefox-esr instead of firefox, dbus-x11 instead of dbus-user-session, gnupg in ascii vs. gpg in buster/beowulf, live-config-sysvinit instead of live-config-systemd).

clang-4.0
couchdb
dbus-user-session
firefox
gpg
gpg-agent
iio-sensor-proxy
libegl1
libgl1
libgles2
libglvnd0
libglx0
libopengl0
libpam-systemd
libtesseract4
live-config-systemd
mate-power-manager
pyrit
python-pymssql
spike
systemd
systemd-sysv
torbrowser-launcher
wifite

#2119 Re: Installation » Multiboot boot loading UEFI - no tty. » 2018-03-11 22:35:42

It's probably been close to a year since I've tried the nvidia driver on this rig (GeForce 210). I didn't have any trouble installing it. I did have to specify using an older version of gcc to match the one used to compile the kernel, but that's normal, and the installer will tell you if you have a mis-matched gcc.

I see same version of libc6-dev in devuan and debian jessie.

 *** 2.19-18+deb8u10 0
        500 http://pkgmaster.devuan.org/merged/ jessie/main amd64 Packages
        500 http://pkgmaster.devuan.org/merged/ jessie-security/main amd64 Packages
        500 http://auto.mirror.devuan.org/merged/ jessie/main amd64 Packages
        500 http://auto.mirror.devuan.org/merged/ jessie-security/main amd64 Packages

#2120 Re: Installation » Multiboot boot loading UEFI - no tty. » 2018-03-11 19:52:56

First thing to try is adding 'nomodeset' to the linux line of the boot command. Press 'e' at the boot menu to edit the selected item. Don't make it a permanent change, because once you install the nvidia driver, you may need to boot without 'nomodset' to prevent the same problem you're having.

Also, if you changed the resolution in /etc/default/grub, you may need to put it back to 640x480. I think I had to do that on one box with asrock motherboard.

#2121 Re: Devuan » ParrotSec OS, 'considered', switch to Devuan » 2018-03-09 10:45:48

Parrot is based on buster. The devuan equivalent is beowulf, but there are no beowulf repos set up yet and no work done on buster/beowulf versions of software. That would account for "breaking things all around."

Here's something you could try if you have a few spare GB of hard disk space...

1. Get Parrot Now, install it. (is is even supposed to be installed?)
2. Don't update it, and wait until we have beowulf repos up and running.
3. Upgrade it to devuan.

Another option would be to get the package list and try to recreate it in devuan.
From within a running parrot session, run dpkg --get-selections > parrot_package_list
It might even be possible to recreate it in ascii (or get something that's close to the original.)

#2122 Re: Devuan Derivatives » [MiyoLinux] MiyoLinux Accessories website » 2018-03-08 19:45:14

yad_0.38 for gtk2 debs here -
http://distro.ibiblio.org/refracta/file … _packages/

(The ones for jessie seem to work fine in ascii, so use the jessie build for i386.)

This one isn't in the sha256sum file on that page:
yad_0.38.2-1-gtk2-ascii_amd64.deb
2d0aa1dfd0a6f410e3e440fa36b875cea141ead16b2598655098e38570b013ea

#2123 Re: Hardware & System Configuration » How to replace Grub2 with Lilo? KISS multiboot configuration. » 2018-03-07 13:12:06

image=/media/username/9d2c1561-d6d7-4651-9373-bcd440c289dd/boot/vmlinuz

When you are in the process of booting devuan, the filesystem that holds the devuan kernel is not mounted on /media/username. You need to tell the bootloader the location of the kernel before anything is mounted.

I don't think the lack of an initrd in salix should have any impact on devuan. Lilo is happy to boot an OS with or without initrd. It's just a matter of getting the stanza right.

#2124 Re: Hardware & System Configuration » How to replace Grub2 with Lilo? KISS multiboot configuration. » 2018-03-06 19:00:47

I was going to suggest that you get one working and then edit the boot menu manually. You beat me to it.

Maybe you need to change the path to the salix kernel to image=/boot/vmlinuz

#2125 Re: Documentation » Replace GRUB with alternate bootloader: extlinux » 2018-03-06 13:47:57

If you're using gpt with bios, the procedure is slightly different. You may need to do the following steps first.

https://wiki.archlinux.org/index.php/sy … tion_table

GUID partition table

For a GPT, ensure bit 2 of the attributes is set for the /boot partition using gdisk. In other words, the "legacy_boot" flag must be set. Using sgdisk the command is:

# sgdisk /dev/sda --attributes=1:set:2

This would toggle the attribute legacy BIOS bootable on partition 1 of /dev/sda. To check:

# sgdisk /dev/sda --attributes=1:show

 1:2:1 (legacy BIOS bootable)

Then follow the instructions in the first post, except for the dd command.
Change the following

dd if=/usr/lib/EXTLINUX/mbr.bin of=/dev/sda bs=440 count=1

to this:

dd bs=440 count=1 conv=notrunc if=/usr/lib/syslinux/mbr/gptmbr.bin of=/dev/sda

If you want to use UUID instead of device names in the menu, edit the 'append' line to replace

root=/dev/sda1

with something like

root=UUID=xxxxxxxxxxxxxxxxxxx

(replace xxxxx... with the correct uuid.)

Board footer

Forum Software