Linux-Misc Digest #611, Volume #26               Fri, 22 Dec 00 15:13:01 EST

Contents:
  Re: argument list too long ([EMAIL PROTECTED])
  Re: Updating Linux causes previous working script files to error out (Paul Kimoto)
  Re: Question About Timing Functions Under Linux (Michel Bardiaux)
  Re: logrotate "problems" ([EMAIL PROTECTED])
  Re: Mount /tmp in swap (* Tong *)
  Maximum file size gzip can handle? (Dragan Colak)
  Re: Microsoft Shares Tumble. Is LINUX to blame? (James Stafford)
  Oracle on RedHat 6.1 - cannot get webdb to work (Jordan Kelly)
  print prob's ("ailsalogue")
  Re: Microsoft Shares Tumble. Is LINUX to blame? (Harlan Grove)
  Re: GeForce2 MX (Creative) Linux Problem (Bill Baio)
  Re: GeForce2 MX (Creative) Linux Problem (Bill Baio)
  Re: GeForce2 MX (Creative) Linux Problem (Bill Baio)
  Re: How to call 'stty' from inittab? (Michael Heiming)
  Re: Updating Linux causes previous working script files to error out ("Peter T. 
Breuer")
  Re: Updating Linux causes previous working script files to error out ("Peter T. 
Breuer")
  Re: Kernel parameters ("Benjamin")

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

From: [EMAIL PROTECTED]
Subject: Re: argument list too long
Date: Fri, 22 Dec 2000 16:20:36 GMT

In article <[EMAIL PROTECTED]>,
  "Peter T. Breuer" <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > What I want to do is delete a large number of files based on a
search
> > but I get an "argument list too long error".  How do I get around
this?
>
> man xargs. Unix faq?
>
> next!
>
> Peter
>

Cool!  Thank you!

The following worked great.

find . -name 'mail.info.*' -print0 | xargs -0 -r -n $(getconf ARG_MAX)
-P 0 rm -fv



--
MM


Sent via Deja.com
http://www.deja.com/

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

From: [EMAIL PROTECTED] (Paul Kimoto)
Subject: Re: Updating Linux causes previous working script files to error out
Date: 22 Dec 2000 11:31:18 -0500
Reply-To: [EMAIL PROTECTED]

In article <[EMAIL PROTECTED]>, Jeff Pierce wrote:
> #!/bin/sh
> if [ -f /etc/ppp/stay ] ; then
> if [ -f /var/run/ppp0.pid ] ; then
>   ping -c4 -l3 preferred.com 2>&1 | grep "0 packets" > /dev/null && \
>    { /usr/sbin/ppp-off > /dev/null 2>&1 ; sleep 2 ; /usr/sbin/ppp-on2 }
>  else
>   /usr/sbin/ppp-on2
>  fi
> fi
>
> The error is 'unexpected token "else" in line 6'
> The else of the if? Huh?
>
> Out of des[p]eration I changed the "{}"'s to "()"'s in the previous line,
> since they do the same thing.

(No, "()" runs the enclosed commands in a subshell.)

> That fixed the problem!!!!
> Ok, the problem is fixed. The question remains what caused the error in
> this installation's version of bash, /sbin/sh linked to bash, to begin
> with? The "{}" are LEGAL for grouping commands together. Pages 265-266
> of the infamous Hayden books "UNIX Shell Programming" second edition.

The bash(1) man page says:

:        { list; }
:               list  is simply executed in the current shell envi-
:               ronment.  list must be terminated with a newline or
:               semicolon.

Kernighan and Pike (p. 169) says:

: The characters <{> and <}> are like <do> and <done>--they have special
: meaning only if they follow a semi-colon, newline, or other command
: terminator.

> Second, how do you find out the bash version installed?

Try
$ /path/to/bash -version -c ""
or
$ echo $BASH_VERSION
(inside the shell).

-- 
Paul Kimoto
This message was originally posted on Usenet in plain text.  Any images, 
hyperlinks, or the like shown here have been added without my consent,
and may be a violation of international copyright law.

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

From: Michel Bardiaux <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.embedded,comp.os.linux.development.apps,comp.os.linux
Subject: Re: Question About Timing Functions Under Linux
Date: Fri, 22 Dec 2000 16:33:18 GMT

Dave Blake wrote:
> 
> Michel Bardiaux <[EMAIL PROTECTED]> wrote:
> 
> > What about the sched_setscheduler & related functions with a
> > SCHED_RR scheduling regime? What kind of latencies can one
> > expect with that scheme? (My requirements are somewhat less
> > strict: my time-critical process must be able to 'beat' at the
> > 0.250 and .750 millesconds of every *UTC* second, with better
> > than 10 msec accuracy. This is currently running on an SGI
> > INDY, with exactly that kind of scheduling, but we hope..
> > guess what...)
> 
> I assume you mean 250 and 750 milliseconds, not 0.250 and 0.750
> milliseconds with 10 msec accuracy.

Yes, I meant "the 250th millsecond" i.e. "the millisecond labelled
0.250seconds".
> 
> A really simple C program with select (to get you to within 100
> milliseconds) and timing functions (for the fine precision)
> could hit 10 msec on an unloaded machine in linux, even in the
> worst case scenario. This is provided you do not run huge dd
> commands followed by sync, of course.

That was exactly my question: what is going to happen if the machine
*is* loaded, but only with 'normal' but hyperactive processes? (In my
cases, they would be video encoders). Or with other time-critical
processes? (On Indy, each of them receives a specified time interval
during which it is non-preemptible, after which it is scheduled normally
if it still has processing to do).

> And if you spec it and it doesn't work, try the low latency
> patches. I see them pop up on the kernel mailing list from time
> to time, and people spec them at 200 microsecond precision.
> 
> --
> Dave Blake
> [EMAIL PROTECTED]

I've seen mention of these, and the real purpose of my question was:
does sched_setscheduler work on Linux, for my requirements? Or do I have
to look at these patches? (I assume I'd better not touch them if I don't
need them).

-- 
Michel Bardiaux
Peaktime Belgium S.A.  Rue Margot, 37  B-1457 Nil St Vincent
Tel : +32 10 65.44.15  Fax : +32 10 65.44.10

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

From: [EMAIL PROTECTED]
Subject: Re: logrotate "problems"
Date: Fri, 22 Dec 2000 16:33:30 GMT

In article <91vld5$61a$[EMAIL PROTECTED]>,
  -ljl- <[EMAIL PROTECTED]> wrote:
> In article <91t8qp$9ci$[EMAIL PROTECTED]>,
>   [EMAIL PROTECTED] wrote:
> > Uhg!  My logrotate is not performing as I would expect, resulting in
a
> > "bunch" of log files being kept.
> >
> > Example:
> > I have tons of the following files in my /var/log/news directory:
> >
> > news.notice.2.gz.3.gz.2.gz.1.gz.2.gz.1.gz.2.gz.1.gz.2.gz
> >
> > I also have tons of those type of file in my /var/log/mail directory
> >
> > There is nothing strange in my logrotate configuration files that I
> can
> > find.  (I would not know what to put in the configuration files to
> make
> > this happen...)
> >
> > Any help will be well received.
>
> Which distribution?
>
> --
> Louis-ljl-{ Louis J. LaBash, Jr. }
>
> Sent via Deja.com
> http://www.deja.com/
>

i586-mandrake-linux-gnu

I do not know what version of logrotate.  logrotate --usage did not
print the version.  The installed rpm is logrotate-3.3-5mdk.

I modified the syslog, logrotate configuration file for my news and mail
to the following.  (The ... denote stuff I have left out)

/var/log/mail/!(*.gz) {
...
}

They used to look like:

/var/log/mail/* {
...
}

I think that logrotate was rotating everything in the directory
including the rotated logs...  I do not know if my fix will work or not.


--
MM


Sent via Deja.com
http://www.deja.com/

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

From: * Tong * <[EMAIL PROTECTED]>
Subject: Re: Mount /tmp in swap
Date: 22 Dec 2000 12:53:28 -0400

"Eric en Jolanda" <[EMAIL PROTECTED]> writes:

> > [...]
> > Now, having happily stayed in the above situation for a while and
> > gained some more knowledge of the swap, I now realized that maybe
> > the best way is the other way around -- mounting  /tmp in swap,
> > 'cause I can make swap grow in some critical circumstances when the
> > /tmp grows too big.
> >
> > So, how should I mount /tmp in swap? Detailed instruction is very
> > much appreciated. Thanks.
> >
> 
> You can't.
> swap space doesn't have a normal filesystem.
> It's not even in the root tree of the FS.(unless you make a swapfile, then
> ofcourse the *file* is, the swapspace still isn't)

Hmm, yeah, that was my first impression. And it is also the reason
that I went the other way. But... let me show you it is doable in 
Solaris:

$ mount
/ on /dev/dsk/c0t0d0s0 read/write/setuid/largefiles on Tue Dec 19 21:56:18 2000
/usr on /dev/dsk/c0t0d0s6 read/write/setuid/largefiles on Tue Dec 19 21:56:18 2000
/proc on /proc read/write/setuid on Tue Dec 19 21:56:18 2000
/dev/fd on fd read/write/setuid on Tue Dec 19 21:56:18 2000
/export/home on /dev/dsk/c0t0d0s7 setuid/read/write/largefiles on Tue Dec 19 21:56:20 
2000
/tmp on swap read/write on Tue Dec 19 21:56:20 2000

$ uname -svpr
SunOS 5.6 Generic_105181-20 sparc

See the last line "/tmp on swap"? Heeheehee, guys, got to think about
it, 'cause Linux shouldn't be too much different from Unix. well,
hopefully it is not, :-)


Cheers!

-- 
Tong (remove underscore(s) to reply)
  http://members.xoom.com/suntong001/
  - All free contribution & collection & music from the heavens

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

From: Dragan Colak <[EMAIL PROTECTED]>
Subject: Maximum file size gzip can handle?
Date: Fri, 22 Dec 2000 18:23:30 -0100

Hi group,

I'm trying to zip a 5 GByte *.tar file with "gzip filename.tar".
As a result I get an error message that says
"Value too large for defined data type" and no compressed
file.
What is the maximum file size gzip can handle?
I couldn't find anything in the man page.
Does anybody know?

Thanks in advance

Dragan



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

From: James Stafford <[EMAIL PROTECTED]>
Subject: Re: Microsoft Shares Tumble. Is LINUX to blame?
Date: Fri, 22 Dec 2000 17:29:04 GMT

JoeB wrote:
> 
> Microsoft shares have tumbled after issuing a profits warning.
> Is Linux to blame? Please let me hear your opinion.
> Visit http://www.computercontractor.net to join in the discussion.

No, Linux isn't to blame. Microsoft is. If they didn't put out such
crap, and then try and force everyone to use it...

jamess
-- 
"On the side of the software box, in the 'System Requirements' section, 
it said 'Requires Windows 95 or better'. So I installed Linux."

-Anonymous

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

Date: Fri, 22 Dec 2000 10:55:10 -0500
From: Jordan Kelly <[EMAIL PROTECTED]>
Subject: Oracle on RedHat 6.1 - cannot get webdb to work

I have installed Oracle 8i and WEbdb2.2 on a RedHat 6.1 laptop. I cannot
get the webdb configuration page to load to my browser (I had to do a
manual install of the PL/SQL for Webdb 2.2 into Oracle).

I'm using Apache for my listener, not the Oracle listener, since I
couldn't get the oracle listener installation script to work at all.

It's the part where you enter
http://localhost/cgi-bin/wdbcgiw/admin_/gateway.htm

I get an error in the httpd/error.log that indicates "premature end of
script headres". According to the Apache FAQs, that means your script
quit early, probably because of a permissions problem. Unfortunately,
since wdbcgiw calls wdbcgi, which is a compiled executable, I don't know
where the problem is because I don't know what all wdbcgi does.

The error occurs with the printback of the CGI variables to the
error.log where it prints out PATH_TRANSLATED. It seems to be assigning
wdbcgi to the doc root (which is /home/httpd/html in the default Red Hat
installation).

Anyone overcome this particular problem?

Thanks,

JC Kelly


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

From: "ailsalogue" <[EMAIL PROTECTED]>
Subject: print prob's
Date: Fri, 22 Dec 2000 18:30:44 -0000

I have a HP deskjet 320 on the parallel port using Debian.
When I use it, it prints the first line and starts the next line at the end
of the first line

eg

%testprint
               % nextline...............
                                             %nextline.............

All I can print is the first few lines and then it want's a new piece of
paper.
I have tried looking at the printcap file but that hasn't shed any light.

Can anyone help me with this problem or specify the correct settings in
the relevant file?

any help will be appreciated

Andrew Logue
[EMAIL PROTECTED]









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

From: Harlan Grove <[EMAIL PROTECTED]>
Subject: Re: Microsoft Shares Tumble. Is LINUX to blame?
Date: Fri, 22 Dec 2000 19:10:45 GMT

In article <[EMAIL PROTECTED]>,
 [EMAIL PROTECTED] wrote:
>Microsoft shares have tumbled after issuing a profits warning.
>Is Linux to blame? Please let me hear your opinion.

Probably not. PC sales are down compared to last year - no Y2K panic
buying anymore. If PC sales are down, then so would be bundled Windows
and Office license packs. That and a lot of Windows users figuring out
that Windows ME, 2K and Office 2K aren't worth the hassle much less the
price of upgrade.


Sent via Deja.com
http://www.deja.com/

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

From: Bill Baio <[EMAIL PROTECTED]>
Crossposted-To: 
alt.comp.linux,alt.comp.periphs.videocards.nvidia,alt.comp.periphs.videocards.nvidia.programming,comp.os.linux.hardware,comp.os.linux.help,comp.os.linux.questions,comp.os.linux.setup,comp.os.linux.x,linux.redhat,linux.redhat.i
Subject: Re: GeForce2 MX (Creative) Linux Problem
Date: Fri, 22 Dec 2000 14:47:08 -0500

Chan Chung Hang Christopher wrote:

> go get the new version (4.0.2)
> 
> That's the only one that supports the Geforce 2 series.
> 
> Maverick wrote:
> 
> 
>> I'm having problems installing my Creative GeForce2 MX under RedHat Linux 7,
>> the drivers that came with linux don't recognize my GeForce2 MX, then i
>> installed the NVIDIA 0.9-5 drivers, and when i installed them it gave a
>> problem with agpgart module, it wont install that module because it couldn't
>> find a supportable VIA chipset, then i tried the agp_try_unsupported=1 and
>> it installed the agpgart module, and then i was able to install the nvidia
>> drivers, but when i start X-WINDOWS it crahes the computer.
>> 
>> My configuration: Intel Pentium III (EB) 667 Mhz, ASUS CUV4X Motherboard
>> (VIA chipset), 128 MB RAM (133 Mhz), RedHat Linux 7.0, XFree86 4.0.1.

There is another fix for the gforce which was posted a while back by a 
guy who went by the handle of Sam S. Onite.  As I recall, he suggested 
changing the os-agpconfig.h file from the nvidia kernel 9.5 driver.

After  the following line,

#include<linux/autoconf.h>

Insert this line,

/*


Then go down to the following line,

#endif
*/           (insert the asterisk forward slash here)

#ifdef AGPART

(file continues on without further addition)

Once this change is made to the os-agpconfig.h file, type make<ENTER> to 
properly compile the kernel driver.  Then install the nvidia glx 9.5 
driver.  I have used this aand it works fine.  You do not need to go to 
Xfree86 4.02.

Good luck.



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

From: Bill Baio <[EMAIL PROTECTED]>
Crossposted-To: 
alt.comp.linux,alt.comp.periphs.videocards.nvidia,alt.comp.periphs.videocards.nvidia.programming,comp.os.linux.hardware,comp.os.linux.help,comp.os.linux.questions,comp.os.linux.setup,comp.os.linux.x,linux.redhat,linux.redhat.i
Subject: Re: GeForce2 MX (Creative) Linux Problem
Date: Fri, 22 Dec 2000 14:48:10 -0500

Chan Chung Hang Christopher wrote:

> go get the new version (4.0.2)
> 
> That's the only one that supports the Geforce 2 series.
> 
> Maverick wrote:
> 
> 
>> I'm having problems installing my Creative GeForce2 MX under RedHat Linux 7,
>> the drivers that came with linux don't recognize my GeForce2 MX, then i
>> installed the NVIDIA 0.9-5 drivers, and when i installed them it gave a
>> problem with agpgart module, it wont install that module because it couldn't
>> find a supportable VIA chipset, then i tried the agp_try_unsupported=1 and
>> it installed the agpgart module, and then i was able to install the nvidia
>> drivers, but when i start X-WINDOWS it crahes the computer.
>> 
>> My configuration: Intel Pentium III (EB) 667 Mhz, ASUS CUV4X Motherboard
>> (VIA chipset), 128 MB RAM (133 Mhz), RedHat Linux 7.0, XFree86 4.0.1.

There is another fix for the gforce which was posted a while back by a 
guy who went by the handle of Sam S. Onite.  As I recall, he suggested 
changing the os-agpconfig.h file from the nvidia kernel 9.5 driver.

After  the following line,

#include<linux/autoconf.h>

Insert this line,

/*


Then go down to the following line,

#endif
*/           (insert the asterisk forward slash here)

#ifdef AGPART

(file continues on without further addition)

Once this change is made to the os-agpconfig.h file, type make<ENTER> to 
properly compile the kernel driver.  Then install the nvidia glx 9.5 
driver.  I have used this aand it works fine.  You do not need to go to 
Xfree86 4.02.

Good luck.



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

From: Bill Baio <[EMAIL PROTECTED]>
Crossposted-To: 
alt.os.linux.mandrake,alt.comp.linux,alt.comp.periphs.videocards.nvidia,alt.comp.periphs.videocards.nvidia.programming,comp.os.linux.hardware,comp.os.linux.help,comp.os.linux.questions,comp.os.linux.setup,comp.os.linux.x,linux.redhat,linux.redhat.i
Subject: Re: GeForce2 MX (Creative) Linux Problem
Date: Fri, 22 Dec 2000 14:51:26 -0500

Chan Chung Hang Christopher wrote:

> go get the new version (4.0.2)
> 
> That's the only one that supports the Geforce 2 series.
> 
> Maverick wrote:
> 
> 
>> I'm having problems installing my Creative GeForce2 MX under RedHat Linux 7,
>> the drivers that came with linux don't recognize my GeForce2 MX, then i
>> installed the NVIDIA 0.9-5 drivers, and when i installed them it gave a
>> problem with agpgart module, it wont install that module because it couldn't
>> find a supportable VIA chipset, then i tried the agp_try_unsupported=1 and
>> it installed the agpgart module, and then i was able to install the nvidia
>> drivers, but when i start X-WINDOWS it crahes the computer.
>> 
>> My configuration: Intel Pentium III (EB) 667 Mhz, ASUS CUV4X Motherboard
>> (VIA chipset), 128 MB RAM (133 Mhz), RedHat Linux 7.0, XFree86 4.0.1.

There is another fix for the gforce which was posted a while back by a 
guy who went by the handle of Sam S. Onite.  As I recall, he suggested 
changing the os-agpconfig.h file from the nvidia kernel 9.5 driver.

After  the following line,

#include<linux/autoconf.h>

Insert this line,

/*


Then go down to the following line,

#endif
*/           (insert the asterisk forward slash here)

#ifdef AGPART

(file continues on without further addition)

Once this change is made to the os-agpconfig.h file, type make<ENTER> to 
properly compile the kernel driver.  Then install the nvidia glx 9.5 
driver.  I have used this aand it works fine.  You do not need to go to 
Xfree86 4.02.

Good luck.



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

Date: Fri, 22 Dec 2000 20:43:11 +0100
From: Michael Heiming <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: How to call 'stty' from inittab?

Hello,

don't know what you want to do with it...

I have set it up like this:

S0:123:respawn:/sbin/agetty -L 9600 ttyS0

This way a can login using my HP 48 GX Calculator, which has a progam
installed
that emulates
VT52 terminal.

Really cool, if someone has never seen this, that your are able to login
from
this small calculator....:-)
And it can help you to avoid those nasty hard reboot, if there is no way
getting in the machine....

man inittab has lots of info....

Good luck

Michael Heiming
Sysadmin
"Thank god it's friday today!"


"Scott M. Navarre" wrote:

> Hello,
>
>   During my searches through the linux sites, I came across an example which
> ran 'stty' from /etc/inittab.  Well, I lost track of where I found this and
> cannot for the life of me find it again.  I would like to know how to do
> this and also if it is a good idea to do it here rather than in an init
> script such as rc.local.
>
>   From what I remember, the format was something like this:
> m0::bootwait:/bin/stty {options} ttyS0
>
>   Is this correct?  Or should the {options} come after the "ttyS0", or what?
>
> Thanks in advance for helping me straighten this out,
>   Scott Navarre

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

From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: Updating Linux causes previous working script files to error out
Date: Fri, 22 Dec 2000 16:51:07 +0100

Jeff Pierce <[EMAIL PROTECTED]> wrote:
> the script is:
> #!/bin/sh
> if [ -f /etc/ppp/stay ] ; then
>  if [ -f /var/run/ppp0.pid ] ; then
>   ping -c4 -l3 preferred.com 2>&1 | grep "0 packets" > /dev/null && \
>   { /usr/sbin/ppp-off > /dev/null 2>&1 ; sleep 2 ; /usr/sbin/ppp-on2 }
>  else
>   /usr/sbin/ppp-on2
>  fi
> fi

> The error is 'unexpected token "else" in line 6'
> The else of the if? Huh?

Yes, this is an error introduced by bash 2. Use bash 1 to get proper
functionality. COmplain.

(you need a semi-colon now at the end of a list  in braces).

> Out of deseration I changed the "{}"'s to "()"'s in the previous line,
> since they do the same thing.

> That fixed the problem!!!!

Yes.

> Ok, the problem is fixed. The question remains what caused the error in
> this installations version of bash, /sbin/sh linked to bash, to begin

come, come .. I can figure it out. You  can too.

> with? The "{}" are LEGAL for grouping commands together. Pages 265-266

Absolutely. And do the elements have a separator or a terminator?
I.e. is it 

  OBRACE [ { elem SEMI }* elem ] CBRACE

in the grammar, or is it

  OBRACE { elem SEMI }* CBRACE

?

> of the infamous Hayden books "UNIX Shell Programming" second edition.
> Plus, it worked previously......

> Second, how do you find out the bash version installed?

You go "man bash", which tells you how to find out the bash version.


Peter

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

From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: Updating Linux causes previous working script files to error out
Date: Fri, 22 Dec 2000 17:48:39 +0100

Paul Kimoto <[EMAIL PROTECTED]> wrote:
> In article <[EMAIL PROTECTED]>, Jeff Pierce wrote:
>> #!/bin/sh
>> if [ -f /etc/ppp/stay ] ; then
>> if [ -f /var/run/ppp0.pid ] ; then
>>   ping -c4 -l3 preferred.com 2>&1 | grep "0 packets" > /dev/null && \
>>    { /usr/sbin/ppp-off > /dev/null 2>&1 ; sleep 2 ; /usr/sbin/ppp-on2 }
>>  else
>>   /usr/sbin/ppp-on2
>>  fi
>> fi
>>
>> The error is 'unexpected token "else" in line 6'
>> The else of the if? Huh?
>>
>> Out of des[p]eration I changed the "{}"'s to "()"'s in the previous line,
>> since they do the same thing.

> (No, "()" runs the enclosed commands in a subshell.)

I believe a pipeline is necessarily run in a subshell if any of the
elements are not shell builtins (or something convoluted similar to
that).  Or at least I have encountered instances of behaviour where that
is the only possible conclusion as to the semantics.

> The bash(1) man page says:

You mean bash2(1) !

> :        { list; }
> :               list  is simply executed in the current shell envi-
> :               ronment.  list must be terminated with a newline or
> :               semicolon.

> Kernighan and Pike (p. 169) says:

> : The characters <{> and <}> are like <do> and <done>--they have special
> : meaning only if they follow a semi-colon, newline, or other command
> : terminator.

>> Second, how do you find out the bash version installed?

> Try
> $ /path/to/bash -version -c ""
> or
> $ echo $BASH_VERSION
> (inside the shell).
Peter

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

From: "Benjamin" <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux,linux.redhat,linux.sources.kernel
Subject: Re: Kernel parameters
Date: Fri, 22 Dec 2000 12:07:13 -0800


"Stefano Ghirlanda" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> "Nils Magnus Eide Englund" <[EMAIL PROTECTED]> writes:
>
> > > You can set where the kern.* messages go in syslog.conf, see man
> > > syslogd. No kernel parameters needed.
> >
> > Well... I've managed the syslogd part, but I still don't know
> > how to hide the kernel messages at bootup, before the root fs
> > is mounted. Any ideas?
>
> I don't know how to do that, but why do you need it? Just curious.
>
> --
> Stefano



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


** 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 by posting to comp.os.linux.misc.

Linux may be obtained via one of these FTP sites:
    ftp.funet.fi                                pub/Linux
    tsx-11.mit.edu                              pub/linux
    sunsite.unc.edu                             pub/Linux

End of Linux-Misc Digest
******************************

Reply via email to