Greg Lehey wrote:
Do you have small images of this FS, as well as header files that
are redistributable (e.g. BSD license) and/or code?
If you have the tools sources (e.g. newfs, fsck, etc.), this would
be useful, as well, since I could vnconfig a device and recreate an
empty FS image
On Saturday, 15 December 2001 at 0:39:32 -0800, Terry Lambert wrote:
Greg Lehey wrote:
Do you have small images of this FS, as well as header files that
are redistributable (e.g. BSD license) and/or code?
If you have the tools sources (e.g. newfs, fsck, etc.), this would
be useful, as
Brooks Davis wrote:
There was a commit to current a few hours ago disabling hardware
checksums on recieve due to corruption problems. It will be MFC'd in
three days though it's a two line fix so you could apply it your self:
* David Greenman [EMAIL PROTECTED] [011215 03:12] wrote:
Brooks Davis wrote:
There was a commit to current a few hours ago disabling hardware
checksums on recieve due to corruption problems. It will be MFC'd in
three days though it's a two line fix so you could apply it your self:
I am playing with a driver for the Broadcom 5700/5701.
It recognizes the 5700 in my 3Com cards OK, but seems to screw up the
TCP checksum.
Switching off hardware checksum capability fixes it.
Does anyone know the details of which stepping this stuff worked on?
I haven't nailed down the
* David Greenman [EMAIL PROTECTED] [011215 03:12] wrote:
Brooks Davis wrote:
There was a commit to current a few hours ago disabling hardware
checksums on recieve due to corruption problems. It will be MFC'd in
three days though it's a two line fix so you could apply it your self:
hi,
I found this piece of code in boot0.s, is it possible
if you could explain me a bit about it.
.set NHRDRV,0x475# Number of hard drives
The hex value comes out to: 1141.
Does that mean, that this is the amound of maximum
hard drives a user can have on FreeBSD?
If that is so, is
David Greenman wrote:
I believe you will find that the problem is related to the firmware
handling of VLAN tagging, and that the problem only exists if VLAN
tagging is enabled.
You would believe wrongly, then, because the problem that I was seeing did
not involve VLAN tags.
OK; it was
Greg Lehey wrote:
Unfortunately, it's still copyrighted. You need an SCO license; want
to go and get one of them? It doesn't cost anything, but I can't give
the software to anybody who hasn't agreed to the conditions.
8.4(b) says you can't give it to anyone, even if they do have the
David Greenman wrote:
Alfred Perlstein wrote:
You're probably incorrect, it doesn't matter if vlan tags are active
or not, it's most likely wheather or not the firmware is being asked
to handle them at all.
I would think it would get the checksum wrong most of the time if that
were the
We currently have a MD5 driver, but no SHA1 driver, even though
we have SHA1 as part of libmd. So I took md5.c from /usr/src/sbin/md5
and made sha1.c as well as a respective man page. Attached is the
source file, the manual page for it, as well as a makefile.
Hope this is useful and makes its
On Saturday 15 December 2001 11:34 am, Mike Wiacek wrote:
We currently have a MD5 driver, but no SHA1 driver, even though
we have SHA1 as part of libmd. So I took md5.c from
/usr/src/sbin/md5 and made sha1.c as well as a respective man page.
Attached is the source file, the manual page for
Hiten Pandya wrote:
I found this piece of code in boot0.s, is it possible
if you could explain me a bit about it.
.set NHRDRV,0x475# Number of hard drives
The hex value comes out to: 1141.
Does that mean, that this is the amound of maximum
hard drives a user can have on
On 15-Dec-2001 Dominic Marks wrote:
Why not have one program for all the supported hash algorithms as
opposed to individual ones for each (md5, sha1) ?
You could use something like:
hash -a md5 /some/file
hash -a sha1 /some/other/file
Conceivably a fairly simple script or two
On Fri, Dec 14, 2001 at 11:03:49PM +0800, Rafter Man wrote:
2. I hope that in the furture the FreeBSD developers will rewrite the system
in C++.
Geez, talk about a bleak outlook for the future. I see myself flying over
a frozen Hell on the back of a pig before that happens.
--
George C A
English
¦æ·Rªº¯u¿Í ºV¤Ñ°óªºªù
·R¬O«í¤[§Ô@¡A¤S¦³®¦·O¡A·R¬O¤£¶ú§ª¡C·R¬O¤£¦Û¸Ø¡A¤£±i¨g¡A¤£°µ®`²Ûªº¨Æ¡C¤£¨D¦Û¤vªº¯q³B¡A¤£»´©öµo«ã¡A¤£pºâ¤H®aªº´c¡A¤£³ßÅw¤£¸q¡A¥u³ßÅw¯u²z¡C¤Z¨Æ¥]®e¡A¤Z¨Æ¬Û«H¡A¤Z¨Æ¬ß±æ¡A¤Z¨Æ§Ô@¡A¤Z¨Æn§Ô@¡A·R¬O¥Ã¤£¤î®§¡C
On Sat, Dec 15, 2001 at 03:26:27PM +, George Reid wrote:
On Fri, Dec 14, 2001 at 11:03:49PM +0800, Rafter Man wrote:
2. I hope that in the furture the FreeBSD developers will rewrite the system
in C++.
Geez, talk about a bleak outlook for the future. I see myself flying over
a
* Wilko Bulte ([EMAIL PROTECTED]) wrote:
On Sat, Dec 15, 2001 at 03:26:27PM +, George Reid wrote:
On Fri, Dec 14, 2001 at 11:03:49PM +0800, Rafter Man wrote:
2. I hope that in the furture the FreeBSD developers will rewrite
the system in C++.
Geez, talk about a bleak outlook
On Sat, Dec 15, 2001 at 11:58:14AM +, Dominic Marks wrote:
On Saturday 15 December 2001 11:34 am, Mike Wiacek wrote:
We currently have a MD5 driver, but no SHA1 driver, even though
we have SHA1 as part of libmd. So I took md5.c from
/usr/src/sbin/md5 and made sha1.c as well as a
On Sat, Dec 15, 2001 at 06:12:53PM +0100, Alson van der Meulen wrote:
Why not have one program for all the supported hash algorithms as
opposed to individual ones for each (md5, sha1) ?
You could use something like:
hash -a md5 /some/file
hash -a sha1 /some/other/file
It's
subscribe
Jorge Augusto Teles - JFreeBSD
Tecnólogo em Processamento de Dados -
FATEC - Taquaritinga
emails:
[EMAIL PROTECTED]
[EMAIL PROTECTED]
__
Quer ter seu próprio endereço na Internet?
Garanta já o seu e ainda ganhe
On Fri, 14 Dec 2001, Jordan Hubbard wrote:
{.. snip ..}
2. I hope that in the furture the FreeBSD developers
will rewrite the system in C++.
God, I certainly hope NOT.
Jordan, I do agree absolutely and hope your hopes will come true ... :-)
Konrad
Konrad Heuer
David Greenman wrote:
I am playing with a driver for the Broadcom 5700/5701.
It recognizes the 5700 in my 3Com cards OK, but seems to screw up the
TCP checksum.
Switching off hardware checksum capability fixes it.
Does anyone know the details of which stepping this stuff worked on?
I
At 2:56 PM -0800 12/12/01, Jordan Hubbard wrote:
The only thing I get is a math exception because closeprob is zero
since no -c option was given.
Can you provide some sample parameters please ?
Hmmm, how strange, now that I look at the code it's obvious that a
divide by zero will occur with
At 8:19 PM -0800 12/12/01, Jordan Hubbard wrote:
To be clear, what exactly are you doing?
It sounds like you're exporting something from freebsd, mounting it on OSX
and running this tool on OSX against the filesystem exported from freebsd ?
If so, What mount options? NFSv2 or v3?
That is
At 10:08 PM -0800 12/12/01, Matthew Dillon wrote:
Ok, here is the latest patch for -stable. Note that Kirk comitted a
slightly modified version of the softupdates fix to -current already
(the VOP_FSYNC stuff), which I will be MFCing in 3 days.
This still doesn't fix all the
In a message dated 12/15/2001 1:07:28 PM Eastern Standard Time, .@babalo.ru
writes:
At 06:41 PM 12/14/2001, you wrote:
[EMAIL PROTECTED] writes:
Try to front end your machine with a switch...the 5 cards is most
likely your
problem. With each device you increase your bus
Sherlock Wemm writes
FYI, this is another [EMAIL PROTECTED] clone.
and your point is? I dont see any of you helping this guy out; you apparently
are a lot better at tracking me down than problems with ethernet drivers,
which dont ever seem to get addressed unless some company that one of
Hello All.
The subject asks it all. Sorry if this is off-topic.
One other Q, as long as I'm posting: For those releases that have both a
RELENG_X_Y and a RELENG_X_Y_BP branch, what's the difference? AFAIK, the
first is for bug fixes; what's the second for?
Well, now one more: What are RELENG_X
If memory serves me right, D J Hawkey Jr wrote:
One other Q, as long as I'm posting: For those releases that have both a
RELENG_X_Y and a RELENG_X_Y_BP branch, what's the difference? AFAIK, the
first is for bug fixes; what's the second for?
RELENG_X_Y_BP represents the Branch Point where the
Sorry, I mis-wrote:
On Dec 15, at 01:12 PM, D J Hawkey Jr wrote:
One other Q, as long as I'm posting: For those releases that have both a
RELENG_X_Y and a RELENG_X_Y_BP branch, what's the difference? AFAIK, the
first is for bug fixes; what's the second for?
^ should
D J Hawkey Jr wrote:
Hello All.
The subject asks it all. Sorry if this is off-topic.
I won't answer the other questions because they were already
answered. The subject question, though..
The Attic is the directory where deleted files are moved.
This is necessary, since a soruce code
On 15-Dec-01 Hiten Pandya wrote:
hi,
I found this piece of code in boot0.s, is it possible
if you could explain me a bit about it.
.set NHRDRV,0x475# Number of hard drives
The hex value comes out to: 1141.
Does that mean, that this is the amound of maximum
hard drives a user
On Saturday, 15 December 2001 at 3:18:33 -0800, Terry Lambert wrote:
Greg Lehey wrote:
Unfortunately, it's still copyrighted. You need an SCO license; want
to go and get one of them? It doesn't cost anything, but I can't give
the software to anybody who hasn't agreed to the conditions.
Hi:
I've installed the python-2.1.1 package on a 4.3-RELEASE system,
and in the process of building zope, discovered that python is
configured with:
/* Define if the compiler provides a wchar.h header file. */
#define HAVE_WCHAR_H 1
...Which I gather is a lie for 4.3. I'm assuming that
David Greenman wrote:
In any case, disabling it is what ClickArray ended up doing, as well,
for the Tigon II, until the firmware could be fixed.
We're talking about the Tigon III (bge driver for Broadcom BCM5700/BCM5701).
Crap. Thanks for the info.
Have you manually calculated the
John Baldwin wrote:
No. It's the offset in memory of the number of hard drives in the BIOS. The
BIOS has a data segment at 0x40, and at 0x40:0x75 (whose physical address is
0x475) it has a byte which is a count of the number of hard drives installed.
Specifically, Hiten, see:
Page
On Sun, Dec 16, 2001 at 03:56:02AM +0300, .@babolo.ru wrote:
different results. btw, the if_dc driver is one of the drivers optimized for
the alpha (note the m_devget calls)..and can use a bit of tuning. my
this has been fixed recently in both stable and current.
luigi
To
David Greenman wrote:
In any case, disabling it is what ClickArray ended up doing, as well,
for the Tigon II, until the firmware could be fixed.
We're talking about the Tigon III (bge driver for Broadcom BCM5700/BCM5701).
Crap. Thanks for the info.
Have you manually calculated the
[EMAIL PROTECTED] writes:
In a message dated 12/15/2001 1:07:28 PM Eastern Standard Time, .@babalo.ru
writes:
At 06:41 PM 12/14/2001, you wrote:
[EMAIL PROTECTED] writes:
Try to front end your machine with a switch...the 5 cards is most
likely your
problem. With each
On 15-Dec-2001 Kris Kennaway wrote:
Or just ln -sf /usr/bin/openssl /usr/bin/sha1
OpenSSL already checks the name it's invoked under and behaves
accordingly.
Does it grok the options for md5? :)
-s would be easy to simulate in a shell script.
-p would be much more difficult unless
David Greenman wrote:
Alfred Perlstein wrote:
You're probably incorrect, it doesn't matter if vlan tags are active
or not, it's most likely wheather or not the firmware is being asked
to handle them at all.
I would think it would get the checksum wrong most of the time if that
were the
:Once it runs aok for a few million operations, try concurrently running:
:
:#! /bin/sh
:while :
:do
: sync
: sleep 1
:done
:
:In OS X I used that to flush :) out a couple more bugs.
:
:--
:Conrad Minshall, [EMAIL PROTECTED], 408 974-2749
:Apple Computer, Mac OS X Core Operating Systems
In article by Greg Lehey:
[about if and how Caldera is enforcing the Ancient UNIX
http://www2.caldera.com/offers/ancient.html. Note also
that in fact they allow access to the code via
license described at http://www2.caldera.com/offers/ancient001/
In article by Greg Lehey:
That may be easier than you think. I'm copying Warren Toomey on
this. Warren is (a) a FreeBSD user and (b) the person who negotiated
these contracts in the first place. Warren, Peter is thinking of
porting the 2BSD file system (not sure whether that's UFS or the
45 matches
Mail list logo
