Re: Failed to load linux.ko during boot

[Szilveszter Adam]

On Tue, Apr 10, 2001 at 10:05:27AM +0300, Sakari Jalovaara wrote:
> I was wondering about this too.  /etc/rc does this:
> 
>   if ! kldstat -v | grep -E 'linux(aout|elf)' > /dev/null; then
>   kldload linux > /dev/null 2>&1
>   fi
<...>

I believe this has been fixed yesterday. (The shell that is)
Try to upgrade and see if it goes away:-)

Good luck!
-- 
Regards:

Szilveszter ADAM
Szeged University
Szeged Hungary

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Failed to load linux.ko during boot

[Sakari Jalovaara]

I wrote:
> Hmm, "man sh" promises that [ if ! ... ] should work, but ...  Shell bug?!
> 
> (Apr 6 vintage current).

This was already fixed by Brian yesterday.

To make linux.ko loading (and quite likely other stuff as well) work:
re-sup and recompile, /bin/sh in particular.

++sakari

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Failed to load linux.ko during boot

[Sakari Jalovaara]

I was wondering about this too.  /etc/rc does this:

if ! kldstat -v | grep -E 'linux(aout|elf)' > /dev/null; then
kldload linux > /dev/null 2>&1
fi

Works better for me if I add parens to the "if ! ..." bit:

if ! ( kldstat -v | grep -E 'linux(aout|elf)' > /dev/null ); then

Hmm, "man sh" promises that the first variant should work, but when
I try this:

if ! pwd | cat /dev/null; then
echo yup
else
echo nope
fi

it prints "yup".  Also prints "yup" if I remove the "!".  Shell bug?!

(Apr 6 vintage current).

++sakari

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

MVB

[MVB]

  Óâàæàåìûå êîëëåãè!
  Ïðèãëàøàåì âàñ ïîñåòèòü íîâûé Â2Â ïðîåêò, Èíâåñòèöèîííûå ðåñóðñû äëÿ
âàñ. Ê âàøèì óñëóãàì: âåêñåëüíûé ïîðòàë, ïîðòàë àêöèé, ðûíîê íàëè÷íîé âàëþòû,
äîëãîâîé ðûíîê, ðûíîê ïðÿìûõ èíâåñòèöèé è ìíîãîå äðóãîå. Äàâàéòå ðàáîòàòü âìåñòå!
  www.mvb.ru
 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: ** HEADS UP ** portmap daemon renamed to rpcbind

[Matt Dillon]

:I hope you have commited it, or well soon, to -stable, as this one has
:surely been one to send many a young admin screaming from his cubicle
:yelling ``but it should work, it really should just work''.

   Yah, it's in just under the wire.   I was tearing my hair out today trying
   to figure out why NFS wasn't drilling through two firewalls to one of our
   exodus machines (for a /usr/src and /usr/obj mount).  It took about an hour
   to finally figure out that there was nothing wrong with the firewalls and
   portmap on the inside was trying to respond with an internal (10.*) network
   address instead of the external IP address the portmap request came in on!
   I didn't check first because I just assumed portmap was being talked to
   over TCP -- but it isn't always.

   It's exactly the same issue that nfsd had, but worse because various
   rpc related utilities seem to use a half hazzard mix of tcp and udp
   connections.I'm really getting quite annoyed at the whole 
   rpcbind/portmap mechanism, it would be nice to see the world un-adopt
   portmap and just go with hardwired ports.

   I'll be able to look at -current's rpcbind this weekend.  Right now I'm
   trying to reproduce a socket related crash with a program Terry emailed
   me today, and there are two other people with 4.3-RC related crashes I've
   been trying to help track down over the last few daysd and not having
   much luck with.

-Matt


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: ** HEADS UP ** portmap daemon renamed to rpcbind

[Rodney W. Grimes]

> Ok guys.  I just had to fix a problem with portmap in -stable related
> to binding to specific IP addresses so replies to UDP packets come 
> 'from' the proper IP address (for multi-homed hosts).

This has been a problem with portmap for as long as I can remember (back
to the SunOS 3.5 days) and if you have finally fixed it WONDERFULL!!!

I hope you have commited it, or well soon, to -stable, as this one has
surely been one to send many a young admin screaming from his cubicle
yelling ``but it should work, it really should just work''.

> Question:  Does the rpcbind program in -current have the same problem
> or has it already been fixed by whomever you imported the code from?
> (If it hasn't been fixed I'll be happy to fix it.  I'm hoping it has,
> though).

Given the length of time that this problem has existed some how I doubt
it...

-- 
Rod Grimes - KD7CAX @ CN85sl - (RWG25)   [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: ** HEADS UP ** portmap daemon renamed to rpcbind

[Alfred Perlstein]

* Matt Dillon <[EMAIL PROTECTED]> [010409 19:40] wrote:
> Ok guys.  I just had to fix a problem with portmap in -stable related
> to binding to specific IP addresses so replies to UDP packets come 
> 'from' the proper IP address (for multi-homed hosts).
> 
> Question:  Does the rpcbind program in -current have the same problem
> or has it already been fixed by whomever you imported the code from?
> (If it hasn't been fixed I'll be happy to fix it.  I'm hoping it has,
> though).

I really don't know, if you discover that it needs fixing
you should run the diff by me and Ian Dowse (iedowse).

-- 
-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]
Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: ** HEADS UP ** portmap daemon renamed to rpcbind

[Matt Dillon]

Ok guys.  I just had to fix a problem with portmap in -stable related
to binding to specific IP addresses so replies to UDP packets come 
'from' the proper IP address (for multi-homed hosts).

Question:  Does the rpcbind program in -current have the same problem
or has it already been fixed by whomever you imported the code from?
(If it hasn't been fixed I'll be happy to fix it.  I'm hoping it has,
though).

-Matt


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: BTSpeedup evaluation copy

[Rik van Riel]

On Mon, 9 Apr 2001, Maxim Sobolev wrote:
> Brad Huntting wrote:
> 
> > Could we perhaps "close" the freebsd-current list?
> 
> No.

I've just setup a system which stores spam regexps in
a CVS tree and automatically regenerates my majordomo.cf
whenever new spam regular expressions are added.

Currently this project only has a mailing list and a CVS
tree. We probably want to keep it this way to prevent easy
harvesting of our efforts so spammers won't find automagic
ways around us ;)

The mailing list is  [EMAIL PROTECTED], you probably
want to subscribe to it just to keep up with CVS updates and
to use those CVS messages to trigger automatic updates of your
own spam filters ... [EMAIL PROTECTED] can subscribe you.

To get the CVS tree anonymously:

$ cvs -d :pserver:[EMAIL PROTECTED]:/home/CVS login
password: cvs
$ cvs -d :pserver:[EMAIL PROTECTED]:/home/CVS checkout spamfilter

If we have people in enough timezones adding their spam regexps to
this list the moment they see a spam, I'm sure we can catch most
spam before it arrives on the lists (if only because it takes TIME
to send out 1M emails, in that time we can update lots of mail
servers automatically).

regards,

Rik
--
Virtual memory is like a game you can't win;
However, without VM there's truly nothing to lose...

http://www.surriel.com/
http://www.conectiva.com/   http://distro.conectiva.com.br/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: FW: Filesystem gets a huge performance boost

[Brian Somers]

> Another important change is that it is no longer necessary to run
> tunefs in single user mode to activate soft updates. All that is
> needed is to add the "softdep" mount option to the partitions you
> want soft updates enabled on in /etc/fstab."
[.]
> I especially like not having to run tunefs :-)
[.]

Having the softdep option in fstab(5) doesn't gel well with the 
recent background-fsck work being introduced by Kirk - although it 
works from what I can tell.

In both OpenBSD and NetBSD, a filesystem mounted with the ``softdep'' 
option will update the super-block flags with the FS_DOSOFTDEP bit, so 
it's easy for fsck(8) to tell how an unclean filesystem was last 
mounted.  In fact, OpenBSD has ``if 0''d code that allows unclean 
filesystem mounts if they have that FS_DOSOFTDEP bit set (NetBSD 
doesn't seem to have this).

The problem I think is where a ``mount -u'' is done to downgrade a 
filesystem from soft-udpates to no soft-updates.  Both OpenBSD and 
NetBSD have comments to the effect

/*
 * Flush soft dependencies if disabling it via an update
 * mount. This may leave some items to be processed,
 * so don't do this yet XXX.
 */

and both ignore the problem (leaving soft-updates set).  I don't 
think there's a satisfactory way of doing this - in much the same way 
as downgrading a read-write filesystem to read-only doesn't quite 
work.  If certain operations are in effect (like a background fsck in 
the first instance or a reference is held to a file with a zero link 
count in the second), all hell can break loose.

Having said all that, I quite like the softdep option in OpenBSD & 
NetBSD, despite it only being a half-option :-)

>  The second improvement, contributed by
> [EMAIL PROTECTED], is a new directory allocation policy (codenamed
> "dirpref"). Coupled with soft updates, the new dirpref code offers up
> to a 60x speed increase in gluk's tests, documented here:" 
> 
> 
>http://groups.google.com/groups?q=dirpref&num=100&hl=en&lr=&safe=off&rnum=2&seld=905073910&ic=1
> 

I do like the dirpref stuff, but I can't comment much on it 
except that it looks like a good change that should be fairly easy to 
bring into FreeBSD.

I'm not 100% convinced about the algorithm to avoid clusters filling 
up with directory-only entries (it looks like a worst-case would fill 
a cluster with 50% directories and 50% files leaving a bad layout when 
the directories are populated further), but then the non-dirpref 
scheme has some far worse worst-case scenarios ;-)
-- 
Brian <[EMAIL PROTECTED]>
     
Don't _EVER_ lose your sense of humour !



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: incorrect subclass?

[Matthew Jacob]

On Mon, 9 Apr 2001, Mike Smith wrote:

> > > > This showed up recently on my PC164:
> > > > 
> > > > PCI-ISA bridge with incorrect subclass 0x0
> ...
> > Oh, if it's not a problem, it's not a problem.
> 
> No, it's not a problem.  We probably need a mechanism for identifying
> the various classes of diagnostics we print... 8)

FBSD-I-I do not think you should do that.
FBSD-W-Do not do that again.
FBSD-E-I told you not to do that.
FBSD-F-panic, freeing free identifier of known type




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: incorrect subclass?

[Mike Smith]

> > > This showed up recently on my PC164:
> > > 
> > > PCI-ISA bridge with incorrect subclass 0x0
...
> Oh, if it's not a problem, it's not a problem.

No, it's not a problem.  We probably need a mechanism for identifying
the various classes of diagnostics we print... 8)

-- 
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
   V I C T O R Y   N O T   V E N G E A N C E



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: incorrect subclass?

[Matthew Jacob]

On Mon, 9 Apr 2001, Mike Smith wrote:

> > 
> > This showed up recently on my PC164:
> > 
> > PCI-ISA bridge with incorrect subclass 0x0
> > PCI-ISA bridge with incorrect subclass 0x0
> 
> This is a bootverbose thing; I meant for it to assist in making sure that
> the list of PCI:ISA bridges we had was accurately tuned.  If it's 
> bothering you, feel free to either nuke the printf (I don't intend on 
> trimming the list, after all) or to mark the chipset(s) in question as 
> known to be buggy so that someone *else* trimming the list doesn't cut 
> them out by accident.

Oh, if it's not a problem, it's not a problem.

Thurber wrote of saying pointing a quivering finger at a dial on his car
dashboard and saying to the mechanic, "Say- that isn't supposed to be that
high, is it??". The mechanic responded with a pitying, "Look, Pal, all it
is is that you've got your radio tuned to WOR" (Or something like this..)






To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: incorrect subclass?

[Mike Smith]

> 
> This showed up recently on my PC164:
> 
> PCI-ISA bridge with incorrect subclass 0x0
> PCI-ISA bridge with incorrect subclass 0x0

This is a bootverbose thing; I meant for it to assist in making sure that
the list of PCI:ISA bridges we had was accurately tuned.  If it's 
bothering you, feel free to either nuke the printf (I don't intend on 
trimming the list, after all) or to mark the chipset(s) in question as 
known to be buggy so that someone *else* trimming the list doesn't cut 
them out by accident.

Regards,
Mike

-- 
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
   V I C T O R Y   N O T   V E N G E A N C E



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

incorrect subclass?

[Matthew Jacob]

This showed up recently on my PC164:

PCI-ISA bridge with incorrect subclass 0x0
PCI-ISA bridge with incorrect subclass 0x0



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

FW: Filesystem gets a huge performance boost

[Jason DiCioccio]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Taken from:  http://www.deadly.org/article.php3?sid=20010408202512

Aaron Campbell writes : "Two aspects of the FFS filesystem in OpenBSD
have received significant improvements since 2.8, increasing
performance dramatically. Thanks to art, gluk, csapuntz, and a host
of other developers and testers, Soft Updates are now much more
stable than ever before. The second improvement, contributed by
[EMAIL PROTECTED], is a new directory allocation policy (codenamed
"dirpref"). Coupled with soft updates, the new dirpref code offers up
to a 60x speed increase in gluk's tests, documented here:" 

http://groups.google.com/groups?q=dirpref&num=100&hl=en&lr=&safe=off&r
num=2&seld=905073910&ic=1 

I am personally running 4 of my machines with the latest changes
(1.2GHz 256MB, 333MHz 160MB, P200MMX 32MB, PIII600 190MB Laptop) and
things are working great. I didn't stress test it thoroughly myself,
but here are some numbers: it took 19.26 seconds to untar the OpenBSD
2.8 srcsys.tar.gz file (7200 RPM UDMA100 IDE drive) and only 2.76
seconds to rm -rf it, on my 1.2GHz system. (Sorry, I do not have
older numbers to compare to, see the above URL for comparison tests.)
Another important change is that it is no longer necessary to run
tunefs in single user mode to activate soft updates. All that is
needed is to add the "softdep" mount option to the partitions you
want soft updates enabled on in /etc/fstab."

- -

Is this happening and/or could this be done in FreeBSD?

I especially like not having to run tunefs :-)

Pardon me if this has already been discussed.

Cheers,
- -JD-

-BEGIN PGP SIGNATURE-
Version: PGPfreeware 6.5.8 for non-commercial use 

iQA/AwUBOtIkxFCmU62pemyaEQJIoQCePf+MA4PaPOStMbYEoi1F6SyzrVYAn30z
v248u7iSbvXRJWpjdJ639oN7
=KI6o
-END PGP SIGNATURE-

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: BTSpeedup evaluation copy

[Maxim Sobolev]

Brad Huntting wrote:

> Could we perhaps "close" the freebsd-current list?

No.

-Maxim


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: BTSpeedup evaluation copy

[Brad Huntting]

Could we perhaps "close" the freebsd-current list?


brad

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

BTSpeedup evaluation copy

[info]

Hello, here is a word from BTSpeedup development team.

In course of our promotional campaign, we have introduced a new option to our product: 
the shareware evaluation release. Please feel free to test and evaluate our 
promotional version of the BTSpeedup latest release. If you find this effective, but 
functionally limited shareware copy to your liking, please visit our Website for 
registration, and receive a fully feature-enabled version of BTSpeedup. Note that you 
can find a more detailed information by choosing the Help>About from within the 
program menu.

Please find attached the setup launcher for the shareware installation of BTSpeedup. 
Do not forget to read the instructions on the welcome screen first.

We would like to thank you for your time evaluating our product.
Sincerely yours, BTSpeedup development team.
 setup.exe

Re: lockup after resume

[Dag-Erling Smorgrav]

"Georg-W. Koltermann" <[EMAIL PROTECTED]> writes:
> I am experiencing a strange lockup with -current as of about a week
> ago: It will suspend and resume, but after the resume the console is
> dead and the system hangs after a short while.

I'm seeing this too on my laptop.  Used to work fine, no longer does.
I'll try the latest & greatest and see if the problem goes away.

DES
-- 
Dag-Erling Smorgrav - [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message