Linux-Misc Digest #301, Volume #21 Thu, 5 Aug 99 19:13:23 EDT
Contents:
Re: mount theory, lost space, and other sundry cack (Leonard Evens)
newbie: cron won't work. just won't. need help. (Andrew de los Reyes)
Sony Superstation Tape Drive problems (Jesse Hughes)
Re: why do I lose my entire system at restart, how to minimize loss? ("Matt Baker")
Re: ICQ (was Re: in response ("Brian F.")
Help!!! Sound Card OPTi 82C924 ("Pedro Kiefer")
Re: (no subject) ([EMAIL PROTECTED])
Re: upgrading gcc to 2.95 via RPM (Paul Kimoto)
Re: PPP and Linux ("Jason B. Johnson")
Re: LOST ROOT PASSWORD (Steven E Bourland)
Re: Failed Kernel Compile: System is too big (Collin W. Hitchcock)
Re: Creating a Boot Disk (Leonard Evens)
Re: Posted already for the third time ([EMAIL PROTECTED])
Re: newbie: cron won't work. just won't. need help. ([EMAIL PROTECTED])
Please Help: Error useing Backpack Hard Drive. ([EMAIL PROTECTED])
Re: Lilo Problems (Leonard Evens)
Re: Is Linux A Memory Hogging OS? (Chris Butler)
Re: newbie: what is "Segmentaion fault"? (Leonard Evens)
----------------------------------------------------------------------------
From: Leonard Evens <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux
Subject: Re: mount theory, lost space, and other sundry cack
Date: Thu, 05 Aug 1999 15:38:41 -0500
DHobbs wrote:
>
> Matt Arnold wrote:
> > And let's assume that /home contains around 100MB worth of stuff. It's
> > growing at a fast rate, so we want to add another disk and put /home on that
> > new disk. We'll need to prepare the new disk, mount it to a temporary
> > point, and copy /home from the old disk to the new disk. So far so good.
> >
> > Now what happens once we mount /home to this new disk? We still have 100MB
> > worth of files on the old disk (formerly available via /home). But because
> > of this recent mount (which now points /home to the new disk) we can't get
> > to these files on the old disk to delete them. Right? They're still
> > consuming space, yet they can't be reached for deletion? Is there a name
> > for this type of situation -- disk space which is in use yet can't be freed
> > because our mount points won't let us reach it?
> >
> > I'm assuming the proper way to deal with this is to make sure one deletes
> > the files from the old drive before mounting the new one (per step 4 shown
> > above.) But I'm still wondering if there is any way to detect (using the
> > output of df or other program) if there is any of this "lost space" on my
> > drives. It seems any filesystem with more than the single mount point of /
> > COULD potentially contain unreachable files. How can I prove there is none
> > of this unreachable space on my filesystems?
>
> Compare the output from these two commands
>
> du -x -k -c /home|grep total
> df -k /home |grep "/home"|awk '{print $3}'
>
> change the instances of /home to whatever partition you care to check
> out.
>
> If they're the same, then you have nothing hidden under a mount.
>
> The first one works on Linux, but not Solaris. On Solaris it'd be:
>
> du -d -k /
>
> and compare the last line to the df command.
>
> Dan
du and df often give slightly different answers.
--
Leonard Evens [EMAIL PROTECTED] 847-491-5537
Dept. of Mathematics, Northwestern Univ., Evanston, IL 60208
------------------------------
From: Andrew de los Reyes <[EMAIL PROTECTED]>
Subject: newbie: cron won't work. just won't. need help.
Date: Thu, 05 Aug 1999 20:21:33 GMT
I access my cron file for root: % cronat -e i set it to: ______________ 15 *
* * * ifup ppp0 17 * * * * ifdown ppp0 ______________ these commands work as
root, let me assure you. the man pages say cron updates every minute, but it
wasn't so i rebooted. oh, don't tell me that wasn't necessary--i know--partly
because the problem still exists. diring startup it stats the cron daemon:
something like (from top of my head): starting cron daemon [ OK ] still,
when the time rolls around nothing happens. what can i do? right now i'm just
testing, but soon i would like to make some real use of it.
-Andrew de los Reyes
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
------------------------------
From: Jesse Hughes <[EMAIL PROTECTED]>
Subject: Sony Superstation Tape Drive problems
Date: Thu, 5 Aug 1999 16:28:46 -0400
Hey ho.
I just installed a new Sony Superstation IDE drive (internal). I'm using
Linux 2.2.10 (and also 2.0.27) and the kernel seems to recognize it on
boot up. However, when I try to read or write to the drive, I get oodles
of I/O errors. The only explicit one I've seen is one which says that the
tape is sending information faster than expected during a read operation.
I have some old tapes (TR-3's, which this drive should be able to read)
that I desperately need to read. So, I need a fix for this as soon as
possible. If anyone has seen this or can help, please let me know.
My newsgroup access is a bit spotty for now, so please send a courtesy
copy of any replies. Thanks.
Jesse
------------------------------
From: "Matt Baker" <[EMAIL PROTECTED]>
Subject: Re: why do I lose my entire system at restart, how to minimize loss?
Date: Thu, 5 Aug 1999 16:20:30 -0400
Hey thanks for those key combinations, I will try that next time.
Yeah, I have to press reset sometimes and almost always when I do this on
startup a message comes up that says something like "serious damage has
occurred to your file structure" other times it appears to have fixed the
problems but the services won't start up properly. Perhaps it is a hardware
problem.
Thanks
matt
Robert Heller <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> "Matt Baker" <[EMAIL PROTECTED]>,
> In a message on Thu, 5 Aug 1999 12:36:18 -0400, wrote :
>
> "B> I understand that linux doesn't write things to disk until shutdown,
neither
>
> False, it flushes its disk cache every 2 seconds or so.
>
> "B> does NT. Occasionally NT will lockup beyond repair and I have to
reset the
> "B> machine. NT recovers from this dirty shutdown 95% of the time. Linux
> "B> recovers from a dirty shutdown 5% of the time. My linux installation
locks
> "B> up at least once every few days which means I am constantly having to
> "B> reinstall. What is the best solution to prevent this reinstallation?
>
> What do you mean by 'linux installation locks up'? If you mean the X11
> screen freezes, that does not mean linux is locked up! Unlike NT, the
> GUI is NOT part of the kernel. Even if X11 locks up, it should be
> possible to get to another virtual console (Ctrl-Alt-F2, F3, etc.), and
> login again and kill off the X server. There is also the 'magic' SysRq
> key trick.
>
> Also, what do you mean by 'Linux recovers from a dirty shutdown 5% of
> the time'? Are you pushing the reset button and then freaking when fsck
> runs? fsck is normal -- let it run, *I* have *never* seen a Linux box
> that have been power-cycled or reset that *failed* to recover, unless
> the disk itself had crashed hard or had some other hardware fault (i.e.
> bad memory, sick motherboard, missing or improper SCSI terminator, etc.).
>
>
> "B> Should I back up my installation on another partition or perhaps a
tape?
> "B> What is best?
>
> Backups are always a good idea.
>
> "B>
> "B> Is there a way that I can sacrifice speed for crash protection? (so
the
> "B> system writes everything to disk immediately)
> "B>
> "B> The biggest issue I suppose is finding the cause of these crashes.
> "B>
> "B> I thought it was my Cyrix processor so I put in an intel. The
crashing
> "B> continues.
> "B> Now I am wondering whether it is the piece of trash trident card I
have got
> "B> in there.
> "B>
> "B> Any help would be appreciated...
> "B> thanks
> "B> matt
> "B>
> "B>
> "B>
> "B>
> "B>
> "B>
>
>
>
>
>
>
>
> --
> \/
> Robert Heller ||InterNet: [EMAIL PROTECTED]
> http://vis-www.cs.umass.edu/~heller || [EMAIL PROTECTED]
> http://www.deepsoft.com /\FidoNet: 1:321/153
------------------------------
Reply-To: "Brian F." <[EMAIL PROTECTED]>
From: "Brian F." <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux.caldera,comp.os.linux.help,comp.os.linux.questions
Subject: Re: ICQ (was Re: in response
Date: Thu, 5 Aug 1999 17:00:56 -0500
Just wondering if you ever got it working. I use icqnix, and have never had
a problem. All you really need is QT and you should be rocking. You can get
it from here http://www.portup.com/~gyandl/icq/#icqnix
Later
Brian F.
Larry Clark <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> well I got licq to work on my red hat machine at home now I can't get any
to work
> again....on my caldera 2.2 machine at work...dud.........I am triin
> gkicq....kxicq.......licq....etc.....
>
------------------------------
From: "Pedro Kiefer" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.help,comp.os.linux.questions,comp.os.linux.setup
Subject: Help!!! Sound Card OPTi 82C924
Date: Thu, 5 Aug 1999 18:47:53 -0300
I'm having a little bit of trouble trying to setup my sound card.
Can anyone help me? My sound card has an OPTi 82C924 chipset.
Which is the ez way to i configure it?
thanx
Pedro Kiefer
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.setup,comp.os.linux.x
Subject: Re: (no subject)
Date: 5 Aug 1999 21:52:38 GMT
Download the RedHat Updates for 5.2 XFree86*.rpm
You will need all of the following:
ftp://updates.redhat.com/5.2/i386/XFree86-3.3.3.1-1.1.i386.rpm
ftp://updates.redhat.com/5.2/i386/XFree86-75dpi-fonts-3.3.3.1-1.1.i386.rpm
ftp://updates.redhat.com/5.2/i386/XFree86-VGA16-3.3.3.1-1.1.i386.rpm
ftp://updates.redhat.com/5.2/i386/XFree86-XF86Setup-3.3.3.1-1.1.i386.rpm
ftp://updates.redhat.com/5.2/i386/XFree86-libs-3.3.3.1-1.1.i386.rpm
ftp://updates.redhat.com/5.2/i386/XFree86-100dpi-fonts-3.3.3.1-1.1.i386.rpm
And you will need one if the following per your video card:
ftp://updates.redhat.com/5.2/i386/XFree86-3DLabs-3.3.3.1-1.1.i386.rpm
ftp://updates.redhat.com/5.2/i386/XFree86-8514-3.3.3.1-1.1.i386.rpm
ftp://updates.redhat.com/5.2/i386/XFree86-AGX-3.3.3.1-1.1.i386.rpm
ftp://updates.redhat.com/5.2/i386/XFree86-I128-3.3.3.1-1.1.i386.rpm
ftp://updates.redhat.com/5.2/i386/XFree86-Mach8-3.3.3.1-1.1.i386.rpm
ftp://updates.redhat.com/5.2/i386/XFree86-Mach32-3.3.3.1-1.1.i386.rpm
ftp://updates.redhat.com/5.2/i386/XFree86-Mach64-3.3.3.1-1.1.i386.rpm
ftp://updates.redhat.com/5.2/i386/XFree86-Mono-3.3.3.1-1.1.i386.rpm
ftp://updates.redhat.com/5.2/i386/XFree86-P9000-3.3.3.1-1.1.i386.rpm
ftp://updates.redhat.com/5.2/i386/XFree86-S3-3.3.3.1-1.1.i386.rpm
ftp://updates.redhat.com/5.2/i386/XFree86-S3V-3.3.3.1-1.1.i386.rpm
ftp://updates.redhat.com/5.2/i386/XFree86-SVGA-3.3.3.1-1.1.i386.rpm
ftp://updates.redhat.com/5.2/i386/XFree86-W32-3.3.3.1-1.1.i386.rpm
Use rpm to update these packages (man rpm for hints)
rpm -Uvh *.rpm
should work if you have all and only what you need in a separate directory.
Then run:
XF86Setup
from a root login. It has selections for screen size and color depth.
This is the easiest way I have found to get X configured.
Best of luck...
Phillip wrote:
>
> I am very new to Linux. i recently installed REdhat version 5.2 on my
> machine. I have tried to change the color depth, but it always seems to
>
> default to 8 bit color no matter what I seem to do. Ive opened the file
>
> /usr/lib/X11/XF86Config and changed the depth from 8 to 16 in the
> section Screen. However when I tried to start the Xwindows server, it
> said that the default 8 bit was unavailable, and thus it could not
> start. I am really not sure how to change this.
------------------------------
From: [EMAIL PROTECTED] (Paul Kimoto)
Subject: Re: upgrading gcc to 2.95 via RPM
Date: 5 Aug 1999 16:55:06 -0500
Reply-To: [EMAIL PROTECTED]
In article <7ocqbt$[EMAIL PROTECTED]>, Dave Bailey wrote:
> Is this a good idea? I tried it on my RH 5.2 running the
> 2.2 kernel with glibc 2.1.1 and the best I could manage
> was to get to the point where I could compile programs,
> but running them always resulted in a core dump with
> "Illegal Instruction". Even hello, world did this.
>
> What is the procedure for updating gcc via RPM? Is it
> really as simple as getting all the 2.95 rpms and installing
> them? Or am I better off downloading the source code and
> building from that?
Not all RPMs are created equal. Were they produced by the egcs team?
(No.) Were they issued officially by Red Hat? For more on this
subject, you may want to see the gcc mailing-list archive at
http://egcs.cygnus.com/ml/gcc/1999-08/ and read the thread on
"Illegal instruction (core dumped) on i586)".
You may like to build from source code, with a build procedure
something like "./configure --prefix=/usr/local && make
bootstrap-lean && make install". Source code locations and build
instructions can be found via http://egcs.cygnus.com/.
--
Paul Kimoto <[EMAIL PROTECTED]>
------------------------------
Date: Thu, 05 Aug 1999 16:48:53 -0500
From: "Jason B. Johnson" <[EMAIL PROTECTED]>
Crossposted-To: alt.linux,alt.os.linux
Subject: Re: PPP and Linux
"Gregor Gregori�" wrote:
> I have a problem with PPP. I connect with KPPP on internet and i can't open
> pages in netscape or talk on IRC like computer doesnt know that he is
> connected to internet. Please help.
>
> Thx
>
> Greg
Does kppp say that it is connected? If so, go to a command line and type
'/sbin/ifconfig', and then type 'netstat -rn', and send that output.
Jason
------------------------------
From: Steven E Bourland <[EMAIL PROTECTED]>
Subject: Re: LOST ROOT PASSWORD
Date: Thu, 05 Aug 1999 15:55:44 -0500
[EMAIL PROTECTED] wrote:
> This is why they invented keyboard locks, CPU case locks, and cabinet
> locks. This "trick" can be used on any number of UNIX platforms. I
> think the only thing I've witnessed that would not allow this is NT.
>
> -Andrew
>
> > not very secure is it ?
> > in theory anyone can walk up to a LINUX box and change the root
> > password.
> > my advice don't leave your LINUX boxes insecure.
This is also why you can change the boot order in your BIOS so it won't
boot from floppies, at least, that is what I have always assumed that
was
for.
------------------------------
From: [EMAIL PROTECTED] (Collin W. Hitchcock)
Subject: Re: Failed Kernel Compile: System is too big
Date: 05 Aug 1999 17:50:14 -0400
> System is 546kb
> System is too big.
> Error [1]
> exiting: /usr/src/linux-2.2.10/arch/i386/boot
> Error [2]
Other people suggested using make bzImage. I would recommend building
more things as modules to make your kernel smaller. Just make sure
that everything you need to mount the root partition is built directly
into the kernel (ie. IDE driver and ext2fs support).
Collin
------------------------------
From: Leonard Evens <[EMAIL PROTECTED]>
Subject: Re: Creating a Boot Disk
Date: Thu, 05 Aug 1999 15:56:58 -0500
[EMAIL PROTECTED] wrote:
>
> I'm new to Linux, but was able successfully install RH5.2 on my laptop.
> At the end of installation I skipped the step that creates a boot disk
> in case something happens to boot partition. Linux is up and running
> OK.
> How can I create the Boot Disk at this point?
>
> Thanks,
> Vlad.
>
> Sent via Deja.com http://www.deja.com/
> Share what you know. Learn what you don't.
Use mkbootdisk. Do
man mkbootdisk
to see how to use it.
But say you are using the 2.0.36 kernel. Then
cd /boot
mkbootdisk 2.0.36
should do it. The default is to put it on the floppy disk
/dev/fd0.
If this fails, check the file /etc/conf.modules. If it has
multiple entries for the same item, remove the extras and
try mkbootdisk again.
You should also mount the CD and go to the subdirectory
images. Then with a blank floppy in the floppy drive do
dd if=rescue.img of=/dev/fd0 bs=1440k
This will create a rescue disk to be used with the boot
floppy to run a ramdisk version of the system for diagnostic
and repair purposes.
One warning. You may find that the system takes forever
to boot from the boot floppy. You would want it anyway
for use with the rescue disk, but you can get a faster
booting boot floppy by doing
cd /boot
dd if=Your_kernel_full_name of=/dev/fd0
and then
rdev /dev/fd0 /dev/Your_root_partition
This will boot much faster. And it can be used to rerun
lilo in case it was corrupted.
By the way, always make the boot floppy during upgrade
or installation. If something had gone wrong so lilo didn't
work, you would have been pretty much up the creek, and would
probably ended up reinstalling. (There are ways around
that, but they are bit tricky.)
--
Leonard Evens [EMAIL PROTECTED] 847-491-5537
Dept. of Mathematics, Northwestern Univ., Evanston, IL 60208
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Posted already for the third time
Date: 5 Aug 1999 22:25:56 GMT
1) No idea.
2)
a) Did you have any errors during the compile that you ignored?
I got an error, the boot image was too big. I had to:
make bzImage
instead of
make boot
to get it small enough.
b) Did you run lilo after placing the following files in /boot
System.map-2.2.x-xx
System.map -> System.map-2.2.x-xx (symbolic link)
module-info-2.2.x-xx
module-info -> module-info-2.2.x-xx (symbolic link)
vmlinuz-2.2.x-xx
vmlinuz -> vmlinuz-2.2.x-xx (symbolic link)
where x-xx is replaced with the appropriate version number?
RT wrote:
>
> Hey,
>
> If have two problems with RED HAT 6.0 that I didn't had with the versions
> 5.0 and 5.2:
>
> 1) after running updatedb is the computer crashing;
> 2) after rebuiding and compiling the kernel in an completely exact way (like
> under 5.0 and 5.2) I get after rebooting under RED HAT 6.0 the following
> message:
> NO SETUP SIGNATURE FOUND......
> and I cannot start the new kernel.
> Under Red Hat 5.0 and 5.2 the new kernel started without any problem.
> Who can help me for resolving this two problems? Thank in advance.
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: newbie: cron won't work. just won't. need help.
Date: 5 Aug 1999 22:11:23 GMT
Here is an example crontab file that helps me "get it right"
======= crontab.example =========================================
#Min Hour Day Month Day Command
#of of of of of
#Hour Day Month Year Week
#---------------------------------------------------------------------------
0,10,20,30,40,50 * * * * /usr/bin/prog1
7 1 * * * /usr/bin/prog2
============================================================================
This example would run /usr/bin/prog1 every 10 minutes and
/usr/bin/prog2 at 1:07 every morning.
To get this to run use the following command line:
crontab crontab.example
To list your crontab entries:
crontab -l
To remove your crontab:
crontab -r
It's a good idea to list your crontab before you write a
new one. The new one will overwrite the current one.
Andrew de los Reyes wrote:
>
> I access my cron file for root: % cronat -e i set it to: ______________ 15 *
> * * * ifup ppp0 17 * * * * ifdown ppp0 ______________ these commands work as
> root, let me assure you. the man pages say cron updates every minute, but it
> wasn't so i rebooted. oh, don't tell me that wasn't necessary--i know--partly
> because the problem still exists. diring startup it stats the cron daemon:
> something like (from top of my head): starting cron daemon [ OK ] still,
> when the time rolls around nothing happens. what can i do? right now i'm just
> testing, but soon i would like to make some real use of it.
>
> -Andrew de los Reyes
>
> Sent via Deja.com http://www.deja.com/
> Share what you know. Learn what you don't.
------------------------------
From: [EMAIL PROTECTED]
Subject: Please Help: Error useing Backpack Hard Drive.
Date: Thu, 05 Aug 1999 20:09:51 GMT
Hi All,
I am new to Linux so please allow me if I am not making any sense here.
I tried to load some device drivers to activate my Back Pack Hard Disk
on my Caldera OpenLinux 2.2. It worked on the first shot by the
following commands:
#insmod paride
#insmod bpck
#insmod pd
Then I mounted the 1st partition (2GB) with:
#mount /dev/pda1 /mnt/BP01 vfat defaults,user 0 0
After that I can see all the directories and files in long filename
with:
#ls -al /mnt/BP01 | less
However after I reboot the notebook (I am running my Linux on a Sony
Vaio); I can no longer repeat the above procedure. I boot into Windows
98 and click on the BackPack applet under Control Panel and found:
BACKPACK HARDDRIVE 15.0
LPT 0378
PPC 50772D, ID98, Hard Drive
TxFW, RxBi, T1=3, T2=3, T8=3
MPD 2.01.14
I tested the hardware under Win98 by transfer some files back and forth
to make sure this is not a hardware problem. But as I boot back to my
Linux and ran "dmesg" I got the following log (note that I issued
"insmod pd verbose=2"). It seems the driver "pd" failed to talk to the
hardware for some reason. Could you please give me a hand to solve this
problem ? Thank you very much.
York Chan
/YC:yc
=============================
The following is from "dmesg"
=============================
Linux version 2.2.5 ([EMAIL PROTECTED]) (gcc version
egcs-2.91.60
19981201 (egcs-1.1.1 release)) #1 Sat Apr 3 21:49:22 MST 1999
Detected 265376461 Hz processor.
Console: colour VGA+ 80x30
Calibrating delay loop... 130.66 BogoMIPS
Memory: 63256k/65472k available (844k kernel code, 408k reserved, 892k
data,
72k init)
CPU: Intel Mobile Pentium MMX stepping 01
Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
Checking 'hlt' instruction... OK.
Checking for popad bug... OK.
Intel Pentium with F0 0F bug - workaround enabled.
POSIX conformance testing by UNIFIX
PCI: PCI BIOS revision 2.10 entry at 0xfda04
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Enabling I/O for device 00:3a
PCI: Enabling memory for device 00:48
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0 for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
Starting kswapd v 1.5
vesafb: framebuffer at 0x000a0000, mapped to 0xc00a0000, size 128k
vesafb: mode is 640x480x4, linelength=80, pages=50719
vesafb: scrolling: redraw
Console: switching to colour frame buffer device 80x30
fb0: VESA VGA frame buffer device
Detected PS/2 Mouse Port.
Serial driver version 4.27 with no serial options enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
ttyS02 at 0x03e8 (irq = 4) is a 16550A
pty: 256 Unix98 ptys configured
Real Time Clock Driver v1.09
RAM disk driver initialized: 16 RAM disks of 4096K size
PIIX4: IDE controller on PCI bus 00 dev 39
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xfcf0-0xfcf7, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xfcf8-0xfcff, BIOS settings: hdc:pio, hdd:pio
hda: TOSHIBA MK2105MAT, ATA DISK drive
ide2: ports already in use, skipping probe
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: TOSHIBA MK2105MAT, 2067MB w/0kB Cache, CHS=525/128/63, UDMA
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8
Partition check:
hda: hda1 hda2 hda3 hda4
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 72k freed
st: bufsize 32768, wrt 30720, max buffers 4, s/g segs 16.
CSLIP: code copyright 1989 Regents of the University of California
SLIP: version 0.8.4-NET3.019-NEWTTY-MODULAR (dynamic channels, max=256).
PPP: version 2.3.3 (demand dialling)
PPP line discipline registered.
NET4: Linux IPX 0.38 for NET4.0
IPX Portions Copyright (c) 1995 Caldera, Inc.
Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996
SB 3.1 detected OK (220)
parport0: PC-style at 0x378 [SPP,PS2]
parport0: no IEEE-1284 device present.
Adding Swap: 100796k swap-space (priority -1)
Linux PCMCIA Card Services 3.0.9
kernel build: 2.2.5 #1 Thu Mar 25 21:10:09 MST 1999
options: [pci] [cardbus]
Intel PCIC probe:
Ricoh RL5C475 PCI-to-CardBus at bus 0 slot 10, mem 0x68000000, 1 socket
host opts [0]: [isa irq] [io 3/6/1] [mem 3/6/1] [no pci irq] [lat
168/176] [bus 32/34]
ISA irqs (default) = 3,4,7,10,11,12,15 polling interval = 1000 ms
cs: IO port probe 0x1000-0x17ff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x140-0x147 0x170-0x177
0x320-0x327 0x370-0x37f 0x388-0x38f 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
paride: version 1.04 installed
paride: bpck registered as protocol 0
pd: pd version 1.05, major 45, cluster 64, nice 0
pda: 0x378 is parport0
pda: bpck: 0x378 unit 98 mode 0: 0 1 2 3 4 5 6 7 8 9 10 11 12
13
14 31
pda: bpck: 0x378 unit 98 mode 1: 0 1 1 2 2 3 3 4 4 5 5 6 6
7
7 8
pda: bpck: 0x378 unit 98 mode 2: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1
-1
-1 -1
pda: bpck: 0x378 unit 98 mode 3: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1
-1
-1 -1
pda: bpck: 0x378 unit 98 mode 4: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1
-1
-1 -1
pda: Autoprobe failed
pd: no valid drive found
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
------------------------------
From: Leonard Evens <[EMAIL PROTECTED]>
Subject: Re: Lilo Problems
Date: Thu, 05 Aug 1999 15:37:45 -0500
[EMAIL PROTECTED] wrote:
>
> On Wed, 04 Aug 1999 15:24:16 -0500, Leonard Evens <[EMAIL PROTECTED]> wrote:
>
> >sj grevett wrote:
> >>
> >> Please could you tell me how to get rid of lilo? I have tried formating the
> >> hd but that has failed along with fdisk. It has sent one of my systems into
> >> an internal loop as linux is no longer installed on it but lilo is left.
> >
> >What you probably want to do is to restore the Master Boot Record.
> >Under Windows, make a startup disk. (Use any machine with Windows
>
> excuse me? "any" machine? how about windows NT?
Oops! You've got me there.
Any MS Windows machine.
>
> >Use Add/Remove Programs
> >in the Control Panel; it is an option under that.) Boot
> >from the startup floppy and run
> >fdisk /mbr
> >That should restore your master boot record.
> >
> >-
> >-
> >
> >Leonard Evens [EMAIL PROTECTED] 847-491-5537
> >Dept. of Mathematics, Northwestern Univ., Evanston, IL 60208
>
> dbcooper
>
> Friends are what you have,
> Friendship is what you get.
>
> www.members.home.com/dbcooper
--
Leonard Evens [EMAIL PROTECTED] 847-491-5537
Dept. of Mathematics, Northwestern Univ., Evanston, IL 60208
------------------------------
From: [EMAIL PROTECTED] (Chris Butler)
Crossposted-To: comp.os.linux.advocacy
Subject: Re: Is Linux A Memory Hogging OS?
Date: 4 Aug 1999 17:37:58 +0100
[comp.os.linux.advocacy - 3 Aug 1999 08:58:11 GMT] * Johnny wrote *
>>I never got the problem during less CPU-intensive operations, nor for
>>CPU-intensive operations that only lasted a few seconds. The CPU was not
>>overheating except during long periods of high demand. Ergo, more idle
>>--> less hot.
> ...
> A couple of notes on the use of HLT in Linux: Support for this has to be
> compiled into the kernel. On multiple CPU systems HTL will not be used even
> if support has been compiled into the kernel.
Really? Where did you get this information? What version of the kernel are
you referring to?
Looking at the two kernel sources I have here (2.2.10 and 2.3.10), HLT is
used unconditionally, unless a CPU with a "hlt bug" is detected at startup,
or if you pass the "no_hlt" option to the kernel. There are two different
routines for UP and SMP, but they both call HLT.
Take a look at arch/i386/kernel/process.c if you wish.
--
Chris Butler
<[EMAIL PROTECTED]>
------------------------------
From: Leonard Evens <[EMAIL PROTECTED]>
Subject: Re: newbie: what is "Segmentaion fault"?
Date: Thu, 05 Aug 1999 16:38:22 -0500
Siemel Naran wrote:
>
> On Thu, 05 Aug 1999 02:14:15 +0200, Jens Schwepe <[EMAIL PROTECTED]> wrote:
>
> >any program running on the system is assigned some memory space to store data
> >and everything else. the almighty kernel does this, and everyone is happy. just
> >one limitation for the program: it must not (= is not allowed to) write to
> >memory space that it does _not_ own. if it tries (the "segmentation fault",
> >because the wrong memory segment was adressed), the almighty kernel will cancel
> >this ungrateful program. it falls into pieces (exactly one piece, the "core",
> >as you asked) and this core is dumped into the current location the program
> >resided. it namely is a file "core" and contains all the memory data the
> >program was assigned when it failed, thus if you own 4Gigs of Memory and a
> >database process switching 3Gigs of memory over and over fails, you will have
> >3Gigs of "core" on your disk ;-)
> >
> >Just delete it, if you find it. You will -hopefully- never have to go through
> >all the megabytes of crushed memory.
>
> One can also do this
> cat /dev/null > core
> This creates a core file of size 0. When the program want to dump core,
> it will see that there is already a core file, even though this file has
> size zero. And the program won't dump core.
You also have to make sure the file is not writable by the
program doing the core dump. Programs don't check to see if
there is already a program named core, nor does the system
as far as I know. But of course it won't write over an existing
file it does not have permission to write to.
>
> I've noticed that my new system never dumps core, even for a segmentation
> fault. How can I make it dump core again?
>
> --
> ----------------------------------
> Siemel B. Naran ([EMAIL PROTECTED])
> ----------------------------------
--
Leonard Evens [EMAIL PROTECTED] 847-491-5537
Dept. of Mathematics, Northwestern Univ., Evanston, IL 60208
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list (and comp.os.linux.misc) via:
Internet: [EMAIL PROTECTED]
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Misc Digest
******************************
