Re: Sysv-rc (Urgent)
On Monday 07 September 2009 03:08:49 debian-user-digest- requ...@lists.debian.org wrote: Purging bittorrent and the othes leaves me with obsolete init.d scripts from jackd and timidity. I want these packages but not necessarily the init.d scripts to start them. (In fact, Timidity now has a separate daemon package.) So how do I fix this. The correct way to disable is not to remove the symlinks (which insserv complains about) but to rename the S?? symlinks to K?? symlinks. See also man(8) update-r.cd If you do that, then the upgrade check should no longer complain. Not necessarily. The timidity symlinks are all k's. Since I do not want jackd starting at boot and all the init.d script does is say to change /etc/default/jackd if I do want it, I can dispense with that one. For running timidity system-wide at bootup, there is now a separate timidity- daemon package to this init.d script is actually obsolete. So I move them out of the way. My questions remain: 1. Were I to upgrade the hddtemp and remove the offending init.d scripts and get a clean test, is it really safe to go over to the new bootup and do I still have the choice? 2. It may be a while before many debianers will in fact migrate. Some may never do so. Sysv-rc is uninstallable if the safety-check comes up with errors. Since, once these errors are fixed and one rally wants to go over, one must run dpkg-reconfigure, why should sysv-rc be unconfigured? This should probably be a bug-report. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Sysv-rc (Urgent)
Am 07.09.2009 15:04, schrieb David Baron: 2. It may be a while before many debianers will in fact migrate. Some may never do so. Sysv-rc is uninstallable if the safety-check comes up with errors. Since, once these errors are fixed and one rally wants to go over, one must run dpkg-reconfigure, why should sysv-rc be unconfigured? This should probably be a bug-report. That is indeed a bug, and I guess it's http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=545261 which you encountered. It's already been fixed and a new package has been uploaded Cheers, Michael signature.asc Description: OpenPGP digital signature
Re: Sysv-rc (Urgent)
On 2009-09-06 19:30:40 +0300, David Baron wrote: The upgrade from sid finds it unsafe to change to dependency based boot and leaves it unconfigured with a couple of missing .rc files. Unconfigured? This is probably the following bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=545261 but it is now fixed (sysv-rc is now configured as expected, even though the migration hasn't been enabled yet due to bugs in other packages). -- Vincent Lefèvre vinc...@vinc17.org - Web: http://www.vinc17.org/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.org/blog/ Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Sysv-rc (Urgent)
The upgrade from sid finds it unsafe to change to dependency based boot and leaves it unconfigured with a couple of missing .rc files. 1. Is the system bootable at this point? 2. Downgrade this to testing? I did that but can always re-upgrade. 3. Leaving the co-version sysvinit-utils for now until this is resolved but the testing and previously installed sid versions do not match. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Sysv-rc (Urgent)
On 2009-09-06 18:30 +0200, David Baron wrote: The upgrade from sid finds it unsafe to change to dependency based boot and leaves it unconfigured with a couple of missing .rc files. What are .rc files? 1. Is the system bootable at this point? I think yes, you will get the same boot order as before. 2. Downgrade this to testing? I did that but can always re-upgrade. This might not be safe, there are numerous changes and I don't know if downgrades have been tested at all. 3. Leaving the co-version sysvinit-utils for now until this is resolved but the testing and previously installed sid versions do not match. It seems that sysvinit lacks a versioned dependency on sysvinit-utils, because /sbin/bootlogd has moved from sysvinit to sysvinit-utils in version 2.86.ds1-66. If you don't use the bootlogd (BOOTLOGD_ENABLE=No in /etc/default/bootlogd) it shouldn't matter, though. Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Sysv-rc (Urgent)
On Sunday 06 September 2009 21:23:10 debian-user-digest- requ...@lists.debian.org wrote: The upgrade from sid finds it unsafe to change to dependency based boot and leaves it unconfigured with a couple of missing .rc files. What are .rc files? Reinstalling over testing did not flag them again! 1. Is the system bootable at this point? I think yes, you will get the same boot order as before. 2. Downgrade this to testing? I did that but can always re-upgrade. This might not be safe, there are numerous changes and I don't know if downgrades have been tested at all. So I put the new one on.. 3. Leaving the co-version sysvinit-utils for now until this is resolved but the testing and previously installed sid versions do not match. It seems that sysvinit lacks a versioned dependency on sysvinit-utils, because /sbin/bootlogd has moved from sysvinit to sysvinit-utils in version 2.86.ds1-66. If you don't use the bootlogd (BOOTLOGD_ENABLE=No in /etc/default/bootlogd) it shouldn't matter, though. I installed this as well. Probably has the rc files here Interesting that the problems preventing the migration are: 1. bittorent left obsolete init.d script I have no need for bittorent, actually. 2. jackd left behind and obsolete init.d script. I do not start jackd using this script since many audio things do not work with it. I need to use jackd manually. 3. Mono-xsp left behind an obsolete init.d script. This is a standalone asp.net knockoff--I can remove this as well since were I to use mono-xsp, I would do so using apache. 4. Package pcscd removed by not purged. I am purging it. 5. Reniced removed by not purged. I use and instead of this one. Purge it. 6. Timidity left behind and obsolete init.d script. 7. Virtual Box 2.0 removed by not purge (OK, already, change by to but)-- Sun should fix this. Vbox upgrades do not replace the old one--one must remove it and then install the new one. Shame on them. Purging them. 8. K20hddtemp missing LSB tags and overrides. The only one really relevant? Purging bittorrent and the othes leaves me with obsolete init.d scripts from jackd and timidity. I want these packages but not necessarily the init.d scripts to start them. (In fact, Timidity now has a separate daemon package.) So how do I fix this. Then there is the k20hddtemp. I have had insserv around for a while but never used it because I was afraid to end up with an unbootable system and no recourse. Since insserv warns that one cannot turn back while debian maintainers say best to go ahead what to do? Actually, sysv-rc becomes just one of a number of unconfigured packages--all those java-gcj ecj things which I would just as well get rid of except openoffice seems to need one or more of these. Would love to see this resolved. I use Sun's own Java. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Sysv-rc (Urgent)
Hint: your mails are easier to read if you put a blank line between citations and your reply. On 2009-09-06 21:47 +0200, David Baron wrote: On Sunday 06 September 2009 21:23:10 debian-user-digest- requ...@lists.debian.org wrote: The upgrade from sid finds it unsafe to change to dependency based boot and leaves it unconfigured with a couple of missing .rc files. What are .rc files? Reinstalling over testing did not flag them again! That does not answer my question, I still do not know what .rc files are in the first place. Interesting that the problems preventing the migration are: 1. bittorent left obsolete init.d script I have no need for bittorent, actually. 2. jackd left behind and obsolete init.d script. I do not start jackd using this script since many audio things do not work with it. I need to use jackd manually. 3. Mono-xsp left behind an obsolete init.d script. This is a standalone asp.net knockoff--I can remove this as well since were I to use mono-xsp, I would do so using apache. 4. Package pcscd removed by not purged. I am purging it. 5. Reniced removed by not purged. I use and instead of this one. Purge it. 6. Timidity left behind and obsolete init.d script. 7. Virtual Box 2.0 removed by not purge (OK, already, change by to but)-- Sun should fix this. Vbox upgrades do not replace the old one--one must remove it and then install the new one. Shame on them. Purging them. 8. K20hddtemp missing LSB tags and overrides. The only one really relevant? Purging bittorrent and the othes leaves me with obsolete init.d scripts from jackd and timidity. I want these packages but not necessarily the init.d scripts to start them. (In fact, Timidity now has a separate daemon package.) So how do I fix this. Remove the obsolete scripts by hand. Then there is the k20hddtemp. You should upgrade the hddtemp package, the missing LSB info has been fixed in version 0.3-beta15-41. I have had insserv around for a while but never used it because I was afraid to end up with an unbootable system and no recourse. Since insserv warns that one cannot turn back while debian maintainers say best to go ahead what to do? The warning that the system may become unbootable is in fact greatly exaggerated, I have yet to see a bug report about that. Most problems with incorrect LSB headers are more subtle and only play a role under relatively obscure circumstances (like having /usr on NFS). Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Sysv-rc (Urgent)
David Baron wrote: Purging bittorrent and the othes leaves me with obsolete init.d scripts from jackd and timidity. I want these packages but not necessarily the init.d scripts to start them. (In fact, Timidity now has a separate daemon package.) So how do I fix this. The correct way to disable is not to remove the symlinks (which insserv complains about) but to rename the S?? symlinks to K?? symlinks. See also man(8) update-r.cd If you do that, then the upgrade check should no longer complain. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: Sysv-rc (Urgent)
Hi,
On Sun, Sep 06 2009, Sven Joachim wrote:
Hint: your mails are easier to read if you put a blank line between
citations and your reply.
On 2009-09-06 21:47 +0200, David Baron wrote:
On Sunday 06 September 2009 21:23:10 debian-user-digest-
requ...@lists.debian.org wrote:
The upgrade from sid finds it unsafe to change to dependency based boot
and leaves it unconfigured with a couple of missing .rc files.
What are .rc files?
Reinstalling over testing did not flag them again!
That does not answer my question, I still do not know what .rc files
are in the first place.
:rc file: /R-C fi:l/ /n./ [Unix: from `runcom files' on
the {CTSS} system ca.1955, via the startup script
`/etc/rc'] Script file containing startup instructions for an
application program (or an entire operating system), usually a text
file containing commands of the sort that might have been invoked
manually once the system was running but are to be executed
automatically each time the system starts up. See also {dot
file}, {profile} (sense 1).
:dot file: [Unix] /n./ A file that is not visible by default to
normal directory-browsing tools (on Unix, files named with a
leading dot are, by convention, not normally presented in directory
listings). Many programs define one or more dot files in which
startup or configuration information may be optionally recorded; a
user can customize the program's behavior by creating the
appropriate file in the current or home directory. (Therefore, dot
files tend to {creep} -- with every nontrivial application
program defining at least one, a user's home directory can be
filled with scores of dot files, of course without the user's
really being aware of it.) See also {profile} (sense 1), {rc
file}.
manoj
--
This body is worn out with age, a nest of diseases and falling apart.
The mass of corruption disintegrates, and death is the end of life. 148
Manoj Srivastava sriva...@acm.org http://www.golden-gryphon.com/
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
