The officially official Devuan Forum!

You are not logged in.

#1 Re: News & Announcements » Beowulf Beta is here! » 2020-03-20 09:35:43

Beowulf beta "netinstall"  without network gives you nothing. Try using "server" or "desktop" rather.

#2 Re: Desktop and Multimedia » [SOLVED] Running X11 as non-root user » 2020-03-18 22:43:31

I don't know much about this, but my first guess would be that X is actually started via the Xorg.wrap program, which has its configuration file at /etc/X11/Xwrapper.config, and this has a line

allowed_users=console

that probably should be different.

My suggestion comes from the shallow investigation:

find /usr -perm /u=s

followed by some guess work, which made me look at man Xorg.wrap.

HTH

#3 Re: Other Issues » Can't execute program. System doesn't recognize it's location. » 2020-03-11 03:30:39

More importantly you'll need to spell the argument the way it was given,
i.e. --print-architecture rather than --print-architexture

#4 Re: Installation » Issues with very new hardware » 2020-03-09 08:24:19

rolfie  wrote:

The PC now is stuck at "waiting for /dev to be fully populated", there is no more login window poppping up now.

That same thing happens for me with the (forthcoming) beowulf installation on qemu, but this recovers by using ctrl-alt-f2 for an alternate login. Maybe it's the same for you?

#5 Re: Other Issues » Iptables standartd issue » 2020-03-01 22:00:31

Are you saying that iptables decrements the given option code by 1?

Or is it that you find it confusing that the --tcp-option parameter rejects code 0?

Rejecting option code 0 is of course consistent with the code table, since code 0 is an "end of options list" marker, and not an option code in itself.

#6 Re: Other Issues » Hwclock issue » 2020-03-01 20:44:56

@Eaglet,
you might want to read man hwclock more carefullly, and then pay special attention to the documentation of the --show option, which clearly states, in so many words:

The time shown is always in local time, even  if  you  keep  your  Hardware  Clock  in  UTC.

The options --utc and --localtime are for you to tell about time basis of your clock. The program then presents the clock reading in ISO 8601 format local time with respect to that basis.

#7 Re: Installation » Problem with *.iso file » 2020-02-20 20:15:01

When written to a flash, I assume you'd written it to /dev/sdf and not /dev/sdf1 (which is the first partition) and maybe the mdfsum from there matches the iso file?

head -c 4675600384 /dev/sdf | md5sum

#9 Re: Installation » Beowulf and MySQL » 2019-12-31 02:38:56

For whatever reasons, mysql-* are not avaiable in beowulf. You might need to try version 5.7.26-1 from unstable. Note that mysql is not forked and that Devuan reflects Debian in these packages.

#10 Re: Other Issues » [SOLVED] Apt-get show one package per line? » 2019-12-17 04:41:22

Yes, it would be nice to have a built-in option. As is, one has to resort to manual output filtering, e.g. by adding

 | sed "/^  /{s/\\b /\n  /g}"

to the command. That merely "pretty-prints" and doesn't provide the version details.

#11 Re: Hardware & System Configuration » Passwordless root execution in scripts » 2019-12-13 12:02:00

The SUID bit makes the executable run as the owner of the executable.

#12 Re: Devuan » Debian considering going systemd init only » 2019-12-08 10:38:49

hmm; don't you think the silent "non-" could be confusing for a casual visitor ?

#13 Re: Installation » Refracta Snapshot VM mount points question. » 2019-12-06 20:55:38

That missing "/" before "dev/sr0", is that a typo in this post, or a typo in "fstab"?

#14 Re: Off-topic » disable touchpad without disabling trackpoint [SOLVED] » 2019-11-19 20:35:13

I think synclient has an option to disable the "TouchPad" - see man synaptics. Though that might be co-joined with the nipple as well.

#15 Re: Installation » Problem with *.iso file » 2019-11-19 08:22:06

Yes, the 2.0.0 ISO builder(s) took the easy way out and excluded isolinux.bin from the md5sum.txt file.
That's of course one way to avoid a false negative smile

#16 Re: Installation » Problem with *.iso file » 2019-11-18 23:33:12

It's a good observation. The ISO sets of 2.0.0 and 2.1 where produced in different ways, and obviosuly the 2.1 method is somewhat lacking in care. A re-release of the latter would indeed be a good thing.

thanks,

Ralph.

#17 Re: Installation » Problem with *.iso file » 2019-11-18 21:29:06

Note that isolinux/isolinux.bin is the "El Torito boot image", and that mkisofs does something to the first 64 bytes on transfer from disk to CD/DVD image, i.e. when the .iso is created.

Thus, the published md5sum in md5sum.txt for isolinux/isolinux.bin should be ignored.

Probably someone could work out exactly what changes and how, and unless it includes some checksum of the content (esp the md5sum.txt file) and/or some time stamp, those changes could be applied to the source prior to checksumming it.

#18 Re: Other Issues » ASCII i386 repositories [deb.devuan.org] » 2019-11-12 07:43:53

ah right. I'm still in the ipv4 universe. lucky me smile

EDIT:

"onefang", who does ipv6 in his sleep, suggests that there probably are some networking issues at the client end, and that an investigation with traceroute, or traceroute6 I suppose, might tell something.

#20 Re: Other Issues » SSL error » 2019-10-12 23:23:07

brownh wrote:

"Error during connection to dev1galaxy.org/ SSL received a record that exceeded the maximum possible length (Error code: SSL_ERROR_RX_RECORD_TOO_LONG)"

When your SSL client says the above, most likely the actual response from dev1galaxy is (in clear text):

Your IP address has been tagged as dubious. If this is in error,
please contact dev1galaxy forum adminstrators on #d1g-users at freenode.

Like many/most forum sites, dev1galaxy includes a couple of attempted barriers against spam and unwanted intrusions, which results in IP addresses becoming tagged as "dubious". Due to being fully automated, it sometimes (but rarely) makes a false positive judgement, and then it requires some corrective hands-on.

#21 Re: Other Issues » 32bit packages on a 64bit system » 2019-09-22 21:29:07

Note that there is version competition between the i386 and amd64 for some packages.

In particular the util-linux group of packages have got version mismatch between these architectures (with i386 the newer). This results in a bit of a havoc if one attempts to install something (like wine32) that (indirectly) depends on one of those, as it essentially ends up wanting to replace almost everything.

It's something to careful with.

#22 Re: Installation » Installing Devuan on a 2007(!) iMac » 2019-09-20 12:57:00

Perhaps it's worth trying an extlinux boot rather than grub. There's an excellent instruction for this at https://wiki.syslinux.org/wiki/index.php?title=EXTLINUX, and in general it involves 3 steps:

  1. install the extlinux package

  2. run its boot loader installer (which replaces grub's boot loader on MBR)

  3. prepare the boot configuration for your system

Notionally it follows the same procedure as a grub boot; that the boot loader loads the configuration file, which points out where the kernel and initrd are found, and then it runs that kernel. The differences between them are probably plenty in the nitty-gritty, most of which I don't know anything about.

For your system, I think the configuration file /boot/extlinux/extlinux.conf could be along the lines of

DEFAULT Devuan
SAY Now booting Devuan using exlinux just like Ralph said...
LABEL Devuan
    KERNEL /vmlinuz
    APPEND ro root=/dev/sda1 initrd=/initrd.img vga=auto nomodeset

Check out https://wiki.syslinux.org/wiki/index.php?title=Config for details and extras. Note that I dropped in a nomodeset kernel boot parameter just for illustration.

extlinux and grub are alternative bootstrap solutions, and while you may have them both installed in the sense of their software and configurations residing on the file system, the one whose boot loader gets installed to MBR (i.e., disk block zero) is the ruling one, and you may as well purge the one you are not using. As always with these things, some people prefer the one and others prefer the other, and many people don't care either way as long as it works.

Final note: the installation disk probably uses extlinux.

#23 Re: Installation » Installing Devuan on a 2007(!) iMac » 2019-09-19 23:39:24

I think update-grub uses blkid information about partitions, not fstab. Therefore, it will install that uuid into grub.cfg regardless. Then upon boot, it's view of partitions fails to use those uuids, for whatever reasons.

A quick glance at man update-grub leads to man grub-mkconfig, which leads to info grub-mkconfig (it's always good to make documentation hard to find, isn't it smile), which suggests that you should put GRUB_DISABLE_LINUX_UUID=true in /etc/default/grub to avoid using uuid as partition identifications in grub.cfg, and instead use the "hardware path", which would be /dev/sda1 (i.e. grub refers to "where" the partition is, rather than via its content).

Then you need another update-grub to execute that wish, and everything works like magic cool

#24 Re: Installation » Installing Devuan on a 2007(!) iMac » 2019-09-19 14:21:36

The core problem seems to be with the partition identifier for the root file system. At some time it was 9cb7fe29-135e-4471-8b2c-d3e08d6ad44f, and now it appears to be something else. But that identifier has got into /etc/fstab.

So replace that to say /dev/sda1 instead.

And you would "activate" the swap space by replacing #UUID=b10e083f-db41-40e4-ac56-13e66da6ee32 (including the #) with /dev/sda2.

#25 Re: Installation » Installing Devuan on a 2007(!) iMac » 2019-09-19 10:59:18

No, If you reboot the installer, but choose the "go back" option as soon as there is one, you'll drop down to the installer steps menu, where you can cherry pick the steps. In this case, it'd be the grub installation step (I've forgotten its exact name).

Or, after having a network up, you could go C-A-F2 and chroot into /target, which then is the previously installed file system, for running grub-install manually, followed by update-grub. If you choose this path, you'll also need some bind mounts before chroot; something like this

mount -o bind /dev /target/dev
mount -t proc proc /target/proc
mount -t sysfs sys /target/sys
chroot /target
grub-install /dev/sda
update-grub
exit
reboot

If you're lucky, that'll work smile

Board footer

Forum Software