> Not to jump down your throat, or anything, but you seem to be
> perpetuating some incorrct assumptions about both effect and
> proposed implementation details, and they must be stomped. 8-).
I was assuming that mandatory locking, in the context of this
discussion, does not mean automatic, for
On Wed, 25 Aug 1999, Mark Newton wrote:
> Matthew Dillon wrote:
>
> > The question I am putting to the group is whether it is "time" for us,
> > with today's large disks, to increase the system-compiled default
> > from 8 to 16 partitions. Instead of a-h we would have a-p
>
> It
On Wed, 25 Aug 1999, Mark Newton wrote:
> Matthew Dillon wrote:
>
> > The question I am putting to the group is whether it is "time" for us,
> > with today's large disks, to increase the system-compiled default
> > from 8 to 16 partitions. Instead of a-h we would have a-p
>
> I
> > Hi,
> >
> > I need to add a keypad to a product in development that will co-exist
> > with the standard keyboard. It will be a fairly dumb pad capable of
> ...
>
> You could just design the pad using a "keyboard wedge" so that it lives
> on the same bus as the keyboard. This is well-un
> > Hi,
> >
> > I need to add a keypad to a product in development that will co-exist
> > with the standard keyboard. It will be a fairly dumb pad capable of
> ...
>
> You could just design the pad using a "keyboard wedge" so that it lives
> on the same bus as the keyboard. This is well-u
On 25-Aug-99 Nik Clayton wrote:
> On Mon, Aug 23, 1999 at 07:58:52PM +0900, Daniel C. Sobral wrote:
>> While going through old cvs commit log, I spotted this:
>
>
>
>> +
>> +/* Please update doc/en/handbook/ports/chapter.sgml when changing
>> */
>> #undef __FreeBSD_version
>> #define __FreeBS
On 25-Aug-99 Nik Clayton wrote:
> On Mon, Aug 23, 1999 at 07:58:52PM +0900, Daniel C. Sobral wrote:
>> While going through old cvs commit log, I spotted this:
>
>
>
>> +
>> +/* Please update doc/en/handbook/ports/chapter.sgml when changing
>> */
>> #undef __FreeBSD_version
>> #define __FreeB
On Thu, Aug 26, 1999 at 09:09:33AM +0930, Greg Lehey wrote:
> On Wednesday, 25 August 1999 at 6:05:11 -0400, Thomas David Rivers wrote:
> >> All the files under Tandem's NSK has mandatory locking. The file cannot be
> >> opened if another process has it opened. some thing like
> >>
> >> * if the
On Wednesday, 25 August 1999 at 6:05:11 -0400, Thomas David Rivers wrote:
>> All the files under Tandem's NSK has mandatory locking. The file cannot be
>> opened if another process has it opened. some thing like
>>
>> * if the file is opened for reading, any one can open it for
>> reading bu
On Thu, Aug 26, 1999 at 09:09:33AM +0930, Greg Lehey wrote:
> On Wednesday, 25 August 1999 at 6:05:11 -0400, Thomas David Rivers wrote:
> >> All the files under Tandem's NSK has mandatory locking. The file cannot be
> >> opened if another process has it opened. some thing like
> >>
> >> * if th
On Wednesday, 25 August 1999 at 6:05:11 -0400, Thomas David Rivers wrote:
>> All the files under Tandem's NSK has mandatory locking. The file cannot be
>> opened if another process has it opened. some thing like
>>
>> * if the file is opened for reading, any one can open it for
>> reading b
On Wed, 25 Aug 1999, Wes Peters wrote:
> "Jordan K. Hubbard" wrote:
> >
> > I
> > prodded Scott McNealy a couple of weeks ago about this, and he
> > responded...
great.. I didn't see the original mail so I'll never know what he
said.
:-)
>
> That's Jordan, out doing that "CEO Club" thin
Heh, I didn't prod him *personally* - we're not quite in the same
social circles as that (yet ;).
- Jordan
> "Jordan K. Hubbard" wrote:
> >
> > I
> > prodded Scott McNealy a couple of weeks ago about this, and he
> > responded...
>
> That's Jordan, out doing that "CEO Club" thing again. The ne
Wayne Cuddy wrote:
>
> Ok, if you suggested the TCP_NODELAY option you were right. Once we set this
> FreeBSD sent 25 msgs/second, Linux did 22 msgs/second and HPSUX did 15
> msgs/second. (we TCP_NODELAY on all platforms)
>
> Is the Linux Nangle algo broken/different?
It can be turned off by de
Matthew Dillon wrote:
>
> :
> :Back around 1980, I overclocked my 5MHz z80 to 6MHz. It worked without
> problems, except that for-next loops in comal didn't exit as expected. That
> was also reproducible...
> :
> :Leif
>
> In the early 90's I regularly ran 10 MHz 68000's at 20 MHz (which wa
"Jordan K. Hubbard" wrote:
>
> I
> prodded Scott McNealy a couple of weeks ago about this, and he
> responded...
That's Jordan, out doing that "CEO Club" thing again. The next time you
bump into Scott, throw him a body-check for me. ;^)
--
"Where am I, and what am I doing in this
> Hi,
>
> I need to add a keypad to a product in development that will co-exist
> with the standard keyboard. It will be a fairly dumb pad capable of
> generating
> the equivalent of function keys F1 thru F8. The desired goals are:
>
> invisible to the syscons driver (and thus X11).
>
On Wed, 25 Aug 1999, Wes Peters wrote:
> "Jordan K. Hubbard" wrote:
> >
> > I
> > prodded Scott McNealy a couple of weeks ago about this, and he
> > responded...
great.. I didn't see the original mail so I'll never know what he
said.
:-)
>
> That's Jordan, out doing that "CEO Club" thi
Heh, I didn't prod him *personally* - we're not quite in the same
social circles as that (yet ;).
- Jordan
> "Jordan K. Hubbard" wrote:
> >
> > I
> > prodded Scott McNealy a couple of weeks ago about this, and he
> > responded...
>
> That's Jordan, out doing that "CEO Club" thing again. The n
Wayne Cuddy wrote:
>
> Ok, if you suggested the TCP_NODELAY option you were right. Once we set this
> FreeBSD sent 25 msgs/second, Linux did 22 msgs/second and HPSUX did 15
> msgs/second. (we TCP_NODELAY on all platforms)
>
> Is the Linux Nangle algo broken/different?
It can be turned off by d
I've added Tor Egge's "kludge" fix of adding
while (rtcin(RTC_INTR) & RTCIR_PERIOD)
statclock(&frame);
..to the beginning of clkintr() in /sys/i386/isa/clock.c, but when will
there be a genuine fix? Is this an Asus problem? We are two BIOS
revisions behind...would upgra
Matthew Dillon wrote:
>
> :
> :Back around 1980, I overclocked my 5MHz z80 to 6MHz. It worked without problems,
>except that for-next loops in comal didn't exit as expected. That was also
>reproducible...
> :
> :Leif
>
> In the early 90's I regularly ran 10 MHz 68000's at 20 MHz (which was
"Jordan K. Hubbard" wrote:
>
> I
> prodded Scott McNealy a couple of weeks ago about this, and he
> responded...
That's Jordan, out doing that "CEO Club" thing again. The next time you
bump into Scott, throw him a body-check for me. ;^)
--
"Where am I, and what am I doing in this
> Hi,
>
> I need to add a keypad to a product in development that will co-exist
> with the standard keyboard. It will be a fairly dumb pad capable of generating
> the equivalent of function keys F1 thru F8. The desired goals are:
>
> invisible to the syscons driver (and thus X11).
>
Hi,
I need to add a keypad to a product in development that will co-exist
with the standard keyboard. It will be a fairly dumb pad capable of generating
the equivalent of function keys F1 thru F8. The desired goals are:
invisible to the syscons driver (and thus X11).
works in parall
I've added Tor Egge's "kludge" fix of adding
while (rtcin(RTC_INTR) & RTCIR_PERIOD)
statclock(&frame);
..to the beginning of clkintr() in /sys/i386/isa/clock.c, but when will
there be a genuine fix? Is this an Asus problem? We are two BIOS
revisions behind...would upgr
Hi,
I need to add a keypad to a product in development that will co-exist
with the standard keyboard. It will be a fairly dumb pad capable of generating
the equivalent of function keys F1 thru F8. The desired goals are:
invisible to the syscons driver (and thus X11).
works in paral
> The thing about well-intentioned but incorrect locking code is that
> it will appear to work fine, until it trips over the one code path
> where it forgets to lock some file that it should have locked. And
> even then, the code will "work" just fine, until multiple processes
> are accessing that
> [Cc's trimmed]
>
> On Wed, Aug 25, 1999 at 12:15:24AM -0600, Wes Peters wrote:
> > > >
> > > > How 'bout "anyone who can kill the process holding the lock?"
> > >
> > > + file owner ( + root ).
> >
> > Which processes can't root kill?
>
> Zombies? :)
Kill their parents. Eventually, you wi
> > All the files under Tandem's NSK has mandatory locking. The file cannot be
> > opened if another process has it opened. some thing like
> >
> > * if the file is opened for reading, any one can open it for
> > reading but opening for writing gives error
> > * if the file is open for wri
Not to jump down your throat, or anything, but you seem to be
perpetuating some incorrct assumptions about both effect and
proposed implementation details, and they must be stomped. 8-).
> > And how many programmers with nearly (or more than) two decades of UNIX
> > experience it takes to convin
On Mon, Aug 23, 1999 at 07:58:52PM +0900, Daniel C. Sobral wrote:
> While going through old cvs commit log, I spotted this:
> +
> +/* Please update doc/en/handbook/ports/chapter.sgml when changing
> */
> #undef __FreeBSD_version
> #define __FreeBSD_version 48 /* Master, propagated to n
On Mon, Aug 23, 1999 at 07:58:52PM +0900, Daniel C. Sobral wrote:
> While going through old cvs commit log, I spotted this:
> +/* Please update doc/en/handbook/ports/chapter.sgml when changing
> */
> #undef __FreeBSD_version
> #define __FreeBSD_version 48 /* Master, propagated to newve
> > And how many programmers with nearly (or more than) two decades of UNIX
> > experience it takes to convince someone it really is useful.
Har! 8-).
> I must say, I'm really amazed at some of the opinions that have been
> voiced in this thread. Of course, that's all they are, and they show
>
> The thing about well-intentioned but incorrect locking code is that
> it will appear to work fine, until it trips over the one code path
> where it forgets to lock some file that it should have locked. And
> even then, the code will "work" just fine, until multiple processes
> are accessing tha
:
:Back around 1980, I overclocked my 5MHz z80 to 6MHz. It worked without
problems, except that for-next loops in comal didn't exit as expected. That was
also reproducible...
:
:Leif
In the early 90's I regularly ran 10 MHz 68000's at 20 MHz (which was
about the limit the dynamic ram at
> [Cc's trimmed]
>
> On Wed, Aug 25, 1999 at 12:15:24AM -0600, Wes Peters wrote:
> > > >
> > > > How 'bout "anyone who can kill the process holding the lock?"
> > >
> > > + file owner ( + root ).
> >
> > Which processes can't root kill?
>
> Zombies? :)
Kill their parents. Eventually, you w
> > All the files under Tandem's NSK has mandatory locking. The file cannot be
> > opened if another process has it opened. some thing like
> >
> > * if the file is opened for reading, any one can open it for
> > reading but opening for writing gives error
> > * if the file is open for wr
Not to jump down your throat, or anything, but you seem to be
perpetuating some incorrct assumptions about both effect and
proposed implementation details, and they must be stomped. 8-).
> > And how many programmers with nearly (or more than) two decades of UNIX
> > experience it takes to convi
> >
> > After rechecking all the jumpers it turns out that the supplier
> > had set the core voltage to 2.2V instead of 2.4V!
>
> Interesting that the error was reproducible, if this was the cause of
> it. The problem never varied from that exact point? I'd like to say
> that I find that a
On Mon, Aug 23, 1999 at 07:58:52PM +0900, Daniel C. Sobral wrote:
> While going through old cvs commit log, I spotted this:
> +/* Please update doc/en/handbook/ports/chapter.sgml when changing
> */
> #undef __FreeBSD_version
> #define __FreeBSD_version 48 /* Master, propagated to newv
On Mon, Aug 23, 1999 at 07:58:52PM +0900, Daniel C. Sobral wrote:
> While going through old cvs commit log, I spotted this:
> +
> +/* Please update doc/en/handbook/ports/chapter.sgml when changing
> */
> #undef __FreeBSD_version
> #define __FreeBSD_version 48 /* Master, propagated to
I've done a bit more work on the VFS cleanup part of my diffs.
Unfortunatly I had overlooked some of the filesystems and they
were not compiling cleanly. (ext2fs)
http://big.endian.org/~bright/freebsd/in_progress/vfs-fhsyscall.diff
The fh*() syscalls are still being worked on, but I'd really li
> > And how many programmers with nearly (or more than) two decades of UNIX
> > experience it takes to convince someone it really is useful.
Har! 8-).
> I must say, I'm really amazed at some of the opinions that have been
> voiced in this thread. Of course, that's all they are, and they show
:
:Back around 1980, I overclocked my 5MHz z80 to 6MHz. It worked without problems,
:except that for-next loops in comal didn't exit as expected. That was also
:reproducible...
:
:Leif
In the early 90's I regularly ran 10 MHz 68000's at 20 MHz (which was
about the limit the dynamic ram
On Wed, 25 Aug 1999, Jordan K. Hubbard wrote:
>
> Actually, what needed to get updated was the hotel, not our web pages. :)
>
> I just called them and they had apparently listed this under "Walnut
> Creek CDROM", not the most obvious thing to ask for. That's why
> queries have been either bou
> (I believe it got bounced due to my mistake in To: line.
> sorry if you got it multiple times)
>
> Hello, if this mailing list is inappropriate please tell me so.
>
> I contacted radisson hotels for FreeBSDCon reservation with
> special discount, to get the followi
> >
> > After rechecking all the jumpers it turns out that the supplier
> > had set the core voltage to 2.2V instead of 2.4V!
>
> Interesting that the error was reproducible, if this was the cause of
> it. The problem never varied from that exact point? I'd like to say
> that I find that a
> On Mon, 23 Aug 1999 11:28:20 -0400
> Dennis wrote:
>
> > I heard a rumor that freebsd runs on a sparc, but I dont see any backing
> > for that. Is it in the works?
>
> FreeBSD does not run on the SPARC. I think they've been talking about it
> for ... what, 5 years now... but it never mate
I've done a bit more work on the VFS cleanup part of my diffs.
Unfortunatly I had overlooked some of the filesystems and they
were not compiling cleanly. (ext2fs)
http://big.endian.org/~bright/freebsd/in_progress/vfs-fhsyscall.diff
The fh*() syscalls are still being worked on, but I'd really l
On Wed, 25 Aug 1999, Jordan K. Hubbard wrote:
>
> Actually, what needed to get updated was the hotel, not our web pages. :)
>
> I just called them and they had apparently listed this under "Walnut
> Creek CDROM", not the most obvious thing to ask for. That's why
> queries have been either bo
> (I believe it got bounced due to my mistake in To: line.
> sorry if you got it multiple times)
>
> Hello, if this mailing list is inappropriate please tell me so.
>
> I contacted radisson hotels for FreeBSDCon reservation with
> special discount, to get the follow
> On Mon, 23 Aug 1999 11:28:20 -0400
> Dennis <[EMAIL PROTECTED]> wrote:
>
> > I heard a rumor that freebsd runs on a sparc, but I dont see any backing
> > for that. Is it in the works?
>
> FreeBSD does not run on the SPARC. I think they've been talking about it
> for ... what, 5 years now.
Greg Lehey wrote:
>
> On Wednesday, 25 August 1999 at 0:11:23 -0600, Wes Peters wrote:
> > "Daniel C. Sobral" wrote:
> >>
> >> Christopher Masto wrote:
> >>>
> >>> I don't see the use for it.
> >>
> >> :-)
> >>
> >> The thing is SO obviously flawed, that I wonder how many marketoid
> >> drones it
Christopher Seiwald wrote...
>Archie's mod to qsort:
>
>| >- if (swap_cnt == 0) { /* Switch to insertion sort */
>| >+ if (n <= 32 && swap_cnt == 0) { /* Switch to insertion sort */
>
>As Akira Wada points out, this eliminates the benefit of the optimization
>in the first place, which i
Greg Lehey wrote:
>
> On Wednesday, 25 August 1999 at 0:11:23 -0600, Wes Peters wrote:
> > "Daniel C. Sobral" wrote:
> >>
> >> Christopher Masto wrote:
> >>>
> >>> I don't see the use for it.
> >>
> >> :-)
> >>
> >> The thing is SO obviously flawed, that I wonder how many marketoid
> >> drones i
Christopher Seiwald wrote...
>Archie's mod to qsort:
>
>| >- if (swap_cnt == 0) { /* Switch to insertion sort */
>| >+ if (n <= 32 && swap_cnt == 0) { /* Switch to insertion sort */
>
>As Akira Wada points out, this eliminates the benefit of the optimization
>in the first place, which
On Wed, 25 Aug 1999, Tim Vanderhoek wrote:
:[Cc's trimmed]
:
:On Wed, Aug 25, 1999 at 12:15:24AM -0600, Wes Peters wrote:
:> > >
:> > > How 'bout "anyone who can kill the process holding the lock?"
:> >
:> > + file owner ( + root ).
:>
:> Which processes can't root kill?
:
:Zombies? :)
ps sho
[Cc's trimmed]
On Wed, Aug 25, 1999 at 12:15:24AM -0600, Wes Peters wrote:
> > >
> > > How 'bout "anyone who can kill the process holding the lock?"
> >
> > + file owner ( + root ).
>
> Which processes can't root kill?
Zombies? :)
> > Otherwise I would be able to lock ~wes/FreeBSDmarkers a
On Wed, 25 Aug 1999, Tim Vanderhoek wrote:
:[Cc's trimmed]
:
:On Wed, Aug 25, 1999 at 12:15:24AM -0600, Wes Peters wrote:
:> > >
:> > > How 'bout "anyone who can kill the process holding the lock?"
:> >
:> > + file owner ( + root ).
:>
:> Which processes can't root kill?
:
:Zombies? :)
ps sh
[Cc's trimmed]
On Wed, Aug 25, 1999 at 12:15:24AM -0600, Wes Peters wrote:
> > >
> > > How 'bout "anyone who can kill the process holding the lock?"
> >
> > + file owner ( + root ).
>
> Which processes can't root kill?
Zombies? :)
> > Otherwise I would be able to lock ~wes/FreeBSDmarkers
On Tue, 24 Aug 1999, Jun-ichiro itojun Hagino wrote:
> (I believe it got bounced due to my mistake in To: line.
> sorry if you got it multiple times)
>
> Hello, if this mailing list is inappropriate please tell me so.
>
> I contacted radisson hotels for FreeBSDCon reser
On Tue, 24 Aug 1999, Jun-ichiro itojun Hagino wrote:
> (I believe it got bounced due to my mistake in To: line.
> sorry if you got it multiple times)
>
> Hello, if this mailing list is inappropriate please tell me so.
>
> I contacted radisson hotels for FreeBSDCon rese
w...@softweyr.com (Wes Peters) writes:
> And how many programmers with nearly (or more than) two decades of UNIX
> experience it takes to convince someone it really is useful.
It should only take one, as long as the arguments made are not bogus.
IMHO Greg made some very silly arguments (or at l
> All the files under Tandem's NSK has mandatory locking. The file cannot be
> opened if another process has it opened. some thing like
>
> * if the file is opened for reading, any one can open it for
> reading but opening for writing gives error
> * if the file is open for writing, it can
[EMAIL PROTECTED] (Wes Peters) writes:
> And how many programmers with nearly (or more than) two decades of UNIX
> experience it takes to convince someone it really is useful.
It should only take one, as long as the arguments made are not bogus.
IMHO Greg made some very silly arguments (or at
> All the files under Tandem's NSK has mandatory locking. The file cannot be
> opened if another process has it opened. some thing like
>
> * if the file is opened for reading, any one can open it for
> reading but opening for writing gives error
> * if the file is open for writing, it ca
On Tue, Aug 24, 1999 at 03:44:32PM -0700, John Plevyak wrote:
> On Tue, Aug 24, 1999 at 02:33:48PM -0700, Matthew Dillon wrote:
> > :I am experiencing reproducible crashes with FreeBSD (3.2-STABLE) on
> > :a K6/3-450 running on an ASUS P5S-VM motherboard. The problem is highly
> > :repeatable (ha
[ tech-userle...@netbsd.org removed from cc:, it's not a userlevel issue
any more ]
On Tue, Aug 24, 1999 at 07:49:02PM +0100, Neil A. Carson wrote:
> ext2fs in Linux already has some support for mount downgrading or forcable
> unomunting (maybe) in the case of an FS error. For something like a
>
Ok, I'm going to start doing a bit of work on this
so as to enable the periodic output to be customised
I'll post my changes later for ppl that maybe interested
(these changes will still be useful for myself anyway)
I'll see if I can put all your suggestions in, thanks
for the feedback.
Cillian
> My clerk just started reading down the names. When I heard walnut
you should have asked him to read both names and rates, complete the
list and then "oh yes, mine was the 19.95 per night..."
cheers
luigi
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe fr
On Tue, Aug 24, 1999 at 03:44:32PM -0700, John Plevyak wrote:
> On Tue, Aug 24, 1999 at 02:33:48PM -0700, Matthew Dillon wrote:
> > :I am experiencing reproducible crashes with FreeBSD (3.2-STABLE) on
> > :a K6/3-450 running on an ASUS P5S-VM motherboard. The problem is highly
> > :repeatable (h
In message Bill
Fumerola writes:
: It took me 10 minutes of explanation for the reservation clerk to finally
: figure out just what the hell I was talking about. WC CDROM did the
: trick.
My clerk just started reading down the names. When I heard walnut
creek cdrom, I said "ding ding ding ding
On Tue, Aug 24, 1999 at 04:25:26PM -0400, John W. DeBoskey wrote:
>The subject says it all... We have some code that scans files
> backwards...
I've asked about it a year ago, see
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=487426+0+archive/1998/freebsd-hackers/19980726.freebsd-hackers
[ [EMAIL PROTECTED] removed from cc:, it's not a userlevel issue
any more ]
On Tue, Aug 24, 1999 at 07:49:02PM +0100, Neil A. Carson wrote:
> ext2fs in Linux already has some support for mount downgrading or forcable
> unomunting (maybe) in the case of an FS error. For something like a
> floppy,
Ok, I'm going to start doing a bit of work on this
so as to enable the periodic output to be customised
I'll post my changes later for ppl that maybe interested
(these changes will still be useful for myself anyway)
I'll see if I can put all your suggestions in, thanks
for the feedback.
Cillian
> My clerk just started reading down the names. When I heard walnut
you should have asked him to read both names and rates, complete the
list and then "oh yes, mine was the 19.95 per night..."
cheers
luigi
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freeb
In message <[EMAIL PROTECTED]> Bill Fumerola
writes:
: It took me 10 minutes of explanation for the reservation clerk to finally
: figure out just what the hell I was talking about. WC CDROM did the
: trick.
My clerk just started reading down the names. When I heard walnut
creek cdrom, I said "
78 matches
Mail list logo
