Wed, Jun 03, 2009 at 11:03:45AM +0200, Dag-Erling Sm??rgrav wrote:
> Isn't it clearly described in the preceding comment? Specifically, by
> the first two sentences: "Replace multiple slashes by a single slash and
> trailing slashes by a null. This must be done before VOP_LOOKUP()
> because some
Eygene Ryabinkin writes:
> "Dag-Erling Smørgrav" writes:
> > Eygene Ryabinkin writes:
> > > Perhaps 'XXX for direnter()' should be changed to something like
> > > 'strip trailing slashes in cnp->cn_nameptr'.
> > I'll just remove it, since the previous comment clearly explains
> > what is going o
Tue, Jun 02, 2009 at 01:28:34PM +0200, Dag-Erling Sm??rgrav wrote:
> Eygene Ryabinkin writes:
> > For the current code state, check "*cp == '\0'" seems to be redundant:
> > [...] By the way, comment before the test "if (rdonly)' seems to be
> > slightly misleading [...]
>
> OK, I see that. I've
Bruce Evans writes:
> This comment could do with some rewording to emphasize inheritance of the
> flag and to improve the grammar of the comment.
Suggestions? For reference, here's the entire comment:
/*
* Replace multiple slashes by a single slash and trailing slashes
Eygene Ryabinkin writes:
> For the current code state, check "*cp == '\0'" seems to be redundant:
> [...] By the way, comment before the test "if (rdonly)' seems to be
> slightly misleading [...]
OK, I see that. I've removed the check and rewritten the comment.
What about this "temporary asser
Dag-Erling, good day.
Fri, May 29, 2009 at 06:58:08PM +0200, Dag-Erling Sm??rgrav wrote:
> Index: sys/kern/vfs_lookup.c
> ===
> --- sys/kern/vfs_lookup.c (revision 193028)
> +++ sys/kern/vfs_lookup.c (working copy)
> @@ -454,7
Fri, May 29, 2009 at 06:53:22PM +0200, Dag-Erling Sm??rgrav wrote:
> Bruce Evans writes:
> > % /*
> > %* Get a buffer for the name to be translated, and copy the
> > %* name into the buffer.
> > % @@ -533,6 +536,8 @@
> > % if (*cp == '\0') {
> > % trailing_sla
How's this?
Index: sys/kern/vfs_lookup.c
===
--- sys/kern/vfs_lookup.c (revision 193028)
+++ sys/kern/vfs_lookup.c (working copy)
@@ -454,7 +454,6 @@
int docache;/* == 0 do not cache last compon
Bruce Evans writes:
> Dag-Erling Smørgrav writes:
> % Index: sys/kern/vfs_lookup.c
> % ===
> % --- sys/kern/vfs_lookup.c (revision 192899)
> % +++ sys/kern/vfs_lookup.c (working copy)
> % @@ -147,6 +147,9 @@
> % cnp->
Mel, good day.
Thu, May 28, 2009 at 11:07:12AM +0200, Mel Flynn wrote:
> On Tuesday 26 May 2009 23:20:01 Dag-Erling Sm??rgrav wrote:
> > Dag-Erling Sm??rgrav writes:
> > > Like bde@ pointed out, the patch is incorrect. It moves the test for
> > > v_type != VDIR up to a point where, in the case o
On Tuesday 26 May 2009 23:20:01 Dag-Erling Smørgrav wrote:
> Dag-Erling Smørgrav writes:
> > Like bde@ pointed out, the patch is incorrect. It moves the test for
> > v_type != VDIR up to a point where, in the case of a symlink, v_type is
> > always (by definition) VLNK.
>
> Hmm, actually, symlink
Eygene Ryabinkin writes:
> 'if ()' looks suspicious: ISLASTCN is set some lines below so it could
> be not yet flagged. Seems like we could omit 'if ()' clause but leave
> it's body for the current state of the code -- it will be equivalent to
> the mine's check.
Yes, I was a little too quick th
Oliver Pinter writes:
> This is a redefinitions of PARAMASK in the patch, that you attached
Sorry, I forgot to regenerate the patch after fixing it.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.fre
Hi!
This is a redefinitions of PARAMASK in the patch, that you attached
---8<-
...
#definePARAMASK0x0e00 /* mask of parameter descriptors */
+#defineTRAILINGSLASH 0x1000 /* path ended in a slash */
+#definePARAMASK0x1e00 /* mask
Wed, May 27, 2009 at 06:44:35PM +0200, Dag-Erling Sm??rgrav wrote:
> Eygene Ryabinkin writes:
> > [new three-part patch]
>
> I committed the namei.h cleanup patch and the vfs_lookup.c comment
> patch.
Thanks!
> I made a number of changes to the trailing-slash patch. Can you
> double-check it b
Bruce Evans writes:
> This seems to be equivalent to the patch in the PR at the time of PR,
> except it risks breaking some other cases, so I don't see how it can
> work.
As discussed on -hackers, it doesn't. This one does, though.
DES
--
Dag-Erling Smørgrav - d...@des.no
Index: sys/kern/vfs_
Eygene Ryabinkin writes:
> [new three-part patch]
I committed the namei.h cleanup patch and the vfs_lookup.c comment
patch.
I made a number of changes to the trailing-slash patch. Can you
double-check it before I commit it?
DES
--
Dag-Erling Smørgrav - d...@des.no
Index: sys/kern/vfs_lookup.
Eygene Ryabinkin writes:
> Regarding the 'ln -s /etc/motd file; ln -s file/ anotherone': do you
> (or anyone reading this) think that 'cat anotherone' should really
> show the contents of /etc/motd or patch's behaviour is good?
if you mean
$ ln -fs /etc/motd foo
$ ln -fs foo/ bar
$ readlink foo
Wed, May 27, 2009 at 02:39:07PM +0200, Dag-Erling Sm??rgrav wrote:
> I was working on head. The code is (mostly) the same, just shifted
> somewhere between ~50 and ~90 lines depending on where you look. Your
> patch should apply cleanly.
>
> BTW, you made a lot of whitespace changes in namei.h.
Eygene Ryabinkin writes:
> "Dag-Erling Smørgrav" writes:
> > (don't be fooled by the comment on line 270;
> > the code inside the if statement is for the *non*-symlink case).
> Me sees this on the line 226, but may be I hadn't updated my 7.x.
I was working on head. The code is (mostly) the same
Wed, May 27, 2009 at 01:07:15PM +0200, Dag-Erling Sm??rgrav wrote:
> Eygene Ryabinkin writes:
> > May be the attached patch will fix the thing?
>
> I'm not entirely convinced. Try the regression test I wrote
> (head/tools/regression/vfs/trailing_slash.t)
I see: you mean that the bare '/' at th
Eygene Ryabinkin writes:
> May be the attached patch will fix the thing?
I'm not entirely convinced. Try the regression test I wrote
(head/tools/regression/vfs/trailing_slash.t)
> It adds an additional flag, but this was the only thing I was able to
> invent to avoid ABI breakage.
The flag is
Dag-Erling, *, good day.
Tue, May 26, 2009 at 10:13:21PM +0200, Dag-Erling Sm??rgrav wrote:
> [moving from security@ to hack...@]
>
> Jakub Lach writes:
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/21768
>
> Like bde@ pointed out, the patch is incorrect. It moves the test for
> v_type !
Dag-Erling Smørgrav writes:
> Like bde@ pointed out, the patch is incorrect. It moves the test for
> v_type != VDIR up to a point where, in the case of a symlink, v_type is
> always (by definition) VLNK.
Hmm, actually, symlinks are resolved in namei(), not lookup(). This is
not going to be pret
Dag-Erling Smørgrav writes:
> The attached patch should work.
Oops. It actually triggers a KASSERT.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To uns
[moving from security@ to hack...@]
Jakub Lach writes:
> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/21768
Like bde@ pointed out, the patch is incorrect. It moves the test for
v_type != VDIR up to a point where, in the case of a symlink, v_type is
always (by definition) VLNK.
The reason wh
Peter B wrote:
3ware 9650 in RAID6 mode with firmware version 3.08.00.004 seems to cause
data corruption when rebuilding a single disc with raid6.
http://www.webmasternetwork.se/f4t23551.html (Swedish)
I thought this was serious enough for people to know. If another mailinglist
is more appropia
Peter B wrote:
3ware 9650 in RAID6 mode with firmware version 3.08.00.004 seems to cause
data corruption when rebuilding a single disc with raid6.
http://www.webmasternetwork.se/f4t23551.html (Swedish)
I thought this was serious enough for people to know. If another mailinglist
is more appropia
Hi again;
Reading more deeply,the patch was made to be able to run Linux's crossover
office, but it would seem like it's not required on FreeBSD though as out mmap
behaves similar to the linux one.
FWIW, I found this reference on the NetBSD mailing lists:
http://mail-index.netbsd.org/tech-kern/
On Tue, Sep 09, 2003 at 09:58:03PM -0700, Pedro F. Giffuni wrote:
> taken from wine HQ:
[snip]
Does this make Wine significantly faster for you? Has anybody prepared
benchmarks for this?
I can take a look at implementing this if it's likely to offer benefits.
BMS
On Fri, 29 Aug 2003, Kris Kennaway wrote:
> On Thu, Aug 28, 2003 at 05:34:29PM -0400, Marc Ramirez wrote:
> >
> > supped as of ~ 1:40pm EST today
> >
> > The panic:
> >
> > Fatal trap 12: page fault while in kernel mode
>
> This is probably hardware-related, but it's possible it may be due to
> a
On 28 Aug 2003, at 17:34, Marc Ramirez wrote:
> c0271430 T vm_page_remove
> c02714f8 T vm_page_lookup
Your fault address is between those two, so it happened sometime
after you entered vm_page_remove.
This particular failure is often related to running out of KVM/KVA
space (or hardware problem
On Thu, Aug 28, 2003 at 05:34:29PM -0400, Marc Ramirez wrote:
>
> supped as of ~ 1:40pm EST today
>
> The panic:
>
> Fatal trap 12: page fault while in kernel mode
This is probably hardware-related, but it's possible it may be due to
a kernel problem. As a first step, you need to try and get a
Also, incase your intrested, you can also use icpcon with the iir driver
incase you want to fool with the raid from userland. icpcon looks alot
like the interface you get when booting. You can look for failures,
rebuild the raid, and get statistics.
To use icpcon, you just need to:
mknod /dev/i
Mike Smith wrote:
>
> > So the driver writers
> > are forced to at least recompile their drivers for each release.
>
> This isn't typically the case, actually. 4.x has in fact been very
> good in this regard.
What about between 3.x and 4.x ? And 5.x is going to be yet another
major change.
On Thu, 18 Oct 2001, Mike Smith wrote:
> > Well, honestly, FreeBSD makes the life of the developers of third-party
> > binary-only drivers fairly difficult.
>
> It does? On the whole, actually, I'd say we do a pretty good job of
> making it easy.
>
> > The reason is that there
> > are a lot
Tim,
Your license with SBS for the DDK would prevent you from posting your
code. If you read through it, you'll find that it prohibits the release
of any of their DDK code under any circumstances. You could release
everything EXCEPT the API for the card that SBS provides and offer the
rest in o
> Well, honestly, FreeBSD makes the life of the developers of third-party
> binary-only drivers fairly difficult.
It does? On the whole, actually, I'd say we do a pretty good job of
making it easy.
> The reason is that there
> are a lot of API changes happening between the releases (take
> Juli
Ted Mittelstaedt wrote:
>
> >From: Doug Hass [mailto:[EMAIL PROTECTED]]
> >The lack of flexibility in accepting various requirements illustrates the
> >difference between an OS WITH legs in the market and one WITHOUT legs.
> >
> >Much to my chagrin, FreeBSD continues to fall more and more into th
- Original Message -
From: "Tim Wiess" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, October 19, 2001 7:12 AM
Subject: Re: FYI
> > If anyone has an interest in adding support for the SBS WAN cards to
> > FreeBSD, feel free to contact m
> If anyone has an interest in adding support for the SBS WAN cards to
> FreeBSD, feel free to contact me. I'll be glad to help.
I'm actually working on a driver for the SBS WANic 600 and 800 cards.
There is still a lot of work and testing to be done, but (assuming there
are no problems with the
> If anyone has an interest in adding support for the SBS WAN cards to
> FreeBSD, feel free to contact me. I'll be glad to help.
I'm actually working on a driver for the SBS WANic 600 and 800 cards.
There is still a lot of work and testing to be done, but (assuming there
are no problems with the
Doug Hass wrote:
> It's not a generalization at all. Honestly, compared to the market
> traction that Linux, VxWorks, Solaris and others have, FreeBSD is
> definitely without legs. The WAN card and RAS card markets are good
> examples of where the attitude toward "BSD-licensed code or bust" has
> >You're a) misrepresenting the project, b) dismissing the opinions and
> >statements of others that are arguably more in touch with the project,
> >and c) you won't let this stupid thread die.
>
> I do not feel that this thread is stupid.
This much is obvious. You are, however, largely alone
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED]]On Behalf Of Mike Smith
>Sent: Wednesday, October 17, 2001 10:32 PM
>To: Ted Mittelstaedt
>Cc: Doug Hass; Leo Bicknell; Jim Bryant; MurrayTaylor;
>[EMAIL PROTECTED]; [EMAIL PROTECTED]
>Subjec
>-Original Message-
>From: Bill Fumerola [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, October 17, 2001 11:13 PM
>To: Ted Mittelstaedt
>Cc: Doug Hass; Mike Smith; Leo Bicknell; Jim Bryant; MurrayTaylor;
>[EMAIL PROTECTED]; [EMAIL PROTECTED]
>Subject: Re: FYI
>
>
On Wed, Oct 17, 2001 at 10:51:25PM -0700, Ted Mittelstaedt wrote:
> When we have a choice, we take the BSD code and improve it as necessary.
> Otherwise, we take what we can get. Sometimes, even, companies that release
> the stuff
> closed source end up opening it up when they see that by doing
>-Original Message-
>From: Doug Hass [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, October 17, 2001 10:20 AM
>To: Mike Smith
>Cc: Ted Mittelstaedt; Leo Bicknell; Jim Bryant; MurrayTaylor;
>[EMAIL PROTECTED]; [EMAIL PROTECTED]
>Subject: Re: FYI
>
>I'm glad
> >Doug; I would recommend against falling for Ted's flamebait here, since
> >that's really all it is.
>
> That's silly, what did you find in it that's flamebait? I think you didn't
> read it.
You're a) misrepresenting the project, b) dismissing the opinions and
statements of others that are
>-Original Message-
>From: Mike Smith [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, October 17, 2001 9:46 AM
>To: Doug Hass
>Cc: Ted Mittelstaedt; Leo Bicknell; Jim Bryant; MurrayTaylor;
>[EMAIL PROTECTED]; [EMAIL PROTECTED]
>Subject: Re: FYI
>
>
>> >
>-Original Message-
>From: Doug Hass [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, October 17, 2001 11:10 AM
>To: void
>Cc: Mike Smith; Ted Mittelstaedt; Leo Bicknell; Jim Bryant;
>MurrayTaylor; [EMAIL PROTECTED]; [EMAIL PROTECTED]
>Subject: Re: FYI
>
>
>
>-Original Message-
>From: Doug Hass [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, October 17, 2001 9:19 AM
>To: Ted Mittelstaedt
>Cc: Leo Bicknell; Jim Bryant; MurrayTaylor; [EMAIL PROTECTED];
>[EMAIL PROTECTED]
>Subject: RE: FYI
>
>
>> Doug, in the enti
At 12:50 PM -0700 10/17/01, Jordan Hubbard wrote:
>I fully support your idea of offering a "bounty" to anyone writing
>drivers for your cards and think you're being more than generous in
>offering it. I wish more vendors would do that and I'm sorry that
>this discussion has gotten as polarized as
In message <[EMAIL PROTECTED]>, Jordan Hubbard writes:
>I fully support your idea of offering a "bounty" to anyone writing
>drivers for your cards and think you're being more than generous in
>offering it. I wish more vendors would do that and I'm sorry that
>this discussion has gotten as polari
> We certainly support the right for companies to protect their intellectual
> property in whatever way they see fit, even if the FreeBSD community does
> not.
Oh my. I can see that we've gone somewhat polemic here.
As someone who's been around since the very beginning, I think I can
fairly sta
Let me cut through all this with a bit of experience if you permit:
1. BSD licensed sources are undoubtedly always preferred.
2. Other open-source licences are the best alternative.
3. closed source solutions are always risky because you don't know
if the company will be willing to, or even
If you didn't say it, then you weren't the one I was talking about, was I?
:-)
I got several other private mails saying that BSD licensed code was the
one and only way, and 2 or 3 mails (from Ben, among others) saying that
BSD-licensed was preferred.
Either approach is as flawed as someone who
* Doug Hass <[EMAIL PROTECTED]> [011017 12:51] wrote:
> > > If anyone has an interest in adding support for the SBS WAN cards to
> > > FreeBSD, feel free to contact me. I'll be glad to help.
> >
> > Just package your driver with your cards, or stick it on your support
> > site. The whole point
> > If anyone has an interest in adding support for the SBS WAN cards to
> > FreeBSD, feel free to contact me. I'll be glad to help.
>
> Just package your driver with your cards, or stick it on your support
> site. The whole point being that you don't *have* to get your code into
> the tree;
> It's not a generalization at all. Honestly, compared to the market
> traction that Linux, VxWorks, Solaris and others have, FreeBSD is
> definitely without legs. The WAN card and RAS card markets are good
> examples of where the attitude toward "BSD-licensed code or bust" has
> resulted in Fre
> > We certainly support the right for companies to protect their intellectual
> > property in whatever way they see fit, even if the FreeBSD community does
> > not.
>
> Doug; I would recommend against falling for Ted's flamebait here, since
> that's really all it is. His characterisation of th
> > Doug, in the entire history of the FreeBSD project, when given a choice
> > between a better driver or code that is closed source, and a worse
> > driver that has open source, the FreeBSD community has never chosen the
> > driver or code with closed source. In fact I can only remember ONCE
>
> Doug, in the entire history of the FreeBSD project, when given a choice
> between a better driver or code that is closed source, and a worse
> driver that has open source, the FreeBSD community has never chosen the
> driver or code with closed source. In fact I can only remember ONCE
> that the
> Is there any way to get some of this - NOT under GPL and NOT under NDA?
> There's at least one person during this thread who was looking for a
> DS-3 card like a WANic 8xx You _did_ mention that some of the card modules
> in SAND are not under NDA?
All of the code is licensed under either the
t;; <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Wednesday, October 17, 2001 3:32 PM
Subject: RE: FYI
> >-Original Message-
> >From: [EMAIL PROTECTED]
> >[mailto:[EMAIL PROTECTED]]On Behalf Of Doug Hass
> >Sent: Tuesday, October 16, 2001 9:54 AM
>
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED]]On Behalf Of Doug Hass
>Sent: Tuesday, October 16, 2001 9:54 AM
>To: Ted Mittelstaedt
>Cc: Leo Bicknell; Jim Bryant; MurrayTaylor; [EMAIL PROTECTED];
>[EMAIL PROTECTED]
>Subject: RE: FYI
>
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED]]On Behalf Of Julian Elischer
>Sent: Tuesday, October 16, 2001 5:29 PM
>To: Doug Hass
>Cc: Ted Mittelstaedt; Jim Bryant; MurrayTaylor;
>[EMAIL PROTECTED]; [EMAIL PROTECTED]; Alfred
>S
Better than a published interface and white paper, we also provide the
direct code itself. You could certainly make a netgraph/SAND interface
module.
Doug
On Tue, 16 Oct 2001, Julian Elischer wrote:
>
>
> On Tue, 16 Oct 2001, Doug Hass wrote:
>
> > > The "hardware API" or the actual registe
On Tue, 16 Oct 2001, Len Conrad wrote:
> Unfortunately, I still looking for somebody who actually uses SBEI and
> Cyclades T1 boards with FreeBSD.
With IBM 2210 series routers going for well under $100 on the used market
I can't see why anyone would opt for a host based solution.
The people with
On Tue, Oct 16, 2001 at 06:35:43PM -0500, Len Conrad wrote:
> Unfortunately, I still looking for somebody who actually uses SBEI and
> Cyclades T1 boards with FreeBSD.
I ran across them earlier when looking for what T1 boards were out
there. Their boards seem nice, and they do have a driver, in
>If there's a published interface, we could make a netgraph/SAND interface
>module
I think it's better use of hackers' time to look at vendors who already
support FreeBSD, such as SBEI and Cyclades, and see why their support for
FreeBSD, while apparently useful, is behind the functionality the
On Tue, 16 Oct 2001, Doug Hass wrote:
> > The "hardware API" or the actual register interface code, is a binary-only
> > module that is "snapped in" to SAND. SAND is GPL and is similar to the
> > FreeBSD Netgraph module - it provides all the higher-level protocol stuff,
> > like
> > Frame Rela
> As someone else pointed out in this forum, the Hitachi chipset is an
> older design. I'm sure that it's probably possible today to design a
> sync controller chip that sells for a lot less than the Hitachi part,
> perhaps even under the $30 level. Certainly, async chips sell at that
> level in
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED]]On Behalf Of Doug Hass
>Sent: Tuesday, October 16, 2001 7:28 AM
>To: Ted Mittelstaedt
>Cc: Leo Bicknell; Jim Bryant; MurrayTaylor; [EMAIL PROTECTED];
>[EMAIL PROTECTED]
>Subject: RE: FYI
>
> There is depending on the price. I'll freely admit however that I have not
> priced the competitive serial sync cards that are currently supported
> under FreeBSD, so I don't know how the WANic 400 or 500 stacks up against
> them. For all I know right now there's someone just bringing a T1 int
> The "hardware API" or the actual register interface code, is a binary-only
> module that is "snapped in" to SAND. SAND is GPL and is similar to the
> FreeBSD Netgraph module - it provides all the higher-level protocol stuff,
> like
> Frame Relay, PPP, HDLC, and such. SAND goes between the OS T
>-Original Message-
>From: Doug Hass [mailto:[EMAIL PROTECTED]]
>Sent: Monday, October 15, 2001 8:56 AM
>To: Leo Bicknell
>Cc: Ted Mittelstaedt; Jim Bryant; MurrayTaylor;
>[EMAIL PROTECTED]; [EMAIL PROTECTED]
>Subject: Re: FYI
>
>
>In a private e-mail,
>-Original Message-
>From: Doug Hass [mailto:[EMAIL PROTECTED]]
>Sent: Monday, October 15, 2001 8:04 AM
>To: Leo Bicknell
>Cc: Ted Mittelstaedt; Jim Bryant; MurrayTaylor;
>[EMAIL PROTECTED]; [EMAIL PROTECTED]; Alfred
>Shippen
>Subject: Re: FYI
>
>
>>
>-Original Message-
>From: Doug Hass [mailto:[EMAIL PROTECTED]]
>Sent: Monday, October 15, 2001 6:53 AM
>To: Ted Mittelstaedt
>Cc: Jim Bryant; MurrayTaylor; [EMAIL PROTECTED];
>[EMAIL PROTECTED]; Alfred Shippen
>Subject: RE: FYI
>
Hi Doug,
I'm going to a
>-Original Message-
>From: Andrew C. Hornback [mailto:[EMAIL PROTECTED]]
>Sent: Monday, October 15, 2001 2:59 PM
>To: Doug Hass; Ted Mittelstaedt
>Cc: Jim Bryant; MurrayTaylor; [EMAIL PROTECTED];
>[EMAIL PROTECTED]; Alfred Shippen
>Subject: RE: FYI
>
&g
> > 1) FreeBSD users can still get the WANic 400 and RISCom cards from the
> > second hand market, as another person mentioned.
>
> What is wrong with THIS picture? You're telling people to purchase used
> hardware, instead of purchasing components from your company? *shakes his
> head*
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Doug Hass
> Sent: Monday, October 15, 2001 9:53 AM
> To: Ted Mittelstaedt
> Cc: Jim Bryant; MurrayTaylor; [EMAIL PROTECTED];
> [EMAIL PROTECTED]; Alfred Shippen
> Subject: RE: F
In a private e-mail, Leo writes:
> You offered a discount on these boards on the list. If you think there
> is a real opportunity to sell these to the *BSD crowd, I recomend you
> take that 15% (or some part of it) and offer to partially fund a driver
> developer. There are many freelance progr
> Would your agreements allow you to provide resources to a small
> number of developers (under NDA and all that of course) to produce
> drivers that you would then release in binary form (eg a kernel
> module) under a free license?
It sure would.
> If you cannot release the source code to your
On Mon, Oct 15, 2001 at 08:53:14AM -0500, Doug Hass wrote:
> We are bound by third party agreements and are not allowed to release any
> more free code (legally) than we already have. If we were not restricted
> by SBS, Trillium, and Rockwell (among others), we would release all of the
> code und
> And if you want to sell these to FreeBSD users then make your Linux driver
> source (not the SAND stuff) available so that we can mod it into our own
> driver. Many other companies do this and as a matter of fact, we (meaning
> FreeBSD) have even found bugs in crummy Linux drivers that have bee
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED]]On Behalf Of Doug Hass
>Sent: Sunday, October 14, 2001 7:23 PM
>To: Jim Bryant
>Cc: Ted Mittelstaedt; [EMAIL PROTECTED]; MurrayTaylor;
>[EMAIL PROTECTED]; [EMAIL PROTECTED]; Alfred
>Shippen
>
Also--understand that the replacement for the 400 and 405 is a
multi-interface card (supports all of the wiring specs instead of just 1),
and costs virtually the same (or less as a reseller or in volume) than the
400/405 did.
Doug
On Sun, 14 Oct 2001, Jim Bryant wrote:
> No offense to you or yo
No offense taken--if I was in a position to need the 400 series cards, I'd
be snapping up all the used and auction lots I could. Nortel just
auctioned off about 1000 of them, so I'd expect that there will be a glut
on the used market.
If money is the only concern, those cards should be available
No offense to you or your sales partners, but the way I see it, this means that tons
of these will be available for a song on eBay
soon, and will be in the hands of a lot of FreeBSD and Linux people [not all of which
can afford top-of-the-line all of the time].
Doug Hass wrote:
> Ted,
>
> We
urrayTaylor;
> >[EMAIL PROTECTED]; [EMAIL PROTECTED]
> >Cc: Alfred Shippen
> >Subject: Re: FYI
> >
> >
> >I'm providing this to the people whose addresses appear in the original
> >messages. My apologies if this gets cross-posted or sent multiple times
> >
gt;[EMAIL PROTECTED]; [EMAIL PROTECTED]
>Cc: Alfred Shippen
>Subject: Re: FYI
>
>
>I'm providing this to the people whose addresses appear in the original
>messages. My apologies if this gets cross-posted or sent multiple times
>to the same place. As I mention below, the W
I'm providing this to the people whose addresses appear in the original
messages. My apologies if this gets cross-posted or sent multiple times
to the same place. As I mention below, the WANic 400 series cards and all
of the RISCom/N2 series cards are now End Of Life, and only available in
speci
"Jeroen C. van Gelderen" wrote:
>
> Warner Losh wrote:
> >
> > In message <[EMAIL PROTECTED]> Warner Losh writes:
> > : RSA Security Releases RSA Encryption Algorithm into Public Domain
> >
> > Note that other information at the site says that RSAREF isn't
> > released into the public domain. It
On Thu, 7 Sep 2000, Peter Wemm wrote:
> Mike Silbersack wrote:
> > Ok, now I have a question. Using STARTTLS with sendmail is obviously OK
> > for us, since sendmail got the export liscense. However, AFAIK, qmail and
> > postfix have obtained no such permission.
>
> Postfix has done the BXA h
Mike Silbersack wrote:
>
> On Wed, 6 Sep 2000, Warner Losh wrote:
>
> > http://www.rsasecurity.com/news/pr/000906-1.html
> >
> > RSA Security Releases RSA Encryption Algorithm into Public Domain
>
> Ok, now I have a question. Using STARTTLS with sendmail is obviously OK
> for us, since sendma
> Somehow I rather doubt they're trying to trick people into using RSA for
> the next week, and then going on a mass lawsuit spree.
No idea about RSA motives, but "Submarice patents" are a well known strategem.
AFAIR owners of compress.c registered it, then published it, & only years later
tried
On Wed, 6 Sep 2000, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Warner Losh writes:
> : RSA Security Releases RSA Encryption Algorithm into Public Domain
>
> Note that other information at the site says that RSAREF isn't
> released into the public domain. Its use is still governed by
>
From the rsa website (the quiz, hey- who can resist a free T-Shirt)
there is the following tidbit...
> With the patent expiration, software developers are now free to develop
> their own implementation of the RSA algorithm from scratch. However,
> RSA BSAFE and RSAREF code is still proprietary
Mike Silbersack wrote:
>
> On Wed, 6 Sep 2000, Jeroen C. van Gelderen wrote:
>
> > [1] The press release talk about RSADSI "waiving its
> > rights to enforce the RSA patent for any development
> > activities"
> >
> > This is very cunning as the patent never actually
> > covered d
1 - 100 of 105 matches
Mail list logo
