You are not logged in.
Developers, Please add this code
The package is drawn from Debian's repositories (using amprolla) so if you want the init script to be modified then you will have to ask the Debian package maintainer instead.
And your modifications have some issues:
if [ ! $(lsmod | grep jitterentropy_rng) ]; then
No need to use the [ test and no need for lsmod:
if ! grep -q jitterentropy_rng /proc/modules; thenif [ ! $(cat /etc/modules | grep jitterentropy_rng) ]; then
Useless use of cat and again, no need for [:
if ! grep -q jitterentropy_rng /etc/modules; thenHTH
EDIT: on reflection I really don't think an init script should be changing system configuration files. Just the modprobe should be sufficient.
It was intended as genuine advice rather than a criticism.
The grub> prompt indicates that grub.cfg can't be found or that it does not contain any menuentry stanzas so check /boot/grub/grub.cfg (or post it here if you're not sure) and also run the set command from the prompt to list all the variables and find where GRUB is looking for the configuration file.
Another possibility is that this is a UEFI system and the firmware is loading the wrong NVRAM entry. Use the efibootmgr -v command to list all of the boot entries. Check for /sys/firmware/efi to confirm that the system is booted in UEFI mode. See https://wiki.archlinux.org/index.php/Un … t_efivarfs if the NVRAM variables cannot be listed even if the box is booted in UEFI mode.
Which log?
No idea, sorry. FWIW the systemd journal is excellent for stuff like this. *dives for cover*
when I use a search engine, for anything to do with Devuan, I always get answers for Debian.
Most answers applicable to Debian can also be used for Devuan.
What is it that you want from this mysterious "bind-utils" package? http://www.linuxfromscratch.org/blfs/vi … utils.html suggests that the bind9 package will provide everything you need.
There is a specific bind-utils package in Debian's experimental repositories, perhaps you could try backporting that.
I found nothing on the logs.
Which logs did you check? Perhaps you should upload them to a pastebin and share the link here so that we can check to see if you missed anything.
If I had to guess I would suggest that the problem lies here:
network-manager | default
^ That starts on the same runlevel as Opensmtpd so it might be running too late and causing the problem.
Perhaps try ifupdown (ie, /etc/network/interfaces & /etc/init.d/networking) instead of NetworkManager, that starts at the sysinit runlevel and so would ensure that the network is up before Opensmtpd starts.
See interfaces(5) & https://wiki.debian.org/WiFi/HowToUse#W … d_WPA2-PSK for the configuration methods.
Can we see the entire (un-grep'd) output? I only use OpenRC with Alpine Linux so I'm not sure how Devuan order their services.
Otherwise check the logs for any clues.
Why it is alluring to so many people?
Well the 5nm process is pretty good, especially considering that Intel are still stuck with their antediluvian 14nm dies, and the reported benchmarks are actually quite impressive. But Ryzen still kills it ![]()
Anyway I'm with steve_v — Apple are a bunch of ****s. I threw a massive party when Steve Jobs died.
"i5" is pretty meaningless in isolation because it applies to all CPUs from 2009. FWIW beowulf won't support 10th generation Intel hardware even with the backported kernel because the intergrated graphics chip needs a newer Mesa version.
Did you try using fsck on the partition?
For example
# fsck /dev/sdc1Replace 1 with the correct partition number.
The varnish package is drawn from Debian's repositories so it may be best to reproduce this bug in a Debian system and open a bug report against their package with the patch attached. Just don't mention Devuan in the bug report, some of the Debian developers are funny about that.
Threw away Openbox in favor of CWM
Very nice :-)
Is that still tint2?
Would I edit with 'Buster' option?
Sorry, I don't understand the question but to install the non-free firmware /etc/apt/sources.list should look like this:
deb http://deb.devuan.org/merged beowulf main contrib non-free
deb http://deb.devuan.org/merged beowulf-updates main contrib non-free
deb http://deb.devuan.org/merged beowulf-security main contrib non-freeThen use
# apt update
# apt install firmware-misc-nonfreeDevuan already supports the 64-bit ARM architecture (arm64) but the various subsystems on their M1 SoC will need to have drivers added to the kernel, along with drivers for the rest of the attached hardware.
EDIT: and bootloader support as well, which will probably be a challenge because Apple will try to lock it out as much as possible.
There's also live-sdk.
EDIT: and Debian's live-build but I haven't been able to make that work with sysvinit as PID1. Of course that could just be because I'm useless ![]()
Check the enabled services with
rc-updateIf it's not listed then try to add it with
rc-update add opensmtpdThat's strange, the LXQt desktop metapackage only lists wicd as a Recommends and it also has network-manager-gnome or nm-tray as alternatives for that.
Does this work:
apt install --simulate nm-tray wicd{,-cli,-curses,-daemon,-gtk}-If that still results in a mass removal then just disable wicd instead:
# update-rc.d wicd defaults-disabledI am not talking about the proprietary drivers. The open source nouveau drivers may need the proprietary NVIDA firmware (not driver) for them to work properly and provide hardware acceleration.
IT WORKS!
Fantastic. Please edit the title of the thread (in the first post) and prepend [SOLVED] to help others who may encounter this issue.
why the system suggests installing systemd?
Perhaps because systemd allows for socket activation, which is not possible under sysvinit. But that's just a guess.
And please also note that those packages are still marked for autoremoval so you should attend to that unless you don't want them.
The aptitude command auto-autoremoves so you may have removed a metapackage that depends on those packages. See also http://forums.debian.net/viewtopic.php?t=104157
Why did you install the backported libpcsclite1 package anyway? It's usually best to stick to the stable versions whenever possible.
root@portable:/etc/apt/sources.list.d# apt -s -o Debug::pkgProblemResolver=yes pcscd E: Command line option 's' [from -s] is not understood in combination with the other options.
Oops, sorry:
apt -s -o Debug::pkgProblemResolver=yes install pcscdAnd please use code tags when posting terminal output (as I have added to your quotes), it greatly aids readability.
EDIT: ah, I see the problem — you have the backported version of the libpcsclite1 dependency installed so you need the backported pcscd version:
# apt install -t beowulf-backports pcscdOr try aptitude instead, that would probably offer to upgrade pcscd from beowulf-backports.
eid-mw : Depends: pcscd but it is not going to be installed eid-viewer : Depends: pcscd but it is not going to be installed
Well the package is there. What happens if you try to install it manually?
# apt install pcscdIf the error message is non-informative then debug the resolver:
apt -s -o Debug::pkgProblemResolver=yes pcscd500 http://files2.eid.belgium.be/debian stretch/main amd64 Packages release o=FedICT,a=oldstable,n=stretch,l=FedICT,c=main,b=amd64 origin files2.eid.belgium.be 500 http://files.eid.belgium.be/debian stretch/main amd64 Packages release o=FedICT,a=oldstable,n=stretch,l=FedICT,c=main,b=amd64 origin files.eid.belgium.be
^ So those are the dodgy third-party repositories and the reason why they've broken your box is because you've tried to use their stretch repositories rather than the buster versions. So change stretch to buster in the sources file then update the package database and try installing the packages again.
Use this to find the relevant sources file:
grep 'eid.belgium.be' /etc/apt/sources.list{,.d/*}any reason not to remove wicd?
Probably not but you can check by simulating a removal:
aptitude --simulate purge wicd{,-cli,-curses,-daemon,-gtk}