Linux-Development-Sys Digest #122, Volume #7 Mon, 30 Aug 99 03:14:28 EDT
Contents:
Re: Help!! LILO booting stopping on LI (Yuval Yosef)
Re: Strange thread & kernel behavior (David Wragg)
Re: LispOS? (Chris Mahmood)
Re: 497.2 days ought to be enough for everybody (Peter Samuelson)
Re: 497.2 days ought to be enough for everybody (Phil Howard)
LILO oddity. (Omri Schwarz)
Emulating network interfaces in user space (Phil Howard)
Re: Emulating network interfaces in user space (Peter Samuelson)
Re: LILO oddity. (Peter Samuelson)
Re: Help needed: kernel patch problem (Peter Samuelson)
Re: Kernel compile problem with (P)GCC 2.95 (Peter Samuelson)
libc or glibc? (Arthur Chiu)
Re: LILO oddity. (Omri Schwarz)
what is the largest partition Linux file system can handle? (ken@y)
Re: 497.2 days ought to be enough for everybody (Kaz Kylheku)
Re: how to 'scandisk' in linux (Leonard Evens)
----------------------------------------------------------------------------
From: Yuval Yosef <[EMAIL PROTECTED]>
Subject: Re: Help!! LILO booting stopping on LI
Date: Tue, 24 Aug 1999 05:23:55 +0300
Well I had this problem too, you massed your bios bootstrap partition
what worked for me was:
1. reboot linux from cd\diskette and fdisk it with linux fdisk
since msdos fdisk won't do the job, clean all your linux partitions
2. reboot from msdos diskette boot and do fdisk /mbr
3. you propably installed a dual boot, so when re-installing again
install windows first, and than linux but not on your MBR as your
primary partition
this is realy a must.
3.follow the mini-HOWTO exactly as how to config your loader to work
with windows loader
from my expirience with NT-LILO it's working great.
Yuval
Ronald Cole wrote:
>
> [EMAIL PROTECTED] (Horst von Brand) writes:
> > LI means the geometry lilo is seeing doesn't agree with what the kernel
> > knows. Try using the "linear" option, or redefining your disk (LBA, LARGE,
> > etc) via BIOS settings.
>
> Doesn't setting LBA in the BIOS just juggle the heads/cylinders to
> maneuver around the 1024 cylinder limit?
>
> --
> Forte International, P.O. Box 1412, Ridgecrest, CA 93556-1412
> Ronald Cole <[EMAIL PROTECTED]> Phone: (760) 499-9142
> President, CEO Fax: (760) 499-9152
> My PGP fingerprint: 15 6E C7 91 5F AF 17 C4 24 93 CB 6B EB 38 B5 E5
--
=====BEGIN PGP PUBLIC KEY BLOCK=====
Version: PGPfreeware 6.5.1 for non-commercial use <http://www.pgp.com>
mQGiBDe3Q5ERBADEqCdT/nmFHMjPY1aRxBn8h/2NOfjW6VtK5OvbbzdH0DJ9LMzy
uFNHtE6W+lmhloLvlQQDPd7SLBcde62uXXE5vQGvSqc907l/NbMXuuoJiLXT7Ndv
3gexOclSbrTYrw215LJHnYldzno5DgwgxfL3vmJBhrOIE8niZcmZoEDCuwCg/+NB
TpT1SabjfqGtY4+cRo/33bcEAJ55ph4CaISJokmwmpsxH9Q7up5OE4HF7dlWDT08
FBBx6XFRwdoSccKuBucNenXdqWjS9axbbefX/sW4WueIcL+1rFNN93yUA3KOhoaB
VozOehy/GylHtNZA4ibeOmasCRSbfNBv+ouLY4mSDkZAvGasQlakommHOkamMguu
UVhQA/9nXkd5rIPtZNNXV+quZtzQkiwuTnBDvcGj/kXuWMdWVx3OIzKbq8ErEpMj
FObFvnD9czyJXJKqK29uijZDLBehEpJbvW+PeJE9WbswwGZ8XLshpKsVXFJdgEH/
4aX+babH9ySzbvH3k4PwM+tj3P28iBn7R0SRyER9Pq/8hZu1wLQeWXV2YWwgWW9z
ZWYgPHl1dmlAaXNkbi5uZXQuaWw+iQBUBBARAgAUBQI3t0ORBQkAdVWABAsDAgEC
GQEACgkQZtS6Z8Rz7rKkuwCg3hultGssJy4k/Hba0Ar93HZpRTgAn0dY5ryZuXZU
GhAS4jpQWJu7+e5YuQQNBDe3Q5IQEAD5GKB+WgZhekOQldwFbIeG7GHszUUfDtjg
o3nGydx6C6zkP+NGlLYwSlPXfAIWSIC1FeUpmamfB3TT/+OhxZYgTphluNgN7hBd
q7YXHFHYUMoiV0MpvpXoVis4eFwL2/hMTdXjqkbM+84X6CqdFGHjhKlP0YOEqHm2
74+nQ0YIxswdd1ckOErixPDojhNnl06SE2H22+slDhf99pj3yHx5sHIdOHX79sFz
xIMRJitDYMPj6NYK/aEoJguuqa6zZQ+iAFMBoHzWq6MSHvoPKs4fdIRPyvMX86RA
6dfSd7ZCLQI2wSbLaF6dfJgJCo1+Le3kXXn11JJPmxiO/CqnS3wy9kJXtwh/CBdy
orrWqULzBej5UxE5T7bxbrlLOCDaAadWoxTpj0BV89AHxstDqZSt90xkhkn4DIO9
ZekX1KHTUPj1WV/cdlJPPT2N286Z4VeSWc39uK50T8X8dryDxUcwYc58yWb/Ffm7
/ZFexwGq01uejaClcjrUGvC/RgBYK+X0iP1YTknbzSC0neSRBzZrM2w4DUUdD3yI
sxx8Wy2O9vPJI8BD8KVbGI2Ou1WMuF040zT9fBdXQ6MdGGzeMyEstSr/POGxKUAY
EY18hKcKctaGxAMZyAcpesqVDNmWn6vQClCbAkbTCD1mpF1Bn5x8vYlLIhkmuqui
XsNV6z3WFwACAhAAubRcf8IP+KcaELCJXQ7Fo2M9pLdCkpUs+Nuz/WrEjERa5jzC
5VxBCdszaK2rph3J5tmAP38TUhzolyL1ENW6ljjWc2zC2LYW/DEDhrVV2jsKp0Ey
n5z/3dhcP/wAogRSzgOigYibNeN0CSTvTK/Dzjo4/yTBFKpwb+Z7PCj94aHHfNHJ
drfzYPy4aQdkFH/749aVBaGBh/j0isr6LoVWfS+A26sJS8AbrPD8JyLxz3Aj2JXE
ADS9qsMCy8PlRu/ExAaYVNhvE69962CC8zBykfpejr07sNwiFNdTpSxX6cPQaLtF
16Yqwvz9ZZ05jvsO14wALCplqKCNF2MPY2TQNy0fgUtbW/bKv2CxDVSVCy7GUd6+
Pr62zEIAQKh0T9DIJjRAZvmmKFgSaIf3kEtmzuFaT7hs1X/1w47KoRu0FC2Vv/tP
REMykQtu/ygl9DPOYKbsfCQs8RB/OtsKLap+SwxzX6A64c6Ts3OVThO8tQZcjihn
SnK0ygzE9uS0Ui5/QRIRyYjJQ1Q5nc0iNIKRLD0frm60HHHUzJ+4E/a5a9TR6GQh
6h9bAOke7XlRdqkgA5Fpr8eHFYOATMQF/N3Q8DxJlugCjqT0C3nHC2qfZjwBFbPh
tfFNfwxAd4PAsR6coO2cKpYCoc2FmExx0JIkoaXnVbMpx2CvoCqFxZHUyLaJAEwE
GBECAAwFAje3Q5IFCQB1VYAACgkQZtS6Z8Rz7rKXrgCglXOqT9xOcXstWRYt2zdJ
HSdXpBoAniC1gFWPEywd0prfVuMF7/L5y+uB
=SVfq
=====END PGP PUBLIC KEY BLOCK=====
------------------------------
From: David Wragg <[EMAIL PROTECTED]>
Subject: Re: Strange thread & kernel behavior
Date: 28 Aug 1999 15:07:44 +0000
Esa J Kallioniemi <[EMAIL PROTECTED]> writes:
> Ok, I have dual 350 Mhz P2 machine with 128 MB memory. Linux is RedHat
> 5.2 with 2.0.36 kernel + addtional 2.2.9 selfcompiled kernel. I have
> written small proggy, that spawns 32 threads (LinuxThreads).
Do these threads actually do anything, or does the program just spawn
threads that immediately exit?
> When
> running "time proggy" I get about 0.04 secs with 2.0.36 kernel.
> BUT when
> running with 2.2.9 (with SMP on) I get extremely random behavior !
> Time says anything between 0.04 and 5.0 secs for the exactly same
> proggy...
For times much less than a second, you are liable to get some random
variation. 5 seconds seems high, but without more details of the
program it is difficult to guess at the cause.
> And xosview (SMP compatible version) shows that system
> is sometimes 100% in "system mode" for both processors !!!
That is what I would expect, if you are spawning threads which
immediately exit.
> So it would seem that there's something wrong with kernel ?? Or I
> have managed to create really strange bug ;) I would be more than
> happy if someone could suggest possible reasons for this... (and
> remedies of course ;) )
Without being able to reproduce what you describe, it is impossible to
say.
David Wragg
------------------------------
From: Chris Mahmood <[EMAIL PROTECTED]>
Subject: Re: LispOS?
Date: 29 Aug 1999 16:10:11 -0700
[EMAIL PROTECTED] (Depeche) writes:
> I, too, think that this is a sad affair. I wonder if there would be
> support for a true LISP based openSource reimplementation.
Well, how much longer will it be before we can just boot emacs?
-ckm
------------------------------
From: [EMAIL PROTECTED] (Peter Samuelson)
Subject: Re: 497.2 days ought to be enough for everybody
Date: 29 Aug 1999 21:14:26 -0500
Reply-To: Peter Samuelson <[EMAIL PROTECTED]>
[Ross Crawford <[EMAIL PROTECTED]>]
> Is it possible to organise a shutdown & reboot sometime before you
> go? This'd certainly be one option I'd be looking at 8?)
No, the point was to try and maintain the high uptime -- for its own
sake. The point is that a quality operating system like Linux
shouldn't *have* to be rebooted once a week or even once every 497
days. I know an NT admin who reboots the server once a week, just to
prevent problems. <shudder> There's is a habit I'm glad I can leave to
the NT people.
And the other point is that Linux kernel people have been applying a
*lot* of jiffies wrap fixes late in the 2.1.x game (which doesn't help
the original poster who is running 2.0.35 IIRC) so that there would
*not* be this arbitrary limitation in the future. Not because most
users can't or won't reboot after 497.2 days, but because *if you have
to, it's a bug* -- and each individual instance of the bug is trivial
to fix.
--
Peter Samuelson
<sampo.creighton.edu!psamuels>
------------------------------
From: [EMAIL PROTECTED] (Phil Howard)
Subject: Re: 497.2 days ought to be enough for everybody
Date: Mon, 30 Aug 1999 01:33:24 GMT
On 24 Aug 1999 05:28:21 GMT Ray ([EMAIL PROTECTED]) wrote:
| By the way, while setting up the process killer I found something funny:
| you can't sleep beyond the magical date. I am about 6000 minutes before
| the rollover now, and when I type "sleep 6200" at the shell, it returns
| immediately :) Bit of a problem for me now, because I just planned to
| do "sleep 6000m; kill everything; sleep 10m; restart everything" - the
| sleep 10m would of course fail because of this. I'll have to think about
| something else... "rsh anotherhost sleep" - rsleep? :) Oh no, ssh of course.
| I want to sleep secure :)
If sleep fails (check to make sure you can see if it does, as interval
timing may be difficult across the "event", then divide the amount of time
to sleep in half and try again. As you get closer and closer the sleep
times become less and less. Finally at the last second, something that
loops for a few seconds (or a few minutes like dd if=/dev/hda of=/dev/null)
should slide you across the event.
--
Phil Howard KA9WGN
[EMAIL PROTECTED] [EMAIL PROTECTED]
------------------------------
From: Omri Schwarz <[EMAIL PROTECTED]>
Subject: LILO oddity.
Date: Sun, 29 Aug 1999 22:47:38 -0400
I'm in 2.2.7. I build 2.2.10.
I make a new first entry for 2.2.10 in lilo.conf.
I run lilo. no error messages.
I reboot. Boom, I'm back in 2.2.7.
Huh?
--
Omri Schwarz ---
Timeless wisdom of biomedical engineering:
"Noise is principally due to the presence of the
patient." -- R.F. Farr
------------------------------
From: [EMAIL PROTECTED] (Phil Howard)
Subject: Emulating network interfaces in user space
Date: Mon, 30 Aug 1999 02:26:51 GMT
Is there a way to emulate a network interface in user process space?
I would only car to implement IP on this interface. So it should
get all IP packets routed out to that interface, and be able to put
all IP packets that would "come in" in that interface. Also, ioctl
would be done somehow. Does such a facility exist? Would it be
very easy to do if not? The process would run as root.
--
Phil Howard KA9WGN
[EMAIL PROTECTED] [EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (Peter Samuelson)
Subject: Re: Emulating network interfaces in user space
Date: 29 Aug 1999 23:23:13 -0500
Reply-To: Peter Samuelson <[EMAIL PROTECTED]>
[Phil Howard <[EMAIL PROTECTED]>]
> Is there a way to emulate a network interface in user process space?
> I would only car to implement IP on this interface. So it should get
> all IP packets routed out to that interface, and be able to put all
> IP packets that would "come in" in that interface. Also, ioctl would
> be done somehow. Does such a facility exist? Would it be very easy
> to do if not? The process would run as root.
Hmmmm, having read through the docs on Rusty's new `netfilter' patch
which made it into 2.3.15 to replace ipchains and ipmasq/nat, it looks
like netfilter *might* be able to do what you want. You would probably
use dummy.o for your net interface and then control the actual traffic
from userspace with the netfilter hooks, which currently exist,
conveniently, for ipv4 only.
http://netfilter.kernelnotes.org/netfilter-HOWTO.html
HTH.
--
Peter Samuelson
<sampo.creighton.edu!psamuels>
------------------------------
From: [EMAIL PROTECTED] (Peter Samuelson)
Subject: Re: LILO oddity.
Date: 29 Aug 1999 23:26:58 -0500
Reply-To: Peter Samuelson <[EMAIL PROTECTED]>
[Omri Schwarz <[EMAIL PROTECTED]>]
> I'm in 2.2.7. I build 2.2.10.
> I make a new first entry for 2.2.10 in lilo.conf.
>
> I run lilo. no error messages.
>
> I reboot. Boom, I'm back in 2.2.7.
Go over your lilo.conf. A "default=" line could explain a lot. If
still in doubt, post your lilo.conf.
--
Peter Samuelson
<sampo.creighton.edu!psamuels>
------------------------------
From: [EMAIL PROTECTED] (Peter Samuelson)
Subject: Re: Help needed: kernel patch problem
Date: 29 Aug 1999 23:04:59 -0500
Reply-To: Peter Samuelson <[EMAIL PROTECTED]>
[Thomas Jaeger <[EMAIL PROTECTED]>]
> I just noticed, that the latest kernel patches (2.2.xx series and 2.3.xx
> series) sometimes
> contain the line:
>
> \No newline at end of file
>
> This line causes the "patch" command to stop immediately.
As someone already posted, not with a newer patchlevel of patch.
> What is the reason for the above mentioned line?
`diff' produced the line to indicate that one of the two files it was
comparing has a newline at the end and the other doesn't. There's no
other way in the unified diff format to represent that fact.
Anyway, just upgrade `patch'.
And while you're at it [offtopic plug alert] you might download my
patch patch which makes it write .rej files in udiff format. I
couldn't stand having to read cdiff format just to sort out the .rej
files.
http://bugs.debian.org/26675
> Thanks for any help in advance
Help in advance? That would be a trick to pull off....
--
Peter Samuelson
<sampo.creighton.edu!psamuels>
------------------------------
From: [EMAIL PROTECTED] (Peter Samuelson)
Subject: Re: Kernel compile problem with (P)GCC 2.95
Date: 29 Aug 1999 23:12:40 -0500
Reply-To: Peter Samuelson <[EMAIL PROTECTED]>
[Andreas Spengler <[EMAIL PROTECTED]>]
> I recently upgraded my compiler to GCC 2.95 and now whenever I try to
> compile a kernel (tried it with 2.3.11-15 and 2.2.9) and do a make
> bzlilo, towards the end I get the warnings
> Warning; using %eax instead of %ax due to ..... ???
> When I reboot the system the kernel hangs at
> Uncompressing Linux. OK. Booting kernel......
Funny, doesn't happen here. From your target `bzlilo' I assume you're
on i386. Are you sure gcc is getting the flag `-fno-strict-aliases'
like gcc 2.95 needs? Recent (2.2.12 and 2.3.something) versions of the
Makefile take care of this automatically but IIRC 2.2.9 does not.
Come to think of it I use the `bzImage' rather than the `bzlilo' target
... but I doubt that's the difference here.
--
Peter Samuelson
<sampo.creighton.edu!psamuels>
------------------------------
From: Arthur Chiu <[EMAIL PROTECTED]>
Subject: libc or glibc?
Date: Mon, 30 Aug 1999 12:43:11 +0800
I'm new to Linux.
People are talking about changing from libc to glibc. I'm using RH5.2. I can find
descriptions of libc by 'info libc' but get nothing with 'info glibc'. What's the
difference between libc and glibc?
------------------------------
From: Omri Schwarz <[EMAIL PROTECTED]>
Subject: Re: LILO oddity.
Date: Mon, 30 Aug 1999 02:06:13 -0400
Peter Samuelson wrote:
>
> [Omri Schwarz <[EMAIL PROTECTED]>]
> > I'm in 2.2.7. I build 2.2.10.
> > I make a new first entry for 2.2.10 in lilo.conf.
> >
> > I run lilo. no error messages.
> >
> > I reboot. Boom, I'm back in 2.2.7.
>
> Go over your lilo.conf. A "default=" line could explain a lot. If
> still in doubt, post your lilo.conf.
No go. There wasn't one before, and lilo -v
listed the new image label as the one being set up as in, where the
asterisk in the output was).
I put a default one in for the new image and ran lilo, and it still
booted to the old
image. I'm guessing the MBR isn't being written.
--
Omri Schwarz ---
Timeless wisdom of biomedical engineering:
"Noise is principally due to the presence of the
patient." -- R.F. Farr
------------------------------
From: ken@y
Crossposted-To: comp.os.linux.misc,comp.os.linux.development.apps.comp.os.linux.setup
Subject: what is the largest partition Linux file system can handle?
Date: 29 Aug 1999 21:22:02 -0700
trying again. never got any answer on this yet.
Any one knows what is the largest partition Linux ext2 can handle?
I've created a 37GB single partition on an IDE drive (new IBM drive).
mkfs works fine. it creates it OK, I can mount it OK, etc..
But every time I reboot, I get errors on that fs (missing inodes, or
duplicate something, etc), running fsck on it does not help, only
way to reboot is to go to /etc/fstab and remove it.
Then tried 2 partitions on the same disk. 18.5 GB each. All OK now.
so, any one knows of linux limitation for size of partition? why ext2
failes to mount a 37 GB partition but not 18 GB one?
this is using SUSE 6.1, kernel 2.2.5
cheers,
ken
------------------------------
From: [EMAIL PROTECTED] (Kaz Kylheku)
Subject: Re: 497.2 days ought to be enough for everybody
Reply-To: [EMAIL PROTECTED]
Date: Mon, 30 Aug 1999 06:11:45 GMT
On 29 Aug 1999 21:14:26 -0500, Peter Samuelson <[EMAIL PROTECTED]> wrote:
>[Ross Crawford <[EMAIL PROTECTED]>]
>> Is it possible to organise a shutdown & reboot sometime before you
>> go? This'd certainly be one option I'd be looking at 8?)
>
>No, the point was to try and maintain the high uptime -- for its own
>sake. The point is that a quality operating system like Linux
>shouldn't *have* to be rebooted once a week or even once every 497
>days. I know an NT admin who reboots the server once a week, just to
>prevent problems. <shudder> There's is a habit I'm glad I can leave to
>the NT people.
NT is designed around the reboot mentality. There are even Win32 API functions
to support this. For example, the RenameFileEx function has a flag which will
cause renaming (or deletion) of a file to be scheduled until the next reboot.
Periodic rebooting is necessary to complete these RenameFileEx() requests that
may have accumulated in the registry.
A mission-critical OS couldn't support such a function in its core API because
the next reboot might not occur for months.
------------------------------
From: Leonard Evens <[EMAIL PROTECTED]>
Crossposted-To: redhat.config,redhat.general
Subject: Re: how to 'scandisk' in linux
Date: Sun, 29 Aug 1999 09:01:32 -0500
zackary wrote:
>
> hello guys
>
> I wonder how to check my disk 'health', as in windows'XX' it have
> 'scandisk' to check the bad block, file system and etc. So what should i
> use to check those things in linux. Would you guys guide me.
>
> Thank You.
>
> -azaria-
>
> ------------------ Posted via CNET Linux Help ------------------
> http://www.searchlinux.com
Scandisk does a variety of things, but the main reason for its
existence is that the FAT file system can be confused by quite
routine operations. The Linux file system is much more robust,
based on Unix file system architecture. It hardly ever gets
in trouble. The one common exception is caused by the fact that the
system has a copy of the filesystem called the Master Block
in memory which is written out to disk periodically---about
every 30 seconds conventionally. This operation is called
syncing. If the system goes down without syncing---as when
there is a power failure or you shut it off without syncing
first---then there is a discrepency between the true state
of the file system and the record on disk. But in these
cases, the program fsck, which is run every time you boot
finds the discrepencies and usually fixes them automatically.
On occasion, the boot process stops and you are asked to
run it manually. If you give the default answer to all the
questions, in almost all cases, that suffices.
--
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.development.system) 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-Development-System Digest
******************************
