Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
#581704 - sysvinit: Failing to run init script (or ordering problem) after upgrade from startpar to makefile - Debian Bug report logs
(at bugs.debian.org)
It’s safe again to dist-upgrade for you, as slh has added a fixed package into the sidux repository.
B) You dist-upgraded without the fixed package
You need to edit concurrency setting
sed -i "/^CONCURRENCY\=/d" /etc/default/rcS
C) You already rebooted, and find your system hangs in the boot process
Boot again with cheat code 1 (gets you into runlevel 1), press Crtl+D when asked, and apply the fix B).
Your system will boot normally again after that.
Either wait, do the sed thing , or install the fixed sidux packages.
For those that use smxi:
smxi checks for sidux sources if it doesn't find sidux in your sources.list it implements the sed fix after dist-upgrade is complete.
Raspberry PI 400 Distro: Raspberry Pi OS Base: Debian Sid Kernel: 5.15.69-v8+ aarch64 DE: MATE Ram 4GB Debian - "If you can't apt install something, it isn't useful or doesn't exist" My Giant Sources.list
At least there's a fix. For people who aren't clear on what the sed script above does, it simply removes the CONNCURENCY line from /etc/default/rcS. This forces sysvinit to use a setting that will boot properly.
mzilikazi wrote:So did you learn the hard way like I did?
No saw the bug said whatever, went ahead and did apt-get dist-upgrade then just a few minutes ago h2 asked me about it in #smxi, I did apt-get update and the sidux packages showed up. Weird crap like this is the only reason I keep sidux in my sources,list.
The bug didn't bite me since I rarely reboot.
Raspberry PI 400 Distro: Raspberry Pi OS Base: Debian Sid Kernel: 5.15.69-v8+ aarch64 DE: MATE Ram 4GB Debian - "If you can't apt install something, it isn't useful or doesn't exist" My Giant Sources.list
The fixed packages have been uploaded to Debian mirrors.
Raspberry PI 400 Distro: Raspberry Pi OS Base: Debian Sid Kernel: 5.15.69-v8+ aarch64 DE: MATE Ram 4GB Debian - "If you can't apt install something, it isn't useful or doesn't exist" My Giant Sources.list
did sidux actually add a CONCURRENCY "startpar" "shell" entry to /etc/default/rcS?
did it add any parallelism to boot? liquoix
Bugs, did you notice any difference with makefile?
I didn't...
In memory of Ian Ashley Murdock (1973 - 2015) founder of the Debian project.
/etc/default/rcS
#
# /etc/default/rcS
#
# Default settings for the scripts in /etc/rcS.d/
#
# For information about these variables see the rcS(5) manual page.
#
# This file belongs to the "initscripts" package.
Other than when I boot it saying something about starting in something using makefile in run level S. I haven't noticed any difference.
Raspberry PI 400 Distro: Raspberry Pi OS Base: Debian Sid Kernel: 5.15.69-v8+ aarch64 DE: MATE Ram 4GB Debian - "If you can't apt install something, it isn't useful or doesn't exist" My Giant Sources.list
thanks
I see that message now right after
INIT: Entering runlevel:
and at shutdown it shows up as well....
you can change the style to either startpar-style or makefile-style concurrent boot....
both startpar and shell give startpar-style
and makefile gives makefile-style
And I don't notice any difference in the way the scripts are loaded, either...
In memory of Ian Ashley Murdock (1973 - 2015) founder of the Debian project.
I find it interesting that I find a post on sidux, and AbsentMind gets on me about "advertise
n" sidux. I did apply a corrected post after my inital one, providing more substantial information.
I am amused now...
Sorry to burst your bubble but as nice as Sidux may be it is it's own distro and although based on Debian, it is not actually Debian.
Now to look at your post from a differnt angle. Advertisement for something not approved by administration is concidered spam. As your post is (as stated by you) to promote (advertise) Sidux. Who gave you authorzation to advertise it here? Or should I concider your users account one use for spamming and eliminate you ability to post?
I do appreciate the sid/sidux update notice though. I forget to check current deployment statuses.
Thank You,
Mauser1891
AMD A6-3400M 8G DDR3 Samsung EVO 120 powered Gateway laptop
FX-8350, 7970, 32G DDR3, 8G RamDisk/SSD/SSHD/HD, Win 8.1 Pro desktop
I found this thread helpful while pursuing an upgrade path from Ubuntu Karmic->Lucid -> DebianSid.
For a while after eliminating upstart I had to hold syssvinit at 2.67 because of LSB problems,
These have now disappeared and I've set concurrency to makefile .. whiich I unnderstand is the mechanism by which iniit scripts can signal their dependencies when defining the boot sequence.
My apt sources list and preferences attempts to be ( Debian)flavour agnostic. - it points to debian, ubuntu & sidux repos as well as a bunch of Launchpad PPA's
The system is pinned to Sid - but with occasional forays into Ubuntu Maverick - for instance to grab the latest 2.6.35 kernel- which helped overcome my last WiFi problems.
Get rid of the Ubuntu repos in your sources.list, if you need a newer kernel than what is in the Debian repos use the liquorix kernel.
Linux craigevil 2.6.35-2.dmz.1-liquorix-686 #1 ZEN SMP PREEMPT Sun Aug 15 00:44:01 UTC 2010 i686 GNU/Linux
Raspberry PI 400 Distro: Raspberry Pi OS Base: Debian Sid Kernel: 5.15.69-v8+ aarch64 DE: MATE Ram 4GB Debian - "If you can't apt install something, it isn't useful or doesn't exist" My Giant Sources.list
Search the forum here and at linuxquestions.org, Ubuntu is not binary compatible with Debian, The depends can be different, where things get installed can be different, version numbers can be different, any number of things which can easily destroy a working Debian system.
There are very few packages that Ubuntu are in the Ubuntu repos that aren't in a Debian repo. If you can't find something look at the Giant sources.list in my signature.
Raspberry PI 400 Distro: Raspberry Pi OS Base: Debian Sid Kernel: 5.15.69-v8+ aarch64 DE: MATE Ram 4GB Debian - "If you can't apt install something, it isn't useful or doesn't exist" My Giant Sources.list
craigevil wrote:Search the forum here and at linuxquestions.org, Ubuntu is not binary compatible with Debian, The depends can be different, where things get installed can be different, version numbers can be different, any number of things which can easily destroy a working Debian system.
Debian is indestructible. Overwriting some binaries with others that are not compatible with the system can still be repaired through a Live Linux CD. As long as one knows what is wrong, repairs are always possible. After all, what is an operating system if not a collection of files?
Debian == { > 30, 000 packages }; Debian != systemd
The worst infection of all, is a false sense of security!
It is hard to get away from CLI tools.