Re: PPP link kills routing table
On Tue, 18 Jun 1996, Mark Phillips wrote: > Hi, > > Thank's to all the people who have helped me recently. Every time I > solve one problem, another appears. > > I tried establishing a ppp link and found it didn't work. To find out > what was going on, I ran route and got: > What exactly happens when you try to run pppd? Any messages in /var/adm/messages or /var/adm/debug? [...] > > I tried several things to try and get it to work. Previously ppp had > worked when I had nothing in my /etc/modules file, so I tried > commenting out the entries and rebooted. PPP now works (as you can > see by the fact that I am typing this), however I think ppp working is > the result of a side effect: namely, that as a result my local > ethernet network wasn't setup. If I now type route, before running > pppd, I get: > Remove the eth0 entries by using ifconfig and try to run pppd. It could be as simple as an interrupt conflict between your ethernet card and the serial port pppd is using. I had that problem a while ago. My ethernet and my ppp link was mutually exclusive. /Bengt-Ove Johansson!
Re: zip in bootup.
Ze Ji Li wrote: >Is there a boot disk that have the ZIP driver in it? If not, how >can I make a boot disk with the ZIP driver? By the way, the ZIP >drive is the parallel version. I like to try out debian on the ZIP drive. >Thank you very much. I was just looking into this for a revised version of the FAQ (yes, this is an FAQ). In the process, I found this mail message from Bruce Perens which explains what needs to be done: >> I have one of the IOMEGA ZIP-drives,100MB, parralell version, and was >> wondering if it is, if it can, and if it will be possible to have one's >> linux system one of these ZIP disks. > >Probably yes. > >Make a boot floppy, because the ZIP isn't directly bootable. >Hand-edit the syslinux.config parameters in the boot floppy to add > root=. Make sure that the correct device exists in /dev . >Build a custom kernel with the "ppa" driver linked in, because the root > filesystem can't come from a module. > >This is a low-performance solution, but can be used to advantage as an >installation disk in installing Debian on a number of systems - for example >in a computer lab. Our installation system will let you put base1_1.tgz on >the ZIP and will then not require the base floppies. You can also put Debian >packages on the ZIP drive and use dpkg-scanpackages to build a Packages file >for each ZIP disk so that "dselect" will work with them. > >Bruce > I have more notes on this in the revised FAQ, which I will upload later today (I hope). Susan Kleinmann [EMAIL PROTECTED]
how does kernel-source link current modules?
I've used the kernel-source package to build a custom kernel, and then installed the result with dpkg --[myflags] kernel-image-2.0.0. Then I copied /boot/vmlinuz-2.0.0 to my dos disk so that I could continue to boot with loadlin. But I notice that /lib/modules/current still points to my previous kernel. Shouldn't this step be part of the kernel-image postinst file? If not, it might be a good idea to mention a "best practice" in the debian.README file contained in the kernel-source package. Comments? Regards, Susan Kleinmann [EMAIL PROTECTED]
zip in bootup.
hi.. Is there a boot disk that have the ZIP driver in it? If not, how can I make a boot disk with the ZIP driver? By the way, the ZIP drive is the parallel version. I like to try out debian on the ZIP drive. Thank you very much. ze
