Linux-Misc Digest #409, Volume #24                Tue, 9 May 00 02:13:01 EDT

Contents:
  Re: Benchmarks and relative speeds (Richard Steiner)
  Re: Extracting multiple, COMPRESSED, tar files? (Allin Cottrell)
  Re: Need Write Access to Linux ext-fs from DOS/Win95! (Rod Smith)
  Re: finding out what distribution you have (s. keeling)
  kde system events sound (h8te)
  Re: PPPProblems (Bill Unruh)
  Re: tar vs afio usage - help please (s. keeling)
  Re: Extracting multiple, COMPRESSED, tar files? (mh)
  Re: Using mount from general user account (mh)
  Re: kde system events sound (Patricia)
  install halts (Alexander K)
  What is the /boot/System.map file in RedHat distrib ? (Pierre Vigneras)
  mail all users ("Jason Kayarian")
  Re: K7V support ("Kevin J. Walchko")
  Re: What is the best source for working with core dumps? (Leonard Evens)

----------------------------------------------------------------------------

From: [EMAIL PROTECTED] (Richard Steiner)
Crossposted-To: uk.comp.os.linux
Subject: Re: Benchmarks and relative speeds
Reply-To: [EMAIL PROTECTED]
Date: Mon, 08 May 2000 21:58:58 -0500

Here in comp.os.linux.misc, [EMAIL PROTECTED] (brian moore)
spake unto us, saying:

>On 08 May 2000 17:10:55 +0100 (BST), 
> David Damerell <[EMAIL PROTECTED]> wrote:

>> Older versions of the _kernel_ do not automagically discover memory above
>> 64Mb, irrespective of the BIOS - this needs the append argument.
> 
>And current versions with some newer BIOS's.  (Check deja for this going
>back to December -- some BIOS makers changed the API they use around
>then, and several people who 'upgraded' their BIOS found that even the
>current kernels would no longer detect their RAM correctly.)
>
>Even with 2.2, some systems still require the 'mem='.

Very true.  My IBM IntelliStations are not new (PPros with 128MB and
96MB respectively), but the 2.2.14 kernel packaged with Mandrake 6.1
can't see anything at all about 64MB unless explicitly told about it
in that manner.

-- 
   -Rich Steiner  >>>--->  [EMAIL PROTECTED]  >>>--->  Bloomington, MN
      OS/2 + BeOS + Linux + Solaris + Win95 + WinNT4 + FreeBSD + DOS
       + VMWare + Fusion + vMac + Executor = PC Hobbyist Heaven! :-)
        Real programmers use ER SNAP$ and read Fieldata (in octal!)

------------------------------

From: Allin Cottrell <[EMAIL PROTECTED]>
Subject: Re: Extracting multiple, COMPRESSED, tar files?
Date: Mon, 08 May 2000 23:48:13 -0400

mh wrote:
> 
> Dances With Crows wrote:

> > #!/bin/bash

> > for i in `ls *.tar.gz`; do

simpler: 
    for i in *.tar.gz ; do

(for each file satisfying the globbing pattern)

> >    tar xvzf $i

unpack that file, OK

> >    j=echo $i | sed -e 's/\.tar\.gz//' -
> >    cd $j

oof!
       cd ${i%.tar.gz}

cd to the directory whose name is found by stripping the 
'tar.gz' off the original filename.  And so on.

> You're right. That is nasty! 

Well, not really.  It's an example of a sequence of actions 
which can be programmed quite easily in one little shell
script, but that would leave the average (or even above
average) GUI aficionado futzing around with the mouse for
ages.

-- 
Allin Cottrell
Department of Economics
Wake Forest University, NC

------------------------------

Reply-To: [EMAIL PROTECTED]
From: [EMAIL PROTECTED] (Rod Smith)
Subject: Re: Need Write Access to Linux ext-fs from DOS/Win95!
Crossposted-To: comp.os.linux.setup
Date: Tue, 09 May 2000 04:26:19 GMT

[Posted and mailed]

In article <8f80lr$s1f$[EMAIL PROTECTED]>,
        [EMAIL PROTECTED] writes:
> Hi, there,
> 
> I tried to re-partition my SCSI HD during the weekend
> to recover some space. Somehow, the partition number
> for the two Linux partitions (from sda8 & sda9 to
> sda6 & sda7). Now Linux won't boot.
> 
> I think I have to modify these two files:
> lilo.conf
> fstab
> (is there any files I have to modify?)

Editing /etc/lilo.conf alone won't make the system bootable; you'll need
to re-run lilo after making the changes, and of course you can't do that
until you've booted. Once you get access to the disk, though, you can copy
your kernel file to a DOS disk and load it using LOADLIN.EXE. That'll get
you up and running. You'll still need to modify /etc/fstab, though, as you
say.

> Of course, I don't have a Linux boot disk!
> Is there any SW out there that allow me to edit these
> files from DOS/Win95?

Yes. Check out Explore2fs:

http://uranus.it.swin.edu.au/~jn/linux/Explore2fs.htm

One caution: Beware of DOS-vs-Linux line ending differences. I don't
recall offhand if Explore2fs has the ability to automatically handle
this. If not, you may need to convert back and forth in Windows. I don't
know if /etc/fstab is one of those files that'll cause problems if it's
got the wrong sort of EOL characters.

-- 
Rod Smith, [EMAIL PROTECTED]
http://www.rodsbooks.com
Author of books on Linux networking & multi-OS configuration

------------------------------

From: [EMAIL PROTECTED] (s. keeling)
Subject: Re: finding out what distribution you have
Reply-To: [EMAIL PROTECTED]
Date: Tue, 09 May 2000 04:30:18 GMT

On Tue, 09 May 2000 03:00:09 GMT, \
Stewart Honsberger <[EMAIL PROTECTED]> wrote:
> On 8 May 2000 13:35:19 -0700, Sam E. Trenholme wrote:
> >>I am a user on two mail servers running under Linux at our
> >>college. How can I tell the distribution from which Linux was
> >>installed?
> >
> >Each distribution has a signature.
> 
> Agreed. If you find any instance of "yast" or "yast2", you're on a SuSE box.

Debian's are /etc/debian_version, dpkg, and apt-get.

-- 
[EMAIL PROTECTED] (Stephen) TopQuark Software & Serv. Enquire within.
    [sed 's/NO@SPAM./@/g']               Contract programmer, server bum.  
    Any technology distinguishable from magic is insufficiently advanced.

------------------------------

From: h8te <[EMAIL PROTECTED]>
Subject: kde system events sound
Date: Tue, 09 May 2000 04:30:08 GMT

hey i got a problem , i cant use any sound for my sysetem events , all
other sound works fine , i can play cd and stuff , just cant have any sound
for the system stuff ie: log on , log off , any help? , my sound works fine
with gnome just not kde!

--
Posted via CNET Help.com
http://www.help.com/

------------------------------

From: [EMAIL PROTECTED] (Bill Unruh)
Subject: Re: PPPProblems
Date: 9 May 2000 04:33:24 GMT

In <[EMAIL PROTECTED]> Ruud Mol <[EMAIL PROTECTED]> writes:

]Hey there...
]Got this small problem - well actually "problem" is a big word but it
]just annoys me...
]I'm using Slackware 7.0 with KDE 1.1.2 and my self-compiled kernel
]2.2.13. somehow at boot time i get 
]an annoying message saying that my PPP modules have not been loaded,
]right after the message saying "PPP line registered". This is not really
]annoying; the most annoying bit is that kppp tells me that there are no
]ppp modules loaded and when i try to connect all goes well. And that
]warning annoys me because I have to click something  :)
]Does anyone know what I've screwed up this time?

Yes, you used kppp. It is a bug in kppp. They apparently used a bug in
the kernel to determine if ppp was available in the kernel. When that
bug was fixed, kppp broke. Get an upgrade to kppp (or stop using it).
]Tnx!

]Ruud

]-- 
]COGITO ERGO CONFUSIO
]I think therefor I am confused

------------------------------

From: [EMAIL PROTECTED] (s. keeling)
Subject: Re: tar vs afio usage - help please
Reply-To: [EMAIL PROTECTED]
Date: Tue, 09 May 2000 04:36:32 GMT

On Mon, 08 May 2000 20:58:48 GMT, jsrockford <[EMAIL PROTECTED]> wrote:
> I'm trying to changeover from using 'tar' for backups to 'afio' as it
> has better recovery capabilities if the archive file gets corrupted.
> Currently I'm using 'tar' as follows:
> 
> tar czvf BACKUP.tar.gz -T FILELIST.LIST
> 
> but haven't been able to figure out how to get 'afio' to accept input
> from the FILELIST.LIST file.  I've read the man pages and searched
> DejaNews but haven't figured it out. Can someone give me the correct
> usage for this? TIA

fwiw, I've never used that.  I just go:

  find / -depth -print | grep -v "^/proc" | afio -o -s 2000m /dev/st0
  
hth.

-- 
[EMAIL PROTECTED] (Stephen) TopQuark Software & Serv. Enquire within.
    [sed 's/NO@SPAM./@/g']               Contract programmer, server bum.  
    Any technology distinguishable from magic is insufficiently advanced.

------------------------------

Date: Tue, 09 May 2000 04:38:40 +0000
From: mh <[EMAIL PROTECTED]>
Subject: Re: Extracting multiple, COMPRESSED, tar files?

Dances With Crows wrote:
> 
> On Tue, 09 May 2000 02:49:36 +0000, mh
> <<[EMAIL PROTECTED]>> shouted forth into the ether:
> >Dances With Crows wrote:
> >You're right. That [shell script]is nasty!
> 
> Well, I never claimed to be Larry Wall... :-)
> 
> I'll dissect the thing line-by-line so you can figure things out:
> 
> >> #!/bin/bash
> first line of any script; tells kernel to run this with /bin/bash.
> 
> >> # Warning, this is hasty and tasteless and nasty.
> >> # call this from the directory containing the first collection of tarballs
> >> # this only goes 2 levels deep
> >> # making it go deeper/recurse is left as an exercise
> comments.
> 
> >> for i in `ls *.tar.gz`; do
> Start of a loop.  This means "Take the results of the command 'ls
> *.tar.gz' and set the variable i to each result in turn, then do the stuff
> inside the loop for each value of i."
> 
> >>    tar xvzf $i
> Extract the file that i is set to.
> 
> >> j=`echo $i | sed -e 's/\.tar\.gz//' -`
> The worst line to understand.  This strips the .tar.gz from the value of i
> and assigns it to the variable j, because by convention,
> "blah-1.2.3.tar.gz" untars to a directory called "blah-1.2.3" which
> contains a bunch of files.
> 
> >>    cd $j
> cd to the directory we created by untarring, of course.
> 
> >>    for k in `ls *.tar.gz`; do
> List all tarballs, set the value of k to each tarball in turn
> 
> >>        tar xvzf $k
> Extract all tarballs in the subdirectory.
> 
> >>        done
> Finish of the k loop
> 
> >>    cd ..
> Go back up to the directory we started in
> 
> >>    done
> Finish of i loop.
> 
> >Perhaps you could recommend a GUI archiver?  Didn't know they existed,
> >or could process recursive tar-zipped archives.
> 
> There's something for KDE called ark; it handles ZIPs and tarballs.  I'm
> certain that similar packages exist for GNOME as well, and indeed for raw
> Xlib.  Check out http://freshmeat.net and search for "GUI archiver";
> you'll find at least 10 programs to try out.  Wish I could be more help
> here, but since I've been using Linux for almost a year now I've become a
> total command-line junkie....
> 
Thanks for the tutorial. You're awesome!  Hard to believe you've only
been playing with Linux for a year.  That's about how long I've been
using it. Yeah, the command line is amazingly efficient--once you have
the syntax and the options down.  You seem to be a regular among the
Linux ngs. Thanks for the GUI archiver tip, and keep up the good work. I
know I appreciate it.  :-)

------------------------------

Date: Tue, 09 May 2000 04:47:51 +0000
From: mh <[EMAIL PROTECTED]>
Subject: Re: Using mount from general user account

Kari Pahula wrote:
> 
> jason denton <[EMAIL PROTECTED]> wrote:
> >I'm running Suse 6.3 and I have several devices marked as user mount in fstab;
> >my floppy drive, zip drive, and cdrom. However, whenever I try to mount these
> >devices as anything other than root I get a message saying that only root may
> >use mount. All the docs seem to suggest that this is not the case, and that
> >I should be able to mount those things appropriate marked in fstab. How can
> >I fix this so that I can mount floppy/zip/cdroms without being root?
> 
> Users may use mount to mount devices only to their designated mount
> points, mount doesn't allow an user to define any other mount point.
> 
> For example, to mount floppy, you can use either of these:
> $ mount /dev/fd0
> $ mount /floppy (or whatever Suse has)
> 
> but never:
> $ mount /dev/fd0 /floppy
> 
> Mount command seems to be a bit stupid and only look for the presence
> of a second argument, not what it says.  Also, you can't use -t to
> specify the file system type (not even for floppies... :-( ).
> 
> Also, the user must have a permission to read (and maybe write) the
> devices.  The sanest way of doing this is with:
> # adduser luser floppy

Hey, thanks a bunch for the solution to my problem.  I posted this same
issue some time ago, but never got an answer.  It's little stuff like
this that will make you crazy!  I gave up and just did everything root.
You've just made life a little easier (and saner) for at least 2
people.  :-)

------------------------------

From: Patricia <[EMAIL PROTECTED]>
Subject: Re: kde system events sound
Date: Tue, 9 May 2000 06:50:22 +0200

On Tue, 09 May 2000, h8te wrote:
>hey i got a problem , i cant use any sound for my sysetem events , all
>other sound works fine , i can play cd and stuff , just cant have any sound
>for the system stuff ie: log on , log off , any help? , my sound works fine
>with gnome just not kde!
>
>--
>Posted via CNET Help.com
>http://www.help.com/
Hi
As root type
ln -s /etc/sysconfig/soundcard /etc/sysconfig/sound 
--
Good Luck
Patricia

http://www.crosswinds.net/~beginnerslinux
Red Hat Linux release 6.0 (Hedwig)
Kernel 2.2.5-15 
  6:50am  up  9:57,  2 users,  load average: 0.19, 0.31, 0.33
Tue May  9 06:50:43 CEST 2000

------------------------------

From: Alexander K <[EMAIL PROTECTED]>
Subject: install halts
Date: Tue, 09 May 2000 04:45:21 GMT

hello!

i had mandrake7 on my puter and removed it a few days ago. repartitioned
the hdd and reinstalled win on 4gig (hdd is total 13.5gig).

now i've tried reinstalling linux both via ftp, cdrom and hdd.
almost nothing worked.
first i tried slack but erased it due to the NIC not working.

so i tried mandrake7 again. a skeletoninstall (only bout 300meg no X),
but it just froze about 15-20% into the actual installing.
i have tried these:
mandrake7 ftp (ftp.sunet.se)
mandrake7 hdd
redhat6.2 ftp      -"-
redhat6.2 hdd
bestlinux ftp      -"-
(both man, rh and best bootdisks recognized my NIC properly as rtl8139)


ALL of these freeze just like that.

and i also have a cdrom with redhat6.0. when i tried that it froze when
writing the ext2 filesystem. (hdderror?)
i have also tried different ftp's.

when formatting the partitions i let it check for bad blocks.
none of the (attempted) installs reported any problems.

so where can the problem be?

funny thing is that slackware CAN be installed. it doesnt hang.
now i am also on my way to getting the NIC working (found the driver
among the experimental ones when compiling the kernel (2.2.15)).

but of course i still feel i need to know why those other installs
failed.
could it after all be a hdd problem? (since they all seem to freeze
after about the same amount of installed software)

i have slack on the rest of the hdd (4part: / /home /x +swap)
could i do a thorough hdd examination via some command? (which?)
and why didn't slack complain in that case??? (cause it seems to work
ok... but i have only had it a day so i cant really tell i guess)


and another thing:)
what's the /etc/conf.modules for?
in that file i see:
alias net-pf-4 off
alias net-pf-5 off

what's that for?
do i need to change anything here when i recompile the kernel (and
choose >=1 module)?


thanks in advance / alex

puter-specs:
PIII 450
192M ram
13.5gig IBM deskstar
accton e1207d-tx nic (realtek 8139) on a 10mbps ethernetconnection



--
. 
. 
... ak42 at kurir dot net ...

--
. 
. 
... ak42 at kurir dot net ...


Sent via Deja.com http://www.deja.com/
Before you buy.

------------------------------

From: Pierre Vigneras <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: What is the /boot/System.map file in RedHat distrib ?
Date: Tue, 09 May 2000 07:15:05 +0200

This is a multi-part message in MIME format.
==============476B5C6366491C41AAF28FB1
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hello everyone !

Sorry if this question has already been asked but i didn't found the
answer anywhere !

Here the problem:

What are System.map* files ? Can i remove them (since lilo only use
/boot/map) ?
What are module-info files ?
How can i boot with my new kernel (vmlinuz-2.2.14smp) ?

My configuration :
I'm using RedHat 6.1.
I have build a new kernel (2.2.14smp) and i have modified my
/etc/lilo.conf:

/******************************************************/
[root@moucheron /root]# cat /etc/lilo.conf 
boot=/dev/sda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
default=linux

image=/boot/vmlinuz-2.2.12-20smp
        label=linux
        initrd=/boot/initrd-2.2.12-20smp.img
        read-only
        root=/dev/sda2

image=/boot/vmlinuz-2.2.12-20
        label=linux-up
        initrd=/boot/initrd-2.2.12-20.img
        read-only
        root=/dev/sda2

image=/boot/vmlinuz-2.2.14smp
        label=new
        read-only
        root=/dev/sda2
        vga=ask

[root@moucheron /root]#
/***********************************************************/

After running lilo :

/***********************************************************/
[root@moucheron /root]# lilo -t -v -v -v   // The real command (without
'-t' option (test)) didn't show any errors !
LILO version 21, Copyright 1992-1998 Werner Almesberger

Caching device /dev/hda (0x0300)
[...]
Caching device /dev/sdb8 (0x0818)
Reading boot sector from /dev/sda
Merging with /boot/boot.b
Device 0x0802: BIOS drive 0x80, 64 heads, 8715 cylinders,
               32 sectors. Partition offset: 1050624 sectors.
Secondary loader: 8 sectors.
Device 0x0802: BIOS drive 0x80, 64 heads, 8715 cylinders,
               32 sectors. Partition offset: 1050624 sectors.
Boot image: /boot/vmlinuz-2.2.12-20smp
Device 0x0802: BIOS drive 0x80, 64 heads, 8715 cylinders,
               32 sectors. Partition offset: 1050624 sectors.
Setup length is 7 sectors.
Mapped 1268 sectors.
Mapping RAM disk /boot/initrd-2.2.12-20smp.img
Device 0x0802: BIOS drive 0x80, 64 heads, 8715 cylinders,
               32 sectors. Partition offset: 1050624 sectors.
RAM disk: 614 sectors.
Added linux *
    <dev=0x80,hd=63,cyl=109,sct=146>
    "ro root=802"
Boot image: /boot/vmlinuz-2.2.12-20
Device 0x0802: BIOS drive 0x80, 64 heads, 8715 cylinders,
               32 sectors. Partition offset: 1050624 sectors.
Setup length is 7 sectors.
Mapped 1219 sectors.
Mapping RAM disk /boot/initrd-2.2.12-20.img
Device 0x0802: BIOS drive 0x80, 64 heads, 8715 cylinders,
               32 sectors. Partition offset: 1050624 sectors.
RAM disk: 613 sectors.
Added linux-up
    <dev=0x80,hd=0,cyl=110,sct=138>
    "ro root=802"
Boot image: /boot/vmlinuz-2.2.14smp
Device 0x0802: BIOS drive 0x80, 64 heads, 8715 cylinders,
               32 sectors. Partition offset: 1050624 sectors.
Setup length is 7 sectors.
Mapped 888 sectors.
Added new
    <dev=0x80,hd=47,cyl=126,sct=156>
    "ro root=802"
Map file size: 30720 bytes.
The boot sector and the map file have *NOT* been altered.
[root@moucheron /root]# 
/***************************************************************/

After a reboot : i see
/***************************************************************/
[...]
VFS: Mounted root (ext2 filesystem).
ncr53c8xx: at PCI bus 0, device 11, function 0
ncr53c8xx: 53c875E detected with Tekram NVRAM
ncr53c875E-0: rev=0x26, base=0xdd000000, io_port=0xa400, irq=17
ncr53c875E-0: Tekram format NVRAM, ID 7, Fast-20, Parity Checking
ncr53c875E-0: on-chip RAM at 0xdc800000
ncr53c875E-0: restart (scsi reset).
ncr53c875E-0: Downloading SCSI SCRIPTS.
scsi0 : ncr53c8xx - version 3.2a-2
scsi : 1 host.
  Vendor: IBM       Model: DDRS-39130D       Rev: DC1B
  Type:   Direct-Access                      ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 6, lun 0
ncr53c875E-0-<6,0>: tagged command queue depth set to 8
ncr53c875E-0-<6,*>: FAST-20 WIDE SCSI 40.0 MB/s (50 ns, offset 15)
SCSI device sda: hdwr sector= 512 bytes. Sectors= 17850000 [8715 MB]
[8.7 GB]
 sda: sda1 sda2 sda3
Kernel panic : VFS can't mount root on /dev/sda2
/********************************************************************/
The last message is something "the like"...

I suppose that since Redhat installation use ramdisk (initrd), there is
a problem with my new kernel wich didn't use it.

If i see in the /boot directory :
/*************************************************/
[root@moucheron /root]# ls -al /boot
total 10781
drwxr-xr-x   2 root     root         1024 May  5 15:22 .
drwxr-xr-x  24 root     root         1024 Mar  2 15:19 ..
lrwxrwxrwx   1 root     root           20 Feb 11 18:19 System.map ->
System.map-2.2.12-20
-rw-r--r--   1 root     root       191102 Sep 27  1999
System.map-2.2.12-20
-rw-r--r--   1 root     root       182834 Sep 27  1999
System.map-2.2.12-20BOOT
-rw-r--r--   1 root     root       202226 Sep 27  1999
System.map-2.2.12-20smp
-rw-r--r--   1 root     root          512 Jul  9  1999 boot.0800
-rw-r--r--   1 root     root         4568 May  5 11:47 boot.b
-rw-r--r--   1 root     root          612 Sep 22  1999 chain.b
-rw-r--r--   1 root     root       313673 Feb 11 18:26
initrd-2.2.12-20.img
-rw-r--r--   1 root     root       314036 Feb 11 18:26
initrd-2.2.12-20smp.img
-rw-r--r--   1 root     root       308009 Jul  9  1999
initrd-2.2.5-15.img
-rw-r--r--   1 root     root       308488 Jul  9  1999
initrd-2.2.5-15smp.img
lrwxrwxrwx   1 root     root           22 Jul 31  1999
initrd-2.2.5-22smp.img -> initrd-2.2.5-15smp.img
-rw-r--r--   1 root     root       695162 Jul 31  1999
kernel-2.2.5-22smp.my
-rw-r--r--   1 root     root          237 May  5 12:18 kernel.h
-rw-------   1 root     root        30720 May  5 12:15 map
lrwxrwxrwx   1 root     root           21 Feb 11 18:19 module-info ->
module-info-2.2.12-20
-rw-r--r--   1 root     root        11773 Sep 27  1999
module-info-2.2.12-20
-rw-r--r--   1 root     root        11773 Sep 27  1999
module-info-2.2.12-20smp
-rw-r--r--   1 root     root          620 Sep 22  1999 os2_d.b
-rwxr-xr-x   1 root     root      1544394 Sep 27  1999 vmlinux-2.2.12-20
-rwxr-xr-x   1 root     root      1469971 Sep 27  1999
vmlinux-2.2.12-20BOOT
-rwxr-xr-x   1 root     root      1647660 Sep 27  1999
vmlinux-2.2.12-20smp
lrwxrwxrwx   1 root     root           17 Feb 11 18:19 vmlinuz ->
vmlinuz-2.2.12-20
-rw-r--r--   1 root     root       622784 Sep 27  1999 vmlinuz-2.2.12-20
-rw-r--r--   1 root     root       592397 Sep 27  1999
vmlinuz-2.2.12-20BOOT
-rw-r--r--   1 root     root       647807 Sep 27  1999
vmlinuz-2.2.12-20smp
-rw-r--r--   1 root     root       453234 May  5 09:29 vmlinuz-2.2.14smp
-rw-r--r--   1 root     root       709302 Jul 23  1999
vmlinuz-2.2.5-15smp.new
-rw-r--r--   1 root     root       695161 Aug  6  1999
vmlinuz-2.2.5-22smp.new
[root@moucheron /root]# 
/****************************************************/
What are System.map* files ? Can i remove them (since lilo only use
/boot/map) ?
What are module-info files ?
How can i boot with my new kernel (vmlinuz-2.2.14smp) ?

Please help ...




-- 
Pierre Vign�ras
http://dept-info.labri.u-bordeaux.fr/~vigneras/

Equipe syst�mes et objets distribu�s
http://jccf.labri.u-bordeaux.fr/jodo/

LaBRI
http://dept-info.labri.u-bordeaux.fr/
==============476B5C6366491C41AAF28FB1
Content-Type: text/x-vcard; charset=us-ascii;
 name="vigneras.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for Pierre Vigneras
Content-Disposition: attachment;
 filename="vigneras.vcf"

begin:vcard 
n:Vign�ras;Pierre
tel;cell:06.81.50.55.51
tel;work:05.56.84.24.87
x-mozilla-html:FALSE
url:http://dept-info.labri.u-bordeaux.fr/~vigneras/
org:LaBRI;Computer Science
version:2.1
email;internet:[EMAIL PROTECTED]
title:Student
adr;quoted-printable:;;R=E9sidence les pierres du 
campus=0D=0AA/26;Gradignan;;33170;France
note;quoted-printable:<A 
href=3D"http://jccf.labri.u-bordeaux.fr/jodo/">=0D=0ADistributed Systems and Objects 
team</A>=0D=0A=0D=0A=0D=0A
x-mozilla-cpt:;-32672
fn:Pierre Vign�ras
end:vcard

==============476B5C6366491C41AAF28FB1==


------------------------------

From: "Jason Kayarian" <[EMAIL PROTECTED]>
Subject: mail all users
Date: Tue, 9 May 2000 01:19:16 -0700

Hello,

I'm running RH 5.2 and would like to send an e-mail message to every user on
the system without having to do each one individually. Any ideas? Is there a
command on the system for this or do I have to do it with a script. Would
anyone please mail me directly at my address, [EMAIL PROTECTED]

Thank You
Jason
[EMAIL PROTECTED]



------------------------------

From: "Kevin J. Walchko" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware
Subject: Re: K7V support
Date: Tue, 09 May 2000 05:27:58 GMT

i have a k7v w/ 700 athlon running mandrake 7.0, redhat 6.1 would not
install for some reason.

kevin

Ed Camacho wrote:
> 
> Sandhitsu R Das wrote:
> >
> >
> > Asus K7V w/ Athlon and WD 7200 ATA/66 HDD - is this combination well
> > supported in Linux ?
> >
> 
> I'm running an Athlon 750 w/ a K7V and 2 WD 7200 ATA/66 drives.  I tried to
> install Mandrake 6.1 (I think I got that ver right) and it flaked out
> everytime when trying to boot (MTRR error I think).  I just got a hold of
> Mandrake 7.0, installed it, and away I went.  I dumbed down the drive that
> runs linux to ATA33, but I've heard there is ATA66 support in Kernel 2.3.x?
> I'll look into it, but as for now, a K7V and Athlon will run Mandrake 7 (and
> consequently RH I guess) beautifully.  No problems at all.
> 
> --
> Posted via CNET Help.com
> http://www.help.com/

------------------------------

From: Leonard Evens <[EMAIL PROTECTED]>
Subject: Re: What is the best source for working with core dumps?
Date: Tue, 09 May 2000 00:20:34 -0500

brian moore wrote:
> 
> On Mon, 08 May 2000 19:10:31 -0500,
>  Leonard Evens <[EMAIL PROTECTED]> wrote:
> > Harlan Grove wrote:
> > >
> > > So does this mean there's no way to pull information from
> > > core files without having the source code and a binary with
> > > debugging information? What's the format of a core file? I
> > > assume it's the memory image of the errant process, but
> > > does it include the stack and register status at the moment
> > > of failure? If so, at the end?
> >
> > Of course you can always find out which program produced the
> > core dump by using the command
> > file core
> > The core dump is a memory image as you say.   I've never tried
> > to look at one under Linux, but I did under SunOS.   You can
> > probably get information about stack and register status, but
> > what good would that do you?
> 
> With source?  It would allow you to see what it was doing when it
> crashed, which may provide the clue to fixing the cause of the crash.
>

Wouldn't you have to translate the source into assembly code
first?
 
> --
> Brian Moore                       | Of course vi is God's editor.
>       Sysadmin, C/Perl Hacker     | If He used Emacs, He'd still be waiting
>       Usenet Vandal               |  for it to load on the seventh day.
>       Netscum, Bane of Elves.

-- 

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
******************************

Reply via email to