Re: Discussion of guidelines for additional version control mechanisms (fwd)

Hi Folks, Before I address Robert's questions directly I'd like to make a few comments. Now, I'm not a committer, I'm a newbie as far as working on FreeBSD itself goes, but I've been a faithful consumer of this stuff since early NetBSD days and was runing Free around 2.2.7. I a

Re: Broken (?) unistd.h

On Wed, 27 Feb 2002, Bruce Evans wrote: > On Tue, 26 Feb 2002, Bill Fenner wrote: > > > Here's a patch for bind's port/freebsd/include/port_before.h . > > > > --- port_before.h.orig Tue Feb 26 20:57:35 2002 > > +++ port_before.h Tue Feb 26 21:02:18 2002 > > @@ -15,6 +15,7 @@ > > #define S

Re: Are there periodic "GOOD" tags in CVS for -CURRENT?

On Tue, 26 Feb 2002, George V. Neville-Neil wrote: > Hi Folks, > I'm wondering if anyone has been laying down periodic "good" tags in > -CURRENT so that people who are just starting with it have a place to start > that is reasonably stable. Several of us have asked for this repeate

Re: Discussion of guidelines for additional version control

My general opinion is that a developer should not claim ownership of anything, it should simply be apparent from the traffic the developer posts to the public lists, discussion, and his commits. This implies that the developer is only actively working on one thing at a time, a

Re: NetBSD-style rc.d Project

On Tue, 26 Feb 2002, Crist J. Clark wrote: > Looking at the repository, I have not really seen anything done with > building a NetBSD-style rc.d system that will provide FreeBSD > functionality for a long time. Several of us have started on this, and either run out of time, or interest (

Re: Today's panic on boot problem

Mike Silbersack wrote: > On Wed, 27 Feb 2002, Mike Silbersack wrote: > > >>Disabling PG_G allows it to work here again as well. Given the problems >>we're experiencing, backing out the pmap changes of the last two days >>seems like a good idea. >> >>Mike "Silby" Silbersack >> > > Well, I sorta

Re: setpgrp(1, 1) does not FAIL

On Wed, 27 Feb 2002 15:44:23 +0900, HIROSHI OOTA <[EMAIL PROTECTED]> said: oota> The following will succeed in non privilege user. oota> I think it should fail. oota> main() oota> { oota>printf("%d\n", setpgrp(1, 1)); oota> } Fixed in rev 1.138 of kern/kern_prot.c, thanks! -- Seigo Tani

Re: Discussion of guidelines for additional version controlmechanisms (fwd)

In message: <[EMAIL PROTECTED]> "George V. Neville-Neil" <[EMAIL PROTECTED]> writes: : The problem here is process. The FreeBSD project now has more than : 12 core members and more than 12 committers. With any number larger : than 12 it is VERY HARD to reach consensus on anything. W

Re: Discussion of guidelines for additional version control mechanisms (fwd)

In message <[EMAIL PROTECTED]>, "M. Warner Losh" writes: >In message: <[EMAIL PROTECTED]> >"George V. Neville-Neil" <[EMAIL PROTECTED]> writes: >: The problem here is process. The FreeBSD project now has more than >: 12 core members and more than 12 committers. With any number larger

Going to CURRENT from STABLE

Well, I've decided to go to CURRENT from STABLE, but much of the kernel sources break, because of -Werror. I solve my problem passing NO_WERROR=1 on make command line, but this was not documented. :-=(( -- Dimitar Peikov GnuPG key http://www.bgzone.com/~mitko/mitko.key.asc Key fingerpri

Re: Going to CURRENT from STABLE

* Dimitar Peikov <[EMAIL PROTECTED]> [020227 03:54] wrote: > > Well, I've decided to go to CURRENT from STABLE, but much of the > kernel sources break, because of -Werror. I solve my problem passing > NO_WERROR=1 on make command line, but this was not documented. :-=(( Since 5.x is a moving targ

Re: Latest versions of bsd.lib.mk break picobsd...

On Mon, Feb 25, 2002 at 04:38:29PM -0800, George V. Neville-Neil wrote: > Hi Folks, > > I've tried contacting [EMAIL PROTECTED] directly but haven't seen anything so I > figure I'll throw this out to the list. On 21 Feb 2002 a change was made to > the > You'll have to pay some money if y

panic: bad peter

Using ``FreeBSD 5.0-CURRENT #0: Wed Feb 27 02:00:14 EST 2002''. While cvs updating in /usr/ports: TPTE at 0xbfca0348 IS ZERO @ VA 280d2000 panic: bad peter cpuid = 0; lapic.id = 0100 Looks like there was plenty committed to src/sys in the last few hours, so I'm rebu

Re: Going to CURRENT from STABLE

In message: <[EMAIL PROTECTED]> Dimitar Peikov <[EMAIL PROTECTED]> writes: : Well, I've decided to go to CURRENT from STABLE, but much of the : kernel sources break, because of -Werror. I solve my problem passing : NO_WERROR=1 on make command line, but this was not documented. :-=((

Re: Today's panic on boot problem

On Tue, Feb 26, 2002 at 09:29:51PM -0800, Peter Wemm wrote: > FWIW, turning off PG_G see_ms to help. Change in pmap.c: > #if !defined(SMP) || defined(ENABLE_PG_G) > to: > #if /*!defined(SMP) ||*/ defined(ENABLE_PG_G) > and see how you go. This got me past atkbd0, but it is a very worrying > sign

Re: Going to CURRENT from STABLE

On Wed, 27 Feb 2002 06:44:19 MST, "M. Warner Losh" wrote: > It was documented when you typed config: > You may need to use the make -DNO_WERROR flag if you hit unfixed warnings. Output from config(8) is lost in the noise when you use the buildkernel target. Ciao, Sheldon. To Unsubscribe: sen

Re: Discussion of guidelines for additional version control mechanisms (fwd)

One of the disagreements that seems to be evolving is whether or not the project formally supports a task-oriented structure. A couple of people have asserted that people might claim tasks (such as myself) and by virtue of claiming the task, be provided with some notion of ownership that is supp

Re: Broken (?) unistd.h

On Wed, 27 Feb 2002, Doug Barton wrote: > On Wed, 27 Feb 2002, Bruce Evans wrote: > > >From style(9): > > > > Kernel include files (i.e. sys/*.h) come first; normally, include > > OR , but not both. includes > > , and it is okay to depend on that. > > Based on a suggestion from

valgrind

hi, I found this tool called valgrind (http://devel-home.kde.org/~sewardj/) a few days ago and find it really interesting. It is something similair to purify (memory use debugger one could call it I guess) but GPL'ed and developed by the KDE team from what I can tell. I have been looking for this

double panic in todays kernel

Using ``FreeBSD 5.0-CURRENT #1: Wed Feb 27 09:07:28 EST 2002''. While building some port (-pipe probably played its fatal role)... -mi (kgdb) symbol-file kernel.debug Reading symbols from kernel.debug...done. (kgdb) exec-file /boot/mi/kernel (kgdb) core-file /ccd/crash/vmcore.28 IdlePTD

Re: valgrind

I'm working on porting this right now. Be forewarned, though, that the FreeBSD hacks for this tool will *never* be allowed into the main distro. Why? Licence. Valgrind includes some code from the Linux kernel and libc. When we hack it for FreeBSD, we'll end up putting some BSD-licenced code

Re: Discussion of guidelines for additional version control mechanisms (fwd)

: My feeling has always been that imposing some modicrum of structure is : important: to avoid people stepping on toes, people can announce what : they're working on, and expect that others might avoid replicating the : work, or at least be communicated with before it happens. The rationale : for

Re: valgrind

On Wed, Feb 27, 2002 at 11:00:14AM -0500, Matthew Emmerton wrote: > > I'm working on porting this right now. great news! what is the current status and have you set up a website for the project or will it be a "simple" portsentry with some patches? (I thought it would require some more rewriting

Re: setpgrp(1, 1) does not FAIL

Can you look into PR kern/29844 as well? I think after your fix, it should fail even when invoked by super user. Regards, In article <[EMAIL PROTECTED]>, Seigo Tanimura <[EMAIL PROTECTED]> wrote: >On Wed, 27 Feb 2002 15:44:23 +0900, > HIROSHI OOTA <[EMAIL PROTECTED]> said: oota> The fo

Re: valgrind

On Wed, Feb 27, 2002 at 11:00:14AM -0500, Matthew Emmerton wrote: > Be forewarned, though, that the FreeBSD hacks for this tool will > *never* be allowed into the main distro. Why? Licence. Valgrind > includes some code from the Linux kernel and libc. When we hack it for > FreeBSD, we'll end u

-Current is stable enough for use again

FWIW, now that Peter has temporarily backed out his pmap-related changes, -current has stabilized again. Those who were having trouble with panics on boot (or within a few minutes after) with kernels built during the last day or two should definitely cvsup. Mike "Silby" Silbersack To Unsubscr

Re: Today's panic on boot problem

Peter Wemm wrote: > Mike Silbersack wrote: > > On Tue, 26 Feb 2002, Peter Wemm wrote: > > > Mike Silbersack wrote: > > > > Hm, sounds like UP got optimized out. > > > Gah! That would be a first. :( > > Well, until I can build a working kernel, I'll just assume that it's a > > feature. > FWIW, tur

Re: -Current is stable enough for use again

>Date: Wed, 27 Feb 2002 10:52:38 + (GMT) >From: Mike Silbersack <[EMAIL PROTECTED]> >FWIW, now that Peter has temporarily backed out his pmap-related changes, >-current has stabilized again. Those who were having trouble with panics >on boot (or within a few minutes after) with kernels built

Re: setpgrp(1, 1) does not FAIL

[Please write in us-ascii] On Thu, 28 Feb 2002 01:39:11 +0900, Takanori Saneto <[EMAIL PROTECTED]> said: Takanori> Can you look into PR kern/29844 as well? Takanori> I think after your fix, it should fail even when invoked by super Takanori> user. The superuser fails as well. Takanori> In a

Re: valgrind

Matthew Emmerton wrote: > I'm working on porting this right now. > > Be forewarned, though, that the FreeBSD hacks for this tool will > *never* be allowed into the main distro. Why? Licence. Valgrind > includes some code from the Linux kernel and libc. When we hack it for > FreeBSD, we'll end

Re: you broke current in some weird way... etc

:date: 2002/02/27 09:51:32; author: peter; state: Exp; lines: +245 -191 :Back out all the pmap related stuff I've touched over the last few days. :There is some unresolved badness that has been eluding me, particularly :affecting uniprocessor kernels. Turning off PG_G helped (which is a bad :s

Re: valgrind

Michael Lucas wrote: > Actually, this doesn't cause as many as you might think. > > GPL'd code can swallow BSDL'd code. BSDL'd code cannot swallow GPL'd > code. You could probably get your code assimilated into the main > valgrind distro. No, it can't. You can't change the license on the orig

Re: you broke current in some weird way... etc

Matthew Dillon wrote: > :date: 2002/02/27 09:51:32; author: peter; state: Exp; lines: +245 -191 > :Back out all the pmap related stuff I've touched over the last few days. > :There is some unresolved badness that has been eluding me, particularly > :affecting uniprocessor kernels. Turning off

Re: Discussion of guidelines for additional version control mechanisms (fwd)

> There are only only 8 core team members, unless you mean something > different by "core" here than [EMAIL PROTECTED] I guess I was going based on the meeting I attended back at BSD Con. > Otherwise, I tend to agree with your basic premise that it is process > and not tools at the heart of this

Re: you broke current in some weird way... etc

:Matthew Dillon wrote: :> :date: 2002/02/27 09:51:32; author: peter; state: Exp; lines: +245 -191 :> :Back out all the pmap related stuff I've touched over the last few days. :> :There is some unresolved badness that has been eluding me, particularly :> :affecting uniprocessor kernels. Turnin

Re: Discussion of guidelines for additional version control mechanisms (fwd)

> In addition to process it might be attitude. > It might be a stretch but they are kind of the same. Good processes come from good attitude. It is extraordinarily hard for most people (especially smart people) to be introspective on such questions when they think they already have the answer.

Re: Discussion of guidelines for additional version controlmechanisms (fwd)

In message: <[EMAIL PROTECTED]> "George V. Neville-Neil" <[EMAIL PROTECTED]> writes: : > There are only only 8 core team members, unless you mean something : > different by "core" here than [EMAIL PROTECTED] : : I guess I was going based on the meeting I attended back at BSD Con. The

Re: Latest versions of bsd.lib.mk break picobsd...

> You'll have to pay some money if you need a 24-hour responsiveness. :-) > The check is in the mail ;-) > What src/release PicoBSD script should I try to run to reproduce this? > -CURRENT as of Monday. Things work fine in a checkout from 20 Feb 2002 and that's what I'm working with. If yo

Re: Discussion of guidelines for additional version control mechanisms (fwd)

+---[ George V. Neville-Neil ]-- | > In addition to process it might be attitude. | > | | So, how do we get our attitudes adjusted before hitting a wall, | as many companies I've worked for did? Alcohol and a cam-corder d8) -- Totally Holistic Enterprises Internet|

Re: Discussion of guidelines for additional version controlmechanisms (fwd)

In message: <[EMAIL PROTECTED]> "George V. Neville-Neil" <[EMAIL PROTECTED]> writes: : So, how do we get our attitudes adjusted before hitting a wall, : as many companies I've worked for did? It comes back to agreeing : on a process by which we work. We have one now, it may not all :

Re: Discussion of guidelines for additional version control mechanisms (fwd)

> One of the disagreements that seems to be evolving is whether or not the > project formally supports a task-oriented structure. A couple of people > have asserted that people might claim tasks (such as myself) and by virtue > of claiming the task, be provided with some notion of ownership that

Re: you broke current in some weird way... etc

Matthew Dillon wrote: > :> I'm just going to use this opportunity to plug the concept of temporary > :> sysctl-instrumentation for a commit like this. > : > :Overall, this is a good idea. However, it can't apply to > :any code that runs before init_main.c runs the SI_SUB_TUNABLES. > >

usb product identified as ugen

A friend of mime give me (only for some days) an external usb hard disk device (a normal ide 2.5" with an interface from ide to usb, self powered). When I attach I got this info, I need it show as umass to mount the msdos (fat32) file system on it, right? Need I some special kernel configuration

Re: Discussion of guidelines for additional version controlmechanisms (fwd)

"M. Warner Losh" wrote: > That's the $64k question. Our current worst case is the "rock > tumbler" school of management. You put everybody together in one big > hopper and spin. This knockes the rough edges off people. However, > it doesn't take into account differing "hardness" of the materia

Re: you broke current in some weird way... etc

In message <[EMAIL PROTECTED]> Matthew Dillon writes: : Sometimes features in early boot can be adjusted by breaking into DDB : and w/l changing the sysctl variable, but perhaps not in this case. I think this is an excellent idea. I have many of these tunables in the cardbus/oldcard code

Is Adaptec ATA Raid Supported

I am looking for a mid-range Raid solution for my database server. I hate to put down a significant chunk of change for SCSI Raid for a website that still doesn't quite pay its bills. Now for my question. I was looking at an: Adaptec ATA RAID 2400A controller card. It is a four channel ATA/10

Re: usb product identified as ugen

You don't mention how your kernel is presently configured or what other troubleshooting you've done, so all you can hope to receive are wild guesses like: - Configure a kernel with the umass, scbus, and da devices, along with the standard usb devices. This is documented in both the GENERIC confi

Re: Discussion of guidelines for additional version controlmechanisms (fwd)

Hi Folks, I've put up the following TWiki page: http://www.neville-neil.com/twiki/bin/view/Freebsd/DevelopmentProcess as a scribbling area for a possible set of rules/practices that we can use to address the issues raised in this discussion. For those not familiar with TWiki who want t

Re: Is Adaptec ATA Raid Supported

On Wed, 2002-02-27 at 11:32, Wm Brian McCane wrote: > I am looking for a mid-range Raid solution for my database server. I hate > to put down a significant chunk of change for SCSI Raid for a website that > still doesn't quite pay its bills. Now for my question. I was looking at > an: > > Adap

Re: Why is xe building while commented out?

On Wed, Feb 27, 2002 at 03:44:03PM +0100, Christopher Sharp wrote: > * Stephen L. Palmer ([EMAIL PROTECTED]) wrote: > > /usr/src/sys/dev/isp/isp.c: In function `isp_reset': > > /usr/src/sys/dev/isp/isp.c:633: warning: cast discards qualifiers from > > pointer target type > > *** Error code 1 > A s

Re: Why is xe building while commented out?

On Wed, 27 Feb 2002, David O'Brien wrote: > Fixes to "make it compile" are not desired. Fixes that are are *FIXES* > are. If you are unable to understand why dv_ispfw is `const'; just > follow the advice of adding: > > makeoptions NO_WERROR=true > > to your kernel configuration. > Did that

Re: NetBSD-style rc.d Project

On Wed, Feb 27, 2002 at 02:02:11AM -0800, Doug Barton wrote: > On Tue, 26 Feb 2002, Crist J. Clark wrote: > > > Looking at the repository, I have not really seen anything done with > > building a NetBSD-style rc.d system that will provide FreeBSD > > functionality for a long time. > > Seve

Re: Latest versions of bsd.lib.mk break picobsd...

On Wed, Feb 27, 2002 at 09:49:28AM -0800, George V. Neville-Neil wrote: > > You'll have to pay some money if you need a 24-hour responsiveness. :-) > > > > The check is in the mail ;-) > > > What src/release PicoBSD script should I try to run to reproduce this? > > > > -CURRENT as of Monday.

Financial freedom / One-up Club!! 59291914119

$750/DAY IN 20 DAYS! AMAZING ONE-UP PLAN GENERATES CASH FASTER THAN EVER BEFORE! FEATURES: * One-Time $50 Out-of-Pocket! * One Invitee To Qualify Forever! * Two To Cash In! * Administration Fee Only $20/Year! * Monthly Residuals Forever! Here's How It Works: Day 1: Invite one person Day 2:

controversial fix or some errors breaking LINT

There are saveral places (e.g. if_ie.c) where data is copied out of a buffer that is shared with the hardware. The pointer to this is correctly labelled as "volatile", though at the time we will copy the data out we know it to be stable. the problem is that it uses "bcopy()" to do this, and tha

Re: controversial fix or some errors breaking LINT

:/* : * Note: the "volatile" below does not REQUIRE that the argument be : * volatile, but rather ony says that it is OK to use a volatile * i : * there. Same for the const. I know a const volatile sounds strange : * but it only indicates that either is acceptable. : */ :voidbcopy __P((volati

Re: controversial fix or some errors breaking LINT

ok so I leave it to other people to fix LINT I'm not going near it any more one small example: ../../../dev/ie/if_ie.c:1471: warning: passing arg 1 of pointer to function discards qualifiers from pointer target type ../../../dev/ie/if_ie.c:1480: warning: passing arg 1 of pointer to function disc

Re: controversial fix or some errors breaking LINT

: :ok so I leave it to other people to fix LINT :I'm not going near it any more It's the responsibility of whoever added -Werror to the default compile to unbreak the tree, either by fixing the problem or by backing out his commit. -Matt To U

Re: controversial fix or some errors breaking LINT

* Matthew Dillon <[EMAIL PROTECTED]> [020227 14:51] wrote: > > : > :ok so I leave it to other people to fix LINT > :I'm not going near it any more > > It's the responsibility of whoever added -Werror to the default > compile to unbreak the tree, either by fixing the problem or by > b

Re: controversial fix or some errors breaking LINT

>No. Leave it in, this will benifit us all in the long run. Until we start hitting the broken/buggy warnings, which will cause people to write more obfuscated or harder to maintain code in order to avoid the warnings. Bill To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe fre

Re: controversial fix or some errors breaking LINT

At 1:27 PM -0800 2/27/02, Julian Elischer wrote: >There are saveral places (e.g. if_ie.c) where data >is copied out of a buffer that is shared with the hardware. > >The pointer to this is correctly labelled as "volatile", though >at the time we will copy the data out we know it to be stable. Note

Re: usb product identified as ugen

On 27-Feb-2002 (18:35:18/GMT) Scott long wrote: > You don't mention how your kernel is presently configured > or what other troubleshooting you've done, so all you can > hope to receive are wild guesses like: Usually I don't make stupid questions (I think), sorry for wasting your time, but after

Re: controversial fix or some errors breaking LINT

Alfred Perlstein wrote: > * Matthew Dillon <[EMAIL PROTECTED]> [020227 14:51] wrote: > > > > : > > :ok so I leave it to other people to fix LINT > > :I'm not going near it any more > > > > It's the responsibility of whoever added -Werror to the default > > compile to unbreak the tree, ei

Re: controversial fix or some errors breaking LINT

On Wed, Feb 27, 2002 at 03:15:09PM -0800, Peter Wemm wrote: > If there are files that are too hard to fix, or vendor files, or the fix > isn't clear, we should use the nowerror conf/files* flags. > > It is important that we stop new warnings turning up when the compile > output is so damn large t

Re: controversial fix or some errors breaking LINT

It's not my problem as jhb has volunteered to fix all these. :-) we just add an entry point for bcopy_volatile() next to that for bcopy. (I called it vbcopy in my suggestion.) bzero has the same thing bzero_volatile() I guess. Though I still feel that it breaks POLA to not be able to use bcop

Re: controversial fix or some errors breaking LINT

I presume then that you also feel that allowing bcopy to copy volatile regions is a bad idea? On Wed, 27 Feb 2002, Peter Wemm wrote: > Alfred Perlstein wrote: > > * Matthew Dillon <[EMAIL PROTECTED]> [020227 14:51] wrote: > > > > > > : > > > :ok so I leave it to other people to fix LINT > >

Re: controversial fix or some errors breaking LINT

In message Garance A Drosihn writes: : How philosophically sickening would it be to create a macro: : : #define bcopy_volatile(x,y) bcopy((casts)x,(casts)y) How about just using bus_space in these drivers? That's the right solution and isn't too hard to d

Re: usb product identified as ugen

On Wed, 2002-02-27 at 16:07, Riccardo Torrini wrote: > On 27-Feb-2002 (18:35:18/GMT) Scott long wrote: > > > You don't mention how your kernel is presently configured > > or what other troubleshooting you've done, so all you can > > hope to receive are wild guesses like: > > Usually I don't make

Re: controversial fix or some errors breaking LINT

sure.. does bus-space have a bzero? On Wed, 27 Feb 2002, Warner Losh wrote: > In message Garance A Drosihn writes: > : How philosophically sickening would it be to create a macro: > : > : #define bcopy_volatile(x,y) bcopy((casts)x,(casts)y) > > How abou

Re: you broke current in some weird way... etc

On Wed, Feb 27, 2002 at 09:33:48AM -0800, Matthew Dillon wrote: > I'm just going to use this opportunity to plug the concept of temporary > sysctl-instrumentation for a commit like this. Any thoughts on having a root oid for sysctl oids like this, so they're not forgotten, and aren't as

Re: you broke current in some weird way... etc

:On Wed, Feb 27, 2002 at 09:33:48AM -0800, Matthew Dillon wrote: :> I'm just going to use this opportunity to plug the concept of tempora= :ry :> sysctl-instrumentation for a commit like this. =20 : :Any thoughts on having a root oid for sysctl oids like this, so they're :not forgotten, a

Re: controversial fix or some errors breaking LINT

In message: <[EMAIL PROTECTED]> Julian Elischer <[EMAIL PROTECTED]> writes: : does bus-space have a bzero? Effectively yes. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: usb product identified as ugen

On 27-Feb-2002 (23:17:15/GMT) Scott Long wrote: I forgot this piece of messages, it happens only once, when I manually detached usb cable but never again when I rescan it. -8<-[ messages ]-8<- ...kernel: ugen0: at uhub0 port 2 (addr 2) disconnected ...kernel: ugen0: detached ...k

Re: usb product identified as ugen

On 27-Feb-2002 (23:17:15/GMT) Scott Long wrote: > Is the umass device compiled into the kernel, or loaded as a > module? If it's a module, is it loaded before you attach the > drive? The usb daemon isn't smart enough yet to load it... Now I have all compiled in. Something happens... -8<

Re: controversial fix or some errors breaking LINT

Peter Wemm wrote: > Alfred Perlstein wrote: > > * Matthew Dillon <[EMAIL PROTECTED]> [020227 14:51] wrote: > > > > > > : > > > :ok so I leave it to other people to fix LINT > > > :I'm not going near it any more > > > > > > It's the responsibility of whoever added -Werror to the default > > >

lock order reversal (vfs_syscalls.c)

I got this message on today's -current: lock order reversal 1st 0xc036afc0 allproc @ ../../../kern/vfs_syscalls.c:452 2nd 0xc7ecce34 filedesc structure @ ../../../kern/vfs_syscalls.c:457 -- Jun Kuriyama <[EMAIL PROTECTED]> // IMG SRC, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] wit

Re: setpgrp(1, 1) does not FAIL

thanks for your quick fixing. but, It should return EPERM instead of ESRCH. Because ESRCH means `The requested process does not exist'. thanks, -- HIROSHI OOTA [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] wit

Re: controversial fix or some errors breaking LINT

* Peter Wemm <[EMAIL PROTECTED]> [020227 15:44] wrote: > Alfred Perlstein wrote: > > * Matthew Dillon <[EMAIL PROTECTED]> [020227 14:51] wrote: > > > > > > : > > > :ok so I leave it to other people to fix LINT > > > :I'm not going near it any more > > > > > > It's the responsibility of whoev

Re: usb product identified as ugen

On Thu, Feb 28, 2002 at 01:39:55AM +0100, Riccardo Torrini wrote: > On 27-Feb-2002 (23:17:15/GMT) Scott Long wrote: > > > Is the umass device compiled into the kernel, or loaded as a > > module? If it's a module, is it loaded before you attach the > > drive? The usb daemon isn't smart enough ye

Re: usb product identified as ugen

On 28-Feb-2002 (05:05:40/GMT) Scott Long wrote: >> Anyway, ugen0 disappear from /dev/ but _no_ umass0 appear, >> only xpt0... > The debug trace looks very good. I think this is the only good news... > No umass0 device should appear in /dev. Instead, you should > get a da device. Do 'camcont

Re: Latest versions of bsd.lib.mk break picobsd...

> This still doesn't answer my question -- how can I reproduce the problem? > > cd /foo/bar > make grrr > > Something like that... Whoops, sorry. To reproduce this do: cd /usr/src ./release/picobsd/build/picobsd --src /usr/src --init yes, I know that --src is unnecessary but I always use it

Re: setpgrp(1, 1) does not FAIL

On Thu, 28 Feb 2002 13:18:06 +0900, HIROSHI OOTA <[EMAIL PROTECTED]> said: oota> but, It should return EPERM instead of ESRCH. Because ESRCH oota> means `The requested process does not exist'. Setpgrp(2) should fail in this case because pid 1 (which is usually init(8)) is not a child of the c