When a package is installed or upgraded and it require a startup script, update-rc.d is invoked to set up the appropriate links in the runlevels to start the service at bootime. If a user want to install a package but he don't want to start up the related service at boot time, he have to invoke "update-rc.d -f <script_name> remove". But if now he upgrade the related package, the start up links in the various runlevel are created again ! We can wonder about why a user have to install a package and not to startup the service, but "why he can't do such a thing" ? We can add a database to update-rc.d that record the user preference and use it as a run-level manager. What do you think about it ? Cheers. -- - Zack - Stefano Zacchiroli <firstname.lastname@example.org> ICQ# 33538863 Home Page: http://www.students.cs.unibo.it/~zacchiro Undergraduate Student of Computer Science at University of Bologna, Italy SysAdm of verdicchio.students.cs.unibo.it (220.127.116.11) "Information wants to be Open"
Description: PGP signature