Linux-Development-Sys Digest #676, Volume #7 Mon, 13 Mar 00 08:13:12 EST
Contents:
Root Passwords ("2 Bit Unix, Inc.")
kernel upgrade problem (Totoro)
glibc make failure - stdio_lim.st? (Kevin Brosius)
Rebuild Kernal (cwlau)
Re: Rebuild Kernal ("David ..")
set_blocksize: b_count 1, dev ide1(22,1), block 32192! ([EMAIL PROTECTED])
Re: kernel upgrade problem (Anders Larsen)
Pseudo Tty ? ("Jaron Chou")
Re: Help with finding the ftp source code (Alan Donovan)
Distinction between linux.* and comp.os.linux.* (Alan Donovan)
Re: kernel upgrade problem (Totoro)
Re: kernel in C++ (M Sweger)
PROBLEM WITH MPROTECT (OR MMAP) MY SYSYEM CRASH !!! (David)
Re: Absolute failure of Linux dead ahead? (Donal K. Fellows)
----------------------------------------------------------------------------
From: "2 Bit Unix, Inc." <[EMAIL PROTECTED]>
Subject: Root Passwords
Date: Sun, 12 Mar 2000 23:45:49 -0800
====== Posted via Newsfeeds.Com, Uncensored Usenet News ======
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
======= Over 80,000 Newsgroups = 16 Different Servers! ======
------------------------------
From: Totoro <[EMAIL PROTECTED]>
Subject: kernel upgrade problem
Date: Mon, 13 Mar 2000 04:30:04 GMT
I am using Red Hat 6.0 and kernel 2.2.5 and was trying to upgrade to kernel
2.2.12.-20. What I did was:
0. Downloaded the update files of Red Hat 6.1
1. rpm -Uvh mkinitrd*rpm SysVinit*rpm initscripts*
2. rpm -Uvh kernel-headers-2.2.12-20.i386.rpm
kernel-sources-2.2.12-20.i386.rpm
3. rpm -ivh kernel-2.2.12-20.i686.rpm kernel-ibcs-2.2.12-20.i386.rpm
kernel-pcmcia-cs-2.2.12-20.i386.rpm
4. Then did a make xconfig, make dep and make bzImage
5. Copied bzImage to /boot and renamed it to my kernel
After that, I rebooted but what I got was:
Welcome to Red Hat Linux
Press 'I' to enter interactive startup
e2fsck: need terminal for interactive repairs [FAILED]
*** An error occured during the fule system check
*** Dropping you to a shell; the systerm will reboot
*** when you leave the shell
Give root password for maintenance
...
...
So I did what I was told in some newsgroups and typed in "e2fsck -b 8193
/dev/hda8" where /dev/hda8 was the partition for my / directory. It fixed a
few problems but when I rebooted, I got the same errors again. And here was
where I got stuck since I did not know how to fix the problem. Any
suggestion or idea would be greatly appreciated. Thank you.
--
Posted via CNET Help.com
http://www.help.com/
------------------------------
From: Kevin Brosius <[EMAIL PROTECTED]>
Subject: glibc make failure - stdio_lim.st?
Date: Sun, 12 Mar 2000 23:46:02 -0500
I've looked for this in the FAQ, but haven't seen any report of this
build problem. Is anyone aware of what might cause this? This is Linux
2.2.13 with libc5 presently installed. I've done a little looking
through the Makefiles, but don't understand them, or the error message
enough to find the problem. Any suggestions appreciated! Thanks in
advance.
make -C csu subdir_lib
make[2]: Entering directory `/p5/glibc-2.1.3/csu'
make[2]: *** No rule to make target `../stdio-common/stdio_lim.h.in',
needed by `/p5/glibc-build/bits/stdio_lim.st'. Stop.
make[2]: Leaving directory `/p5/glibc-2.1.3/csu'
make[1]: *** [csu/subdir_lib] Error 2
make[1]: Leaving directory `/p5/glibc-2.1.3'
make: *** [all] Error 2
--
Kevin
------------------------------
Date: Mon, 13 Mar 2000 16:37:35 +0800
From: cwlau <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.setup,comp.os.linux.networking,comp.os.linux.misc,comp.os.linux.development.apps
Subject: Rebuild Kernal
Hello
I am a newbie in Linux. I started with Caldera's OpenLinux
but unfortuately it didn't recognise my network card which
is 3com Fast Etherlink XL 10/100 Mb TX (3C905B-TX).
I got the driver patch from 3com's web site but it needed
to rebuild the kernal. I just don't know how to rebuild the
kernal particularly for Caldera's OpenLinux.
Could anyone please tell me how to do it ?
Thank you very much.
Bye.
------------------------------
From: "David .." <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.setup,comp.os.linux.networking,comp.os.linux.misc,comp.os.linux.development.apps
Subject: Re: Rebuild Kernal
Date: Mon, 13 Mar 2000 02:44:53 -0600
http://www.linuxdoc.org/docs.html#guide
Boook named:
Get Acquainted with Linux Security and Optimization System
author: Gerhard Mourani
Read it carefully as it tells about building a monolithic kernel but
also includes info about modules.
Also you can do it this way.
I downloaded the kernel-2.2.14-5.0.src.rpm or whatever the correct name
is.
Installed it which puts it in /usr/src/redhat/SOURCES/
Then did a cd /usr/src/redhat/SPECS/ #enter
rpm -bp kernel-2.2.14.spec
Which applies a bunch of patches and puts the patched and un-tarred
directory into /usr/src/redhat/BUILD/
Then I cp /usr/src/redhat/BUILD/linux /usr/src/
cd /usr/src/linux/
make menuconfig
and then did the compile. It worked great and I let rpm install all the
patches.
Just my 2 cents.
--
Due to extreme SPAM abuse! Remove z's and x's from above to reply.
Thnak the spammer's A..holes that they are. Still can't reach me?
Then your address range is already blocked due to previous spam.
Sorry! I hate spam!!
------------------------------
From: [EMAIL PROTECTED]
Subject: set_blocksize: b_count 1, dev ide1(22,1), block 32192!
Date: Mon, 13 Mar 2000 08:38:24 GMT
kernel version 2.2.14
mke2fs version 1.15
mount version 2.9v
I formatted a small partition with a blocksize of 2K and when I mounted
it I got the kernel error messages below. Anyone know what this means?
The source code didn't seem to be of much help, other than it appeared
to be going through a free list and got something it didn't expect.
When I use a blocksize of 1K this does not happen. When I do 4K on much
larger partitions, also this does not happen. Is large blocksize still
not a mature feature?
set_blocksize: b_count 1, dev ide1(22,1), block 32192!
set_blocksize: b_count 1, dev ide1(22,1), block 32193!
set_blocksize: b_count 1, dev ide1(22,1), block 32194!
set_blocksize: b_count 1, dev ide1(22,1), block 32195!
set_blocksize: b_count 1, dev ide1(22,1), block 32196!
set_blocksize: b_count 1, dev ide1(22,1), block 32197!
set_blocksize: b_count 1, dev ide1(22,1), block 32198!
set_blocksize: b_count 1, dev ide1(22,1), block 32199!
set_blocksize: b_count 1, dev ide1(22,1), block 32200!
set_blocksize: b_count 1, dev ide1(22,1), block 32201!
set_blocksize: b_count 1, dev ide1(22,1), block 32202!
set_blocksize: b_count 1, dev ide1(22,1), block 32203!
set_blocksize: b_count 1, dev ide1(22,1), block 32204!
set_blocksize: b_count 1, dev ide1(22,1), block 32205!
set_blocksize: b_count 1, dev ide1(22,1), block 32206!
set_blocksize: b_count 1, dev ide1(22,1), block 32207!
set_blocksize: b_count 1, dev ide1(22,1), block 32208!
set_blocksize: b_count 1, dev ide1(22,1), block 32209!
set_blocksize: b_count 1, dev ide1(22,1), block 32210!
set_blocksize: b_count 1, dev ide1(22,1), block 32211!
set_blocksize: b_count 1, dev ide1(22,1), block 32212!
set_blocksize: b_count 1, dev ide1(22,1), block 32213!
set_blocksize: b_count 1, dev ide1(22,1), block 32214!
set_blocksize: b_count 1, dev ide1(22,1), block 32215!
set_blocksize: b_count 1, dev ide1(22,1), block 32216!
set_blocksize: b_count 1, dev ide1(22,1), block 32217!
set_blocksize: b_count 1, dev ide1(22,1), block 32218!
set_blocksize: b_count 1, dev ide1(22,1), block 32219!
set_blocksize: b_count 1, dev ide1(22,1), block 32220!
set_blocksize: b_count 1, dev ide1(22,1), block 32221!
set_blocksize: b_count 1, dev ide1(22,1), block 32222!
set_blocksize: b_count 1, dev ide1(22,1), block 32223!
--
| Phil Howard - KA9WGN | for headlines that | Just say no to absurd patents |
| [EMAIL PROTECTED] | really matter: | Boycott Amazon.Com (AMZN) |
| Dallas - Texas - USA | linuxhomepage.com | Shop http://bn.com/ instead |
------------------------------
From: Anders Larsen <[EMAIL PROTECTED]>
Subject: Re: kernel upgrade problem
Date: Mon, 13 Mar 2000 10:13:20 +0100
Totoro wrote:
>
> I am using Red Hat 6.0 and kernel 2.2.5 and was trying to upgrade to kernel
> 2.2.12.-20. What I did was:
> 0. Downloaded the update files of Red Hat 6.1
> 1. rpm -Uvh mkinitrd*rpm SysVinit*rpm initscripts*
> 2. rpm -Uvh kernel-headers-2.2.12-20.i386.rpm
> kernel-sources-2.2.12-20.i386.rpm
> 3. rpm -ivh kernel-2.2.12-20.i686.rpm kernel-ibcs-2.2.12-20.i386.rpm
> kernel-pcmcia-cs-2.2.12-20.i386.rpm
> 4. Then did a make xconfig, make dep and make bzImage
> 5. Copied bzImage to /boot and renamed it to my kernel
Did you remember to run /sbin/lilo ?
> After that, I rebooted but what I got was:
With /sbin/shutdown, or did you just press the reset-button?
> Welcome to Red Hat Linux
> Press 'I' to enter interactive startup
>
> e2fsck: need terminal for interactive repairs [FAILED]
>
> *** An error occured during the fule system check
> *** Dropping you to a shell; the systerm will reboot
> *** when you leave the shell
> Give root password for maintenance
> ...
> ...
>
> So I did what I was told in some newsgroups and typed in "e2fsck -b 8193
> /dev/hda8" where /dev/hda8 was the partition for my / directory. It fixed a
> few problems but when I rebooted, I got the same errors again. And here was
> where I got stuck since I did not know how to fix the problem. Any
> suggestion or idea would be greatly appreciated. Thank you.
--
Anders Larsen
------------------------------
From: "Jaron Chou" <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.development.apps,comp.os.linux.networking,comp.unix.sco.misc,comp.unix.sco.programmer,comp.unix.unixware.misc,it.comp.os.linux.development,it.comp.os.linux.software
Subject: Pseudo Tty ?
Date: 13 Mar 2000 09:22:24 GMT
Hi,
Does anybody know how to add pseudo tty in Linux/Unixware/Unix SVR42
How to do that ?
Thank you!.
------------------------------
From: Alan Donovan <[EMAIL PROTECTED]>
Crossposted-To: linux.dev.kernel,linux.sources.kernel,comp.os.linux.development
Subject: Re: Help with finding the ftp source code
Date: Mon, 13 Mar 2000 09:55:28 +0000
Xiaofeng Tan wrote:
>
> I am really new to the linux kernel. I just wonder if anyone could tell
> me where I can find the ftp source code? Thanks a lot.
Firstly,the ftp source code has nothing whatever to do with the kernel.
Secondly, as with all "where do I find the source?" questions, the
answer is either:
1. consult the documentation for the program (e.g. man ftp; in this
case, not very helpful)
2. use your package manager. With RPM, you would type:
% rpm -qf /usr/bin/ftp
ftp-0.10-22
% rpm -qi ftp
Name : ftp Relocations: (not
relocateable)
Version : 0.10 Vendor: Red Hat Software
Release : 22 Build Date: Sun Mar 21
21:16:22 1999
Install date: Fri Jul 2 18:56:52 1999 Build Host:
porky.devel.redhat.com
Group : Applications/Internet Source RPM:
ftp-0.10-22.src.rpm
[...]
And note the Source RPM is ftp-0.10-22.src.rpm. Then go to rpmfind.net
and look it up, and download it.
alan
========================================================================
Alan Donovan [EMAIL PROTECTED] http://www.imerge.co.uk
Imerge Ltd. +44 1223 875265
------------------------------
From: Alan Donovan <[EMAIL PROTECTED]>
Subject: Distinction between linux.* and comp.os.linux.*
Date: Mon, 13 Mar 2000 09:59:18 +0000
I just noticed for the first time today that 152 groups have appeared
under linux.*. Pardon me if I'm slow to notice, but is there any obvious
distinction (in subject & readership) between those groups and the ones
that appear in what I thought was the conventional place,
comp.os.linux.*?
cheers,
alan
--
========================================================================
Alan Donovan [EMAIL PROTECTED] http://www.imerge.co.uk
Imerge Ltd. +44 1223 875265
------------------------------
From: Totoro <[EMAIL PROTECTED]>
Subject: Re: kernel upgrade problem
Date: Mon, 13 Mar 2000 11:30:03 GMT
Anders Larsen wrote:
>
> Totoro wrote:
> >
> > I am using Red Hat 6.0 and kernel 2.2.5 and was trying to upgrade to
kernel
> > 2.2.12.-20. What I did was:
> > 0. Downloaded the update files of Red Hat 6.1
> > 1. rpm -Uvh mkinitrd*rpm SysVinit*rpm initscripts*
> > 2. rpm -Uvh kernel-headers-2.2.12-20.i386.rpm
> > kernel-sources-2.2.12-20.i386.rpm
> > 3. rpm -ivh kernel-2.2.12-20.i686.rpm kernel-ibcs-2.2.12-20.i386.rpm
> > kernel-pcmcia-cs-2.2.12-20.i386.rpm
> > 4. Then did a make xconfig, make dep and make bzImage
> > 5. Copied bzImage to /boot and renamed it to my kernel
>
> Did you remember to run /sbin/lilo ?
>
Yes, I edited the /etc/lilo.conf file and ran lilo.
> > After that, I rebooted but what I got was:
>
> With /sbin/shutdown, or did you just press the reset-button?
I used shutdown and rebooted my Linux box, not just logout and then log
back in.
>
> > Welcome to Red Hat Linux
> > Press 'I' to enter interactive startup
> >
> > e2fsck: need terminal for interactive repairs [FAILED]
> >
> > *** An error occured during the fule system check
> > *** Dropping you to a shell; the systerm will reboot
> > *** when you leave the shell
> > Give root password for maintenance
> > ...
> > ...
> >
> > So I did what I was told in some newsgroups and typed in "e2fsck -b
8193
> > /dev/hda8" where /dev/hda8 was the partition for my / directory. It
fixed a
> > few problems but when I rebooted, I got the same errors again. And
here was
> > where I got stuck since I did not know how to fix the problem. Any
> > suggestion or idea would be greatly appreciated. Thank you.
>
> --
> Anders Larsen
Did you see a problem in my procedure?
--
Posted via CNET Help.com
http://www.help.com/
------------------------------
From: [EMAIL PROTECTED] (M Sweger)
Subject: Re: kernel in C++
Date: 13 Mar 2000 12:07:04 GMT
Reply-To: [EMAIL PROTECTED]
One place that C++ exceptions could be used is in kernel GFP's
such that on kernel error an exception is used to cause the Oops.
The second place is on detected the Pentitum floating point bug.
When it causes an exception, it causes the kernel to then do
everyting in s/w emulation mode automatically.
The third place to used exceptions is during kernel debugging,
such that when schedulers miss deadlines due to race conditions
or hardware drivers miss interupts an "informative" message is
output to syslog for debugging. They can also be used to set
parameters in the kernel for test hooks and monitored via the
exceptions to collect performance data.
: With this discussion we easily can fill up a discussion group
: of it's on (is there some group already?). This C++ discussion
: came up again and again with no result. Yes, many things might
: be expressed much much clearer using C++, but it is simply
: impossible for several reasons: Who is willing to rewrite the
: whole kernel in C++? If you start now, it would take years to
: do that and to test it and find all bugs you will introduce.
: Meanwhile the original kernel will continue to develop much
: faster than your C++ project, you will never overhaul it.
: Even if all programmers, including Linus himself, will stop using
: C and turn to C++ this means, that all development of linux will
: stop for years too. Its really hard to accept, but the C train
: runs too fast, to jump off now without beeing killed.
: So it's right to refuse the statement: "all parts of the kernel
: schould be recoded in C++ using all language features", but
: on the other hand, it is silly to refuse any goods of C++
: due to some bad properties of C++, like exceptions, which
: are in fact absolutely unusuable within a linux kernel
: environment. Also the statement "C++ is too buggy to be
: taken into account" will not hold for ever.
: The question should be: under which circumstances would it
: be possible to introduce C++ into the kernel? There are big
: parts which are not dealing directly with hardware or interrupts,
: i.e. the filesystem parts. If you once have interfaces and wrapper
: classes around the kernel structures you can start testing C++
: without affecting the inner kernel construction. If it turns out
: to be usuable, you may have a change to convert the inner kernel
: routines step by step in the far future.
: Dieter
: --
: Dieter St�ken, con terra GmbH, M�nster
: [EMAIL PROTECTED] [EMAIL PROTECTED]
: http://www.conterra.de/ http://qgp.uni-muenster.de/~stueken
: (0)251-980-2027 (0)251-83-334974
--
Mike,
[EMAIL PROTECTED]
------------------------------
From: David <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.apps
Subject: PROBLEM WITH MPROTECT (OR MMAP) MY SYSYEM CRASH !!!
Date: Mon, 13 Mar 2000 12:27:09 GMT
I have an dynamic library and link single program (Hello World) with It.
When It starts run, I ummap all code and data, for make a memory access
monitor. How the init function is into shared lib, the memory is not the
same that main program (I have checked it in /proc ...). When I unmap
(or mprotect( dir , PROT_NONE ) ) my program crash ... and LINUX with it
(I need reinstall some packages, so each probe is mortal).
If a dlopen is made, you can unmap and mprotect all his regions.
This is my code:
// It executes before main ...
void init( void ) __attribute__ (( constructor )) ;
void init( void )
{
struct sigaction act ;
struct sigaction new_signal ;
void *c_ini , *c_fin , *d_ini , *d_fin ;
// FIRST : INSTALL SIGNALS
new_signal.sa_handler =3D trat_segv ;
sigaddset( &new_signal.sa_mask , SIGSEGV ) ;
sigaddset( &new_signal.sa_mask , SIGALRM ) ;
new_signal.sa_flags =3D SA_RESTART | SA_NOCLDSTOP ;
sigaction( SIGSEGV , &new_signal , NULL ) ;
=
// This funtion works. It obtains region of code and data directions.
// c_ini =3D code_initial_direction
// d_ini =3D data_initial_direction
// c_fin =3D code_final_direction
// d_fin =3D data_final_direction
obtain_regions( prog_name , &c_ini , &c_fin , &d_ini , &d_fin ) ;
// THE REGIONS AT THIS POINT ARE WELL OBTAINED AND DIRECTION OF PC IS
NOT
// THE SAME AS ANY PAGE OF REGIONS.
// PROGRAM CRASH IN THE NEXT LINE =
munmap( c_ini , ((unsigned int)c_fin - ((unsigned int)c_ini)) ) ;
munmap( d_ini , ((unsigned int)d_fin - ((unsigned int)d_ini)) ) ;
...
=BF What can I make munmap ?
=BF Is there any manner of map a program frame into my memory address ?
Thaks,
DTM
------------------------------
From: [EMAIL PROTECTED] (Donal K. Fellows)
Crossposted-To: comp.os.linux.advocacy
Subject: Re: Absolute failure of Linux dead ahead?
Date: 13 Mar 2000 12:33:34 GMT
In article <89lqkb$oru$[EMAIL PROTECTED]>, Joseph T. Adams <[EMAIL PROTECTED]> wrote:
> I've always had a love/hate relationship with binary RPMs. I love the
> fact that they *usually* work or at least yield sufficiently useful
> clues as to make it possible to make them work. But I hate the idea
> of using binaries. They introduce potential security risks; they may
> have subtle bugs caused by slightly differing library versions; they
> may very well break if I upgrade my kernel, and then I'm stuck going
> out and getting the source anyway. They certainly won't work reliably
> if I change to a very different distribution such as Debian where the
> system files tend to live in different places.
For the number one use of binary RPMs, namely installing an OS and
accompanying applications off CD, they are pretty good indeed. They
just happen to be used for many other things besides.
> The more complex software becomes, the more necessary it is to
> automate the testing process. It's hard for me to understand how any
> robust software could possibly get built without it.
Amen! It seems strange that so many software packages (both OSS and
commercial) come without decent regression test suites. Without that
(and, preferentially, full software verification[*]) how can you even
tell if the software is working?
Donal (who still builds from tarballs preferentially...)
[* OK, so that really *is* rare! But close to my heart too. ]
--
Donal K. Fellows http://www.cs.man.ac.uk/~fellowsd/ [EMAIL PROTECTED]
-- The small advantage of not having California being part of my country would
be overweighed by having California as a heavily-armed rabid weasel on our
borders. -- David Parsons <o r c @ p e l l . p o r t l a n d . o r . u s>
------------------------------
** 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
******************************
