Linux-Misc Digest #423, Volume #24 Wed, 10 May 00 07:13:03 EDT
Contents:
Re: Programs for Linux (Carsten Pitz)
Print Jobs are not deleted (Philipp Maier)
Re: Need solid facts: Why Linux over NT (Peter Buijsman)
Re: Damaged tar.gz file (rob)
Re: SCSI devices and SMP kernels (Pierre Vigneras)
invalid superblock: e2fsck -f- b 8193 failed (Uwe Brauer)
Re: Fvwm2 and Gnome/KDE ?!? (Marc D. Williams)
Re: Damaged tar.gz file (Hoosain Madhi)
Re: Damaged tar.gz file (Hoosain Madhi)
Re: LILO 1024 cyl thing (Robert Heller)
Re: Where is stddef.h? (Will Dyke)
Remove CD without umount ("P.G. Willemsen")
----------------------------------------------------------------------------
From: Carsten Pitz <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.advocacy,linux.dev.newbie
Subject: Re: Programs for Linux
Date: Wed, 10 May 2000 10:02:41 GMT
(1) GNU assembler (gas)
(2) Oracle maybe is a good choice
BTW, I am quite intersted in why you need an assembler.
Carsten
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: Philipp Maier <[EMAIL PROTECTED]>
Subject: Print Jobs are not deleted
Date: Wed, 10 May 2000 12:01:26 +0000
Reply-To: [EMAIL PROTECTED]
Hi,
a collegue of mine has a problem with lpr (Suse Linux 6.3): Originally
he had set up a remote printer (using Yast) and everthing worked fine.
Then, however, he decided to install StarOffice and since then lpr shows
a strange behavior: Print jobs are not deleted, the printer queue gets
longer and longer and only the first document is printed.
Example:
1. He wants to print test1.txt - test1.txt is printed, but afterwards
lpc status remote still shows "1 entry in spool area".
2. He wants to print test2.txt - test1.txt (!) is printed and lpc status
shows "2 entries in spool area".
3. He wants to print test3.txt - test1.txt is printed and lpc status
shows "3 entries in spool area".
If the print jobs are deleted manually 1 document can be printed, then
the whole trouble starts again.
Any suggestions? Help is appreciated!
Philipp Maier
--
Sylt, SuSE Linux, Maerklin mini-club, Psion Serie 5mx Pro & GPS:
http://www.philipp-maier.de
------------------------------
From: Peter Buijsman <[EMAIL PROTECTED]>
Subject: Re: Need solid facts: Why Linux over NT
Date: Wed, 10 May 2000 12:13:14 +0200
Reply-To: [EMAIL PROTECTED]
On Wed, 10 May 2000 02:10:48 GMT, Jim Morrissey <[EMAIL PROTECTED]>
wrote:
>I need to put together a presentation to convince management to use
>Linux rather than NT. To do this properly and succeed, I need solid
>facts and figures on why Linux is the better OS. Any help or pointers to
>URL's that cover this topic would be well appreciated!
Are you talking about servers only, or do you also want to replace the
clients?
I see a lot op companys that use a hybride server park: some of them
are Linux, some of them are NT.
Most widely used NT program is M$ Exchange server and Outlook clients.
That alone is enough reason for a lot of server admins to keep on
using at least one NT server for internal mail handling. (Internet)
connectivity is preferably transfered to Linux. It's much cheaper to
run a simple Linux machine that handles huge amounts of mail, http and
ftp traffic, than to have a huge and very expensive NT machine that is
still only able to do half of the requests.
Linux is much more configurable, NT is preffered by sysadmins who like
to get things done without having to understand every bit of it.
Replacing clients is something you should really reconsider. It might
be a good choice based on cost and interconnectivity, however, the
people who are supposed to work with it are probably used to Windows
software. As a system administrator it's one of your tasks to create a
workstation people can work on. Most of the users are completely
computer-illeterate but feel they have the knowledge to play around.
More than once I've encountered users calling the helpdesk asking why
their downloaded program won't install, or why their dos-prompt is
looking so weird. They just won't understand there's life beyond
Windows. :-) If you are planning to replace the clients, first make
sure EVERY application your users are working with has a equivalent
version for Linux.
Linux is free, support is everywhere, security is far better than NT
machines, it requires less maintenance once everything is set up and
it is not so CPU/memory (=cost) demanding.
NT is fairly easy to configure without reading lots of manuals, it
works great with windows clients and hardware support is much better.
Hope this helps a bit.
--
Peter
------------------------------
From: rob <[EMAIL PROTECTED]>
Subject: Re: Damaged tar.gz file
Date: Wed, 10 May 2000 11:08:44 +0100
or use file(1)
for example
file home.tar.gz
Eric wrote:
> Hoosain Madhi wrote:
> >
> > I have a damaged tar.gz file and was wondering if there is a utility to
> > fix it.
> >
> > I get the following error
> >
> > madhih:~$ tar xzvf home.tar.gz
> >
> > gzip: stdin: invalid compressed data--format violated
> > tar : Unexpected EOF on archive
> > tar : Child returned status 1
> > tar : Error exit delayed from previous errors
> Are you sure it's a gzipped file, just having the extensions doesn't
> mean it's gzipped, try viewing the file with a hex/text viewer or try
> tar -tf home.tar.gz to see if it's just tarred and not zipped.
>
> Eric
------------------------------
From: Pierre Vigneras <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: SCSI devices and SMP kernels
Date: Wed, 10 May 2000 12:16:07 +0200
This is a multi-part message in MIME format.
==============6C5EA2C8D11639EC328AB221
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
You're right :
[root@moucheron /boot]# sfdisk -l /dev/sda
Disk /dev/sda: 8715 cylinders, 64 heads, 32 sectors/track
Units = cylinders of 1048576 bytes, blocks of 1024 bytes, counting from
0
Device Boot Start End #cyls #blocks Id System
/dev/sda1 0+ 512 513- 525296 82 Linux swap
/dev/sda2 513 4513 4001 4097024 83 Linux
/dev/sda3 4514 8714 4201 4301824 c Win95 FAT32 (LBA)
/dev/sda4 0 - 0 0 0 Empty
[root@moucheron /boot]#
But, why can i boot with a ramdisk and not with my new kernel ?
Can anyone answer to questions about the /boot/* files (see below...) ?
Eric wrote:
>
> Just to make sure: you didn't make the partition where the kernel
> resides (possibly in /boot) too large so it crosses the 1024th cylinder?
>
> Eric
>
> Pierre Vigneras wrote:
> >
> > Johan Kullstam wrote:
> > >
> > > Eric <[EMAIL PROTECTED]> writes:
> > >
> > > > Henrique Seganfredo wrote:
> > > > >
> > > > > Anybody here knows about the behaviour of SMP kernels with SCSI drivers?
> > > > >
> > > > > I am trying to set up a right out of the box RPM package with a SMP
> > > > > kernel (the same version non SMP is already running)...when I boot, I
> > > > > get "kernel panic" cause the root fs (on sda1) could not be mounted due
> > > > > a problem loading the aic7xxx.o module....no, its not a version issue or
> > > > > something like that....
> > > > >
> > > > > ...some dudes told me that I can't use some SCSI drivers with SMP
> > > > > kernels...is that a fact?
> > > > >
> > > > you can't have scsi support as a module if you want to boot from a scsi
> > > > disc
> > > > it must be compiled into your kernel
> > >
> > > this is not quite true. you can put the scsi module on an initial
> > > ramdisk (initrd). this is what most distributions do because
> > > compiling every possible scsi driver into their kernel would be a bit
> > > much.
> > >
> > > however, i agree that it is a damned good recommendation. if you can
> > > compile yourself a kernel, by all means build the scsi driver into it.
> >
> > That's what i did, but i got a
> > "kernel panic" too : "unable to mount on /dev/sda2".
> >
> > I did compile the scsi drive into the kernel.
> > And moreover, i have :
> >
> > [root@moucheron /boot]# rdev vmlinuz-2.2.14smp
> > Root device /dev/sda2
> > [root@moucheron /boot]#
> >
> > which is the current root device :
> >
> > [root@moucheron /boot]# rdev
> > /dev/sda2 /
> > [root@moucheron /boot]#
> >
> > Running lilo show :
> >
> > [root@moucheron /boot]# lilo -v
> > LILO version 21, Copyright 1992-1998 Werner Almesberger
> >
> > Reading boot sector from /dev/sda
> > Merging with /boot/boot.b
> > Boot image: /boot/vmlinuz-2.2.12-20smp
> > Mapping RAM disk /boot/initrd-2.2.12-20smp.img
> > Added linux *
> > Boot image: /boot/vmlinuz-2.2.12-20
> > Mapping RAM disk /boot/initrd-2.2.12-20.img
> > Added linux-up
> > Boot image: /boot/vmlinuz-2.2.14smp
> > Added new
> > /boot/boot.0800 exists - no backup copy made.
> > Writing boot sector.
> > [root@moucheron /boot]#
> >
> > But booting my new kernel is always a kernel panic !
> > i don't understand why !
> > I suppose the redhat ramdisk as set a strange /boot/map:
> >
> > [root@moucheron /boot]# ls -al
> > total 10781
> > drwxr-xr-x 2 root root 1024 May 10 09:33 .
> > 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 10 09:33 map
> > lrwxrwxrwx 1 root root 21 Feb 11 18:19 module-info ->
> > module-in o-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.1 -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 /boot]#
> >
> > Can i remove some of this files (System.map*) ?? What are their use (i
> > know ps use it, for its WCHAN field, but is there another use ??) ? What
> > are module-info* files ? Can i remove some of this files ?
> >
> > Here my /etc/lilo.conf :
> >
> > [root@moucheron /boot]# 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 /boot]#
> >
> > My new kernel is /boot/vmlinuz-2.2.14smp (which i can't boot like
> > describe above).
> >
> > --
> > 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/
> >
> > ------------------------------------------------------------------------
> >
> > Name: vigneras.vcf
> > vigneras.vcf Type: VCard (text/x-vcard)
> > Encoding: 7bit
> > Description: Card for Pierre Vigneras
--
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/
==============6C5EA2C8D11639EC328AB221
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
==============6C5EA2C8D11639EC328AB221==
------------------------------
From: Uwe Brauer <[EMAIL PROTECTED]>
Subject: invalid superblock: e2fsck -f- b 8193 failed
Date: 10 May 2000 11:50:34 +0000
Hello
Does anybody know about a tool which allows to repair damaged
superblocks
for me
e2fsck -f- b 8193 /dev/hda3 did not work.
Thanks
Uwe Brauer
------------------------------
From: [EMAIL PROTECTED] (Marc D. Williams)
Subject: Re: Fvwm2 and Gnome/KDE ?!?
Reply-To: [EMAIL PROTECTED]
Date: Wed, 10 May 2000 10:22:11 GMT
On 1 May 2000 17:51:31 -0400, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> I read that fvwm2 is not KDE/Gnome compliant and that it probably never
>will be. Perhaps I saw it on fvwm.org? But, most apps work fine, some crash
>when you try to open files, eg. kiconedit... No drag&drop... you can load the
>panels for each though and they seem to work fine, same with the
>filemanager/desktop icons.
> About the compliance, if I understand correctly there is a whole set of
>instructions that KDE and Gnome need in addition to the standard window
>manager calls, ie for drag&drop or whatever...
>
I'm running fvwm 2.3.15. It is GNOME compliant.
>From the NEWS file:
Changes in alpha release 2.3.4 (June 1999)
* Fvwm is GNOME compliant.
--
>>ANIME SENSHI<<
Marc D. Williams
[EMAIL PROTECTED]
http://www.oldskool.org/~tvdog/ -- DOS Internet & Tandy 1000
http://www.geocities.com/SiliconValley/Platform/8269/ -- Win3.x Makeover
------------------------------
Date: Wed, 10 May 2000 12:34:33 +0200
From: Hoosain Madhi <[EMAIL PROTECTED]>
Subject: Re: Damaged tar.gz file
file home.tar.gz
give the fll output
home.tar.gz : gzip compressed data, deflated, last modified .... os:UNIX
tar -tf home.tar.gz
give the fll output
tar: Hmm, this does not look like a tar archive
tar:Skipping to next file header
tar:Only read 3006 bytes from archive home.tar.gz
tar: error is not recoverable: exiting now
rob wrote:
> or use file(1)
> for example
> file home.tar.gz
>
> Eric wrote:
>
> > Hoosain Madhi wrote:
> > >
> > > I have a damaged tar.gz file and was wondering if there is a utility to
> > > fix it.
> > >
> > > I get the following error
> > >
> > > madhih:~$ tar xzvf home.tar.gz
> > >
> > > gzip: stdin: invalid compressed data--format violated
> > > tar : Unexpected EOF on archive
> > > tar : Child returned status 1
> > > tar : Error exit delayed from previous errors
> > Are you sure it's a gzipped file, just having the extensions doesn't
> > mean it's gzipped, try viewing the file with a hex/text viewer or try
> > tar -tf home.tar.gz to see if it's just tarred and not zipped.
> >
> > Eric
------------------------------
Date: Wed, 10 May 2000 12:46:13 +0200
From: Hoosain Madhi <[EMAIL PROTECTED]>
Subject: Re: Damaged tar.gz file
I should add that zcat home.tar.gz show the full contents of the archive. I
possibly download this file in ASCII mode as opposed to BINARY mode.
Hoosain Madhi wrote:
> file home.tar.gz
> give the fll output
> home.tar.gz : gzip compressed data, deflated, last modified .... os:UNIX
>
> tar -tf home.tar.gz
> give the fll output
> tar: Hmm, this does not look like a tar archive
> tar:Skipping to next file header
> tar:Only read 3006 bytes from archive home.tar.gz
> tar: error is not recoverable: exiting now
>
> rob wrote:
>
> > or use file(1)
> > for example
> > file home.tar.gz
> >
> > Eric wrote:
> >
> > > Hoosain Madhi wrote:
> > > >
> > > > I have a damaged tar.gz file and was wondering if there is a utility to
> > > > fix it.
> > > >
> > > > I get the following error
> > > >
> > > > madhih:~$ tar xzvf home.tar.gz
> > > >
> > > > gzip: stdin: invalid compressed data--format violated
> > > > tar : Unexpected EOF on archive
> > > > tar : Child returned status 1
> > > > tar : Error exit delayed from previous errors
> > > Are you sure it's a gzipped file, just having the extensions doesn't
> > > mean it's gzipped, try viewing the file with a hex/text viewer or try
> > > tar -tf home.tar.gz to see if it's just tarred and not zipped.
> > >
> > > Eric
------------------------------
From: Robert Heller <[EMAIL PROTECTED]>
Subject: Re: LILO 1024 cyl thing
Date: Wed, 10 May 2000 10:57:51 GMT
Rick Hoffman <[EMAIL PROTECTED]>,
In a message on Tue, 09 May 2000 19:49:04 -0400, wrote :
RH> Robert Heller wrote:
RH>
RH> > RH> >
RH> > RH> > /dev/hda1 1-2gig - FAT16 Win C: drive (base system + base applications)
RH> > RH> > /dev/hda2 64meg - Ext2 linux root: /
RH> > RH> > /dev/hda3 up to 1/2 way point - FAT32 Win D: drive (put your docs, MP3s,
MOVs,
RH> > RH> > AVIs, etc. here)
RH> > RH> > /dev/hda4 <extended -- the second 1/2 of the disk>
RH> > RH> > /dev/hda5 128meg -- swap
RH> > RH> > /dev/hda6 1.5gig -- Ext2 /usr
RH> > RH> > /dev/hda7 64meg -- Ext2 /var
RH> > RH> > /dev/hda8 rest of disk -- Ext2 /home
RH> > RH> >
RH> > RH> > This sort of partitioning should allow all of /dev/hda1 and /dev/hda2 to
RH> > RH> > be completely below cylinder 1024. The stock lilo will be happy,
RH> > RH> > Windows will be happy. Everything should work just fine.
RH> > RH> >
RH>
RH> >
RH> > Under Linux/UNIX things *appear* to always be one file system, whether it is
RH> > one partition or 256 partitions. One can 'mount' physical file system
RH> > (disks / partitions) anywhere that is 'convenient'.
RH> >
RH> > The Linux installer will make a file system tree something like this:
RH> >
RH> > /
RH> > /dev
RH> > /boot
RH> > /bin
RH> > /sbin
RH> > /lib
RH> > /etc
RH> > /mnt
RH> > /tmp
RH> > /var
RH> > /var/log
RH> > /var/spool
RH> > /var/run
RH> > /var/tmp (some systems)
RH> > /var/lock
RH> > /usr
RH> > /usr/bin
RH> > /usr/sbin
RH> > /usr/lib
RH>
RH> /usr/local
RH>
RH> > /usr/man
RH> > /usr/share
RH> > /usr/tmp
RH> > /home
RH> >
RH>
RH> Thank you for your very informative explaination. Using your above example, I
know you
RH> said there was more but I thought I would include /usr/local. Isn't that an
important
RH> path as well? Now mounting partitions as / or /boot or /usr or /var are obvious.
What
RH> if I choose to call them /root or /partitionOne and /partitionTwo, ... etc. How
would
RH> the installer negotiate that?
The installer won't put anything on '/partitionOne' or '/partitionTwo'.
There is not really any good reason to do this, unless /partitionOne and
/partitionTwo are spare / scratch partitions or some special purpose
partitions. Linux (and UNIX) has a certain standard file system layout.
About /usr/local -- one can make a separate partition if you want.
Sometimes I just make it a symlink to /home/local. Allocating 1.5gig to
/usr generally leaves enough space for a reasonable collection of
'local' software (/usr/local/...).
RH>
RH> Next, answering the previous question might answer this one but what if I wanted
more
RH> grandularity and named my partitions /boot, /, /usr, /usr/local, /var,
/var/spool, /tmp
RH> for example. How would the installer know automatically how to handle that?
RH>
Yep. That would work as well. Like I said earlier -- you can have up to 256
filesystems mounted. The default 2.2.x kernel has NR_SUPER set to 256 --
the fs.h file can be edited and a custom kernel built if you feel you
need more partitions (this really only makes sense if you have lots of
NFS servers, each with a number of exported file systems that you want
to mount).
RH> >
RH> > On a running Linux (or UNIX) system, *partitions* are not a *visible*
RH> > part of the file system tree, unless one uses the df command. One uses
RH> > the cd command to move from directory to directory *seamlessly* --
RH> > a different *physical* file system (partition/disk) is not selected by
RH> > some special syntax or command, like it is in MS-DOS/MS-Windows. If you
RH> > never use the df command, you are presently with the *illusion* of one
RH> > single file system, even when it is broken up across multiple disks and/or
RH> > partitions.
RH> >
RH>
RH> I wrote earlier >> But how do I get the data to the partitions and have a working
file
RH> system afterwards?
RH> I had a feeling the installer was going to hypothetically be the one to do all the
work.
RH> But like I worded the question before how do I get the data into the partitions
like I
RH> want them. Lets say I have a functional Linux system on a source drive with one
big
RH> partition and I break up another disk into many partitions. These partitions are
ext2
RH> formatted. How do I get the directories I pick and choose from the source disk to
the
RH> destination disk and have a functional OS on the destination disk? In other words
I do
RH> the work of the installer from one disk to another and am basically wanting to
clone the
RH> OS but from one partition to many.
RH>
RH> Lastly, Robert, how do you recommend partitioning a Linux system and why?
It depends...
A 'normal' pure Linux box that is up 24/7 (typical partitioning of the
machines I manage at UMass (RH 6.x)):
Partition size mount point
===========================================
/dev/sda1 64meg /
/dev/sda2 128meg <swap>
/dev/sda3 1.5gig /usr
/dev/sda4 <rest of disk> <extended>
/dev/sda5 64meg /var
/dev/sda6 2gig /home
/dev/sda7 <rest of disk> /scratch
My home box is a FidoNet node and runs INND:
Filesystem 1024-blocks Used Available Capacity Mounted on
/dev/sdc1 64419 23453 37639 38% /
/dev/sdc7 1015656 944815 18362 98% /home
/dev/sdc8 1015656 101235 861942 11% /home2
/dev/sdc9 805669 105601 658444 14% /home3
/dev/sdc3 1015672 724970 238222 75% /usr
/dev/sdc5 64419 19273 41819 32% /var
/dev/sdc6 254736 9850 231729 4% /var/spool
/dev/sdc2 is swap, /dev/sdc4 is extended. This is a 4gig disk. I'm
running RH 5.2 at present. RH 6.x wants more space in /usr.
I have Slackware 3.0 on a 2gig disk on my home system as well:
Filesystem 1024-blocks Used Available Capacity Mounted on
/dev/sdb1 50541 11033 36898 23% /slack30
/dev/sdb3 100134 23270 71693 25% /slack30/var
/dev/sdb7 1020647 855280 112632 88% /slack30/home
/dev/sdb6 553035 330792 193675 63% /slack30/usr
/dev/sdb5 254751 14266 227327 6% /slack30/var/spool
(For the curious, /dev/sda1 is a 345meg drive, formatted as a FAT16 and
has MS-DOS 6.2 on it.)
RH>
RH> Thanks so much.
RH>
RH> hoffy
RH>
RH>
--
\/
Robert Heller ||InterNet: [EMAIL PROTECTED]
http://vis-www.cs.umass.edu/~heller || [EMAIL PROTECTED]
http://www.deepsoft.com /\FidoNet: 1:321/153
------------------------------
From: Will Dyke <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux
Subject: Re: Where is stddef.h?
Date: Wed, 10 May 2000 11:02:07 +0000
"U.V. Ravindra" wrote:
>
> Doesn't Linux come with a <stddef.h>?
>
> I am trying to port some code from Solaris to Linux (Alpha,
> if that matters), and one of my files tries to include
> <stddef.h>, which I can't find on the system.
>
> Does a standard distribution of Linux (whatever that may
> mean) include <stddef.h> or not?
$ locate stddef.h
/usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/include/stddef.h
/usr/lib/bcc/include/stddef.h
/usr/src/linux-2.2.12/include/linux/stddef.h
/usr/i386-glibc20-linux/include/linux/stddef.h
So Linux (or at least Redhat 6.1 and almost certainly almost any
other distribution) comes with stddef.h, it's just a matter of
ensuring that your compiler knows where to find it. What compiler
are you using? If it's not gcc, you may experience problems.
If it is, I'd suggest having a look through the gcc info pages
to determine how to ensure that gcc knows where to look.
HTH
Will Dyke
--
Manchester Visualization Centre
http://www.man.ac.uk/MVC/students/will
Manchester Computing mailto:[EMAIL PROTECTED]
Oxford Road Tel: +44 161 275 6945
Manchester M13 9PL
------------------------------
From: "P.G. Willemsen" <[EMAIL PROTECTED]>
Subject: Remove CD without umount
Date: Wed, 10 May 2000 12:57:50 +0200
Hi all,
To access my cd-rom I seem to have to call 'mount /cdrom', but as soon
as I've done that, I cannot open my cd-rom drive anymore, I first have
to call 'umount /cdrom'. Can these procedures be skipped? Pretty
annoying when looking for a file on different cds...
Thanks,
Peter Willemsen
------------------------------
** 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
******************************
