Re: newbie can't install packages from floppy
"Darryl Röthering" wrote: > > What is the proper procedure for installing packages from a floppy? I > downloaded them via my NT box (hiss, hiss) at work, but can't seem to read > them (dpkg -info, or dpkg --install) when I mount the floppy as type vfat. Post a transcript of what you tried and the errors you got back. There's an infinite number of things you could have typed, and a similar number of responses. > What additionally puzzles me is that after I get the package I want from the > web site, I get a list of ftp sites to get it from, but never get an option > for the architecture involved. Don't these packages contain binaries? Which website ? Which page on the website ? Which packages ? Regards, Paul
Re: Problem with g77
[EMAIL PROTECTED] wrote: > Please help! People are asking to use this program, and I can't > get it to work It doesn't answer your question of why the build is failing, but why not just install the binaries to get the system up and running ? Your users may not be fussy about which compiler, or how much optimisation ... :-) Regards, Paul
Re: bogomips
Alberto Maurizi wrote: > > Is this normal? I mean, that so low bogomips value. > model name : Pentium 60/66 > cpu MHz : 59.999660 > bogomips: 23.91 I've got an Intel P133. Approximating pro rata using your data gives 23.91 / 60 * 133 = 53. Actual reported value is 53.25 So I'd say it looks exactly right. Regards, Paul
Re: LogCheck and it's rules
Robert Ramiega wrote: > Maybe You are right but then why this: > named[.*]: Cleaned cache of .* RRsets > causes logcheck to exclude matching lines and the line at the top does not > ?? Are you sure it does ? Perhaps there is another line in your ignore file which matches it. That line should not. I did a test : /tmp/grep$ echo "named[1010]: blah blah blah" | grep -v "named[.*]:" named[1010]: blah blah blah /tmp/grep$ echo "named[1010]: blah blah blah" | grep -v "named\[.*\]:" /tmp/grep$ The first line does not filter out your pattern, but the second one does. I meant to add that the convention seems to be "named.*:", since any well-formed log message will always have the name, the [pid#] and a colon. Less typing, I suppose ... Regards, Paul
Re: Trying for over a week to fix apt-get
Antonio Rodriguez wrote: > > I attach here what apt-get spits out to the screen. What should I do? A > similar thing I get when I try to install kernel-source-2.2.13. Please > help, > Thanks, > Antonio. > Please note I have no experience with apt, but I did experience a similar problem when upgrading mozilla recently with dselect / dpkg. Regarding the gcc error message you get, it seems to be a limitation in the apt program. It also appears in dselect. If you have two conflicting packages which provide the same file, you need to remove the old and install the new. Unfortunately, the install system is trying to install gcc before removing egcc, and so you get the "trying to overwrite file XXX supplied by package YYY" message. If you manually remove the egcc package first, the gcc will (probably) install fine, since the conflicting files are gone. There may be a good reason why apt doesn't do this itself by default. The Debian packaging system is certainly complex, and it's a huge task to cope with all the possible scenarios. By and large, though, the Deb folks are doing a pretty decent job. Good luck. -- Regards, Paul
Re:
> Jason Winters wrote: > > does anyone know why packages would install right, then when I try to > run them nothing happens? Could you be any more vague ? Paul
Re: Help Please, potato ne2000 install problem
(Courtesy CC sent) Hi Stan, I've got a Realtek-8029, which is a PCI NE2000 clone, so it might be similar. IIRC, the NE2k cards depend on the 8390 module. You will need this module to avoid the unresolved symbols. To associate the card with the eth0 interface, I add the line alias eth0 ne2k-pci into the /etc/modutils/aliases file (your module might not be the ne2k-pci one, substitute as necessary) and run update-modules to regenerate the /etc/modules.conf file. The alias makes the ne2k-pci module get autoloaded when the "ifconfig eth0 ... up" is encountered (usually in /etc/init.d/network) Hope this helps, Paul Stan Brown wrote: > > Help please. > > I am trying to install from the latest unstable on a machine with a > NE200 network card. > > During the initial boot session, I select this module, and configure > networking, and am able to access the network. > > However after the first reboot, the network does not come up. ifconfig > -a does not find the eht0 device. Atempting to load the ne module by > hand at this point results in unresolved symbols. > > What am I doing wrong? > > -- > Stan Brown [EMAIL PROTECTED] > 843-745-3154 > Westvaco > Charleston SC. > -- > Windows 98: n. > useless extension to a minor patch release for 32-bit extensions and > a graphical shell for a 16-bit patch to an 8-bit operating system > originally coded for a 4-bit microprocessor, written by a 2-bit > company that can't stand for 1 bit of competition. > - > (c) 1999 Stan Brown. Redistribution via the Microsoft Network is prohibited. > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
