You are not logged in.
Also perhaps check with a live ISO that boots with systemd to see how udev handles the devices.
Is there actually much delay when starting the desktop? It could be that the eudev stuff is done in the background after a working desktop is reached. I've seen that before with systemd-analyze output.
Looks like eudev takes forever. Do you have many devices connected?
You could try udev instead but that's from the systemd crowd so people might throw rotten fruit at you.
Glad you got it working.
sed -i 's|#!/usr/bin/python|&3|' pybootchartgui.py
./pybootchartgui.pyEDIT: monkey patching ftw! ![]()
bash: ./pybootchartgui.py: /usr/bin/python: bad interpreter: No such file or directory
freeartist@devuan:/usr/bin$ sudo ln -fs python3 python
It would have been *much* better to change the shebang in pybootchartgui.py instead of mangling your system. Remove that symlink.
No path given, trying /var/log/bootchart.tgz warning: path '/var/log/bootchart.tgz' does not exist, ignoring.
So I presume you didn't boot with the required initcall_debug printk.time=y init=/sbin/bootchartd kernel parameters then?
This is like pulling teeth... ![]()
Was the script executable?
Sorry, that was a stupid question. Files in /etc/profile.d/ are sourced rather than executed. D'oh!
Was the script executable?
Links to the .debs are in my exclamation mark (see fsmithred's post just above mine for bootlogd), along with an explanation of how to get bootchart working in chimaera.
The command can be added to /etc/rc.local but that feels hacky af.
Have you tried
# virsh net-autostart default^ I think that should enable it to auto start without having to run your command.
Reference: https://libvirt.org/sources/virshcmdref … start.html
I want to run a 'sudo' command at login.
Why do you want to do that? What are you trying to achieve?
See also https://xyproblem.info/
I would post a link on FDN but that surely would get me banned
Yeah, I'm sure that would blow @donald's tiny... mind ![]()
Nice article. The author even links to dasein's Revisionist History thread so they clearly know their stuff. I might start buying that magazine now...
is this necessary to get rid of slim ?
There is a metapackage installed that has x-display-manager listed as a (virtual) dependency. If slim is removed lightdm is needed to satisfy the dependency.
If you prefer (for example) GDM instead use
# apt install slim- gdm3But you don't need to remove slim at all — just disable it:
# update-rc.d slim disableThis will have to be repeated if the slim package is updated.
To actually remove slim see https://forums.debian.net//viewtopic.php?f=16&t=104157, which explains how to deal with the metapackage problem.
A "core dev" left
Ha! Good riddance Tobin you fat cunt.
"Mentally ill" my ass. Autism != mental illness. FFS.
EDIT: apologies for the off-topic post. I couldn't contain my glee.
I think that's the standard Xfce dock. I might be wrong though.
Looks like Xfce with Faenza icons. The wallpaper is a picture of the Victory Arch in Baghdad.
Did you check the LightDM logs?
I don't like bluetooth, for some obvious reasons, insecurity and its supposedly hazardous in other ways...
Does OpenBSD disable it by default?
OpenBSD does better than that — there is no Bluetooth support at all ![]()
Is a wifi card needed in an OpenBSD router, I think it does probably right?
Only if you want to provide a wireless access point. Ethernet-only routers are a thing.
A card that supports HostAP mode is required though, see https://www.openbsd.org/faq/faq6.html#Wireless for a list of chipsets that should work.
I assume the MALI isn't needed for a router?
I can't see the point of a graphics card on a router, no.
how do I connect to the device, to make wifi zones and then of course, connect other devices to them.
Btw, I assume you don't connect this to a modem directly right?
See the FAQ. It is comprehensive.
For any specific implementation-related questions that aren't covered by the documentation you can open a thread over at http://daemonforums.org — I'm also a member there and the community is very knowledgable and friendly. Just bear in mind that it's a BSD forum so a high signal-to-noise ratio is preferred for all posts. Don't chatter like you would on a Linux forum ![]()
Works for me:
root@devuan:~# cat /etc/devuan_version
daedalus/ceres
root@devuan:~# modprobe -v zram
insmod /lib/modules/5.18.0-1-amd64/kernel/mm/zsmalloc.ko
insmod /lib/modules/5.18.0-1-amd64/kernel/drivers/block/zram/zram.ko
root@devuan:~# file /dev/zram0
/dev/zram0: block special (253/0)
root@devuan:~# echo 1G>/sys/block/zram0/disksize
root@devuan:~# mkswap /dev/zram0
Setting up swapspace version 1, size = 1024 MiB (1073737728 bytes)
no label, UUID=0b9792b3-e7ce-4b5e-84f7-2f4dc3247db2
root@devuan:~# swapon /dev/zram0
root@devuan:~# cat /proc/swaps
Filename Type Size Used Priority
/dev/zram0 partition 1048572 0 -2
root@devuan:~#If you have errors post them here in full.
EDIT: zram-tools is installed but udisks2-zram is not.
EDIT2: and yes, it also works in chimaera. I tried it there first then brought the system up to daedalus to confirm the 5.18 kernel also works.
wondering if its possible to do something similar to this on a pinebook single board device:
Yes: https://bsandro.tech/posts/openbsd-7.1- … rockpro64/
See also https://cdn.openbsd.org/pub/OpenBSD/7.1 … TALL.arm64
how much, bloatware does Devuan use in the situation of a router by default?
Lots. OpenBSD's install71.iso will happily run in QEMU with only 128MiB of RAM. Devuan's chimaera netinstall ISO image won't even start with so little memory available.
OpenBSD is the absolute best choice for a router IMO. Accept no substitute. And don't install any ports. Base system ftw!
EDIT: and arm64 is particularly good because the OpenBSD developers have managed to remove almost all ROP gadgets:
pager /proc/meminfo /bin/sh : command not foundso far the pager in busybox and/or the d-i
![]()
Ha! Yes, well, my point was more general — why cat the content of a file to another file and then read the other file when you could just use a pager (any pager) to read the file. But anyway...
messed up USB sticks, which do not behave as one would expect when isos are copied to them without proper complete erasing old partitions, mbr GBT and the like.
^ This raises my suspicions.
How exactly did you transfer the ISO image to the USB stick?
If you used the correct method then the image itself would erase old partitions.
Failure trying to run : chroot "/target" dpkg --force-depends --install /var/cache/apt/archives/some......deb
Is that everything you see when you check TTY4?
There is https://forums.debian.net/viewtopic.php?t=79785 in which the OP was trying to use debootstrap on an NTFS partition. Would that apply here?
cat /proc/meminfo > meminfo more meminfo
Lolwut?
pager /proc/meminfo![]()
silently fails the installer without telling the true reason
check TTY4 for full error messages
So press <ctrl>+<alt>+F4 to read them (or just <alt>+F4 if you're using the non-graphical installer).
there is no top and the ps of busybox has no options. so I cannot see how much RAM is in use.
cat /proc/meminfoEDIT: check TTY4 for full error messages.
The hardening-runtime package applies many of the sysctl settings suggested by madaidan.