Linux-Development-Sys Digest #803, Volume #7 Wed, 26 Apr 00 14:15:40 EDT
Contents:
modules not working after kernel compile (Andre)
Re: Problems with MACRO in glibc include (Andreas Jaeger)
Re: GLIBC 2 - Which version. (Andreas Jaeger)
Glibc2 install. Oh boy... ([EMAIL PROTECTED])
Re: File questions (Alan Donovan)
Re: boot messages (Alan Donovan)
Re: Glibc2 install. Oh boy... (Andreas Jaeger)
Re: Problems with MACRO in glibc include (Nix)
Re: My experience installing red hat from CD-ROM
Re: Trouble installing GNU C from Red Hat 6.0 CD (Rasputin)
Re: cli() & sti()... ("Dmitry A. Fedorov")
kernel modul: serial port interrupt problem ([EMAIL PROTECTED])
Re: Glibc2 install. Oh boy... ([EMAIL PROTECTED])
Re: How legal is it??? (Barry Schwarz)
Re: modules not working after kernel compile ([EMAIL PROTECTED])
Re: boot messages (James Moger)
Re: cli() & sti()... (���ظ� Chun-Mok Chung)
Re: cli() & sti()... (Bill Waddington)
Need DDD v3.2 RPM ("Michael A. Crawford")
basic remove files (Sylvain Pajot)
Re: basic remove files (Daniel de Rauglaudre)
----------------------------------------------------------------------------
From: Andre <[EMAIL PROTECTED]>
Subject: modules not working after kernel compile
Date: Wed, 26 Apr 2000 07:30:05 GMT
Hi,
I have RH 6.2 with kernel 2.2.14 and I have a HP 7500i IDE CD RW. To be
able to burn CDs, I have to enable scsi-ide emulation. I folowed
instructions from a whole lot of howto's and finally got the kernel
compiled and the CD-RW is identified as a scsi device (I compiled the scsi
emulation into the kernel, not as a module) The problem is now that no
modules are working, not even with the old kernel, when they used to work.
The result of depmod -a is "Unresolved symbols in /lib/modules/<module>"
All modules that are being loaded at boot-up fails.
When I compiled the kernel, I did a make dep, make clean, make modules,
make modules_install, make bzImage, with noe error messages.
Can anyone tell me what could be wrong and how do I get my modules to work
again?
I would also like to know what the /boot/module-info-2.2.14-5.0 file is
for?
Thanks
--
Posted via CNET Help.com
http://www.help.com/
------------------------------
From: Andreas Jaeger <[EMAIL PROTECTED]>
Subject: Re: Problems with MACRO in glibc include
Date: 26 Apr 2000 09:38:54 +0200
>>>>> Sangohn Christian writes:
> Hi!
> I�d like to use the macro defined as follows in the /usr/include/unistd.h:
> #ifdef __USE_GNU
> /* Evaluate EXPRESSION, and repeat as long as it returns -1 with `errno'
> set to EINTR. */
> # define TEMP_FAILURE_RETRY(expression) \
> (__extension__ \
> ({ long int __result; \
> do __result = (long int) (expression); \
> while (__result == -1L && errno == EINTR); \
> __result; })) \
> But despite of
> #include <unistd.h> /* UNIX Standard functions */
> #define __USE_GNU 1 /* */
> in my header file and/or -D__USE_GNU as compiler flag, the macro is still
> not referenced and is considered undeclared by the compiler.
> What am I doing wrong and what should I do?
Read the manual on feature test macros or check <features.h>.
_GNU_SOURCE is the right macro to use.
Andreas
--
Andreas Jaeger
SuSE Labs [EMAIL PROTECTED]
private [EMAIL PROTECTED]
------------------------------
From: Andreas Jaeger <[EMAIL PROTECTED]>
Subject: Re: GLIBC 2 - Which version.
Date: 26 Apr 2000 09:40:09 +0200
>>>>> mcnuttj writes:
> Hey all,
> For various reasons, I'm trying to get glibc 2 - a.k.a. libc 6 - installed
> on my box. What is the latest stable version? According to the HOWTO on
> www.linux.org, 2.0.6 is the example. However, various 2.1.x versions are
> available on ftp.gnu.org, and something I read someplace refers to v2.1 as
> the "next stable release".
> I'm running a very old version of Slackware, so RPMs aren't going to help.
> I was planning on compiling it, but when I got glibc-2.1.3.tar.gz and the
> latest glibc-crypt, glibc-linuxthreads, and glibc-localedata from ftp.gnu.org
> it failed the 'make'.
There's no localedata add-on for glibc 2.1.3 - it's been integrated
into 2.1.3. If you're using an old localedata add-on, you do get
problems.
> Ideas/suggestions?
Start again without localedata.
Andreas
--
Andreas Jaeger
SuSE Labs [EMAIL PROTECTED]
private [EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED]
Subject: Glibc2 install. Oh boy...
Date: 25 Apr 2000 22:33:59 GMT
Okay, now I'm in big trouble.
I got glibc-2.1.3 to compile. I got it to 'make check' successfully. I
moved all my old libs and my old *.o and old symlinks. I even edited
my specs file.
'make install' in the target glibc directory gives me the following:
CC="gcc" /usr/bin/perl scripts/test-installation.pl /usr/src/glibc-target/
In file included from /usr/include/stdio.h:57,
from /tmp/test-prg8281.c:2:
/usr/include/libio.h:370: parse error before `_IO_seekoff'
/usr/include/libio.h:370: parse error before `_G_off64_t'
/usr/include/libio.h:371: parse error before `_IO_seekpos'
/usr/include/libio.h:371: parse error before `_G_fpos64_t'
Execution of GCC failed!
...and then it gives me some suggestions on how to fix it. I'm pretty sure
it isn't the specs file, and I'm pretty sure it isn't a symlink thing (the
two suggestions listed by 'make').
Any ideas? My system still seems to work, since I moved all by old libs
properly, but I can't compile anything until this is fixed, and I need
libc.so.6 for several programs I want to run.
Thanks!
--J
------------------------------
From: Alan Donovan <[EMAIL PROTECTED]>
Subject: Re: File questions
Date: Wed, 26 Apr 2000 10:33:03 +0100
John Jacques wrote:
>
> http://www.aie.nl/software_doc/tlk-html/node102.html#SECTION001120000000000000000
>
> I read this about the Linux VFS (Virtual File System). Am I interpreting
> the article correctly as saying all inode and directory information is
> stored in RAM once it is accessed?
No. inode and directory information is read in and flushed out as
determined by the kernel's caching policy. Inodes reside on disk,
V-nodes are the in-core datastructure that hold basically the same
information. AFAIK V-nodes are subject to flushing too.
> I'm currently using mySQL with my own C program to access a database. I
> need more control over the data. I was thinking I can store the data
> like this:
>
> database/table/fieldname/record#/data
> Now that I know this will not work I am thinking of this:
>
> database/table/fieldname_a/data
> database/table/fieldname_b/data
> database/table/fieldname_c/data
> database/table/fieldname_d/data
> database/table/fieldname_e/data
> database/table/fieldname_f/record#/data (this is unlimited binary/text
> records)
Please excuse me if I have misunderstood, but if you are already using a
database, then it's simply a matter of making queries to the database
engine from your process. The database will manage all the storage and
access more compactly than one file per record, and the price you pay is
a process context switch per query (which can of course retrieve
multiple records). Unless this is prohibitive, it sounds like a solution
to me.
What you describe seems to duplicate all the storage and hierarchy of a
database without the clean semantics (ACID) that a DB gives you.
alan
--
========================================================================
Alan Donovan [EMAIL PROTECTED] http://www.imerge.co.uk
Imerge Ltd. +44 1223 875265
------------------------------
From: Alan Donovan <[EMAIL PROTECTED]>
Subject: Re: boot messages
Date: Wed, 26 Apr 2000 10:37:51 +0100
Sake wrote:
> I'm integrating a Linux application box. I don't want the user
> to see those kernel booting messages every time they turn on the
> machine. Is there a way to divert those messages ? Idealy, I would
> like to be able to put up a grafic logo on the screen when the machine
> is booting (I mean before the log-on screen)
This is a perennial question, to which the answer is, sorry, there are
no plans to make the bootup any prettier. Those messages are just so
useful in understanding problems if they should arise that no-one who
hacks that code is tempted to spend any effort making it prettier (i.e.
harder to debug). And besides, Linux users spend so little of their
lives rebooting that they don't need a pretty screen saying "Windows 95
is booting". :-)
> e-mail response is greatly appreciated.
But would suggest you can't be bothered to wait around for a reply.
alan
--
========================================================================
Alan Donovan [EMAIL PROTECTED] http://www.imerge.co.uk
Imerge Ltd. +44 1223 875265
------------------------------
From: Andreas Jaeger <[EMAIL PROTECTED]>
Subject: Re: Glibc2 install. Oh boy...
Date: 26 Apr 2000 11:37:54 +0200
>>>>> mcnuttj writes:
> Okay, now I'm in big trouble.
> I got glibc-2.1.3 to compile. I got it to 'make check' successfully. I
> moved all my old libs and my old *.o and old symlinks. I even edited
> my specs file.
> 'make install' in the target glibc directory gives me the following:
> CC="gcc" /usr/bin/perl scripts/test-installation.pl /usr/src/glibc-target/
> In file included from /usr/include/stdio.h:57,
> from /tmp/test-prg8281.c:2:
> /usr/include/libio.h:370: parse error before `_IO_seekoff'
> /usr/include/libio.h:370: parse error before `_G_off64_t'
> /usr/include/libio.h:371: parse error before `_IO_seekpos'
> /usr/include/libio.h:371: parse error before `_G_fpos64_t'
> Execution of GCC failed!
> ...and then it gives me some suggestions on how to fix it. I'm pretty sure
> it isn't the specs file, and I'm pretty sure it isn't a symlink thing (the
> two suggestions listed by 'make').
> Any ideas? My system still seems to work, since I moved all by old libs
> properly, but I can't compile anything until this is fixed, and I need
> libc.so.6 for several programs I want to run.
Read the FAQ:
2.29. Compiling programs I get parse errors in libio.h (e.g. "parse error
before `_IO_seekoff'"). How should I fix this?
Andreas
--
Andreas Jaeger
SuSE Labs [EMAIL PROTECTED]
private [EMAIL PROTECTED]
------------------------------
From: Nix <$}xinix{[email protected]>
Subject: Re: Problems with MACRO in glibc include
Date: 25 Apr 2000 23:34:48 +0100
Sangohn Christian <[EMAIL PROTECTED]> writes:
> But despite of
> #include <unistd.h> /* UNIX Standard functions */
> #define __USE_GNU 1 /* */
> in my header file and/or -D__USE_GNU as compiler flag, the macro is still
> not referenced and is considered undeclared by the compiler.
>
> What am I doing wrong and what should I do?
>From /usr/include/features.h:
: /* These are defined by the user (or the compiler)
: to specify the desired environment:
:
: __STRICT_ANSI__ ISO Standard C.
: _ISOC99_SOURCE Extensions to ISO C 89 from ISO C 99.
: _ISOC9X_SOURCE Similar, kept for compatibility.
: _POSIX_SOURCE IEEE Std 1003.1.
: _POSIX_C_SOURCE If ==1, like _POSIX_SOURCE; if >=2 add IEEE Std 1003.2;
: if >=199309L, add IEEE Std 1003.1b-1993;
: if >=199506L, add IEEE Std 1003.1c-1995
: _XOPEN_SOURCE Includes POSIX and XPG things. Set to 500 if
: Single Unix conformance is wanted.
: _XOPEN_SOURCE_EXTENDED XPG things and X/Open Unix extensions.
: _LARGEFILE_SOURCE Some more functions for correct standard I/O.
: _LARGEFILE64_SOURCE Additional functionality from LFS for large files.
: _FILE_OFFSET_BITS=N Select default filesystem interface.
: _BSD_SOURCE ISO C, POSIX, and 4.3BSD things.
: _SVID_SOURCE ISO C, POSIX, and SVID things.
: _GNU_SOURCE All of the above, plus GNU extensions.
: _REENTRANT Select additionally reentrant object.
: _THREAD_SAFE Same as _REENTRANT, often used by other systems.
:
: The `-ansi' switch to the GNU C compiler defines __STRICT_ANSI__.
: If none of these are defined, the default is all but _GNU_SOURCE.
: If more than one of these are defined, they accumulate.
: For example __STRICT_ANSI__, _POSIX_SOURCE and _POSIX_C_SOURCE
: together give you ISO C, 1003.1, and 1003.2, but nothing else.
:
: These are defined by this file and are used by the
: header files to decide what to declare or define:
:
: __USE_ISOC9X Define ISO C 9X things.
: __USE_POSIX Define IEEE Std 1003.1 things.
: __USE_POSIX2 Define IEEE Std 1003.2 things.
: __USE_POSIX199309 Define IEEE Std 1003.1, and .1b things.
: __USE_POSIX199506 Define IEEE Std 1003.1, .1b, .1c and .1i things.
: __USE_XOPEN Define XPG things.
: __USE_XOPEN_EXTENDED Define X/Open Unix things.
: __USE_UNIX98 Define Single Unix V2 things.
: __USE_LARGEFILE64 Define LFS things with separate names.
: __USE_FILE_OFFSET64 Define 64bit interface as default.
: __USE_BSD Define 4.3BSD things.
: __USE_SVID Define SVID things.
: __USE_MISC Define things common to BSD and System V Unix.
: __USE_GNU Define GNU extensions.
: __USE_REENTRANT Define reentrant/thread-safe *_r functions.
: __FAVOR_BSD Favor 4.3BSD things in cases of conflict.
:
: The macros `__GNU_LIBRARY__', `__GLIBC__', and `__GLIBC_MINOR__' are
: defined by this file unconditionally. `__GNU_LIBRARY__' is provided
: only for compatibility. All new code should use the other symbols
: to test for features.
:
: All macros listed above as possibly being defined by this file are
: explicitly undefined if they are not explicitly defined.
: Feature-test macros that are not defined by the user or compiler
: but are implied by the other feature-test macros defined (or by the
: lack of any definitions) are defined by the file. */
The first thing that <features.h> does is to undefine all the __USE_*
constants --- and *everything* #includes <features.h>.
You should use _GNU_SOURCE.
--
Root beer --- the drink of the BOFH.
------------------------------
From: <[EMAIL PROTECTED]>
Subject: Re: My experience installing red hat from CD-ROM
Date: Wed, 26 Apr 2000 02:48:24 -0700
Yeah, but my point was, the DOS boot disk didn't work for me on 2
machines... so the Linux boot disk is the way to go.
Sake wrote in message <8e5qqg$1i$[EMAIL PROTECTED]>...
>Making a Libux boot disk takes the same amount of time as making a DOS boot
>disk with CD support
>
><[EMAIL PROTECTED]> wrote in message
>news:[EMAIL PROTECTED]...
>> Maybe this will save someone some headaches - I tried on two PC's to
>install
>> red hat 6.1 from the CD-ROM after booting each with a minimal MS-DOS
>floppy,
>> just enough to access the CD-ROM with MSCDEX and the CD driver... and
>> neither Linux install could find the CD-ROM controller (one of which was
>> SCSI, and one Creative Labs/Panasonic). So I was quietly cursing Linux,
>> when I decided to make a boot floppy from the Linux CD, boot that, and
try
>> the install - and it WORKED PERFECT ON BOTH MACHINES. (Sorry to yell.)
>>
>> So even though installing from MS-DOS is outlined in the red hat docs as
>the
>> next best thing if you can't boot from the CD or from the floppy they
give
>> you (BTW - my in-box Linux floppy was bad, which is what started this
>whole
>> adventure), I would not recommend it - make yourself a Linux boot floppy,
>I
>> think you'll be happier.
>>
>> Scott Clough
>> Clough Labs, LLC
>>
>> www.LaserEnlighten.com - Burning to Learn!
>>
>>
>>
>>
>>
>
>
------------------------------
From: Rasputin <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.apps,comp.os.linux.development
Subject: Re: Trouble installing GNU C from Red Hat 6.0 CD
Date: Wed, 26 Apr 2000 11:23:52 +0100
Raptor wrote:
>
> Lorenzo Bettini wrote:
> >
> > Jason wrote:
> > > This all makes sense except that when I type 'rpm -i *egcs*' I get a
> > > bunch of errors indicating that things couldn't be installed because of
> > > various dependency issues. I'm not sure how to proceed. Also, the
> >
> > These errors say that, in order to install this package, first you have
> > to install the packages it depends on... this is recursive, i.e. while
> > installing one of these package you may have to install other package as
> > well...
> >
> > Lorenzo
>
> I'm a newbie myself, but the book says you can frequently ignore the
> warnings and install the package anyway.
No offence, but your book honks :)
Try looking at the dependencies and install the relevant RPMs until
they're met.
> Tell rpm to ignore the
> situation; see the man page. There's a good chance it'll work, but it
> could also crash hard.
<nods>
If you just haven't got the RPMs you'd need (which is fairly common if
you're installing Suse RPMs onto Redhat from somwehere like rpmfind.net)
*then* try it regardless - "--nodeps" (and excessive overuse of symlinks
to fool ld) is your friend , but I wouldn't like to upgrade glibc that
way...
--
Rasputin.
Jack of All Trades - Master of Nuns.
------------------------------
From: "Dmitry A. Fedorov" <[EMAIL PROTECTED]>
Subject: Re: cli() & sti()...
Date: Wed, 26 Apr 2000 10:23:47 +0000
Villy Kruse wrote:
>
> On Mon, 17 Apr 2000 01:50:38 GMT,
> Johan Kullstam <[EMAIL PROTECTED]> wrote:
>
> >Badrinath Venkatachari <[EMAIL PROTECTED]> writes:
> >
> >> If I happen to have this pair cli() to disable interrupts and sti() to
> >> enable interrupts, then can it be assumed that the process cannot be
> >> preempted while executing code in between them ???
> >>
> >> cli()
> >> /* code comes here */
> >> sti()
> >
> >make sure you consider SMP too.
>
> Exactly. For a multiprocessor system you need a spinlock in addition to
> masking the interrupt to truely protect that piece of code from being
> re-entetered by the other processor getting an interrupt. Masking an
> interrupt only works on the current processor and has no effect on any
> of the other processors.
No. Look at linux-2.2.x/include/asm-i386/system.h for cli and sti
definitions
and pay attention to __SMP__ and non-__SMP__ sections difference.
------------------------------
From: [EMAIL PROTECTED]
Subject: kernel modul: serial port interrupt problem
Date: Wed, 26 Apr 2000 14:20:06 +0200
Hi, to all kernelhackers,
i have the following problem. It is posible to me, in my kernel modul,
to write and to read data from the serial port base
register via outb and inb. But i'm unable to receive any interrupt from
the UART, why???
Please have a look at the code, and help me.
Thanks a lot,
Thomas Edelmann
static int eib_open (struct inode *pinode, struct file *pfile)
{
int result;
if (eib_active)
return -EBUSY;
// Initialisierung des UART
=
eib_reg_mcr =3D DCTS; /* MCR_BITS */
eib_reg_ier1 =3D 0; /* IER_BITS */
eib_reg_lcr1 =3D DLAB; /* LCR_BITS */
eib_reg_lcr2 =3D EPS + PEN + WL8; /* LCR_BITS */
eib_reg_fcr =3D TFIFOR + RFIFOR + FIFOE; /* FCR_BITS */
eib_reg_ier2 =3D ERB; // =3D 0x01 /* IER_BITS */
eib_reg_thb =3D 0x06; /* f=FCr BAUD-Rate =3D =
9600
*/
=
outb (eib_reg_mcr , PORT_MCR(eib_iobase));
outb (eib_reg_fcr, PORT_FCR(eib_iobase));
outb (eib_reg_ier1, PORT_IER(eib_iobase));
=
// Ich glaube hier h=E4ngts, was aber nicht woran, nur so ein Gef=FChl
// eib_irq =3D 4, eib_iobase =3D 0x3f8
result =3D request_irq (eib_irq, eib_interrupt, SA_INTERRUPT,
"eib", NULL);
if (result)
{
printk (KERN_WARNING "EIB: kein Interrupt verf=FCgbar");
return result;
}
printk (KERN_WARNING "EIB: Interrupt registered\n");
// clear any pending interrupt
inb(PORT_LSR(eib_iobase));
inb(PORT_RBR(eib_iobase));
inb(PORT_IIR(eib_iobase));
inb(PORT_MSR(eib_iobase));
=
outb (eib_reg_lcr1, PORT_LCR(eib_iobase));
outb (eib_reg_thb , PORT_THB(eib_iobase));
outb (eib_reg_lcr2, PORT_LCR(eib_iobase));
// UART sollte eigentlich bei jedem receive einen Interrupt ausl=F6sen
outb (eib_reg_ier2, PORT_IER(eib_iobase));
=2E..
}
void eib_interrupt (int irq, void *dev_id, struct pt_regs *regs)
{
*
printk (KERN_WARNING "EIB: !!!Interrupt!!!");
}
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Glibc2 install. Oh boy...
Date: 26 Apr 2000 12:44:43 GMT
Okay, does that mean I can remove all of /usr/i586-pc-linux-gnulibc1/?
That's where the old _G_config.h file was.
--J
P.S. Thanks much! I hate missing stuff in the FAQ.... <grr...>
Andreas Jaeger <[EMAIL PROTECTED]> wrote:
:>>>>> mcnuttj writes:
: > Okay, now I'm in big trouble.
: > I got glibc-2.1.3 to compile. I got it to 'make check' successfully. I
: > moved all my old libs and my old *.o and old symlinks. I even edited
: > my specs file.
: > 'make install' in the target glibc directory gives me the following:
: > CC="gcc" /usr/bin/perl scripts/test-installation.pl /usr/src/glibc-target/
: > In file included from /usr/include/stdio.h:57,
: > from /tmp/test-prg8281.c:2:
: > /usr/include/libio.h:370: parse error before `_IO_seekoff'
: > /usr/include/libio.h:370: parse error before `_G_off64_t'
: > /usr/include/libio.h:371: parse error before `_IO_seekpos'
: > /usr/include/libio.h:371: parse error before `_G_fpos64_t'
: > Execution of GCC failed!
: > ...and then it gives me some suggestions on how to fix it. I'm pretty sure
: > it isn't the specs file, and I'm pretty sure it isn't a symlink thing (the
: > two suggestions listed by 'make').
: > Any ideas? My system still seems to work, since I moved all by old libs
: > properly, but I can't compile anything until this is fixed, and I need
: > libc.so.6 for several programs I want to run.
: Read the FAQ:
: 2.29. Compiling programs I get parse errors in libio.h (e.g. "parse error
: before `_IO_seekoff'"). How should I fix this?
: Andreas
: --
: Andreas Jaeger
: SuSE Labs [EMAIL PROTECTED]
: private [EMAIL PROTECTED]
------------------------------
From: Barry Schwarz <[EMAIL PROTECTED]>
Crossposted-To:
alt.comp.lang.learn.c-c++,comp.lang.asm.x86,comp.lang.c++,comp.os.linux.development.apps,microsoft.public.windowsnt.protocol.tcpip,microsoft.public.win32.programmer.tools
Subject: Re: How legal is it???
Date: 26 Apr 2000 12:51:16 GMT
On 25 Apr 2000 04:35:15 GMT, _Steven Chang
<[EMAIL PROTECTED]> wrote:
>Hi there,
>
>I'm thinking of creating a stealth application that will automatically
>launch itself when the OS starts. I would like the application to
>record the keystrokes made by users, and possibly the mouse movements as
>well. Then, probably buffer these data and have them sent to a server
>over the internet periodically.
>
>Assuming that the user has provided consent for having this program
>installed on one's computer, how legal will it be for such program to be
>running under
>
>a) Linux?
>b) Windows 98/NT/2000?
>
>I would expect this not such a big deal with LINUX, but what about the
>privacy issue?
>
>Any help or referral is appreciated.
>
>Thanks a lot,
>Steven
Why on earth would you even consider accepting legal advice from a
bunch of anonymous strangers of dubious (or at least varied)
competencies?
<<Remove the del for email>>
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: modules not working after kernel compile
Date: 26 Apr 2000 12:49:10 GMT
Try this (assuming same kernel *version*, just different mod setup):
make modules
mv /lib/modules/<version> /lib/modules/<version>.old
make modules_install
Reboot! (for depmod to work)
Reboot again!
That removes all of the old modules from the place where depmod and the
kernel will look for them, so you won't get unresolved symbols on mods
you no longer want.
Rebooting twice gives depmod a chance to run on your new modules with the
new kernel the first time (you might get unresolved symbols once). On the
second reboot, you should have a clean startup.
--J
Andre <[EMAIL PROTECTED]> wrote:
: Hi,
: I have RH 6.2 with kernel 2.2.14 and I have a HP 7500i IDE CD RW. To be
: able to burn CDs, I have to enable scsi-ide emulation. I folowed
: instructions from a whole lot of howto's and finally got the kernel
: compiled and the CD-RW is identified as a scsi device (I compiled the scsi
: emulation into the kernel, not as a module) The problem is now that no
: modules are working, not even with the old kernel, when they used to work.
: The result of depmod -a is "Unresolved symbols in /lib/modules/<module>"
: All modules that are being loaded at boot-up fails.
: When I compiled the kernel, I did a make dep, make clean, make modules,
: make modules_install, make bzImage, with noe error messages.
: Can anyone tell me what could be wrong and how do I get my modules to work
: again?
: I would also like to know what the /boot/module-info-2.2.14-5.0 file is
: for?
: Thanks
: --
: Posted via CNET Help.com
: http://www.help.com/
------------------------------
From: James Moger <[EMAIL PROTECTED]>
Subject: Re: boot messages
Date: Wed, 26 Apr 2000 09:52:37 -0400
Reply-To: [EMAIL PROTECTED]
I've been looking into this too. There are a couple options:
Corel has a package they call BootSplash which merges with Lilo -
replaces the boot sector withtheir graphical boot loader. This masks
the kernel messages - as long as you don't use the framebuffer console
type. Unfortunately, I haven't been to successful at compiling the
sources for this. The BootSplash code is predominately written in
assembler and I think they are making some assumptions about the kernel,
etc, such that I get all sorts of assembler compile errors.
The other option is to use a framebuffer console. With the frame buffer
console you can specify a graphic to be used and you define its size -
so perhaps you could make it full screen or 2/3 the screen and show a
few lines of the kernel booting. This is the approach I am currently
taking. Anyone else know of another?
--
James Moger
===---------------------===
Software Engineer
Transonic Systems, Inc.
{C/C++} {Java} {Smalltalk}
Cornell Engineering '98
===---------------------===
------------------------------
From: ���ظ� Chun-Mok Chung <[EMAIL PROTECTED]>
Subject: Re: cli() & sti()...
Date: Wed, 26 Apr 2000 13:53:37 GMT
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] wrote:
> On Sun, 16 Apr 2000 19:38:20 -0700, Badrinath Venkatachari <[EMAIL PROTECTED]>
>
> What happens is that cli() and sti() are emulated in a bletcherous way on SMP.
> The point I'm trying to get to is that cli() and sti() are obsolete, legacy
> operations---do not use them! Use spinlocks. The operations spin_lock_irqsave()
> and spin_unlock_irqrestore() work correclty under SMP and on a uP kernel they
> collapse into save_flags(); cli() and restore_flags().
>
I cannot find spin_lock_xxx() functions. I can only find spinlock() and
spinunlock() at <asm/locks.h>. I use kernel 2.0.36 with x86 mpu. Where can I
find your saying functions?
--
���ظ� Chun-Mok Chung
LG Information and Communications, Ltd.
Seoul, Korea
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: Bill Waddington <[EMAIL PROTECTED]>
Subject: Re: cli() & sti()...
Date: Wed, 26 Apr 2000 14:15:34 GMT
> The point I'm trying to get to is that cli() and sti() are obsolete,
legacy
> operations---do not use them! Use spinlocks. The operations
spin_lock_irqsave()
> and spin_unlock_irqrestore() work correclty under SMP and on a uP
kernel they
> collapse into save_flags(); cli() and restore_flags().
Hello,
When using the above, does one place similar spinlocks in the interrupt
code?
Thanks,
Bill
--
Bill Waddington
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: "Michael A. Crawford" <[EMAIL PROTECTED]>
Subject: Need DDD v3.2 RPM
Date: Wed, 26 Apr 2000 07:51:28 -0700
I tried to build the sucker from scratch but there is something about
lesstif that it doesn't like. Can someone tell me where to find an RPM for
the 3.2 version of DDD from GNU? Please reply to the e-mail address below
as well as to the list. Thanks.
-Michael
michaelc.at.flashcom.net
------------------------------
From: Sylvain Pajot <[EMAIL PROTECTED]>
Subject: basic remove files
Date: Wed, 26 Apr 2000 17:28:22 +0200
hi all,
How can I remove files in a program by using functions like "mkdir". I
don't want to use exec with the shell-command "rm".
Can you help me ?
Sylvain
--
>>> Email: [EMAIL PROTECTED] <<<
>>> http://www.kevin.fr.st <<<
------------------------------
From: Daniel de Rauglaudre <[EMAIL PROTECTED]>
Subject: Re: basic remove files
Date: Wed, 26 Apr 2000 15:41:31 +0000
> How can I remove files in a program by using functions like "mkdir". I
> don't want to use exec with the shell-command "rm".
man 2 unlink
man 2 mkdir
--
Daniel de RAUGLAUDRE
[EMAIL PROTECTED]
http://cristal.inria.fr/~ddr/
------------------------------
** 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
******************************
