Re: unstable system
On Ma, 16 dec 14, 11:35:26, jesus_...@posteo.de wrote: Hello everyone! I don't no which package really cause the errors, so I write to the mailing list. When I'm using my wifi-stick USRobotics - USR8005423 my syslog file don't stop growing till my root partition is overflowing. This error always repeats: Do you have the package logrotate installed? Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
unstable system
Hello everyone! I don't no which package really cause the errors, so I write to the mailing list. When I'm using my wifi-stick USRobotics - USR8005423 my syslog file don't stop growing till my root partition is overflowing. This error always repeats: Dec 16 09:28:28 jonny kernel: [ 24.672140] usb 2-1.5: firmware: failed to load zd1211/zd1211b_ub (-2) Dec 16 09:28:28 jonny kernel: [ 24.672233] usb 2-1.5: Direct firmware load failed with error -2 Dec 16 09:28:28 jonny kernel: [ 24.672235] usb 2-1.5: Falling back to user helper Dec 16 09:28:28 jonny kernel: [ 24.672799] zd1211rw 2-1.5:1.0: couldn't load firmware. Error number -12 There is a firmware package for this stick (firmware-zd1211). Hereby everything works. But I think it's not good that something could run into an infinite loop and make the system unusable, just through insert a wifi-stick. My system information: -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Thanks! Regards Jonny PS: I hope you understand what I mean, my english is no very well. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54900aee.5000...@posteo.de
Re: unstable system
* jesus_...@posteo.de jesus_...@posteo.de [2014-12-16 11:35 +0100]: Hello everyone! I don't no which package really cause the errors, so I write to the mailing list. When I'm using my wifi-stick USRobotics - USR8005423 my syslog file don't stop growing till my root partition is overflowing. This error always repeats: Dec 16 09:28:28 jonny kernel: [ 24.672140] usb 2-1.5: firmware: failed to load zd1211/zd1211b_ub (-2) # apt-get install firmware-zd1211 Elimar -- Talking much about oneself can also be a means to conceal oneself. -Friedrich Nietzsche -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141216122425.gc...@baumbart.home.lxtec.de
Upgrading the Debian/unstable system makes mplayer run without video output
Just now I upgraded my Debian/unstable ( 2.4.26-1-686) system and when I started mplayer (MPlayer 1.0pre5-3.3.4 ) I found the there is no video ouput. The sound ouput it ok. I compiled and installed the mplayer again without any errors but the problem still exists (no video). Any body else having similar problem with mplayer and debian/unstable? thanks JSS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Upgrading the Debian/unstable system makes mplayer run without video output
JSS wrote: Just now I upgraded my Debian/unstable ( 2.4.26-1-686) system and when I started mplayer (MPlayer 1.0pre5-3.3.4 ) I found the there is no video ouput. The sound ouput it ok. I compiled and installed the mplayer again without any errors but the problem still exists (no video). Any body else having similar problem with mplayer and debian/unstable? thanks JSS additional info: I played the video file with -v and following is the a part of the output (This might help in diagnosing the problem): . . . X11 opening display: :0.0 vo: X11 color mask: (R:F800 G:7E0 B:1F) vo: X11 running at 1600x1200 with depth 16 and 16 bpp (:0.0 = local display) [x11] Detected wm supports NetWM. [x11] Detected wm supports FULLSCREEN state. [x11] Detected wm supports ABOVE state. [x11] Detected wm supports BELOW state. [x11] Current fstype setting honours FULLSCREEN ABOVE BELOW X atoms == Opening video decoder: [mpegpes] MPEG 1/2 Video passthrough VDec: vo config request - 352 x 240 (preferred csp: Mpeg PES) Trying filter chain: vo Could not find matching colorspace - retrying with -vf scale... Opening video filter: [scale] SwScale params: -1 x -1 (-1=no scaling) Trying filter chain: scale vo The selected video_out device is incompatible with this codec. VDecoder init failed :( Opening video decoder: [libmpeg2] MPEG 1/2 Video decoder libmpeg2-v0.3.1 Selected video codec: [mpeg12] vfm:libmpeg2 (MPEG 1 or 2 (libmpeg2)) . . . I tried and it worked with mplayer file.avi -vo x11 but it did not go to full screen !! thanks JSS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem building X.org X11R6.8.0 on a Debian unstable system..
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kevin Cave wrote: [snip] | I'll try the CVS version tomorrow. Just wondering, though, | what environment you compiled it in? Whether it's Debian Stable, | Testing, or Unstabel? I built it from CVS and I am running Debian Testing (Sarge). Only built it yesterday but it seems to be working fine. :-) - -- Anders -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBQWRFLYywqksgYBoRAlIbAKDbdD5IqweNbRrVPNghSrJ7NRYkiQCcDo1L i9JEFYk8qsSt5LX8W4my/TY= =KnFE -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem building X.org X11R6.8.0 on a Debian unstable system..
Anders Karlsson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kevin Cave wrote: [snip] | I'll try the CVS version tomorrow. Just wondering, though, | what environment you compiled it in? Whether it's Debian Stable, | Testing, or Unstabel? I built it from CVS and I am running Debian Testing (Sarge). Only built it yesterday but it seems to be working fine. :-) snip Greetings, well I've checked out the CVS version and it's currently compiling on the dual Athlon system as I type :) So it looks like there might be some problem with the release tarballs, or I made some error. I just hope the X.org build system can handle make -j3 ;) Thanks for the help! Regards. Kevin Cave. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Success! (Re: Problem building X.org X11R6.8.0 on a Debian unstable system..)
Steve Smith wrote: Kevin == Kevin Cave [EMAIL PROTECTED] writes: Hmm, I'm slowly going insane over this. Either I've suddenly lost snip What are you building from, tarballs or CVS? I've personally only tried CVS so you could try that, details at: http://freedesktop.org/XOrg/CvsPage Ok, so the CVS checkout built perfectly , and I'm now typing this email on a desktop running X.org on Debian Sid. Thanks for all the help. I don't know why the tar'ed source didn't work for me - perhaps I didn't do something right with it. Oh well. Regards Kevin Cave. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Problem building X.org X11R6.8.0 on a Debian unstable system..
Hmm, I'm slowly going insane over this. Either I've suddenly lost all my Clue, or the above source just won't compile. So, I've read the documentation on compiling, I've also read Steve Smith's wonderfull howto at http://incubator.vislab.usyd.edu.au/roller/page/Steve/20040909 , and followed that, whilst correcting the small gaffe in it (cp xorgsite.conf host.conf should read cp xorgsite.def to host.def). And when I get to Make World, that's when the problem starts. The make process seems to begin fine, configuration-wise, until it gets to the point where the various subdirectories containing the X server build code need to be compiled, in that in every one I get : make[3]: Nothing to be done for `Makefiles'.. In every instance. Here's a typical example.. === Building on Linux 2.6.8 i686 [ELF] (2.6.8). Linux Distribution: Debian libc version: 6.3.2 binutils version: 21.5 GCC version: 3.3 make[1]: Leaving directory `/usr/src/xc-build' make -f xmakefile Makefiles make[1]: Entering directory `/usr/src/xc-build' making Makefiles in include... make[2]: Entering directory `/usr/src/xc-build' make[2]: Leaving directory `/usr/src/xc-build' make[2]: Entering directory `/usr/src/xc-build/include' making Makefiles in include/bitmaps... make[3]: Entering directory `/usr/src/xc-build/include' make[3]: Leaving directory `/usr/src/xc-build/include' make[3]: Entering directory `/usr/src/xc-build/include/bitmaps' make[3]: Nothing to be done for `Makefiles'. make[3]: Leaving directory `/usr/src/xc-build/include/bitmaps' making Makefiles in include/extensions... make[3]: Entering directory `/usr/src/xc-build/include' make[3]: Leaving directory `/usr/src/xc-build/include' make[3]: Entering directory `/usr/src/xc-build/include/extensions' make[3]: Nothing to be done for `Makefiles'. make[3]: Leaving directory `/usr/src/xc-build/include/extensions' making Makefiles in include/fonts... make[3]: Entering directory `/usr/src/xc-build/include' make[3]: Leaving directory `/usr/src/xc-build/include' make[3]: Entering directory `/usr/src/xc-build/include/fonts' make[3]: Nothing to be done for `Makefiles'. make[3]: Leaving directory `/usr/src/xc-build/include/fonts' ... .. Ad nauseum. And hey presto, nothing gets built. How dull. After that it does what looks like a cleanup routine and attempts to remove an awful lot of files, before ending like : snip a whole lot of rm stuff rm -f glide.man rm -f aiptek.man rm -f ur98.man rm -f XDarwin.man rm -f dumpkeymap.man rm -f *.CKP *.ln *.BAK *.bak *.o core errs ,* *~ *.a .emacs_* tags TAGS make.log MakeOut #* make[4]: Leaving directory `/usr/src/xc-build/doc/man/misc' make[3]: Leaving directory `/usr/src/xc-build/doc/man' cleaning in doc/hardcopy... make: *** hardcopy: No such file or directory. Stop. make: Entering an unknown directorymake: Leaving an unknown directorymake[2]: *** [clean] Error 2 make[2]: Leaving directory `/usr/src/xc-build/doc' make[1]: *** [clean] Error 2 make[1]: Leaving directory `/usr/src/xc-build' make: *** [World] Error 2 picard:/usr/src/xc-build# === So, anyone else managed to compile the source on a Debian unstable box? Anyone have a clue if it's exactly because I'm trying to build on a bleeding edge unstable box? It's driving me nuts :) The compilation environment on this box is : gcc (GCC) 3.3.4 (Debian 1:3.3.4-11) automake (GNU automake) 1.9.1 I'll provide any further details required. Many regards, Kevin Cave. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem building X.org X11R6.8.0 on a Debian unstable system..
Steve Smith wrote: Kevin == Kevin Cave [EMAIL PROTECTED] writes: Hmm, I'm slowly going insane over this. Either I've suddenly lost all my Clue, or the above source just won't compile. So, I've read the documentation on compiling, I've also read Steve Smith's wonderfull howto at http://incubator.vislab.usyd.edu.au/roller/page/Steve/20040909 , and Thanks :) followed that, whilst correcting the small gaffe in it (cp xorgsite.conf host.conf should read cp xorgsite.def to host.def). Oops, corrected. Thanks. No problem, always happy to help ;) `/usr/src/xc-build/doc/man/misc' make[3]: Leaving directory `/usr/src/xc-build/doc/man' cleaning in doc/hardcopy... make: *** hardcopy: No such file or directory. Stop. make: Entering an unknown directorymake: Leaving an unknown directorymake[2]: *** [clean] Error 2 make[2]: Leaving directory `/usr/src/xc-build/doc' make[1]: *** [clean] Error 2 make[1]: Leaving directory `/usr/src/xc-build' make: *** [World] Error 2 picard:/usr/src/xc-build# What are you building from, tarballs or CVS? I've personally only tried CVS so you could try that, details at: http://freedesktop.org/XOrg/CvsPage Cheers, Steve I'll try the CVS version tomorrow. Just wondering, though, what environment you compiled it in? Whether it's Debian Stable, Testing, or Unstabel? Regards, Kevin Cave. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New unstable system, problems isntalling Gnome
On Fri, 26 Dec 2003 22:05:20 -0500, stan wrote: On Fri, Dec 26, 2003 at 05:16:36PM +, Colin Watson wrote: On Thu, Dec 25, 2003 at 05:26:56PM -0500, stan wrote: I'm trying to help a friend build a new Debian machine. Since it's for MythTV, it needs to be an unstabe machine. Is it impossible to backport the relevant bits? When I try to istall teh gnome meta package I egt unmet dependencies: Depends: gnome-office (= 42) but it is not going to be installed Depends: rhythmbox but it is not going to be installed What can I do to resolve this? It's probably just not installable at the moment. Look at gnome's Depends: line and install everything in it apart from the above individually. How can I determine that? Using apt-cache show ...and, of course, the reason it's probably not installable at the moment is because unstable == unstable. -- paul It's working as coded. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New unstable system, problems isntalling Gnome
On Thu, Dec 25, 2003 at 05:26:56PM -0500, stan wrote: I'm trying to help a friend build a new Debian machine. Since it's for MythTV, it needs to be an unstabe machine. Is it impossible to backport the relevant bits? When I try to istall teh gnome meta package I egt unmet dependencies: Depends: gnome-office (= 42) but it is not going to be installed Depends: rhythmbox but it is not going to be installed What can I do to resolve this? It's probably just not installable at the moment. Look at gnome's Depends: line and install everything in it apart from the above individually. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New unstable system, problems isntalling Gnome
On Fri, Dec 26, 2003 at 05:16:36PM +, Colin Watson wrote: On Thu, Dec 25, 2003 at 05:26:56PM -0500, stan wrote: I'm trying to help a friend build a new Debian machine. Since it's for MythTV, it needs to be an unstabe machine. Is it impossible to backport the relevant bits? When I try to istall teh gnome meta package I egt unmet dependencies: Depends: gnome-office (= 42) but it is not going to be installed Depends: rhythmbox but it is not going to be installed What can I do to resolve this? It's probably just not installable at the moment. Look at gnome's Depends: line and install everything in it apart from the above individually. How can I determine that? -- They that would give up essential liberty for temporary safety deserve neither liberty nor safety. -- Benjamin Franklin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
New unstable system, problems isntalling Gnome
I'm trying to help a friend build a new Debian machine. Since it's for MythTV, it needs to be an unstabe machine. When I try to istall teh gnome meta package I egt unmet dependencies: Depends: gnome-office (= 42) but it is not going to be installed Depends: rhythmbox but it is not going to be installed What can I do to resolve this? -- They that would give up essential liberty for temporary safety deserve neither liberty nor safety. -- Benjamin Franklin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Mixed testing/unstable system, and dist-upgrade
Hi, I have kde, and gnome installed from unstable, and as packages get upgraded, and dependancies change, or new versions are available in unstable, I more often than not, have apt-get trying to remove 50-100 packages instead of getting the needed packages from unstable. If I read the apt_preferences manual correctly, once a package has been installed from unstable, and it hasn't been put into my highest priority entry (testing), then future upgrades should be from unstable for that package. Did I do something wrong, or is this a bug? # apt-get -ut unstable install kdelibs-data Reading Package Lists... Done Building Dependency Tree... Done The following extra packages will be installed: kdelibs-bin kdelibs4 libarts1 The following packages will be upgraded kdelibs-bin kdelibs-data kdelibs4 libarts1 4 packages upgraded, 0 newly installed, 0 to remove and 170 not upgraded. Need to get 12.6MB of archives. After unpacking 643kB disk space will be freed. Do you want to continue? [Y/n] Compare this to: Reading Package Lists... Building Dependency Tree... The following packages will be REMOVED: amor ark artsbuilder atlantik cdbakeoven eyesapplet fifteenapplet flashkard kaboodle kaddressbook kalarm kalzium kamera kandy kaphorism kappfinder karbon karm kasteroids kate katomic kaudiocreator kbackgammon kbattleship kbear kblackbox kbounce kcalc kcharselect kchart kcmlinuz kcoloredit kcontrol kcpuload kcron kdat kde kde-amusements kde-core kdeaddons kdeaddons-kfile-plugins kdeadmin kdeadmin-kfile-plugins kdeartwork kdeartwork-style kdebase kdebase-bin kdebase-kio-plugins kdeedu kdegames kdegraphics kdegraphics-kfile-plugins kdelibs kdelibs-bin kdelibs4 kdemultimedia kdemultimedia-kfile-plugins kdemultimedia-kio-plugins kdenetwork kdenetwork-kfile-plugins kdepasswd kdepim kdepim-kfile-plugins kdepim-libs kdeprint kdesktop kdessh kdetoys kdeutils kdf kdict kdm kdvi kedit keduca kenolaba kfax kfind kfloppy kformula kfouleggs kgeo kget kghostview kgpgcertmanager khangman khelpcenter khexedit kicker kicker-applets kiconedit kile kit kiten kivio kjots kjumpingcube klaptopdaemon klettres klickety klines klipper kmahjongg kmail kmailcvt kmenuedit kmerlin kmessedwords kmid kmidi kmines kmix kmoon kmplot kmrml knapster2 knetfilter knetload knewsticker knode knotes kodo koffice koffice-data koffice-libs kolf konq-plugins konqueror konqueror-nsplugins konquest konsole kontour kooka korganizer korn koshell kpackage kpager kpaint kpat kpercentage kpersonalizer kpf kpilot kpoker kpovmodeler kppp kpresenter krdc krec krecord kreversi krfb krita kruler krusader ksame kscd kscreensaver kshisen ksim ksirc ksirtet ksmiletris ksmserver ksnake ksnapshot ksokoban kspaceduel ksplash kspread kstars ksync ksysguard ksysv ktalkd kteatime ktexmaker2 ktimer ktip ktouch ktron ktuberling ktux kugar kuickshow kuser kverbos kview kviewshell kvoctrain kweather kwin kwin4 kword kworldclock kxconfig kxmlrpc libarts1-mpeglib libkdeedu1 libkdegames1 libkdenetwork2 libkonq4 libkregexpeditor libkscan1 lskat megami mpeglib noatun noatun-plugins qtella-kde quanta secpolicy The following packages will be upgraded kdelibs-data 1 packages upgraded, 0 newly installed, 213 to remove and 0 not upgraded. Need to get 0B/5060kB of archives. After unpacking 278MB disk space will be freed. Do you want to continue? [Y/n] here is my apt preferences file: package: * pin: release a=unstable Pin-Priority: 711 package: * pin: release o=Debian Pin-Priority: 722 sources.list: #Stable #deb http://http.us.debian.org/debian/ stable main non-free contrib #deb http://non-us.debian.org/debian-non-US stable/non-US main contrib non-free #Testing deb http://http.us.debian.org/debian/ testing main non-free contrib deb http://non-us.debian.org/debian-non-US testing/non-US main contrib non-free #Unstable deb http://http.us.debian.org/debian/ unstable main non-free contrib deb http://non-us.debian.org/debian-non-US unstable/non-US main contrib non-free #Security deb http://security.debian.org/ stable/updates main contrib non-free deb http://security.debian.org/ testing/updates main contrib non-free #Proposed Updates deb http://http.us.debian.org/debian/ stable-proposed-updates main non-free contrib deb http://http.us.debian.org/debian/ testing-proposed-updates main non-free contrib #Open Office #deb ftp://ftp.vpn-junkies.de/openoffice unstable main contrib #deb http://www.phy.olemiss.edu/openoffice/ testing main contrib #deb http://ftp.freenet.de/pub/ftp.vpn-junkies.de/openoffice/ unstable main contrib #Coda #deb http://www.coda.cs.cmu.edu/pub/coda/linux debian/binary-$(ARCH)/ #Samba Stable #deb http://people.debian.org/~peloy/samba stable main -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Testing/unstable system: keyboard freeze in X on reboot
First post for a while - only recently resubscribed, so here goes: My main box has been running testing for some time, with the odd thing pulled in from unstable. Before shutting it down for the weekend it had been up for a month without incident. Upon return the gdm logon screen would accept no keyboard input, although the mouse continued to function. I was also unable to switch between virtual consoles. When I killed gdm remotely, the keyboard worked fine on the command line. Also, when I killed gdm, my attempts at typing in the login box had appeared on the previously active console. Here's what I've tried: - checked XF86Config-4. This has not been altered for several months and was working fine. - attached another keyboard. Same behaviour as before. - checked that installation of gdm is up to date. - updated glibc to 2.3.1-10 (was runnning 2.3.1-5, so thought I'd upgrade given recent problems). Running gdm 2.2.5.5-2 gnome 1.4 xfree86-server 4.2.1-4 generic ps/2 windows keyboard 2.4.18 kernel Unfortunately I'd failed to get apt-listchanges to mail me, so I'm not entirely certain what's been installed in the last month (won't do that again). Any suggestions much appreciated, Stephanie -- Stephanie Boyd http://www.ixtab.org.uk/slb Gentlemen! You can't fight in here, this is the War Room! President Merkin Muffley, Dr. Strangelove msg26881/pgp0.pgp Description: PGP signature
Re: unstable system dies: apt-get dist-upgrade
Am 04. Jul, 2001 schwäzte Alan E. Davis so: Fairly often however I am harassed by messages from install-info. I have developed a standard operating Don't think I've ever run into that. I am reinstalling, but if I can figure this one out, I will save myself a month of work. This was a well loaded system with lots of self-installed packages. I am starting from potato, now have upgraded to woody. Have you tried apt-get --reinstall? Don't know if it works. The only system I've had hosed enough to need it was well beyond the help available from a reinstall :). Minimally do a dpkg --get-selections /tmp/selections.txt and transfer that file somewhere safe. Then after doing a minimal install, you can dpkg --set-selections /tmp/selections.txt, then do a dist-upgrade. Actually, maybe a dselect-upgrade would be more appropriate at that point. ciao, der.hans -- # [EMAIL PROTECTED] home.pages.de/~lufthans/ www.DevelopOnline.com # Magic is science unexplained. - der.hans
unstable system dies: apt-get dist-upgrade
Yesterday, 3 July (GMT+10) I attempted to resolve dependency problems for the dist-upgrade that I'd left running overnight. My system is now dead. I have installed a new installation on a different filesystem, and am starting from scratch. I do these upgrades fairly often. Sometimes I'll let it go a month, or even two. In general I have few real problems. Fairly often however I am harassed by messages from install-info. I have developed a standard operating procedure in these cases: edit the offending file (eg *.prerm or *postinst) and run dpkg --configure. I'm not happy of course, but this or some other similar procedure *usually* (TM) takes care of these things. I have posted to these lists in the past my feeling about this install-info. Why should installation of documentation be the most common pediment to upgrades? Rarely do I have any other problem. I have begun to think it's time to reinstall. I am sure there is major cruft I am not taking care of. After over perhaps two years of incremental upgrades, one or two major partition shifts, it's time. Well, it happened. I don't even know what. I am embarrassed that I cannot even relate to the list what messages I received. After a number of vexing complaints from apt-get/dpkg, which I overcame in the way I have described, as well as by force-overwrite, etc., the system came to total loss. No keyboard input into login prompts. Messages about init. I think that sysvinit might have been hosed. I had to reinstall login a few weeks ago, to solve a somewhat similar problem. THis is not the libpam issue, as I had gotten through that one in an hour. I am reinstalling, but if I can figure this one out, I will save myself a month of work. This was a well loaded system with lots of self-installed packages. I am starting from potato, now have upgraded to woody. Does any of this mean anything to anyone? Alan Davis
