"deborphan" is a wonderful utility
much thanks to whoever suggested "deborphan" recently to help me
clean out unused libraries. i've been fairly conservative with it,
getting rid of libs a bit at a time and making sure things still run.
someone else locally suggested to just throw caution to the winds
and run:
# aptitude purge $(deborphan)
in fact, run it until it stopped making a difference. is there any
way that can cause problems?
theoretically, i can see that it shouldn't cause any breakage. but
i was curious when i noticed that "libhal1" on this etch system is
listed as an orphan.
coming from a fedora universe, i always thought of the HAL layer as
fairly fundamental, but i guess i've stripped this server down far
enough that even the HAL library isn't being used anymore.
so is removing orphaned libs in bulk a safe thing to do? it would
*seem* to be but i just want to be sure. thanks.
a couple more questions coming shortly.
rday
p.s. starting with a server that had just over 600 packages, i'm now
down to 460, with no loss in functionality. hopefully, this will make
that final upgrade as safe as possible.
p.p.s. i'm starting to like this debian thing more and more. :-)
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
Reply to: