ppp/modem problems .. suggestions?
Interesting little problem here. I have two machines, one at work, one at home, both running slink. As far as I know, both systems are running the same package versions for everything installed (Synced from Slink CD and www.us.debian.org using APT) and both have kernel 2.2.2 from www.us.kernel.org mirror. I have ppp, pppconfig, and ppp-pam installed on both. What's happening is that the machine at home will pass UDP packets but not TCP packets, so I can ping and traceroute from it, but I can't telnet, rlogin, or use ssh. The machine at work can connect and do everything just fine. Also, the machine at work runs the ppp connection fine using the kernel shipped with slink, and was running on another computer with a custom 2.0.3x kernel. The machine at work has a Creative Labs modem blaster jumpered for ttyS0, while the machine at home is an external Ricochet modem on ttyS1. I remember seeing a few posts last month about a similar problem, but I can't seem to locate them ATM. And no, I can't take the Ricochet to work to test on that computer for the time being. Suggestions on what to try? --Ian
Re: problems+suggestions
Hello, Did you *intend* to upgrade to slink? I have the feeling that you might be upgrading to it inadvertently, which would explain most of your problems... If so, you'll have to consider what you want to do now. In general, unless you have a particular reason to go for unstable or frozen, it's probably best to stick with the stable distribution as much as possible. However, if you got this far already, it might be easier to stay here than to go back. Glossary: 2.0 = hamm = stable (the latest released version) 2.1 = slink = frozen (the next version, not yet released) 2.2 = potato = unstable (the version after that) I'll take the suggestion first :) Others already answered this. BTW, many Debian programs will give you a short help text if you run them with just a --help switch, for example: dpkg --help And well, wouldn't it be possible to have a HUGE warning if trying to remove things that dselect (or whatever package program running) depends on? Actually, dselect won't let you do that at all, and the dpkg help says: WARNING - use of options marked [!] can seriously damage your installation. for the relevant option. dselect: error in loading shared libraries /usr/lib/libstdc++-libc6.0-1.so.2: undefined symbol __register__frame__info What deb(s) do I have to do to fix it? Actually, this isn't a problem with a missing deb, it's a miscompiled library. You'll need to download the very latest libstdc++ (check Incoming just to make sure) and manually install that: dpkg -i filename.deb As if that wasn't enough, I can't start X anymore after upgrading the hardware. I swapped motherboard+mem+kbd+mouse(from ps/2 to serial). It just hangs on a black screen or the gray grid like screen at X startup.. Two suggestions: (a) Fix the __register_frame_info problem first, just in case it's related. (b) If you are upgrading to slink from hamm, the X packages were reorganized; you'll be almost certainly missing xterm, and maybe other things. Make sure you either have the old xbase or the new xterm (depending on what you want to do). (xterm is the program that gives you a command prompt in X) HTH Jiri [EMAIL PROTECTED]
Re: problems+suggestions
Hello, Would dpkg --get-selections foo dpkg --set-selections foo not do this? Single '' and '', please. Sorry to nitpick, but a beginning user would probably be quite confused by the prompt for the here-document. Jiri [EMAIL PROTECTED]
Re: problems+suggestions
On Tue, Dec 01, 1998 at 09:26:45PM -0400, wb2oyc wrote: Wouldn't it be nice if a configuration of all installed packages could be saved in some data file that you could put on a disk and whenever you want to install a new machine or go back to this good configuration you just load the data-file into dselect or whatever program that gets/installs packages. Some different default configs could also be shipped with the dist to be used by new debian people. Maybe this is already possible? Tell me please! SuSE Linux does precisely that using its YaST tool. Yeah, and its evil: 1) It is limited. 2) It prevents configuration in the standard way (incompatible to manual configuration). Debian is working on a better solution for this. Not ready yet, though. You can export/import a list of selected packages though, as other people already told you. Thanks, Marcus -- Rhubarb is no Egyptian god.Debian GNU/Linuxfinger brinkmd@ Marcus Brinkmann http://www.debian.orgmaster.debian.org [EMAIL PROTECTED]for public PGP Key http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ PGP Key ID 36E7CD09
Re: problems+suggestions
Wouldn't it be nice if a configuration of all installed packages could be saved in some data file that you could put on a disk and whenever you want to install a new machine or go back to this good configuration you just load the data-file into dselect or whatever program that gets/installs packages. Some different default configs could also be shipped with the dist to be used by new debian people. Maybe this is already possible? Tell me please! SuSE Linux does precisely that using its YaST tool. Paul
Re: problems+suggestions
On Wed, Dec 02, 1998 at 12:49:12AM +0100, Ben Jorgensen wrote: I'll take the suggestion first :) Wouldn't it be nice if a configuration of all installed packages could be saved in some data file that you could put on a disk and whenever you want to install a new machine or go back to this good configuration you just load the data-file into dselect or whatever program that gets/installs packages. Some different default configs could also be shipped with the dist to be used by new debian people. Maybe this is already possible? Tell me please! You could copy your /var/lib/dpkg/status file and replace lines like: Status: install ok installed with: Status: install ok not-installed Then after installing the base system replace the status file with your copy and startup dselect. WARNING: I have never tried this, it is all theory. Maybe a wishlist bug for dpkg to output a special status file just for this would be nice, and having dselect be able to merge this into a new installs' status file would be even better. -- --- - - --- - - - --- Ben Collins [EMAIL PROTECTED] Debian GNU/Linux UnixGroup Admin - Jordan Systems Inc. [EMAIL PROTECTED] -- -- - - - --- --- -- The Choice of the GNU Generation
Re: problems+suggestions
On Tue, 1 Dec 1998, Ben Collins wrote: On Wed, Dec 02, 1998 at 12:49:12AM +0100, Ben Jorgensen wrote: I'll take the suggestion first :) Wouldn't it be nice if a configuration of all installed packages could be saved in some data file that you could put on a disk and whenever you want to install a new machine or go back to this good configuration you just load the data-file into dselect or whatever program that gets/installs packages. Some different default configs could also be shipped with the dist to be used by new debian people. Maybe this is already possible? Tell me please! You could copy your /var/lib/dpkg/status file and replace lines like: Status: install ok installed with: Status: install ok not-installed Then after installing the base system replace the status file with your copy and startup dselect. Would dpkg --get-selections foo dpkg --set-selections foo not do this? Matthew -- Elen sila lumenn' omentielvo Steward of the Cambridge Tolkien Society Selwyn College Computer Support http://www.geocities.com/Area51/Chamber/8841/ http://www.cam.ac.uk/CambUniv/Societies/tolkien/ http://pick.sel.cam.ac.uk/
Re: problems+suggestions
I'll take the suggestion first :) Wouldn't it be nice if a configuration of all installed packages could be saved in some data file that you could put on a disk and whenever you want to install a new machine or go back to this good configuration you just load the data-file into dselect or whatever program that gets/installs packages. Some different default configs could also be shipped with the dist to be used by new debian people. Maybe this is already possible? Tell me please! You can do this with $ dpkg --get-selections file to record the settings, and $ dpkg --set-selections file to get the setting from the file. Then start dselect and skip the selection step. HTH, Eric -- E.L. Meijer ([EMAIL PROTECTED]) | tel. office +31 40 2472189 Eindhoven Univ. of Technology | tel. lab. +31 40 2475032 Lab. for Catalysis and Inorg. Chem. (TAK) | tel. fax+31 40 2455054
problems+suggestions
I'll take the suggestion first :) Wouldn't it be nice if a configuration of all installed packages could be saved in some data file that you could put on a disk and whenever you want to install a new machine or go back to this good configuration you just load the data-file into dselect or whatever program that gets/installs packages. Some different default configs could also be shipped with the dist to be used by new debian people. Maybe this is already possible? Tell me please! Maybe some history function in dselect would be useful to have so it would be possible to go back to a working config. And well, wouldn't it be possible to have a HUGE warning if trying to remove things that dselect (or whatever package program running) depends on? (read on to understand why I think so:) Ok, for the problems... I wanted to remove the gnome packages and somehow some other things slipped away as well. When trying to start dselect now it says dselect: error in loading shared libraries /usr/lib/libstdc++-libc6.0-1.so.2: undefined symbol __register__frame__info What deb(s) do I have to do to fix it? Another things is that I can't get rid of the xfstt because of an error in the startup script... As if that wasn't enough, I can't start X anymore after upgrading the hardware. I swapped motherboard+mem+kbd+mouse(from ps/2 to serial). It just hangs on a black screen or the gray grid like screen at X startup.. IN SHORT: I'm about to re-install.. Now when I'm going to re-install it would've been nice to have a good config to go back to and not having to go through the package selection procedure again... //ben -- http://surf.to/anTiX
