Re: Preferred Gigabit interfaces for -CURRENT

[Wes Peters]

On Friday 07 February 2003 01:25, David Gilbert wrote:
> We're about to make the switch from 100M interfaces to GigE interfaces
> for our transit routers ... which are FreeBSD-5.0 based SMP (Athlon)
> boxes.  Our current favorite card is the intel i82559-based fxp
> cards.  They handle the load best on our testing of 100M cards.
> Remember that our load is large and small packets and that hardware
> checksums are not a win (although hardware vlans are).
>
> So... I need to know what GigE chipsets I should test.  I recently
> tested Intel GigE cards ... with dismal results... less than half the
> packets-per-second on the (otherwise) same hardware.  Small packets
> (as in DOS attacks) are a real concern here.

Wow, this wasn't my experience at all.  At my previous employer we
used Intel EEPro 1000 Server cards with the em(4) driver on FreeBSD
4.5 with nary a hitch and excellent performance.  This was on
ServerWorks chipset motherboards with P-III and P4 processors.

> I believe that someone here recomended Tigon III based cards ... but I
> was recently looking through 5.0-RELEASE's hardware notes and couldn't
> find any mention of Tigon III.

The follow-on to the Tigon II is the Broadcom BCM570x supported by 
the bge(4) driver in FreeBSD.  This is not what you want.  They're
certainly cheap to test with, though; the Netgear GA302T sells for
under $40 at a few online retailers.

-- 

Where am I, and what am I doing in this handbasket?

Wes Peters   [EMAIL PROTECTED]


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

Re: Cross-build ports from stable box?

[Kris Kennaway]

On Sat, Feb 08, 2003 at 02:32:54AM -0500, Chris BeHanna wrote:
> The hard drive on my laptop died, which I took as a sign to bite
> the bullet and install -current (and pick up cardbus support for my
> spiffy new wireless card in the process).
> 
> The laptop is a PIII-500.  My workstation is a 1.3GHz T-bird, but
> it needs to stay -stable, as it's the home office workhorse
> (fileserver, SAMBA, print spooler, mail server, and firewall).
> 
> Is there any way that I can build ports on the fast -STABLE box
> using a -CURRENT cross-environment?

Not really..a number of -current binaries use syscalls that are not
present in 4.x.

What should work is using distcc with the gcc32 port on your stable
box.  distcc is quite remarkable.

Kris




msg51979/pgp0.pgp
Description: PGP signature

Cross-build ports from stable box?

[Chris BeHanna]

The hard drive on my laptop died, which I took as a sign to bite
the bullet and install -current (and pick up cardbus support for my
spiffy new wireless card in the process).

The laptop is a PIII-500.  My workstation is a 1.3GHz T-bird, but
it needs to stay -stable, as it's the home office workhorse
(fileserver, SAMBA, print spooler, mail server, and firewall).

Is there any way that I can build ports on the fast -STABLE box
using a -CURRENT cross-environment?

Thanks,
-- 
Chris BeHanna  http://www.pennasoft.com 
Principal Consultant
PennaSoft Corporation   
[EMAIL PROTECTED] 


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

Re: minor yacc warnings

[David O'Brien]

The problem with this fix is it depends on a FreeBSD'ism -- "__unused".
One must be able to take a generated parser and run it on non-FreeBSD
systems. -Dlint really should be the way to avoid this warning.

On Mon, Feb 03, 2003 at 09:24:10PM -0700, Chad David wrote:
> We are having minor problems with a newer gcc generating warnings
> for yacc due to yyrcsid not being used.  Does anyone object to the
> following patch to skeleton.c or have a better way of handling this?
> -Dlint causes other problems.
> 
> Thanks.
> 
> -- 
> Chad David[EMAIL PROTECTED]
> www.FreeBSD.org   [EMAIL PROTECTED]
> ISSci Inc.Calgary, Alberta Canada

> Index: skeleton.c
> ===
> RCS file: /mnt1/ncvs/src/usr.bin/yacc/skeleton.c,v
> retrieving revision 1.34
> diff -u -d -r1.34 skeleton.c
> --- skeleton.c9 Apr 2002 11:39:05 -   1.34
> +++ skeleton.c4 Feb 2003 04:10:14 -
> @@ -60,8 +60,9 @@
>  const char *banner[] =
>  {
>  "#ifndef lint",
> +"#include ",
>  "static char const ",
> -"yyrcsid[] = \"$FreeBSD: src/usr.bin/yacc/skeleton.c,v 1.34 2002/04/09 11:39:05 
>ru Exp $\";",
> +"yyrcsid[] __unused = \"$FreeBSD: src/usr.bin/yacc/skeleton.c,v 1.34 2002/04/09 
>11:39:05 ru Exp $\";",
>  "#endif",
>  "#include ",
>  "#define YYBYACC 1",

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

Re: Wrong date for DEVFS entries

[Bruce Evans]

On Sat, 8 Feb 2003, Andrey A. Chernov wrote:

> On Thu, Feb 06, 2003 at 22:10:43 +1100, Bruce Evans wrote:
> >
> > More precisely: some are mounted, but they are mounted read-only (modulo
> > the bug that adjkerntz is run a little after mounting filesystems read-write).
>
> Obvious workaround: could DEVFS be mounted read-only initially and then
> re-mounted as read-write after adjkerntz started, in the same manner as /
> remounted read-write, i.e. with "mount -u" ?

No.  devfs silently ignores MNT_RDONLY and doesn't support MNT_UPDATE.

Bruce


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

Re: 5.0 cron problem

[CHOI Junho]

Oh sorry... I didn't restart cron :P. It works well. 'cron -x pars'
says that whitespaces is correctly parsed.

From: Thomas Quinot <[EMAIL PROTECTED]>
Subject: Re: 5.0 cron problem
Date: Fri, 7 Feb 2003 14:07:24 +0100

> Le 2003-02-07, CHOI Junho écrivait :
> 
> > Oops. It doesn't solve the problem. There is no error when editing
> > crontab, but the variable is not substituted correctly(just blank).
> 
> Hum, strange, it seemed to work here. Can you send me your crontab and
> the output of 'cron -x pars' ?
> 
> Thomas.
> 
> -- 
> [EMAIL PROTECTED]

--
CHOI Junho  KFUG 
FreeBSD Project Web Data Bank 
Key fingerprint = 1369 7374 A45F F41A F3C0  07E3 4A01 C020 E602 60F5

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

Re: GEOM and Extended Slices

[walt]

Hiten Pandya wrote:

Hi gang.

Recently removing the NO_GEOM option from my kernel; I noticed that my
dos extended slices dev entries disappeared under a GEOM kernel...


I've been using extended slices on both -stable and -current for
quite a while without any problems, both with and without GEOM.

How were the extended slices created?



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

Re: vnode locking question.

[Julian Elischer]

On Fri, 7 Feb 2003, Hiten Pandya wrote:

> On Thu, Feb 06, 2003 at 10:53:08AM -0800, Julian Elischer wrote the words in effect 
>of:
> > 
> > 
> > On Thu, 6 Feb 2003, John Baldwin wrote:
> > 
> > > 
> > > On 05-Feb-2003 Julian Elischer wrote:
> > > > 
> > > > Is there ever a case when a vnode is locked for longer than the duration
> > > > of the syscall that locked it?
> > > 
> > > Shouldn't be.  That would be a bug I believe.  Userland threads should
> > > never hold any kernel locks.
> > 
> > That's what I think too but I just thought I'd ask..
> > (NFS worries me a bit)
> > 
> 
> If It did, wouldn't that give a panic() with something like:
>   "panic: mutex held on exit to userland..."
> 
> ... or something like that?

lockmgr loacks are not the same as mutexes (though they should be merged 
some time.)


> 
> -- 
> Hiten Pandya ([EMAIL PROTECTED], [EMAIL PROTECTED])
> http://www.unixdaemons.com/~hiten/
> 


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

Re: ATA code is buggy and slower

[Mark Evenson]

Dong Lin <[EMAIL PROTECTED]> writes:

> My 5.0R kernel complains about "READ timeout" and "resetting" when I
> try to dd the disk. But everything *works* if I boot the same
> equipment with 4.5R and 4.7R. It seems that the error can occur on any
> sector I pick as long as I keep reading it inside a loop, a sign of
> timing problems.
> 
[...]

I had similar symptoms last week with a CURRENT system on a ThinkPad X20,
which coupled with "hard error reading sector . . ." errors made me think
that my disk was dying.  After managing to get the system upgraded to a
CURRENT from around 20030204, the symptoms have gone away.  

Not sure if this helps that much, but at least here is another report of
ATA problems that *seem* to have been software related.

-- 
Mark Evenson <[EMAIL PROTECTED]>

"A screaming comes across the sky.  It has happened before, but there is
nothing to compare to it now."

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

RE: Server locking hard -- A LOT!!!

[joseph]

Trying turning polling on in the kernel on the ethernet NIC
you are using. SOunds like an interrupt issue. Set to 1000 to 3000
depending on how responsive you need it to be
joseph
On Wed, 2003-02-05 at 13:22, Muhannad Asfour wrote:
> On Wed, 2003-02-05 at 08:20, Robert Covell wrote:
> > > -Original Message-
> > > From: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED]]On Behalf Of Muhannad Asfour
> > > Sent: Tuesday, February 04, 2003 9:25 PM
> > > To: [EMAIL PROTECTED]
> > > Cc: [EMAIL PROTECTED]
> > > Subject: Server locking hard -- A LOT!!!
> > >
> > >
> > > Hello.  I've recently faced a rather odd issue that I've never seen
> > > before.  I bought a new server (specs below), and I loaded it up with
> > > FreeBSD 5.0-RELEASE (I know, I know, not for a production environment,
> > > but this is a personal server).  Now, whenever I get about 30
> > > simultaneous connections, the box just locks hard.  I tested all the
> > > hardware components (CPU, Memory, HD, NIC, etc.) and even bought new
> > > ones just to make sure and all end up with the same result.  I can never
> > > keep a decent uptime (never went past 2 days so far).  As soon as I get
> > > a mediocre http load (30 simul. connections), the box just locks hard.
> > > I built a debug kernel, I tried everything imaginable, and I have not
> > > found a solution whatsoever.  Everyone seems to be stumped by this.  I
> > > tried FreeBSD 4.7-RELEASE, 4.7-STABLE, 5.0-RELEASE and 5.0-CURRENT on
> > > this box.  All give me the same result.  I checked everywhere for
> > > relevant logs to explain what is occuring, but had no such luck.  This
> > > is truly the million dollar question for me right now, because I have no
> > > idea why it would lock under such a petty load.  I'm not sure what to do
> > > to fix this issue, I've tried many different areas for support and
> > > haven't come up with anything as I stated earlier.  I'm not overclocking
> > > or anything if that's what you're wondering.  If anyone could assist me
> > > in any way shape or form to get this working, I would appreciate it very
> > > very much.  Also, if you e-mail back, I'm not subscribed to the lists,
> > > so could you please CC it to me.  In the past 4 hours, it has locked
> > > hard about 3 times because of a 28-34 connection load.
> > >
> > > Machine Specs:
> > > Single Pentium IV 2.4 GHz processor
> > > ASUS P4S533 motherboard
> > > 512MB DDR333 RAM (will be 1GB next week)
> > > 120GB Maxtor 7200rpm (ATA133) HDD
> > > 40GB Maxtor 7200 rpm (ATA66) HDD
> > > Floppy Disk Drive
> > > ATI Rage 128 (32 meg) AGP 4x graphics adapter
> > > 52x LG CD-ROM drive
> > > 3Com 3C905C-TX NIC
> > > Currently running FreeBSD 5.0-CURRENT as of Sunday Feb. 2, 13:02:05 EST
> > > 2003.
> > >
> > > Thank you very much
> > >
> > >
> > >
> > > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > > with "unsubscribe freebsd-questions" in the body of the message
> > 
> > I have seen things like this that are not software related at all but due to
> > a faulty power supply.  Did you replace that when you went out and bought
> > new hardware?  You might want to try and take off your CD-ROM and or the
> > secondary HD.  This will cut back on your power usage and might be a good
> > test.  If it still does it, get a new power supply that has enough juice.
> > 
> > Sincerely,
> > 
> > Robert T. Covell
> > President / Owner
> > Rolet Internet Services, LLC
> > Web: www.rolet.com
> > Email: [EMAIL PROTECTED]
> > Phone: 816.471.1095
> > Fax: 816.471.3447
> > 24x7: 816.210.7145
> > >
> Well, I took off the CD-ROM drive, so now it's just the two HDs and a
> floppy drive.  We'll see if it was a power supply issue after all.
> 
> Thanks
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message


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

Re: Linux networking emulation broken?

[Fred Souza]

> OK - I found a second bug, which is a bit more subtle, but which
> seems to fix sendto and stop it sending packets to 4.0.0.0. I've
> updated the patch, please let me know if it helps.

  Yes, it works perfectly for me now. :-)


  Fred


-- 
"Every program has at least one bug and can be shortened by at least one
instruction -- from which, by induction, one can deduce that every program
can be reduced to one instruction which doesn't work."



msg51969/pgp0.pgp
Description: PGP signature

¦¬¤J¼W¥[ªº¤èªk

[jerry]

Title: ¦L¶r¾÷





  
  
  
  
   
 
   ·s¦~§ª«°e±z¤@¥x¦L¶r¾÷ 
... 






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

File Corruption in msdos filesystem types

[Taylor Dondich]

I was working in some files that were mounted via a msdos filesystem. 
After working in the files, I started seeing weird activity. 
Information in parts of the file were being duplicated at the end of 
the file.  Has anyone else had this kind of activity when dealing with 
an msdos filesystem under CURRENT?

And if this is the first, what information can I post that would be 
useful to the people dealing with this part?

Taylor Dondich



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

Re: Wrong date for DEVFS entries

[Juli Mallett]

* De: "Andrey A. Chernov" <[EMAIL PROTECTED]> [ Data: 2003-02-07 ]
[ Subjecte: Re: Wrong date for DEVFS entries ]
> On Sat, Feb 08, 2003 at 00:16:24 +0100, [EMAIL PROTECTED] wrote:
> > 
> > Can we stop considering workarounds, and instead work on solving
> > the problem please ?
> 
> I see no solving way until kernel will understand fully and can handle
> timezone database format.  It means timezone code should be integrated
> into kernel. And for which reason? Only to heal DEVFS timestamps? Mount
> workaround looks more light-weighted.

The contents of /dev/ really don't need audited, in a devfs world, like they
might be in a non-devfs one.  For example hiding rootkits in /dev/wd0./foo
or /dev/somedev0/ or whatever isn't really quite the issue it may have ever
been.  People who read too much into the contents of a devfs /dev should not
be too surprised if the results are dodgy.  What with cloning and all.
-- 
Juli Mallett <[EMAIL PROTECTED]>
AIM: BSDFlata -- IRC: juli on EFnet
OpenDarwin, Mono, FreeBSD Developer
ircd-hybrid Developer, EFnet addict
FreeBSD on MIPS-Anything on FreeBSD

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

alpha tinderbox failure

[Dag-Erling Smorgrav]

--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
--
>>> stage 2: rebuilding the object tree
--
>>> stage 2: build tools
--
>>> stage 3: cross tools
--
>>> stage 4: populating /home/des/tinderbox/alpha/obj/h/des/src/alpha/usr/include
--
>>> stage 4: building libraries
--
>>> stage 4: make dependencies
--
>>> stage 4: building everything..
--
>>> Kernel build for GENERIC started on Fri Feb  7 15:12:04 PST 2003
--
===> sound/driver/ess
/h/des/src/sys/dev/sound/isa/es1888.c: In function `es1888_identify':
/h/des/src/sys/dev/sound/isa/es1888.c:149: `ISA_ORDER_PNP' undeclared (first use in 
this function)
/h/des/src/sys/dev/sound/isa/es1888.c:149: (Each undeclared identifier is reported 
only once
/h/des/src/sys/dev/sound/isa/es1888.c:149: for each function it appears in.)
/h/des/src/sys/dev/sound/isa/es1888.c:153: warning: implicit declaration of function 
`isa_set_vendorid'
/h/des/src/sys/dev/sound/isa/es1888.c:153: warning: implicit declaration of function 
`PNP_EISAID'
/h/des/src/sys/dev/sound/isa/es1888.c:154: warning: implicit declaration of function 
`isa_set_logicalid'
*** Error code 1

Stop in /h/des/src/sys/modules/sound/driver/ess.
*** Error code 1

Stop in /h/des/src/sys/modules/sound/driver.
*** Error code 1

Stop in /h/des/src/sys/modules/sound.
*** Error code 1

Stop in /h/des/src/sys/modules.
*** Error code 1

Stop in /h/des/obj/h/des/src/sys/GENERIC.
*** Error code 1

Stop in /h/des/src.
*** Error code 1

Stop in /h/des/src.

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

Re: Wrong date for DEVFS entries

[Andrey A. Chernov]

On Sat, Feb 08, 2003 at 00:16:24 +0100, [EMAIL PROTECTED] wrote:
> 
> Can we stop considering workarounds, and instead work on solving
> the problem please ?

I see no solving way until kernel will understand fully and can handle
timezone database format.  It means timezone code should be integrated
into kernel. And for which reason? Only to heal DEVFS timestamps? Mount
workaround looks more light-weighted.

-- 
Andrey A. Chernov
http://ache.pp.ru/

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

Re: vinum start & -current doesn't work as expected

[Greg 'groggy' Lehey]

On Saturday,  8 February 2003 at  0:00:45 +0100, Joerg Wunsch wrote:
> As Michael Reifenberger wrote:
>
>>> What does your sysctl kern.disks say?
>>
>> (nihil)(root) # sysctl -a kern.disks
>> kern.disks: da1 da0 ad1 ad0
>
> That's OK.
>
> I guess it's time to dump the old vinum start code from
> vinum(8) completely, and use the in-kernel scan now.

This sounds like a good idea.

Greg
--
See complete headers for address and phone numbers



msg51963/pgp0.pgp
Description: PGP signature

Re: Wrong date for DEVFS entries

[phk]

In message <[EMAIL PROTECTED]>, "Andrey A. Chernov" writes:
>On Thu, Feb 06, 2003 at 22:10:43 +1100, Bruce Evans wrote:
>> 
>> More precisely: some are mounted, but they are mounted read-only (modulo
>> the bug that adjkerntz is run a little after mounting filesystems read-write).
>
>Obvious workaround: could DEVFS be mounted read-only initially and then 
>re-mounted as read-write after adjkerntz started, in the same manner as / 
>remounted read-write, i.e. with "mount -u" ?

Can we stop considering workarounds, and instead work on solving
the problem please ?

-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.

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

¦¬¤J¼W¥[ªº¤èªk

[jerry]

Title: ¦L¶r¾÷





  
  
  
  
   
 
   ·s¦~§ª«°e±z¤@¥x¦L¶r¾÷ 
... 






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

curses programmer wanted to help with GEOM admin tools

[Poul-Henning Kamp]

If somebody out there wonder how to make a contribution to FreeBSD
being a good curses programmer, I have the answer for you:

I could use some help with the user-interface side of some admin
tools for GEOM.

Apply in private email.

Poul-Henning

-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.

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

Re: Wrong date for DEVFS entries

[Andrey A. Chernov]

On Thu, Feb 06, 2003 at 22:10:43 +1100, Bruce Evans wrote:
> 
> More precisely: some are mounted, but they are mounted read-only (modulo
> the bug that adjkerntz is run a little after mounting filesystems read-write).

Obvious workaround: could DEVFS be mounted read-only initially and then 
re-mounted as read-write after adjkerntz started, in the same manner as / 
remounted read-write, i.e. with "mount -u" ?

-- 
Andrey A. Chernov
http://ache.pp.ru/

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

Re: vinum start & -current doesn't work as expected

[Joerg Wunsch]

As Michael Reifenberger wrote:

> > What does your sysctl kern.disks say?
> 
> (nihil)(root) # sysctl -a kern.disks
> kern.disks: da1 da0 ad1 ad0

That's OK.

I guess it's time to dump the old vinum start code from
vinum(8) completely, and use the in-kernel scan now.
-- 
cheers, J"org   .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)

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

Re: vinum start & -current doesn't work as expected

[Michael Reifenberger]

On Fri, 7 Feb 2003, Joerg Wunsch wrote:

> Date: Fri, 7 Feb 2003 21:56:45 +0100 (MET)
> From: Joerg Wunsch <[EMAIL PROTECTED]>
> Reply-To: Joerg Wunsch <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Cc: Michael Reifenberger <[EMAIL PROTECTED]>
> Subject: Re: vinum start & -current doesn't work as expected
>
> Michael Reifenberger <[EMAIL PROTECTED]> wrote:
>
> > After reboot, a `vinum start` gives me:
> > ** no drives found: No such file or directory
>
> Do you perchance have a kernel without GEOM?

-current without GEOM? :-)

>
> vinum start has now been changed to use sysctl kern.disks as the list
> of devices to scan.  Hmm.  No, maybe not...  I'm afraid i should
> change the userland to perform the same as the early startup in the
> kernel now does.
>
> What does your sysctl kern.disks say?

(nihil)(root) # sysctl -a kern.disks
kern.disks: da1 da0 ad1 ad0

>
> As a workaround, you can try setting
>
> vinum_load=YES
> vinum.autostart=YES
>
> in your /boot/loader.conf, /and/ remove the start_vinum line from
> rc.conf.  Please tell me whether this gives different results.
>
Will try. Thanks so far!

Bye!

Michael Reifenberger
^.*Plaut.*$, IT, R/3 Basis, GPS

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

Re: Question about devd concept

[Joerg Wunsch]

"M. Warner Losh" <[EMAIL PROTECTED]> wrote:

> devd works for me when I have devices in my machine at boot.  It
> does run the start script for me.

I've got a related problem.  My kernel is a bit modularized, and with
devd, when i insert the card into the running machine, the script
framework properly kldloads the respective driver (using
/usr/local/bin/smart-loader as suggested in the devd.conf template).
However, this doesn't work when the card is already present at boot
time.  Is this likely to be the same problem?

(I'm currently working around it by pre-loading all potential NIC
modules from the loader.)

-- 
cheers, J"org   .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)

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

Re: vinum start & -current doesn't work as expected

[Joerg Wunsch]

Michael Reifenberger <[EMAIL PROTECTED]> wrote:

> After reboot, a `vinum start` gives me:
> ** no drives found: No such file or directory

Do you perchance have a kernel without GEOM?

vinum start has now been changed to use sysctl kern.disks as the list
of devices to scan.  Hmm.  No, maybe not...  I'm afraid i should
change the userland to perform the same as the early startup in the
kernel now does.

What does your sysctl kern.disks say?

As a workaround, you can try setting

vinum_load=YES
vinum.autostart=YES

in your /boot/loader.conf, /and/ remove the start_vinum line from
rc.conf.  Please tell me whether this gives different results.

-- 
cheers, J"org   .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)

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

Re: GEOM and Extended Slices

[phk]

In message <[EMAIL PROTECTED]>, Hiten Pandya writes:
>Hi gang.
>
>Recently removing the NO_GEOM option from my kernel; I noticed that my
>dos extended slices dev entries disappeared under a GEOM kernel.  This
>is sorta bad, but I can bare for now.
>
>Also, I tried searching the sys/geom/ tree if there was anything
>relating to this, but could not find anything for `grep -i extend`.
>
>So, is it just me, or is this is a problem?

Please send me dmesg from a verbose boot in private email.

-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.

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

Âàø çàêàç - FREEBSD-CURRENT

[AqSJeBE]

Title: Ó âàñ íåò çàêàçîâ


Ó âàñ íåò çàêàçîâ? Ïåðåñòàëè
çâîíèòü êëèåíòû? Î Âàøèõ óñëóãàõ íèêòî
íå çíàåò? Íå õâàòàåò äåíåã íà
ïðîâåäåíèå øèðîêîìàñøòàáíîé ðåêëàìû?
Âñå ýòè ïðîáëåìû ìû ñìîæåì ðåøèòü
âñåãî çà 300$. Çà ýòè äåíüãè ó Âàñ
ïîÿâèòüñÿ âîçìîæíîñòü ðàçîñëàòü ñâîå
ñîîáùåíèå íà  3.800.000 ïîëó÷àòåëåé! Òîëüêî
âäóìàéòåñü â ýòó öèôðó! Ðàññûëêà
äëèòüñÿ â òå÷åíèè 1 äíÿ.  áàçó E-Mail
àäðåñîâ ïîïàëè íå òîëüêî îðãàíèçàöèè è
ïðåäïðèÿòèÿ Ìîñêâû è Ðîññèè, íî è âñå
÷àñòíûå ëèöà. Âñÿ áàçà íà 100%
âåðèôèöèðîâàííàÿ è ìû äàåì ãàðàíòèþ íà
å¸ êà÷åñòâî!
ÏËÞÑ! Çàêàçàâ ó íàñ E-Mail ðàññûëêó
ñåé÷àñ, Âû ñìîæåòå âîñïîëüçîâàòüñÿ
íàøåé íàêîïèòåëüíîé ñèñòåìîé (ïîäðîáíîñòè
ïðè çàêàçå).
Çàêàçàòü ðàññûëêó Âû
ñìîæåòå çäåñü.×òîáû
óäàëèòü ñâîé E-Mail,
íàæìèòå çäåñü.(ñ) 2003 DEMETRIUS 
Software.


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

GEOM and Extended Slices

[Hiten Pandya]

Hi gang.

Recently removing the NO_GEOM option from my kernel; I noticed that my
dos extended slices dev entries disappeared under a GEOM kernel.  This
is sorta bad, but I can bare for now.

Also, I tried searching the sys/geom/ tree if there was anything
relating to this, but could not find anything for `grep -i extend`.

So, is it just me, or is this is a problem?

-- 
Hiten Pandya ([EMAIL PROTECTED], [EMAIL PROTECTED])
http://www.unixdaemons.com/~hiten/

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

Re: How to create a device in current

[Kevin Oberman]

> From: Thierry Herbelot <[EMAIL PROTECTED]>
> Date: Fri, 7 Feb 2003 21:32:21 +0100
> 
> Le Friday 07 February 2003 21:24, Kevin Oberman a =E9crit :
> > I maintain a port for FreeBSD that I am trying to fix to run on
> > V5. The port is the mWave modem software for some IBM laptop internal
> > modems and it needs to create a /dev entry which I previously did with
> > a simple mknod. This doesn't work under 5.0, so I am trying to figure
> > out how to get the device node created in the rc script for the port.
> >
> > The command I used in V4 is mknod "/dev/mwave c 96 0". Where so I read
> > up on creating something like this with devfs?
> >
> 
> could this paper be relevant :=20
>  ers/kamp/kamp_html/index.html>
> 
> (it may require some rewriting of the device driver code)

Thanks, Thierry. Looks interesting. Hopefully it will let me fix up
the driver to work with 5.0.

R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: [EMAIL PROTECTED]  Phone: +1 510 486-8634

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

no disks w/ acpi; long wait pnp_probe w/o acpi

[Thomas Stratmann]

Hi everyone,

the situation is the same as described in my previous posting, except:
* new kernel from yesterday's sources
* played around a bit with my device.hint, only minor changes.

Dmesg output from two boots is appended. First is an acpi-boot, second
without acpi (unset acpi_load in loader) with location marked where the boot
waits for approx. five minutes. Very annoying.

Can someone see what's going on?


Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.0-CURRENT #6: Fri Feb  7 17:32:10 GMT 2003
root@curdwarf:/usr/src/sys/i386/compile/bootable_dbg
Preloaded elf kernel "/boot/kernel/kernel" at 0xc049a000.
Preloaded elf module "/boot/kernel/acpi.ko" at 0xc049a0b4.
Calibrating clock(s) ... TSC clock: 233259209 Hz, i8254 clock: 1193038 Hz
CLK_USE_I8254_CALIBRATION not specified - using default frequency
Timecounter "i8254"  frequency 1193182 Hz
CLK_USE_TSC_CALIBRATION not specified - using old calibration method
Timecounter "TSC"  frequency 233288938 Hz
CPU: Pentium/P55C (quarter-micron) (233.29-MHz 586-class CPU)
  Origin = "GenuineIntel"  Id = 0x581  Stepping = 1
  Features=0x8001bf
real memory  = 67174400 (64 MB)
Physical memory chunk(s):
0x1000 - 0x0009efff, 647168 bytes (158 pages)
0x004c1000 - 0x04007fff, 62156800 bytes (15175 pages)
avail memory = 60289024 (57 MB)
bios32: Found BIOS32 Service Directory header at 0xc00f8e20
bios32: Entry = 0xfe95a (c00fe95a)  Rev = 0  Len = 1
pcibios: PCI BIOS entry at 0xf+0xc5f8
pnpbios: Found PnP BIOS data at 0xc00f8e30
pnpbios: Entry = f:90a8  Rev = 1.0
pnpbios: Event flag at 510
pnpbios: OEM ID c932f351
Other BIOS signatures found:
Intel Pentium detected, installing workaround for F00F bug
Initializing GEOMetry subsystem
wlan: <802.11 Link Layer>
null: 
mem: 
random: 
npx0:  on motherboard
npx0: INT 16 interface
acpi0:  on motherboard
ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15
ACPI-0438: *** Error: Looking up [\\_SB_.SBAT] in namespace, AE_NOT_FOUND
ACPI-1287: *** Error: Method execution failed, AE_NOT_FOUND
acpi0: power button is handled as a fixed feature programming model.
ACPI timer looks GOOD min = 0, max = 2, width = 3
ACPI timer looks GOOD min = 0, max = 1, width = 2
ACPI timer looks GOOD min = 0, max = 1, width = 2
ACPI timer looks GOOD min = 0, max = 1, width = 2
ACPI timer looks GOOD min = 0, max = 1, width = 2
ACPI timer looks GOOD min = 0, max = 1, width = 2
ACPI timer looks GOOD min = 0, max = 1, width = 2
ACPI timer looks GOOD min = 0, max = 1, width = 2
ACPI timer looks GOOD min = 0, max = 1, width = 2
ACPI timer looks GOOD min = 0, max = 1, width = 2
Timecounter "ACPI-fast"  frequency 3579545 Hz
acpi_timer0: <32-bit timer at 3.579545MHz> port 0x18a8-0x18ab on acpi0
acpi_cpu0:  on acpi0
acpi_tz0:  on acpi0
acpi_lid0:  on acpi0
acpi_acad0:  on acpi0
acpi_cmbat0:  on acpi0
pci_open(1):mode 1 addr port (0x0cf8) is 0x8000a050
pci_open(1a):   mode1res=0x8000 (0x8000)
pci_cfgcheck:   device 0 [class=06] [hdr=00] is there (id=06011179)
Using $PIR table, 5 entries at 0xc00f8e80
PCI-Only Interrupts: none
Location  Bus Device Pin  Link  IRQs
embedded0   17A   0x01  3 4 5 6 7 9 10 11 12 14 15
embedded0   19A   0x01  3 4 5 6 7 9 10 11 12 14 15
embedded0   19B   0x01  3 4 5 6 7 9 10 11 12 14 15
slot 1  06A   0x01  3 4 5 6 7 9 10 11 12 14 15
slot 1  06B   0x01  3 4 5 6 7 9 10 11 12 14 15
slot 1  0   11A   0x01  3 4 5 6 7 9 10 11 12 14 15
pcib0:  port 0xcf8-0xcff on acpi0
 initial configuration 
\\_SB_.PCI0.EIO_.LNKA irq  11: [  3  4  5  6  7  9 10 11 12 14 15] low,level,sharable 
0.19.0
\\_SB_.PCI0.EIO_.LNKB irq  11: [  3  4  5  6  7  9 10 11 12 14 15] low,level,sharable 
0.19.1
\\_SB_.PCI0.EIO_.LNKC irq  11: [  3  4  5  6  7  9 10 11 12 14 15] low,level,sharable 
0.17.0
\\_SB_.PCI0.EIO_.LNKD irq  11: [  3  4  5  6  7  9 10 11 12 14 15] low,level,sharable 
0.11.0
\\_SB_.PCI0.EIO_.LNKC irq  11: [  3  4  5  6  7  9 10 11 12 14 15] low,level,sharable 
0.6.0
\\_SB_.PCI0.EIO_.LNKD irq  11: [  3  4  5  6  7  9 10 11 12 14 15] low,level,sharable 
0.6.1
 before setting priority for links 
 before fixup boot-disabled links -
 after fixup boot-disabled links --
 arbitrated configuration -
\\_SB_.PCI0.EIO_.LNKA irq  11: [  3  4  5  6  7  9 10 11 12 14 15] low,level,sharable 
0.19.0
\\_SB_.PCI0.EIO_.LNKB irq  11: [  3  4  5  6  7  9 10 11 12 14 15] low,level,sharable 
0.19.1
\\_SB_.PCI0.EIO_.LNKC irq  11: [  3  4  5  6  7  9 10 11 12 14 15] low,level,sharable 
0.17.0
\\_SB_.PCI0.EIO_.LNKD irq  11: [  3  4  5  6  7  9 10 11 12 14 15] low,level,sharable 
0.11.0
\\_SB_.PCI0.EIO_.LNKC irq  11: [  3  4  5  6  7  9 10 11 12 14 15] low,level,sharable 
0.6.0
\\_SB_.PCI0.EIO_.LNKD irq  11: [  3  4  5  6  7  9 10 11 12

Re: How to create a device in current

[Thierry Herbelot]

Le Friday 07 February 2003 21:24, Kevin Oberman a écrit :
> I maintain a port for FreeBSD that I am trying to fix to run on
> V5. The port is the mWave modem software for some IBM laptop internal
> modems and it needs to create a /dev entry which I previously did with
> a simple mknod. This doesn't work under 5.0, so I am trying to figure
> out how to get the device node created in the rc script for the port.
>
> The command I used in V4 is mknod "/dev/mwave c 96 0". Where so I read
> up on creating something like this with devfs?
>

could this paper be relevant : 


(it may require some rewriting of the device driver code)

TfH

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

How to create a device in current

[Kevin Oberman]

I maintain a port for FreeBSD that I am trying to fix to run on
V5. The port is the mWave modem software for some IBM laptop internal
modems and it needs to create a /dev entry which I previously did with
a simple mknod. This doesn't work under 5.0, so I am trying to figure
out how to get the device node created in the rc script for the port.

The command I used in V4 is mknod "/dev/mwave c 96 0". Where so I read
up on creating something like this with devfs?

R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: [EMAIL PROTECTED]  Phone: +1 510 486-8634

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

Re: vnode locking question.

[Robert Watson]

On Fri, 7 Feb 2003, Hiten Pandya wrote:

> On Thu, Feb 06, 2003 at 10:53:08AM -0800, Julian Elischer wrote the words in effect 
>of:
> > 
> > On Thu, 6 Feb 2003, John Baldwin wrote:
> > 
> > > On 05-Feb-2003 Julian Elischer wrote:
> > > > 
> > > > Is there ever a case when a vnode is locked for longer than the duration
> > > > of the syscall that locked it?
> > > 
> > > Shouldn't be.  That would be a bug I believe.  Userland threads should
> > > never hold any kernel locks.
> > 
> > That's what I think too but I just thought I'd ask..
> > (NFS worries me a bit)
> 
> If It did, wouldn't that give a panic() with something like: 
>   "panic: mutex held on exit to userland..." 
> 
> ... or something like that? 

Nope; lockmgr doesn't have that feature, although all the SMPng locking
primitives do, I believe.  In fact, I believe that's the source of
Julian's question, since I've had a conversation with him about adding
that sort of sanity checking.  In adding that sort of sanity checking, you
want to be very sure we don't break any existing assumptions.

Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED]  Network Associates Laboratories



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

Re: -current, IBM A30p & EPSON scanner

[Michael Reifenberger]

On Fri, 7 Feb 2003, Hidetoshi Shimokawa wrote:

> Date: Fri, 07 Feb 2003 22:49:44 +0900
> From: Hidetoshi Shimokawa <[EMAIL PROTECTED]>
> To: Michael Reifenberger <[EMAIL PROTECTED]>
> Cc: Hidetoshi Shimokawa <[EMAIL PROTECTED]>,
>  FreeBSD-Current <[EMAIL PROTECTED]>
> Subject: Re: -current, IBM A30p & EPSON scanner
>
> Try SANE-patch included in:
>
> http://people.freebsd.org/~simokawa/firewire/firewire-20030205.tar.gz
>
Doesn't apply because in sane-backends epson.c seems to have been splitted into
epson.c and epson_scsi.c .

Will try to merge into the two...

Bye!

Michael Reifenberger
^.*Plaut.*$, IT, R/3 Basis, GPS

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

Re: vnode locking question.

[Hiten Pandya]

On Thu, Feb 06, 2003 at 10:53:08AM -0800, Julian Elischer wrote the words in effect of:
> 
> 
> On Thu, 6 Feb 2003, John Baldwin wrote:
> 
> > 
> > On 05-Feb-2003 Julian Elischer wrote:
> > > 
> > > Is there ever a case when a vnode is locked for longer than the duration
> > > of the syscall that locked it?
> > 
> > Shouldn't be.  That would be a bug I believe.  Userland threads should
> > never hold any kernel locks.
> 
> That's what I think too but I just thought I'd ask..
> (NFS worries me a bit)
> 

If It did, wouldn't that give a panic() with something like:
"panic: mutex held on exit to userland..."

... or something like that?

-- 
Hiten Pandya ([EMAIL PROTECTED], [EMAIL PROTECTED])
http://www.unixdaemons.com/~hiten/

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

Re: Linux networking emulation broken?

[David Malone]

> > I'm guessing the short patch at:
> > 
> > http://www.maths.tcd.ie/~dwmalone/linux_sendmsg.patch
> > 
> > should help. Can you try it and let me know?

OK - I found a second bug, which is a bit more subtle, but which
seems to fix sendto and stop it sending packets to 4.0.0.0. I've
updated the patch, please let me know if it helps.

David.

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

Re: pcm channel duplicate lock

[The Anarcat]

Can it be possible that this would be related to the problem I'm having 
with xmms on -release right now? Except that -release don't have WITNESS 
stuff enabled?

I guess I should try enabling debugging.

Just a shot in the dark...

A.

Lars Eggert wrote:

Got thsi when opening gnomemeeting2 while having xmms playing:

acquiring duplicate lock of same type: "pcm channel"
 1st pcm0:record:0 @ /usr/src/sys/dev/sound/pcm/sound.c:191
 2nd pcm0:play:0 @ /usr/src/sys/dev/sound/pcm/sound.c:191
Debugger("witness_lock")
Stopped at  Debugger+0x5a:  xchgl   %ebx,in_Debugger.0
db> trace
Debugger(c0328da1,c6283a54,c0532609,bf,eb3828ac) at Debugger+0x5a
witness_lock(c635ce40,8,c0532609,bf,eb3828d4) at witness_lock+0x142
_mtx_lock_flags(c635ce40,0,c0532609,bf,c5e5) at _mtx_lock_flags+0x63
pcm_chnalloc(c21a9e00,1,c5e5,,8) at pcm_chnalloc+0x66
dsp_open(c03a6a50,7,2000,c6612780,c0534380) at dsp_open+0x12f
spec_open(eb3829c8,eb382ae4,c0217796,eb3829c8,c03b3ae0) at 
spec_open+0x37d
spec_vnoperate(eb3829c8,c03b3ae0,0,180,c6612780) at spec_vnoperate+0x18
vn_open_cred(eb382bd4,eb382cd4,0,c7575600,eb382cc0) at vn_open_cred+0x306
vn_open(eb382bd4,eb382cd4,0,295,eb382b20) at vn_open+0x29
kern_open(c6612780,888ceb0,0,7,0) at kern_open+0x197
open(c6612780,eb382d10,c0363f83,407,c6610c50) at open+0x30
syscall(875002f,2f,bfbf002f,6,0) at syscall+0x3d6
Xint0x80_syscall() at Xint0x80_syscall+0x1d
--- syscall (5, FreeBSD ELF32, open), eip = 0x2932e273, esp = 
0xbfa65abc, ebp = 0xbfa65ad8 ---

Lars




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

Re: rsync --daemon problems

[Hajimu UMEMOTO]

Hi,

> On Thu, 6 Feb 2003 19:33:10 -0500
> David Rhodus <[EMAIL PROTECTED]> said:

david> On one machine that rsync start's on, I get this from netstat.
david> tcp6   0  0  *.873  *.*
david> LISTEN

It seems the daemon mode of rsync depends on an IPv4-mapped IPv6
address.  Since an IPv4-mapped IPv6 address is off by default on
5-CURRENT, rsync doesn't listen on IPv4.
Further, rsync has a bug that it always listen on 1st entry's address
of the result of getaddrinfo() call.
Please try attached patch.  With this patch, rsync listen on both an
IPv4 and an IPv6.

Sincerely,


Index: socket.c
diff -u socket.c.orig socket.c
--- socket.c.orig	Mon Jan 27 12:35:09 2003
+++ socket.c	Sat Feb  8 00:06:59 2003
@@ -292,11 +292,11 @@
  * @param bind_address Local address to bind, or NULL to allow it to
  * default.
  **/
-static int open_socket_in(int type, int port, const char *bind_address,
-			  int af_hint)
+static int *open_socket_in(int type, int port, const char *bind_address,
+			   int af_hint)
 {
 	int one=1;
-	int s;
+	int *s, *socks, maxs;
 	struct addrinfo hints, *all_ai, *resp;
 	char portbuf[10];
 	int error;
@@ -310,41 +310,65 @@
 	if (error) {
 		rprintf(FERROR, RSYNC_NAME ": getaddrinfo: bind address %s: %s\n",
 			bind_address, gai_strerror(error));
-		return -1;
+		return NULL;
+	}
+
+	/* Count max number of sockets we may open */
+	for (maxs = 0, resp = all_ai; resp; resp = resp->ai_next, maxs++)
+		;
+	socks = malloc((maxs + 1) * sizeof(int));
+	if (!socks) {
+		rprintf(FERROR,
+			RSYNC_NAME "couldn't allocate memory for sockets");
+		return NULL;
 	}
 
 	/* We may not be able to create the socket, if for example the
 	 * machine knows about IPv6 in the C library, but not in the
 	 * kernel. */
+	*socks = 0;   /* num of sockets counter at start of array */
+	s = socks + 1;
 	for (resp = all_ai; resp; resp = resp->ai_next) {
-		s = socket(resp->ai_family, resp->ai_socktype,
+		*s = socket(resp->ai_family, resp->ai_socktype,
 			   resp->ai_protocol);
 
-		if (s == -1) 
+		if (*s == -1) 
 			/* See if there's another address that will work... */
 			continue;
 		
-		setsockopt(s, SOL_SOCKET, SO_REUSEADDR,
+		setsockopt(*s, SOL_SOCKET, SO_REUSEADDR,
 			   (char *)&one, sizeof one);
 		
+#ifdef IPV6_V6ONLY
+		if (resp->ai_family == AF_INET6)
+			setsockopt(*s, IPPROTO_IPV6, IPV6_V6ONLY,
+   (char *)&one, sizeof one);
+#endif
+
 		/* now we've got a socket - we need to bind it */
-		if (bind(s, all_ai->ai_addr, all_ai->ai_addrlen) < 0) {
+		if (bind(*s, resp->ai_addr, resp->ai_addrlen) < 0) {
 			/* Nope, try another */
-			close(s);
+			close(*s);
 			continue;
 		}
 
-		freeaddrinfo(all_ai);
-		return s;
+		(*socks)++;
+		s++;
 	}
 
-	rprintf(FERROR, RSYNC_NAME ": open inbound socket on port %d failed: "
-		"%s\n",
-		port, 
-		strerror(errno));
+	if (all_ai)
+		freeaddrinfo(all_ai);
 
-	freeaddrinfo(all_ai);
-	return -1; 
+	if (*socks == 0) {
+		rprintf(FERROR,
+			RSYNC_NAME ": open inbound socket on port %d failed: "
+			"%s\n",
+			port, 
+			strerror(errno));
+		free(socks);
+		return NULL;
+	}
+	return socks;
 }
 
 
@@ -376,19 +400,29 @@
 
 void start_accept_loop(int port, int (*fn)(int, int))
 {
-	int s;
+	fd_set deffds;
+	int *s, maxfd, i, j;
 	extern char *bind_address;
 	extern int default_af_hint;
 
 	/* open an incoming socket */
 	s = open_socket_in(SOCK_STREAM, port, bind_address, default_af_hint);
-	if (s == -1)
+	if (s == NULL)
 		exit_cleanup(RERR_SOCKETIO);
 
 	/* ready to listen */
-	if (listen(s, 5) == -1) {
-		close(s);
-		exit_cleanup(RERR_SOCKETIO);
+	FD_ZERO(&deffds);
+	maxfd = -1;
+	for (i = 1; i <= *s; i++) {
+		if (listen(s[i], 5) == -1) {
+			for (j = 1; j <= i; j++)
+close(s[j]);
+			free(s);
+			exit_cleanup(RERR_SOCKETIO);
+		}
+		FD_SET(s[i], &deffds);
+		if (maxfd < s[i])
+			maxfd = s[i];
 	}
 
 
@@ -406,16 +440,20 @@
 		   forever */
 		log_close();
 
-		FD_ZERO(&fds);
-		FD_SET(s, &fds);
+		FD_COPY(&deffds, &fds);
 
-		if (select(s+1, &fds, NULL, NULL, NULL) != 1) {
+		if (select(maxfd + 1, &fds, NULL, NULL, NULL) != 1) {
 			continue;
 		}
 
-		if(!FD_ISSET(s, &fds)) continue;
-
-		fd = accept(s,(struct sockaddr *)&addr,&addrlen);
+		fd = -1;
+		for (i = 1; i <= *s; i++) {
+			if (FD_ISSET(s[i], &fds)) {
+fd = accept(s[i], (struct sockaddr *)&addr,
+	&addrlen);
+break;
+			}
+		}
 
 		if (fd == -1) continue;
 
@@ -430,7 +468,7 @@
 
 		if ((pid = fork()) == 0) {
 			int ret;
-			close(s);
+			close(s[i]);
 			/* open log file in child before possibly giving
 			   up privileges  */
 			log_open();
@@ -452,6 +490,7 @@
 			close(fd);
 		}
 	}
+	free(s);
 }
 
 

--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
[EMAIL PROTECTED]  [EMAIL PROTECTED]  ume@{,jp.}FreeBSD.org
http://www.imasy.org/~ume/

Re: Linux networking emulation broken?

[Fred Souza]

> I'm guessing the short patch at:
> 
>   http://www.maths.tcd.ie/~dwmalone/linux_sendmsg.patch
> 
> should help. Can you try it and let me know?

  I've just tried that and it still tries connecting to 4.0.0.0:111
  instead of localhost:111. I had to follow Hajimu UMEMOTO's
  suggestion, once with your patch it stopped complaining about
  a casting error (I don't remember exactly what the error was).


  Fred


-- 
"Some people seem to think that `damn' is God's last name."



msg51939/pgp0.pgp
Description: PGP signature

Re: Preferred Gigabit interfaces for -CURRENT

[Oliver Fromme]

David Gilbert <[EMAIL PROTECTED]> wrote:
 > We're about to make the switch from 100M interfaces to GigE interfaces
 > for our transit routers ... which are FreeBSD-5.0 based SMP (Athlon)
 > boxes.  Our current favorite card is the intel i82559-based fxp
 > cards.  They handle the load best on our testing of 100M cards.
 > Remember that our load is large and small packets and that hardware
 > checksums are not a win (although hardware vlans are).

As far as I know, all of the GigE cards do hardware checksums
anyway.  Those which support VLAN de/muxing in hardware are
listed in the vlan(4) manpage and in the respective interface
manpages (bge, em, gx etc.) -- I think most of them do, if
not all.

 > So... I need to know what GigE chipsets I should test.  I recently
 > tested Intel GigE cards ... with dismal results... less than half the
 > packets-per-second on the (otherwise) same hardware.  Small packets
 > (as in DOS attacks) are a real concern here.
 > 
 > I believe that someone here recomended Tigon III based cards ... but I
 > was recently looking through 5.0-RELEASE's hardware notes and couldn't
 > find any mention of Tigon III.

That's the Broadcom BCM570x chipset (bge driver).  It's only
inofficially called "Tigon III" because it's based on the
Tigon I/II from Alteon.

Having said that -- We do have a bunch of Compaq DL360-G2
machines in production, each of which has two of those bge
interfaces.  We make heavy use of VLANs, and the performance
is very good.  However, we're running 4.7 (because they are
production servers), and our packet profile is probably very
different from yours (most of the traffic is NFS, HTTP, SQL
queries and similar things).

Regards
   Oliver

PS:  "a bunch" == about 20 of them, more to come.

-- 
Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München
Any opinions expressed in this message may be personal to the author
and may not necessarily reflect the opinions of secnetix in any way.

"All that we see or seem is just a dream within a dream" (E. A. Poe)

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

Re: -current, IBM A30p & EPSON scanner

[Hidetoshi Shimokawa]

Try SANE-patch included in:

http://people.freebsd.org/~simokawa/firewire/firewire-20030205.tar.gz

/\ Hidetoshi Shimokawa
\/  [EMAIL PROTECTED]
PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html


At Fri, 7 Feb 2003 12:13:25 +0100 (CET),
Michael Reifenberger wrote:
> 
> Hi,
> next phenomen :-)
> 
> I have an 'Epson perfection 2450 Photo' scanner which gets found using firewire  as:
> pass0 at sbp0 bus 0 target 0 lun 0
> pass0:  Fixed Processor SCSI-4 device
> pass0: 50.000MB/s transfers

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

Re: se7500+dual xeon?

[Victor Ponomarev]

Thanks to all!

As I wrote it's a my mistake with kernel installing. I should pay more 
attention on upper part of dmesg ouput to
see that new kernel didn't install.

By the way does anyone compare heavy load multiprocessor performance 
5.0-RELEASE and 4.7-STABLE?
Is it worth to upgrade a production machine?



Marc G. Fournier wrote:

On Thu, 6 Feb 2003, John Baldwin wrote:

 

His board is a WV2, not a CW2.  The WV2's should work fine though they
might need a BIOS update.
   


I can verify the WV2's ... just built a server with one of these .. can't
verify the BIOS issue, as it was upgraded before I got the machine, but
have been most impressd with both the server and the chassis ...

 





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

Preferred Gigabit interfaces for -CURRENT

[David Gilbert]

We're about to make the switch from 100M interfaces to GigE interfaces
for our transit routers ... which are FreeBSD-5.0 based SMP (Athlon)
boxes.  Our current favorite card is the intel i82559-based fxp
cards.  They handle the load best on our testing of 100M cards.
Remember that our load is large and small packets and that hardware
checksums are not a win (although hardware vlans are).

So... I need to know what GigE chipsets I should test.  I recently
tested Intel GigE cards ... with dismal results... less than half the
packets-per-second on the (otherwise) same hardware.  Small packets
(as in DOS attacks) are a real concern here.

I believe that someone here recomended Tigon III based cards ... but I
was recently looking through 5.0-RELEASE's hardware notes and couldn't
find any mention of Tigon III.

A hint on where to buy the cards may be helpful _and_ I'd like to know
if the choice might be different for -STABLE (as some of our routers
run -STABLE).

Dave.

-- 

|David Gilbert, Velocet Communications.   | Two things can only be |
|Mail:   [EMAIL PROTECTED] |  equal if and only if they |
|http://daveg.ca  |   are precisely opposite.  |
=GLO

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

Re: 5.0 cron problem

[Thomas Quinot]

Le 2003-02-07, CHOI Junho écrivait :

> Oops. It doesn't solve the problem. There is no error when editing
> crontab, but the variable is not substituted correctly(just blank).

Hum, strange, it seemed to work here. Can you send me your crontab and
the output of 'cron -x pars' ?

Thomas.

-- 
[EMAIL PROTECTED]

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

[resend] gdb, threads, and corefiles

[Peter Edwards]

Sorry if this appears twice: my webmail client appears to have dropped
the original message on the floor.

gdb didn't find threads in corefiles: The support was just missing. 
The attached patch does the job. 

Also attached is a small test program which easily generates a corefile 
with threads in it, if anyone wants to test/commit it. 

Before and after output below:

> petere@rocklobster$ cc -o threadcore -Wall -g -pthread threadcore.c
> petere@rocklobster$ ./threadcore
> started thread 0
> started thread 1
> started thread 2
> started thread 3
> zsh: bus error (core dumped)  ./threadcore
> petere@rocklobster$ gdb threadcore threadcore.core
> GNU gdb 5.2.1 (FreeBSD)
> Copyright 2002 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you
> are welcome to change it and/or distribute copies of it under certain
> conditions. Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for
> details. This GDB was configured as "i386-undermydesk-freebsd"...
> Core was generated by `threadcore'.
> Program terminated with signal 10, Bus error.
> Reading symbols from /usr/lib/libc_r.so.5...done.
> Loaded symbols for /usr/lib/libc_r.so.5
> Reading symbols from /usr/lib/libc.so.5...done.
> Loaded symbols for /usr/lib/libc.so.5
> Reading symbols from /usr/libexec/ld-elf.so.1...done.
> Loaded symbols for /usr/libexec/ld-elf.so.1
> #0  0x280d5463 in kill () from /usr/lib/libc.so.5
> (gdb) i thr
> * 1 process 41359  0x280d5463 in kill () from /usr/lib/libc.so.5
> (gdb) quit
> petere@rocklobster$ /usr/src/gnu/usr.bin/binutils/gdb/gdb threadcore
> threadcore.core GNU gdb 5.2.1 (FreeBSD)
> Copyright 2002 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you
> are welcome to change it and/or distribute copies of it under certain
> conditions. Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for
> details. This GDB was configured as "i386-undermydesk-freebsd"...
> Core was generated by `threadcore'.
> Program terminated with signal 10, Bus error.
> Reading symbols from /usr/lib/libc_r.so.5...done.
> Loaded symbols for /usr/lib/libc_r.so.5
> Reading symbols from /usr/lib/libc.so.5...done.
> Loaded symbols for /usr/lib/libc.so.5
> Reading symbols from /usr/libexec/ld-elf.so.1...done.
> Loaded symbols for /usr/libexec/ld-elf.so.1
> #0  0x280d5463 in kill () from /usr/lib/libc.so.5
> (gdb) i thr
>   7 Process 41359  0x280d5463 in kill () from /usr/lib/libc.so.5
>   6 Process 41359  0x2807b7ec in _thread_kern_sched () from
>   /usr/lib/libc_r.so.5 5 Process 41359  0x2807b7ec in _thread_kern_sched
>   () from /usr/lib/libc_r.so.5 4 Process 41359  0x2807b7ec in
>   _thread_kern_sched () from /usr/lib/libc_r.so.5 3 Process 41359 
>   0x2807b7ec in _thread_kern_sched () from /usr/lib/libc_r.so.5 2
>   Process 41359  0x2807b7ec in _thread_kern_sched () from
>   /usr/lib/libc_r.so.5
> * 1 Process 41359  0x280d5463 in kill () from /usr/lib/libc.so.5
> (gdb) 

Enjoy,
Peter.

#include 
#include 
#include 
#include 
#include 
#include 

void *thr(void *a)
{
printf("started thread %d\n", (int)a);
pause();
return 0;
}

int main(int argc, char **argv)
{
const int THREADCOUNT = 4;
int i;
pthread_t threads[THREADCOUNT];

for (i = 0; i < THREADCOUNT; i++)
if (pthread_create(&threads[i], 0, thr, (void *)i) != 0)
errx(-1, "cannot create thread");
sleep(1);
kill(0, SIGBUS);
return 0;
}

Index: freebsd-uthread.c
===
RCS file: 
/pub/FreeBSD/development/FreeBSD-CVS/src/gnu/usr.bin/binutils/gdb/freebsd-uthread.c,v
retrieving revision 1.10
diff -u -r1.10 freebsd-uthread.c
--- freebsd-uthread.c   4 Jan 2003 17:35:54 -   1.10
+++ freebsd-uthread.c   7 Feb 2003 12:34:19 -
@@ -46,6 +46,10 @@
 #include 
 #include "gdbcore.h"
 
+int coreops_suppress_target = 1; /* Ugh. Override the version in corelow.c. */
+extern struct target_ops core_ops; /* target vector for corelow.c */
+static struct target_ops orig_core_ops;/* target vector for corelow.c */
+
 extern int child_suppress_run;
 extern struct target_ops child_ops; /* target vector for inftarg.c */
 
@@ -60,6 +64,7 @@
 
 /* Pointer to the next function on the objfile event chain.  */
 static void (*target_new_objfile_chain) (struct objfile *objfile);
+static void freebsd_uthread_find_new_threads (void);
 
 static void freebsd_uthread_resume PARAMS ((ptid_t pid, int step,
enum target_signal signo));
@@ -472,7 +477,10 @@
 
   if (freebsd_uthread_attaching || TIDGET(inferior_ptid) == 0)
 {
-  child_ops.to_fetch_registers (regno);
+  if (target_has_execution)
+   child_ops.to_fetch_registers (regno);
+  else
+   orig_core_ops.to_fetch_registers (regno);
   return;
 }
 
@@ -481,7 +489,10 @

Re: 5.0 cron problem

[CHOI Junho]

From: CHOI Junho <[EMAIL PROTECTED]>
Subject: Re: 5.0 cron problem
Date: Fri, 07 Feb 2003 19:43:04 +0900 (KST)

> 
> I tried it to 5.0-RELEASE. It works with my previous crontab file.
> 

Oops. It doesn't solve the problem. There is no error when editing
crontab, but the variable is not substituted correctly(just blank).

--
CHOI Junho  KFUG 
FreeBSD Project Web Data Bank 
Key fingerprint = 1369 7374 A45F F41A F3C0  07E3 4A01 C020 E602 60F5

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

alpha tinderbox failure

[Dag-Erling Smorgrav]

--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
--
>>> stage 2: rebuilding the object tree
--
>>> stage 2: build tools
--
>>> stage 3: cross tools
--
>>> stage 4: populating /home/des/tinderbox/alpha/obj/h/des/src/alpha/usr/include
--
>>> stage 4: building libraries
--
>>> stage 4: make dependencies
--
>>> stage 4: building everything..
--
>>> Kernel build for GENERIC started on Fri Feb  7 03:10:04 PST 2003
--
>>> Kernel build for GENERIC completed on Fri Feb  7 03:41:04 PST 2003
--
>>> Kernel build for LINT started on Fri Feb  7 03:41:05 PST 2003
--
===> vinum
"Makefile", line 4450: warning: duplicate script for target "geom_bsd.o" ignored
/h/des/src/sys/dev/lmc/if_lmc.c:32:2: warning: #warning "The lmc driver is broken and 
is not compiled with LINT"
/h/des/src/sys/dev/pdq/pdq.c: In function `pdq_initialize':
/h/des/src/sys/dev/pdq/pdq.c:1606: warning: cast discards qualifiers from pointer 
target type
/h/des/src/sys/pci/meteor.c:149:2: warning: #warning "The meteor driver is broken and 
is not compiled with LINT"
/h/des/src/sys/pci/simos.c:30:2: warning: #warning "The simos driver is broken and is 
not compiled with LINT"
/h/des/src/sys/dev/gfb/gfb_pci.c: In function `pcigfb_open':
/h/des/src/sys/dev/gfb/gfb_pci.c:268: `gfb_devclass' undeclared (first use in this 
function)
/h/des/src/sys/dev/gfb/gfb_pci.c:268: (Each undeclared identifier is reported only once
/h/des/src/sys/dev/gfb/gfb_pci.c:268: for each function it appears in.)
cc1: warnings being treated as errors
/h/des/src/sys/dev/gfb/gfb_pci.c:275: warning: passing arg 1 of `genfbopen' from 
incompatible pointer type
/h/des/src/sys/dev/gfb/gfb_pci.c: In function `pcigfb_close':
/h/des/src/sys/dev/gfb/gfb_pci.c:284: `gfb_devclass' undeclared (first use in this 
function)
/h/des/src/sys/dev/gfb/gfb_pci.c:285: warning: passing arg 1 of `genfbclose' from 
incompatible pointer type
/h/des/src/sys/dev/gfb/gfb_pci.c: In function `pcigfb_read':
/h/des/src/sys/dev/gfb/gfb_pci.c:293: `gfb_devclass' undeclared (first use in this 
function)
/h/des/src/sys/dev/gfb/gfb_pci.c:294: warning: passing arg 1 of `genfbread' from 
incompatible pointer type
/h/des/src/sys/dev/gfb/gfb_pci.c: In function `pcigfb_write':
/h/des/src/sys/dev/gfb/gfb_pci.c:302: `gfb_devclass' undeclared (first use in this 
function)
/h/des/src/sys/dev/gfb/gfb_pci.c:303: warning: passing arg 1 of `genfbwrite' from 
incompatible pointer type
/h/des/src/sys/dev/gfb/gfb_pci.c: In function `pcigfb_ioctl':
/h/des/src/sys/dev/gfb/gfb_pci.c:311: `gfb_devclass' undeclared (first use in this 
function)
/h/des/src/sys/dev/gfb/gfb_pci.c:312: warning: passing arg 1 of `genfbioctl' from 
incompatible pointer type
/h/des/src/sys/dev/gfb/gfb_pci.c: In function `pcigfb_mmap':
/h/des/src/sys/dev/gfb/gfb_pci.c:320: `gfb_devclass' undeclared (first use in this 
function)
/h/des/src/sys/dev/gfb/gfb_pci.c:321: warning: passing arg 1 of `genfbmmap' from 
incompatible pointer type
*** Error code 1

Stop in /h/des/obj/h/des/src/sys/LINT.
*** Error code 1

Stop in /h/des/src.
*** Error code 1

Stop in /h/des/src.

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

Your Free Soul-Patrol Newsletter

[Soul-Patrol Newsletter]

Title: Soul-Patrol Newsletter # 4: Black History Month, Soul,
Jazz, Slow Jams, Black Rock, Funk, Doo Wop, Neo Soul, Tom Joyner,
Jazzhole, Victor Wooten, Harptones, Michael B Sutton,



Issue #4 
  Click Here to
Subscribe/Unsubscribe For 
  Your Free Bi-Monthly Issue! 
  
  
  Soul-Patrol.Com || Soul-Patrol.Net Radio || 
  Monthly Soul-Patrol Digest Magazine
|| About Soul-Patrol 
  

  


  

  
  

  



  


Black
History 
Month 

Table of Contents 
1. CD Review - Jazzhole: 
'Circle Of the Sun' 2. CD Review:
Floetry's 
Floetic 3. Commentary - I
have a 
few issues with Tom Joyner (part 1) 4. Concert 
Review - Victor Wooten at the Knitting Factory
1/21/2003 
5. Competition in Radio and Concert Industries
Act: 
Good News For Artists and Consumers (Bad News For
Clear 
Channel, Joyner, Hughes and other KNEE-GRO Radio
Station 
Operators) 6. Soul-Patrol.Net
Radio - 
January Top 20  Programs  
7. Soul-Patrollers In The 
News 8. Febuary Online Chat 
Sessions (Ray, Goodman & Brown, Harptones,
Black 
Ivory, Mtume)9. Soul-Patrol Black History
Month 
Offline Events (DC, Tampa, Pittsburgh, Philly, LA 
&NYC)  




A brief introduction to those of you who
might be 
new to Soul-Patrol.com. 
The award winning 
Soul-Patrol.com website has been one of the
leading 
voices on the internet in the arena of featuring
the 
best on the net in Soul,
Jazz,
Slow 
Jams, Black 
Rock, Funk,
Doo 
Wop, Neo 
Soul and about the culture 
since 1996.We call the 
concept...'GREAT BLACK MUSIC FROM THE
ANCIENT 
TO THE FUTURE'The publication you
are 
reading now is called The Soul-Patrol Newsletter
and it 
is designed to keep you abreast of news and views 
regarding this music/culture on a bi-monthly
basis. Our 
objective is to provide you with information (CD 
Reviews, Concert Reviews, Commentary, Online
Events, 
Offline Events, etc) on a timely basis that will
lead to 
your participation either online or offline in the
many 
musical/cultural things that the great artists we
love 
provide for us.We feel that it is of
paramount 
importance that YOU participate, because without
YOUR 
active participation, the culture we love is going
to 
die a slow and painful death!We hope
that 
you will enjoy this FREE 
publication, from Soul-Patrol.com . 
If you do, and you wish to continue to get
it 
every two weeks for FREE , click 
here , go to the Soul-Patrol.com 
website or use the form below to register to
get it. 


To Subscribe To The 
Soul-Patrol Newsletter:  


Email Address 
  Zip Code   

 
  



Forward it to your friends (artists and music
fans) on 
the internet who love good music and ask them to 
subscribe as well! 

NOTE:All of the music that you
can 
access from this publication is being streamed
via 
RealAudio with the consent of the artist/copy write 
holder with the hope that you will take a
listen 
and decide to give them a chance to earn a place
in your 
music collection. 

Re: -current, IBM A30p & EPSON scanner

[Michael Reifenberger]

Hi,
next phenomen :-)

I have an 'Epson perfection 2450 Photo' scanner which gets found using firewire  as:
pass0 at sbp0 bus 0 target 0 lun 0
pass0:  Fixed Processor SCSI-4 device
pass0: 50.000MB/s transfers

and xsane gives during startup:
...
[epson] Requesting extended status
[epson] No error
[epson] Checking for ADF: (00)
[epson] Checking for TPU: (80)
[epson] Device name = GT-9700
...

epson:/dev/pass0


unfortunetely no scan does work.
Somthing like ...illegal argument...
But no sbp debug messages.

xsane and the scanned does work fine however when using USB.

Do you have a clue what could get wrong?


Bye!

Michael Reifenberger
^.*Plaut.*$, IT, R/3 Basis, GPS

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

Re: 5.0 cron problem

[CHOI Junho]

I tried it to 5.0-RELEASE. It works with my previous crontab file.

From: Thomas Quinot <[EMAIL PROTECTED]>
Subject: Re: 5.0 cron problem
Date: Fri, 7 Feb 2003 11:37:42 +0100

> Right, the according to the man page inner whitespace in the unquoted
> right-hand part of an environment variable assignment should be preserved.
> Please try the following patch:
> 
> Index: lib/env.c
> ===
> RCS file: /home/ncvs/src/usr.sbin/cron/lib/env.c,v
> retrieving revision 1.11
> diff -u -r1.11 env.c
> --- lib/env.c 23 May 2002 13:16:30 -  1.11
> +++ lib/env.c 7 Feb 2003 10:34:48 -
> @@ -193,14 +193,16 @@
>   break;
>   }
>   } else {
> - if (isspace (*c)) {
> - state++;
> - c++;
> - break;
> - }
> - if (state == NAME && *c == '=') {
> - state++;
> - break;
> + if (state == NAME) {
> + if (isspace (*c)) {
> + c++;
> + state++;
> + break;
> + }
> + if (*c == '=') {
> + state++;
> + break;
> + }
>   }
>   }
>   *str++ = *c++;
> @@ -232,9 +234,14 @@
>   Set_LineNum(fileline);
>   return (FALSE);
>   }
> + if (state == VALUE) {
> + /* End of unquoted value: trim trailing whitespace */
> + c = val + strlen (val);
> + while (c > val && isspace (*(c - 1)))
> + *(--c) = '\0';
> + }
>  
> - /* 2 fields from parser; looks like an env setting
> -  */
> + /* 2 fields from parser; looks like an env setting */
>  
>   if (strlen(name) + 1 + strlen(val) >= MAX_ENVSTR-1)
>   return (FALSE);
> 
> -- 
> [EMAIL PROTECTED]

--
CHOI Junho  KFUG 
FreeBSD Project Web Data Bank 
Key fingerprint = 1369 7374 A45F F41A F3C0  07E3 4A01 C020 E602 60F5

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

Re: 5.0 cron problem

[Thomas Quinot]

Le 2003-02-05, Tim Robbins écrivait :

> Since revision 1.11 of src/usr.sbin/cron/lib/env.c, you need to put the
> value of the environment variable inside quotes if it contains any spaces.
> I suspect that this change of behaviour was unintentional given that the
> implementation differs from the manual page. I'll investigate and fix
> it if it's a bug. In the mean time, use something like this instead:
> CVSUP="/usr/local/bin/cvsup -g -L2 -h localhost"

Right, the according to the man page inner whitespace in the unquoted
right-hand part of an environment variable assignment should be preserved.
Please try the following patch:

Index: lib/env.c
===
RCS file: /home/ncvs/src/usr.sbin/cron/lib/env.c,v
retrieving revision 1.11
diff -u -r1.11 env.c
--- lib/env.c   23 May 2002 13:16:30 -  1.11
+++ lib/env.c   7 Feb 2003 10:34:48 -
@@ -193,14 +193,16 @@
break;
}
} else {
-   if (isspace (*c)) {
-   state++;
-   c++;
-   break;
-   }
-   if (state == NAME && *c == '=') {
-   state++;
-   break;
+   if (state == NAME) {
+   if (isspace (*c)) {
+   c++;
+   state++;
+   break;
+   }
+   if (*c == '=') {
+   state++;
+   break;
+   }
}
}
*str++ = *c++;
@@ -232,9 +234,14 @@
Set_LineNum(fileline);
return (FALSE);
}
+   if (state == VALUE) {
+   /* End of unquoted value: trim trailing whitespace */
+   c = val + strlen (val);
+   while (c > val && isspace (*(c - 1)))
+   *(--c) = '\0';
+   }
 
-   /* 2 fields from parser; looks like an env setting
-*/
+   /* 2 fields from parser; looks like an env setting */
 
if (strlen(name) + 1 + strlen(val) >= MAX_ENVSTR-1)
return (FALSE);

-- 
[EMAIL PROTECTED]

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

Re: -current, IBM A30p & 2 external FW-disks

[Hidetoshi Shimokawa]

At Fri, 7 Feb 2003 10:56:33 +0100 (CET),
Michael Reifenberger wrote:
> 
> On Fri, 7 Feb 2003, Hidetoshi Shimokawa wrote:
> 
> ...
> > Do you have any timeout while the test?
> No. Not any longer.
> > I think SBP_QUEUE_LEN or maxopenings is the important parameter.
> > Can you try to change thoes values?
> >
> The are at their defaults at the moment.
> Do you want me to increase them?

hmm, I had changed the process AFTER timeout and I suppose
I don't change the behavior BEFORE timeout...

Anyway it works :-)
If you have any problem later, please let me know.

/\ Hidetoshi Shimokawa
\/  [EMAIL PROTECTED]
PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html

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

vinum start & -current doesn't work as expected

[Michael Reifenberger]

Hi,
me using -current as of today.

I have two firewire disks as:
...
da0 at sbp0 bus 0 target 0 lun 0
da0:  Fixed Simplified Direct Access SCSI-4
device
da0: 50.000MB/s transfers
da0: 194481MB (398297088 512 byte sectors: 255H 63S/T 24792C)
da1 at sbp0 bus 0 target 1 lun 0
da1:  Fixed Simplified Direct Access SCSI-4
device
da1: 50.000MB/s transfers
da1: 194481MB (398297088 512 byte sectors: 255H 63S/T 24792C)
...



They are partitioned as follows:
# /dev/da0s1c:
type: unknown
disk: amnesiac
label:
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 24792
sectors/unit: 398297025
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0   # milliseconds
track-to-track seek: 0  # milliseconds
drivedata: 0

8 partitions:
#size   offsetfstype   [fsize bsize bps/cpg]
  a: 398296962   63 vinum   # (Cyl.0*- 24792*)
  c: 3982970250unused0 0# (Cyl.0 - 24792*)



I used the following config-file for `vinum create`:
drive d0 device /dev/da0s1a
drive d1 device /dev/da1s1a

volume ablage setupstate
 plex name ablage.p0 org concat
  sd name ablage.p0.s0 drive d0 size 0b
 plex name ablage.p1 org concat
  sd name ablage.p1.s0 drive d1 size 0b



After reboot, a `vinum start` gives me:
** no drives found: No such file or directory



A `vinum read /dev/da0s1 /dev/da1s1` does work.

Any problems known that da0 and da1 are not seen during `vinum start`?


Bye!

Michael Reifenberger
^.*Plaut.*$, IT, R/3 Basis, GPS

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

Re: -current, IBM A30p & 2 external FW-disks

[Michael Reifenberger]

On Fri, 7 Feb 2003, Hidetoshi Shimokawa wrote:

...
> Do you have any timeout while the test?
No. Not any longer.
> I think SBP_QUEUE_LEN or maxopenings is the important parameter.
> Can you try to change thoes values?
>
The are at their defaults at the moment.
Do you want me to increase them?


Bye!

Michael Reifenberger
^.*Plaut.*$, IT, R/3 Basis, GPS

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

Re: -current, IBM A30p & 2 external FW-disks

[Hidetoshi Shimokawa]

At Thu, 6 Feb 2003 12:15:38 +0100 (CET),
Michael Reifenberger wrote:
> 
> On Wed, 5 Feb 2003, Michael Reifenberger wrote:
> ...
> > > I have improved recovery code after timeout in -current.
> > > Could you try that?
> >
> > Is scheduled for this evening.
> > Thanks so far!
> >
> ...
> > > > > - fwcontorl -g 20
> > > > > - sysctl hw.firewire.sbp.max_speed=0
> > > > > - change SBP_QUEUE_LEN in sbp.c to 1 and rebuld module.
> > > > > - sysctl machdep.cpu_idle_hlt=0
> > > > > - sysctl debug.sbp_debug=1 and send me a dmesg.
> 
> Ok, I did some extensive tests overnight.
> Essentially I still had `fwcontorl -g 20` and
> SBP_QUEUE_LEN=1 and maxopenings=1 and `debug.sbp_debug=1`.
> hw.firewire.sbp.max_speed started at 0 and got 2 at the end.
> After treating two `iozone -s 51200m -r1024k` on the platters
> overnight without problems I started with a plain sbp.c and
> no `fwcontorl -g 20`. I get constant rates of 13MB/s on each disk.
> No problems so far.
> Seems you got it. Thanks!

Do you have any timeout while the test?
I think SBP_QUEUE_LEN or maxopenings is the important parameter.
Can you try to change thoes values?

> BTW: switching on debug.firewire_debug gives zillions of 'kick'...
> Is this just a notification about the code-path?

Yes, but it doesn't seem necessary anymore, removed.

Thanks,

/\ Hidetoshi Shimokawa
\/  [EMAIL PROTECTED]
PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html

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

Re: tired of crashes

[Vallo Kallaste]

On Wed, Feb 05, 2003 at 11:47:44AM +0200, Vallo Kallaste  wrote:

> accumulated filesystem corruption. This is on UFS2 filesystem,
> haven't tried UFS1 yet. World and kernel are from January 21, PIII
> SMP system. I'll provide any info one needs to track the cause,
> needless to say I'm _really_ tired of it.

So far I've been unable to reproduce it after update to Feb 5 world
and kernel. I'll try to beat it for some more days before
considering it gone.
-- 

Vallo Kallaste
[EMAIL PROTECTED]

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

[adrian@freebsd.org: adduser change: telling you when a group isn't there]

[Adrian Chadd]

Oops. I should have sent this to -current :-P




adrian

- Forwarded message from Adrian Chadd <[EMAIL PROTECTED]> -

Date: Fri, 7 Feb 2003 16:10:56 +0800
From: Adrian Chadd <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: adduser change: telling you when a group isn't there
User-Agent: Mutt/1.4i



Hi,

The adduser in -current doesn't check if a specified group exists until
the call to pw right at the end. eep.

My sh foo isn't terribly great, but this did it for me.

Comments/rewrites are welcome. I'll commit the group consensus. 




Adrian


diff:

--- /usr/src/usr.sbin/adduser/adduser.shFri Jan 24 02:05:51 2003
+++ adduser.sh  Fri Feb  7 08:04:15 2003
@@ -47,6 +47,16 @@
fi
 }
 
+# Check whether the given group exists
+check_group() {
+   ${PWCMD} show group $1 1> /dev/null 2> /dev/null
+   if [ "$?" = "0" ]; then
+   echo "1"
+   return
+   fi
+   echo "0"
+}
+
 # get_nextuid
 #  Output the value of $_uid if it is available for use. If it
 #  is not, output the value of the next higher uid that is available.
@@ -570,8 +580,31 @@
get_user
get_gecos
get_uid
-   get_logingroup
-   get_groups
+   ok="NO"
+
+   # The code creates a group = $user if one doesn't exist.
+   # We are just going to capture other non-existant groups!
+   while [ "$ok" = "NO" ] ; do
+   ok="YES"
+   get_logingroup
+   if [ "$ulogingroup" != "" -a "$username" != "$ulogingroup" -a 
+"`check_group $ulogingroup`" = "0" ]; then
+   echo "Group $ulogingroup does not exist!"
+   ok="NO"
+   fi
+   done
+
+   ok="NO"
+   while [ "$ok" = "NO" ] ; do
+   ok="YES"
+   get_groups
+   for i in $ugroups; do
+   if [ "$username" != "$i" -a "`check_group $i`" = "0" ]; then
+   echo "Group $i does not exist!"
+   ok="NO"
+   fi
+   done
+   done
+
get_class
get_shell
get_homedir


- End forwarded message -

-- 
Adrian Chadd learning is bad
<[EMAIL PROTECTED]>   it just makes the people around you 
dumber
(angryskul == alfred@irc):(


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