You've forgot to tell us in detail, what you really did. And, have you studied "man update-rc.d"?.. there wasn't even a single error message when I tried to remove a non-existent symbolic link.
Hi, folks:
I just came across the mentioned problem while using a persistent overlay to do a mock test on my re-mastering procedure. Apparently, it works on KNOPPIX 7.2 as some messages were spitted out after executing this command in terminal, while on 7.4.2 there wasn't even a single error message when I tried to remove a non-existent symbolic link. Besides, by looking at the time stamps of the symlinks in the /etc/rc[0-6S].d folders, it seems to me that the existing symlinks were created during the mastering stage.
So, I wonder if the update-rc.d command only works in the chroot environment (in the context of KNOPPIX 7.4.2). Any pointers will be much appreciated.
ATB,
You've forgot to tell us in detail, what you really did. And, have you studied "man update-rc.d"?.. there wasn't even a single error message when I tried to remove a non-existent symbolic link.
Thanks for the reply, Werner.
Well... if I still remember right, reading the user's manual before using any piece of equipment is still one of the golden rules on my book. So, no worries, I got that part (man update-rc.d) covered. But I am wrong about the failure of spitting out error message when a non-existent symlink is being removed. Ideally, it emits an error message when an existing symlink whose target is still in place is about to be deleted; in fact, it never do so, regardless of the version of KNOPPIX.
Removing the virtualbox symlinks in /etc/rc*.d is actually what I would like to do. According to the man page of update-rc.d, it shall remove the named symlink, regardless of the existence of /etc/init.d/virtualbox, if the -f argument has also been given. To be crystal clear, the files (/etc/init.d/virtualbox) from VBox 4.2.10+dfsg-1 and 4.3.14+dfsg-1 are identical. So, it's unlikely that the content of the script causes the problem. To be more certain, all the symlinks in /etc/rc?.d are supposed to be wiped out by the following code:
It isn't surprising to see all the symlinks are still intact. So, it seems to me that the update-rc.d and/or its related scripts are where the problem lies. For some reason, removing symlink is the only thing it cannot do.Code:# with root privilege INSANE=`find /etc/rc?.d -type l | sed 's/.*[SK][0-9][0-9]//' | sort | uniq` for i in $INSANE ; do update-rc.d -f "$i" remove ; done
ATB,
I've tested it for myself, and yes, update-rc.d (part of sysv-rc 2.88dsf-53) within Knoppix 7.4.2 is buggy and neither the option "-n" nor the parameter "remove" works. Within Knoppix 7.2.0 there is sysv-rc 2.88dsf-41.
Many thanks for your time, Werner. The sysvc-rc shipped with 7.4.2 is KNOPPIX's own breed; I don't really mind the removal function isn't working , and just need to keep an eye on those folders and remove the symlinks after purging the packages.
--- Really Off Topics ---
To folks who have been following this thread:
Check out KNOPPIX's own repository for the patched version of xscreensaver if you are tired of the "very old" warning message.
ATB,
For people who don't know this server:Check out KNOPPIX's own repository
http://debian-knoppix.alioth.debian....kages/?C=M;O=D
Dell PowerEdge FX2 FX2S Enclosure - 4x PowerEdge FC640 w/ 8x Gold 6132 112C 1TB
$2699.99
Dell PowerEdge FX2 FX2S Enclosure - 4x PowerEdge FC640 w/ 8x Gold 6134 64C 1TB
$3299.99
DELL M630 BLADE SERVER x2 XEON E5-2660V3 @ 2.6GH H730 PERC HDD CADDIES 16GB FC
$50.00
2 x HP ProLiant BL460c (447707-B21) Blade Servers No RAM No HDD
$30.00
Dell PowerEdge M620 0F9HJC Blade Server 2*E5-2670 2.60GHz 192GB RAM 2*300GB SAS
$103.99
Dell PowerEdge M630 Blade Server 1x Xeon E5-2630 v4 CPU / Motherboard P/N 0R10KG
$69.99
HP BL460c 2SFF GEN9 Blade Server 2x 12 Core Xeon E5-2670 v3 256GB RAM 600GB HDD
$199.99
Dell PowerEdge M620 Blade Server
$39.99
Dell PowerEdge M620 Blade Server 2x E5-2670 2.6Ghz 16-Cores 256gb 2x 146gb 15k
$244.99