> Well, I know that it's legal to omit one's own copyright claim, but
> for some organization to lay claim to copyrights owned by you or me
> seems very wrong. It's a violation of BSD-type licenses and a
> violation of the concept of attribution that is behind the licenses.
> A legal entity has m
On Monday 12 January 2004 07:33, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Dag-Erling
> =?iso-8859-1?q?Sm=F8rgrav?=
>
> writes:
> >"M. Warner Losh" <[EMAIL PROTECTED]> writes:
> >> Maybe this would be a good test-case for seeing how well it works?
> >> Maybe not. We do need to ru
On Mon, 12 Jan 2004, Matthew Dillon wrote:
>
> :> Agreed. Like I've said, the main problem I see is complexity. It
> :> wouldn't matter as much if there were 5-10 people with deep knowledge of
> :> SMPng, but with 1 or 2 hackers working on it, the chance that everything
> :> will be ever fix
On Sunday 11 January 2004 04:39 pm, Martin Nilsson wrote:
> Marcin Dalecki wrote:
> > Martin Nilsson wrote:
> >> I'm trying to find out why I can't boot 5.2 from USB CDROM on
> >> Supermicro motherboards. (I have an old Gateway P3 that can!).
> >>
> >> I've found out that that only 0x20 of 0x
In message: <[EMAIL PROTECTED]>
Mark Linimon <[EMAIL PROTECTED]> writes:
: > If nothing happens, vinum is going to break even more very soon.
:
: No ... if you do a commit that changes the code assumptions upon
: which vinum was built, vinum will break. vinum is not going to
: "magica
In message: <[EMAIL PROTECTED]>
Peter Jeremy <[EMAIL PROTECTED]> writes:
: On Sun, Jan 11, 2004 at 01:12:25PM -0600, William Grim wrote:
: >If it's really such a big deal to get rid of floppy support, how about
: >we get rid of it and make sure an older version of FreeBSD 4.x/5.x is
:
:> Agreed. Like I've said, the main problem I see is complexity. It
:> wouldn't matter as much if there were 5-10 people with deep knowledge of
:> SMPng, but with 1 or 2 hackers working on it, the chance that everything
:> will be ever fixed is quite small.
:>
:IMO, the easiest way to start th
On Monday 12 January 2004 01:21 pm, Brooks Davis wrote:
> On Mon, Jan 12, 2004 at 08:26:22AM -0800, Wes Peters wrote:
> > On Monday 12 January 2004 07:22 am, Brooks Davis wrote:
> > > On Sun, Jan 11, 2004 at 09:24:38PM +0100, Nicolas Rachinsky wrote:
> > > > I don't know the release build process,
On Mon, 2004-01-12 at 11:32, Wes Peters wrote:
> A few years ago Perforce was working on a write-through cache so you could
> have a local duplicate of the server environment, but I haven't seen that
> work come out of the company. That would've rocked for our development
> model.
They release
On Mon, Jan 12, 2004 at 08:26:22AM -0800, Wes Peters wrote:
> On Monday 12 January 2004 07:22 am, Brooks Davis wrote:
> > On Sun, Jan 11, 2004 at 09:24:38PM +0100, Nicolas Rachinsky wrote:
> > >
> > > I don't know the release build process, so I don't know how much
> > > effort is neccessary to cre
On Thursday 08 January 2004 13:05, Munish Chopra wrote:
> On 2004-01-08 17:29 +, Doug Rabson wrote:
>
> [...]
>
> > The three main showstoppers for moving FreeBSD to subversion would be:
> >
> > 1. A replacement for cvsup. Probably quite doable using svnadmin
> >dump and load.
> > 2. Suppor
Hi all,
I've noticed a very weird phenomenon with ping which I can't explain.
I have two machines with 2 NICs.
When I started a ping -f with larger packet size (-s 3052) with NIC 1
and simultaneously hammered NIC 2 with UDP using ttcp, I got duplicate
ping replies (on NIC 1, of course). Not many:
On Monday 12 January 2004 05:53 am, Jacques A. Vidrine wrote:
> On Sun, Jan 11, 2004 at 05:48:19PM +, Colin Percival wrote:
> > While browsing the FreeBSD src tree, I came across a number of
> > binary files (listed below); the regression tests are perhaps
> > understandable, but shouldn't th
On Sunday 11 January 2004 12:36 pm, Scott W wrote:
> David Gilbert wrote:
> >>"Poul-Henning" == Poul-Henning Kamp <[EMAIL PROTECTED]> writes:
> >
> >Poul-Henning> In message <[EMAIL PROTECTED]>,
> >Poul-Henning> "Greg 'groggy' Lehey" writes:
> >
> >Poul-Henning> The reason I say this is that ne
On Monday 12 January 2004 07:22 am, Brooks Davis wrote:
> On Sun, Jan 11, 2004 at 09:24:38PM +0100, Nicolas Rachinsky wrote:
> >
> > I don't know the release build process, so I don't know how much
> > effort is neccessary to create such floppies, but the loader seems to
> > have all features neede
On Sun, Jan 11, 2004 at 09:24:38PM +0100, Nicolas Rachinsky wrote:
> * Brooks Davis <[EMAIL PROTECTED]> [2004-01-11 11:02 -0800]:
> > If you could make this work such that you just stuffed GENERIC and the
> > mfsroot onto however many floppies it takes, I think that would almost
> > certaintly solv
On Mon, 12 Jan 2004, Mark Linimon wrote:
> > If nothing happens, vinum is going to break even more very soon.
>
> No ... if you do a commit that changes the code assumptions upon which
> vinum was built, vinum will break. vinum is not going to "magically"
> break by itself.
>
> This gets back
Hi,
Some time ago I released the first public version of my "atuwi" driver (for
Atmel usb wireless adapters). Since then I have made a lot of changes to the
code and today it's time to release the next version...
Version 0.2 features :
* A nice step-by-step guide to installing and using the dri
In message <[EMAIL PROTECTED]>, John Hay writes:
>> >But, in the real world of software engineering, He Who Breaketh It,
>> >Must Fixeth It.
>...
>> In a free software project, you can take any rule like that an put
>> it anywhere you like, in any font, size and color of your choice
>> and it stil
On Mon, Jan 12, 2004 at 11:00:34AM +0100, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Mark Linimon writes:
>
> >But, in the real world of software engineering, He Who Breaketh It,
> >Must Fixeth It.
>
> If we are talking paid jobs, yes, then you can make rules like that
> because w
On Sun, Jan 11, 2004 at 05:48:19PM +, Colin Percival wrote:
> While browsing the FreeBSD src tree, I came across a number of
> binary files (listed below); the regression tests are perhaps
> understandable, but shouldn't the rest of these files be uuencoded?
>
> contrib/groff/doc/gnu.png
> co
On Wed, Dec 31, 2003 at 03:30:15PM +0100, Marc Olzheim wrote:
> So I noticed. But it seems to me as if the undefers could be removed
> from within the if-else-blocks and collapsed into a single undefer just
> beneath the if-else-blocks, right before the
> _thread_leave_cancellation_point();
Hmm, t
In message <[EMAIL PROTECTED]>, Martin Nilsson writes:
>I read the GEOM manpage in 5.2, have looked at your webpage
>(http://people.freebsd.org/~phk) and have found a paper and some slides.
I'm afraid that you have pretty much discovered what there is at this
point in time. Kirk is updating the
> If vinum means a lot to you, you should do something to get it above
> that threshold: start debugging/coding, learn to code if need be,
> donate money so somebody else can code if you can't do anything
> else.
I don't use vinum so I have no stake in this.
OTOH I'm not announcing changes which
> I forgot to mention on rather important factor in this equation:
Er, this is the *only* important factor. IMHO, it made most of the
previous conversation be completely off-the-rails.
> If nothing happens, vinum is going to break even more very soon.
No ... if you do a commit that changes the
Well, I'll look into that in GDB somewhen, when I have time if nobody
else has any idea...
I tried four functions from three different areas of the kernel, and
all crashed, so I didn't bother to try more... But I'll try more
somewhen and see if I find functions which don't cause a panic...
Than
Poul-Henning, do you have a list of GEOM programming info available so
that one have something to start with for example to make Vinum
compatible with GEOM.
I read the GEOM manpage in 5.2, have looked at your webpage
(http://people.freebsd.org/~phk) and have found a paper and some slides.
Are t
On Sun, Jan 11, 2004 at 12:39:22PM +0100, Miguel Mendez wrote:
+> >I started RAIDframe three years ago with the hope of bringing a proven
+> >and extensible RAID stack to FreeBSD. Unfortunately, while it was made
+> >to work pretty well on 4.x, it has never been viable on 5.x; it never
+> >survive
Hello hackers!
Help to understand problem.
I have FreeBSD 4.9 on my box.
# uname -a
FreeBSD wall.ru 4.9-RELEASE-p1 FreeBSD 4.9-RELEASE-p1 #24
I've tried to Upgrade it to 5.1
# cvsup /etc/cvsupfile
# cd /usr/src
# make buildworld
===> lib/libpam/modules/pam
i re-applied the patches to the latest bootp.c, and took care not to
botch up the tabs, but my user friendly emacs was not too helpful :-)
(the diff is now about 500 lines)
the PR is:
http://www.freebsd.org/cgi/query-pr.cgi?pr=61239
thanks,
danny
> Sounds very interesting indeed.
In message <[EMAIL PROTECTED]>, Mark Linimon writes:
>But, in the real world of software engineering, He Who Breaketh It,
>Must Fixeth It.
If we are talking paid jobs, yes, then you can make rules like that
because with the salary you control resource allocation and
prioritization.
My real life
Hello people,
I have a bit of a problem to get my Wacom Graphire3 (USB) to work with
FreeBSD. At first I thought I was doing something wrong, but it seems that
FreeBSD doesnt understand it. I know it works with OpenBSD and NetBSD, and
that it probably is due to uhid.c
http://fxr.watson.org/fxr/
In message <[EMAIL PROTECTED]>, "Greg 'groggy' Lehey"
>> As much as I would hate to see RF and Vinum disappar from our
>> source tree, maybe what we need to do is to kick them both into
>> "training-camp" in p4 while you and Greg look the other way.
>
>Hmm. I can't see why they have to disappear
On Sun, Jan 11, 2004 at 01:12:25PM -0600, William Grim wrote:
>If it's really such a big deal to get rid of floppy support, how about
>we get rid of it and make sure an older version of FreeBSD 4.x/5.x is
>always available for download? This way, floppy users could install an
>older version of
34 matches
Mail list logo
