Daniel O'Connor wrote:
>
> On 28-Aug-99 Kris Kirby wrote:
> > > RS232? RS485? VERY cheap and the later is at least moderatly resistant to
> > > noise
> > Noise shouldn't be an issue. It's going to be handling "clean" data. By
> > cheap, I mean $5 a pop or so. I've got a few 3C503s that I feel l
On Fri, 27 Aug 1999, Matthew N. Dodd wrote:
> I will ask another question; "Anyone want to see what I've got so far?"
>
> http://www.jurai.net/~winter/mca/
>
> README.mca
> mca.diff
> mca.tar.gz
>
> MicroChannel Architecture System detected.
> ...
> m
On 28-Aug-99 Kris Kirby wrote:
> > RS232? RS485? VERY cheap and the later is at least moderatly resistant to
> > noise
> Noise shouldn't be an issue. It's going to be handling "clean" data. By
> cheap, I mean $5 a pop or so. I've got a few 3C503s that I feel like
> cutting into. I'm going to be
Daniel O'Connor wrote:
>
> On 28-Aug-99 Kris Kirby wrote:
> > It's not a bandwidth issue; it's a speed issue. I'm trying to find an
> > extremely cheap way to get data in and out of a PC. I've got the
> > National Semiconductor application sheets for the 8392(?) and plan on
> > using one "cut
Julian Elischer wrote:
>
> plip?
>
Ideally, no. The ethernet card makes the data rather easy to handle into
other means (like a radio modem). It's already serialized, packetized,
has a MAC address for a link address, and it's easy to get seperate RX
and TX lines out of the card, even if it is 10
USB?
http://www.activewire.com/ has a nice board that does I2C as well. With
a bit of plumbing you should be able to stream out 100kb a second.
Nick
On Fri, 27 Aug 1999, Julian Elischer wrote:
> plip?
>
>
> On Fri, 27 Aug 1999, Matthew N. Dodd wrote:
>
> > On Fri, 27 Aug 1999, Kris Kirby w
Matthew N. Dodd wrote:
>
> On Fri, 27 Aug 1999, Kris Kirby wrote:
> > It's not a bandwidth issue; it's a speed issue. I'm trying to find an
> > extremely cheap way to get data in and out of a PC.
>
> How about an I2C bus?
>
> (Or is that -too- slow?)
I'll have to admit I'm totally ignorant of w
> The trade rags here insist it has already happened: M$ stopped 64 bit Alpha
> NT. Beats me if it is true or not.
Here's the confusing part: they say M$ stopped making 64 bit Alpha
NT, but some say they are actually developing Win2000 64 bit for Alpha's.
Since 2000 is NT based, you'd thin
On 28-Aug-99 Kris Kirby wrote:
> > RS232? RS485? VERY cheap and the later is at least moderatly resistant to
> > noise
> Noise shouldn't be an issue. It's going to be handling "clean" data. By
> cheap, I mean $5 a pop or so. I've got a few 3C503s that I feel like
> cutting into. I'm going to b
Daniel O'Connor wrote:
>
> On 28-Aug-99 Kris Kirby wrote:
> > It's not a bandwidth issue; it's a speed issue. I'm trying to find an
> > extremely cheap way to get data in and out of a PC. I've got the
> > National Semiconductor application sheets for the 8392(?) and plan on
> > using one "cut
Julian Elischer wrote:
>
> plip?
>
Ideally, no. The ethernet card makes the data rather easy to handle into
other means (like a radio modem). It's already serialized, packetized,
has a MAC address for a link address, and it's easy to get seperate RX
and TX lines out of the card, even if it is 1
Matthew N. Dodd wrote:
>
> On Fri, 27 Aug 1999, Kris Kirby wrote:
> > It's not a bandwidth issue; it's a speed issue. I'm trying to find an
> > extremely cheap way to get data in and out of a PC.
>
> How about an I2C bus?
>
> (Or is that -too- slow?)
I'll have to admit I'm totally ignorant of
> The trade rags here insist it has already happened: M$ stopped 64 bit Alpha
> NT. Beats me if it is true or not.
Here's the confusing part: they say M$ stopped making 64 bit Alpha
NT, but some say they are actually developing Win2000 64 bit for Alpha's.
Since 2000 is NT based, you'd thi
On 28-Aug-99 Kris Kirby wrote:
> It's not a bandwidth issue; it's a speed issue. I'm trying to find an
> extremely cheap way to get data in and out of a PC. I've got the
> National Semiconductor application sheets for the 8392(?) and plan on
> using one "cut in half": Half duplex, but split in
After all the stuff that has been said on the last locking thread, I
think it's better to restate the case than follow up.
It's obvious from the messages in the last thread that a number of
otherwise clever people have little understanding or knowledge of the
concepts of file locking. I'm appendi
On Wednesday, 25 August 1999 at 18:25:31 +, Terry Lambert wrote:
>>> 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
On Wednesday, 25 August 1999 at 19:53:22 -0400, Christian Kuhtz wrote:
> 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
ope
Mark Ovens wrote:
>
> On Fri, Aug 27, 1999 at 06:29:21PM -0700, Jordan K. Hubbard wrote:
> > > marder-1:/usr/marko{57}% ./a.out
> > > short == 2
> > > int == 4
> > > long == 4
> > > long long == 8
> > > marder-1:/usr/marko{57}%
> >
> > But on the Alpha:
> >
> > j...@beast-> ./foo
> > short == 2
On 28-Aug-99 Kris Kirby wrote:
> It's not a bandwidth issue; it's a speed issue. I'm trying to find an
> extremely cheap way to get data in and out of a PC. I've got the
> National Semiconductor application sheets for the 8392(?) and plan on
> using one "cut in half": Half duplex, but split i
After all the stuff that has been said on the last locking thread, I
think it's better to restate the case than follow up.
It's obvious from the messages in the last thread that a number of
otherwise clever people have little understanding or knowledge of the
concepts of file locking. I'm append
> Tonight while testing my rc file changes I decided to interrupt the spl
>ash
>screen display I have to see the boot messages. I hit scroll lock to do
>this, and it killed the splash screen, but when I went to log in the
>keyboard on the console was pretty much fubar. Every key was mapped t
> On Fri, Aug 27, 1999 at 08:45:31PM -0400, Sergey Babkin wrote:
> > Thomas David Rivers wrote:
> >
> > > Microsoft needs a "business quality" version of Windows,
> > > which it claims is Windows/2000. That version of Windows
> > > could benefit from a 64-bit port, if for marketing only; but
On Wednesday, 25 August 1999 at 18:25:31 +, Terry Lambert wrote:
>>> 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
On Wednesday, 25 August 1999 at 19:53:22 -0400, Christian Kuhtz wrote:
> 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
op
Mark Ovens wrote:
>
> On Fri, Aug 27, 1999 at 06:29:21PM -0700, Jordan K. Hubbard wrote:
> > > marder-1:/usr/marko{57}% ./a.out
> > > short == 2
> > > int == 4
> > > long == 4
> > > long long == 8
> > > marder-1:/usr/marko{57}%
> >
> > But on the Alpha:
> >
> > jkh@beast-> ./foo
> > short == 2
On Fri, Aug 27, 1999 at 06:29:21PM -0700, Jordan K. Hubbard wrote:
> > marder-1:/usr/marko{57}% ./a.out
> > short == 2
> > int == 4
> > long == 4
> > long long == 8
> > marder-1:/usr/marko{57}%
>
> But on the Alpha:
>
> j...@beast-> ./foo
> short == 2
> int == 4
> long == 8
> long long == 8
>
> marder-1:/usr/marko{57}% ./a.out
> short == 2
> int == 4
> long == 4
> long long == 8
> marder-1:/usr/marko{57}%
But on the Alpha:
j...@beast-> ./foo
short == 2
int == 4
long == 8
long long == 8
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" i
> Tonight while testing my rc file changes I decided to interrupt the spl
>ash
>screen display I have to see the boot messages. I hit scroll lock to do
>this, and it killed the splash screen, but when I went to log in the
>keyboard on the console was pretty much fubar. Every key was mapped
plip?
On Fri, 27 Aug 1999, Matthew N. Dodd wrote:
> On Fri, 27 Aug 1999, Kris Kirby wrote:
> > It's not a bandwidth issue; it's a speed issue. I'm trying to find an
> > extremely cheap way to get data in and out of a PC.
>
> How about an I2C bus?
>
> (Or is that -too- slow?)
>
> --
> | Matth
On Fri, Aug 27, 1999 at 08:45:31PM -0400, Sergey Babkin wrote:
> Thomas David Rivers wrote:
>
> > Microsoft needs a "business quality" version of Windows,
> > which it claims is Windows/2000. That version of Windows
> > could benefit from a 64-bit port, if for marketing only; but
> > I don'
On Sat, 28 Aug 1999, Peter Wemm wrote:
> Good stuff! People may ask "why bother?", but it gives us access to a
> heap of embedded POS systems that are stuck with OS/2 and Y2K
> nightmares.
Don't forget the PS/2 laptops that use MCA.
I'm sure the bottom has fallen out of that market and those mac
> On Fri, Aug 27, 1999 at 08:45:31PM -0400, Sergey Babkin wrote:
> > Thomas David Rivers wrote:
> >
> > > Microsoft needs a "business quality" version of Windows,
> > > which it claims is Windows/2000. That version of Windows
> > > could benefit from a 64-bit port, if for marketing only; bu
Zuidam, Hans wrote:
>
> Hi,
>
> The IA64 (merced) is a kind of VLIW (Very Large Instruction Word)
> processor. It is basically a complete new kind of systems architecture
> with a i686 (and of course a i586, ..., 4004) slapped on the side. The
> original processor design was done by HP. See:
>
"Matthew N. Dodd" wrote:
> But instead of lamely asking "Does FreeBSD support MCA?" or "When will
> someone finish MCA support?" (which I suppose is still a valid question.)
> I will ask another question; "Anyone want to see what I've got so far?"
[..]
> I'm planning on committing this stuff to -CU
Jim Bryant wrote:
> > I really don't know how people get started with this. HP has _never_ stated
> > that the chip will handle it; all they have stated is that HPUX applications
> > will continue to be supported.
> >
> > I suggest you people go read comp.arch for a while; there's a fair bit of
>
On Fri, Aug 27, 1999 at 06:29:21PM -0700, Jordan K. Hubbard wrote:
> > marder-1:/usr/marko{57}% ./a.out
> > short == 2
> > int == 4
> > long == 4
> > long long == 8
> > marder-1:/usr/marko{57}%
>
> But on the Alpha:
>
> jkh@beast-> ./foo
> short == 2
> int == 4
> long == 8
> long long == 8
>
Thomas David Rivers wrote:
> Microsoft needs a "business quality" version of Windows,
> which it claims is Windows/2000. That version of Windows
> could benefit from a 64-bit port, if for marketing only; but
> I don't think it would result in the volume of sales Intel
> is looking for.
A
> marder-1:/usr/marko{57}% ./a.out
> short == 2
> int == 4
> long == 4
> long long == 8
> marder-1:/usr/marko{57}%
But on the Alpha:
jkh@beast-> ./foo
short == 2
int == 4
long == 8
long long == 8
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in th
On Fri, 27 Aug 1999, Kris Kirby wrote:
> It's not a bandwidth issue; it's a speed issue. I'm trying to find an
> extremely cheap way to get data in and out of a PC.
How about an I2C bus?
(Or is that -too- slow?)
--
| Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD |
| win.
Matthew N. Dodd wrote:
>
> On Fri, 27 Aug 1999, Kris Kirby wrote:
> > I know there are drivers for the WaveLan card, but I'm looking at going
> > even slower (256Kb!).
> Why do you wnat to do this? If for bandwidht limiting you need look no
> further than 'dummynet'.
It's not a bandwidth issue
plip?
On Fri, 27 Aug 1999, Matthew N. Dodd wrote:
> On Fri, 27 Aug 1999, Kris Kirby wrote:
> > It's not a bandwidth issue; it's a speed issue. I'm trying to find an
> > extremely cheap way to get data in and out of a PC.
>
> How about an I2C bus?
>
> (Or is that -too- slow?)
>
> --
> | Matt
But instead of lamely asking "Does FreeBSD support MCA?" or "When will
someone finish MCA support?" (which I suppose is still a valid question.)
I will ask another question; "Anyone want to see what I've got so far?"
http://www.jurai.net/~winter/mca/
README.mca
mca
On Fri, Aug 27, 1999 at 08:45:31PM -0400, Sergey Babkin wrote:
> Thomas David Rivers wrote:
>
> > Microsoft needs a "business quality" version of Windows,
> > which it claims is Windows/2000. That version of Windows
> > could benefit from a 64-bit port, if for marketing only; but
> > I don
On Sat, 28 Aug 1999, Peter Wemm wrote:
> Good stuff! People may ask "why bother?", but it gives us access to a
> heap of embedded POS systems that are stuck with OS/2 and Y2K
> nightmares.
Don't forget the PS/2 laptops that use MCA.
I'm sure the bottom has fallen out of that market and those ma
Zuidam, Hans wrote:
>
> Hi,
>
> The IA64 (merced) is a kind of VLIW (Very Large Instruction Word)
> processor. It is basically a complete new kind of systems architecture
> with a i686 (and of course a i586, ..., 4004) slapped on the side. The
> original processor design was done by HP. See:
"Matthew N. Dodd" wrote:
> But instead of lamely asking "Does FreeBSD support MCA?" or "When will
> someone finish MCA support?" (which I suppose is still a valid question.)
> I will ask another question; "Anyone want to see what I've got so far?"
[..]
> I'm planning on committing this stuff to -C
Jim Bryant wrote:
> > I really don't know how people get started with this. HP has _never_ stated
> > that the chip will handle it; all they have stated is that HPUX applications
> > will continue to be supported.
> >
> > I suggest you people go read comp.arch for a while; there's a fair bit of
Hi,
I am getting very frequent panics (3 per day) on a 3.2-RELEASE server.:
Fatal trap 12: page fault while in kernel mode
mp_lock = 0002; cpuid = 0; lapic.id =
fault virtual address = 0xbfca0b0c
fault code = supervisor read, page not present
instruction pointer =
Thomas David Rivers wrote:
> Microsoft needs a "business quality" version of Windows,
> which it claims is Windows/2000. That version of Windows
> could benefit from a 64-bit port, if for marketing only; but
> I don't think it would result in the volume of sales Intel
> is looking for.
A
> As Wes Peters wrote ...
> > Mitch Collinsworth wrote:
> > >
> > > ?? I thought we had already established that neither Linux or NT runs
> > > on Merced, only HP-UX so far. I would certainly like to see a FBSD
> > > port as I imagine we will be seeing Merced-based systems here quite
> > > early
On Fri, 27 Aug 1999, Kris Kirby wrote:
> It's not a bandwidth issue; it's a speed issue. I'm trying to find an
> extremely cheap way to get data in and out of a PC.
How about an I2C bus?
(Or is that -too- slow?)
--
| Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD |
| [EM
Matthew N. Dodd wrote:
>
> On Fri, 27 Aug 1999, Kris Kirby wrote:
> > I know there are drivers for the WaveLan card, but I'm looking at going
> > even slower (256Kb!).
> Why do you wnat to do this? If for bandwidht limiting you need look no
> further than 'dummynet'.
It's not a bandwidth issu
But instead of lamely asking "Does FreeBSD support MCA?" or "When will
someone finish MCA support?" (which I suppose is still a valid question.)
I will ask another question; "Anyone want to see what I've got so far?"
http://www.jurai.net/~winter/mca/
README.mca
mc
On Thu, Aug 26, 1999 at 11:34:03PM -0700, Doug wrote:
> Tonight while testing my rc file changes I decided to interrupt
> the splash screen display I have to see the boot messages. I hit
[...]
> Obviously this is a "... well don't do that" case, but I'm not
> sure it should be fatal. Ho
As Wes Peters wrote ...
> Mitch Collinsworth wrote:
> >
> > ?? I thought we had already established that neither Linux or NT runs
> > on Merced, only HP-UX so far. I would certainly like to see a FBSD
> > port as I imagine we will be seeing Merced-based systems here quite
> > early on.
>
> Nope
Hi,
I am getting very frequent panics (3 per day) on a 3.2-RELEASE server.:
Fatal trap 12: page fault while in kernel mode
mp_lock = 0002; cpuid = 0; lapic.id =
fault virtual address = 0xbfca0b0c
fault code = supervisor read, page not present
instruction pointer =
>
> I am trying to compile a sync driver maintenance program on fbsd-stable. I
> keep getting compiler errors:
>
> ft1config.o: In function `run_interactive':
> ft1config.o(.text+0x565): undefined reference to `initscr'
> ft1config.o(.text+0x56a): undefined reference to `cbreak'
> ft1config.o(.t
I had written.
>>As a matter of fact, the standard version of merced includes the PA-RISC
>>engine along with an x86 instruction decoder.
To which you replied...
>Uh, no.
>
>The Merced does not do PA-RISC decoding in hardware. Period.
Wrong. I wish I could send you the Internal design pape
> As Wes Peters wrote ...
> > Mitch Collinsworth wrote:
> > >
> > > ?? I thought we had already established that neither Linux or NT runs
> > > on Merced, only HP-UX so far. I would certainly like to see a FBSD
> > > port as I imagine we will be seeing Merced-based systems here quite
> > > early
I am trying to compile a sync driver maintenance program on fbsd-stable. I
keep getting compiler errors:
ft1config.o: In function `run_interactive':
ft1config.o(.text+0x565): undefined reference to `initscr'
ft1config.o(.text+0x56a): undefined reference to `cbreak'
ft1config.o(.text+0x56f): undef
>If you think Microsoft doesn't have 64-bit NT in development for Merced,
>you're being awfully gullible.
I don't think anyone has suggested it's not being developed. Only that
NT is Not There today. (And that we'd all just love to have a FBSD
port available when systems start shipping! :-)
Jay West wrote:
>
> Keep in mind that the merced chip was not really designed or created by
> Intel at all.
No, you're confusing terms here. Merced is a particular chip, like
Tillamook is a specific Pentium. HP designed the 64-bit architecture
in the Merced, what will become the "IA64", but In
On Thu, Aug 26, 1999 at 11:34:03PM -0700, Doug wrote:
> Tonight while testing my rc file changes I decided to interrupt
> the splash screen display I have to see the boot messages. I hit
[...]
> Obviously this is a "... well don't do that" case, but I'm not
> sure it should be fatal. H
Mitch Collinsworth wrote:
>
> >> I recall a conversation not long ago with a sysadmin in the business
> >> school here. I was asking what their typical laptop configuration was
> >> and was told that some members of their faculty were quite particular
> >> about finding out what their colleagues
Mitch Collinsworth wrote:
>
> ?? I thought we had already established that neither Linux or NT runs
> on Merced, only HP-UX so far. I would certainly like to see a FBSD
> port as I imagine we will be seeing Merced-based systems here quite
> early on.
Nope, it was reported last week a group at I
As Wes Peters wrote ...
> Mitch Collinsworth wrote:
> >
> > ?? I thought we had already established that neither Linux or NT runs
> > on Merced, only HP-UX so far. I would certainly like to see a FBSD
> > port as I imagine we will be seeing Merced-based systems here quite
> > early on.
>
> Nop
>
> I am trying to compile a sync driver maintenance program on fbsd-stable. I
> keep getting compiler errors:
>
> ft1config.o: In function `run_interactive':
> ft1config.o(.text+0x565): undefined reference to `initscr'
> ft1config.o(.text+0x56a): undefined reference to `cbreak'
> ft1config.o(.
I had written.
>>As a matter of fact, the standard version of merced includes the PA-RISC
>>engine along with an x86 instruction decoder.
To which you replied...
>Uh, no.
>
>The Merced does not do PA-RISC decoding in hardware. Period.
Wrong. I wish I could send you the Internal design pap
I am trying to compile a sync driver maintenance program on fbsd-stable. I
keep getting compiler errors:
ft1config.o: In function `run_interactive':
ft1config.o(.text+0x565): undefined reference to `initscr'
ft1config.o(.text+0x56a): undefined reference to `cbreak'
ft1config.o(.text+0x56f): unde
>If you think Microsoft doesn't have 64-bit NT in development for Merced,
>you're being awfully gullible.
I don't think anyone has suggested it's not being developed. Only that
NT is Not There today. (And that we'd all just love to have a FBSD
port available when systems start shipping! :-)
Jay West wrote:
>
> Keep in mind that the merced chip was not really designed or created by
> Intel at all.
No, you're confusing terms here. Merced is a particular chip, like
Tillamook is a specific Pentium. HP designed the 64-bit architecture
in the Merced, what will become the "IA64", but I
In reply:
> On Fri, 27 Aug 1999, Sean Eric Fagan wrote:
>
> > In article
> >
> > you write:
> > Look, people, the Merced WILL NOT excuse PA-RISC code directly. It will be
> > done via emulation/translation, and only a certain particular OS will be
> > supported (HP-UX 11, I believe they stated
Mitch Collinsworth wrote:
>
> >> I recall a conversation not long ago with a sysadmin in the business
> >> school here. I was asking what their typical laptop configuration was
> >> and was told that some members of their faculty were quite particular
> >> about finding out what their colleagues
Mitch Collinsworth wrote:
>
> ?? I thought we had already established that neither Linux or NT runs
> on Merced, only HP-UX so far. I would certainly like to see a FBSD
> port as I imagine we will be seeing Merced-based systems here quite
> early on.
Nope, it was reported last week a group at
On Fri, 27 Aug 1999, Kris Kirby wrote:
> I know there are drivers for the WaveLan card, but I'm looking at going
> even slower (256Kb!).
Why do you wnat to do this? If for bandwidht limiting you need look no
further than 'dummynet'.
--
| Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | Fre
On Fri, Aug 27, 1999 at 01:33:03PM -0500, John Sconiers wrote:
>
> I was looking for followups to this thread and have searched the archives
> for more information without luck. I have a few questions. Has this
> project furthered any and where can one get the diffs / source??? Is
> there a web
Uhm, have any of you actually ever looked at src/sys/kern/vnode_if.src ?
Poul-Henning
In message <199908272018.qaa22...@shekel.mcl.cs.columbia.edu>, Erez Zadok write
s:
>In message <199908261727.kaa23...@apollo.backplane.com>, Matthew Dillon writes:
>[...]
>> I would ask two things though:
>
Maybe this is nit-picking, too, buth those are just
my 0.02 Euros...
Doug wrote in list.freebsd-hackers:
> -# this file, but rather in /etc/defaults/rc.conf. Please check this file
> +# this file, but rather in /etc/defaults/rc.conf. Please check that file
I'd prefer to keep it with two spaces
In reply:
> On Fri, 27 Aug 1999, Sean Eric Fagan wrote:
>
> > In article
><[EMAIL PROTECTED]>
>you write:
> > Look, people, the Merced WILL NOT excuse PA-RISC code directly. It will be
> > done via emulation/translation, and only a certain particular OS will be
> > supported (HP-UX 11, I belie
In message <199908261727.kaa23...@apollo.backplane.com>, Matthew Dillon writes:
[...]
> I would ask two things though:
>
> * First, please add comprehensive /* */ comments in front of each
> vfsnop_*() procedure explaining what it does, why it returns what
> it returns,
On Fri, 27 Aug 1999, Sean Eric Fagan wrote:
> In article
>
> you write:
> Look, people, the Merced WILL NOT excuse PA-RISC code directly. It will be
> done via emulation/translation, and only a certain particular OS will be
> supported (HP-UX 11, I believe they stated -- since HP-UX 11 runs al
On Fri, 27 Aug 1999, Kris Kirby wrote:
> I know there are drivers for the WaveLan card, but I'm looking at going
> even slower (256Kb!).
Why do you wnat to do this? If for bandwidht limiting you need look no
further than 'dummynet'.
--
| Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | Fr
On Fri, Aug 27, 1999 at 01:33:03PM -0500, John Sconiers wrote:
>
> I was looking for followups to this thread and have searched the archives
> for more information without luck. I have a few questions. Has this
> project furthered any and where can one get the diffs / source??? Is
> there a we
In reply:
> In article
>
> you write:
> >Actually, I was reading in a newsgroup, the VMS newsgroup I think it was,
> >that the PA-RISC chip is on the Merced chip. Basically, Intel will sell
> >Merced's with the chip disabled (kind of like the math co-processor on the
> >486 SX's) and HP will se
Uhm, have any of you actually ever looked at src/sys/kern/vnode_if.src ?
Poul-Henning
In message <[EMAIL PROTECTED]>, Erez Zadok write
s:
>In message <[EMAIL PROTECTED]>, Matthew Dillon writes:
>[...]
>> I would ask two things though:
>>
>> * First, please add comprehensive /* */ comm
Maybe this is nit-picking, too, buth those are just
my 0.02 Euros...
Doug wrote in list.freebsd-hackers:
> -# this file, but rather in /etc/defaults/rc.conf. Please check this file
> +# this file, but rather in /etc/defaults/rc.conf. Please check that file
I'd prefer to keep it with two space
In message <[EMAIL PROTECTED]>, Matthew Dillon writes:
[...]
> I would ask two things though:
>
> * First, please add comprehensive /* */ comments in front of each
> vfsnop_*() procedure explaining what it does, why it returns what
> it returns, locking requirements (if
On Fri, 27 Aug 1999, Sean Eric Fagan wrote:
> In article
><[EMAIL PROTECTED]>
>you write:
> Look, people, the Merced WILL NOT excuse PA-RISC code directly. It will be
> done via emulation/translation, and only a certain particular OS will be
> supported (HP-UX 11, I believe they stated -- sinc
In reply:
> In article
><[EMAIL PROTECTED]>
>you write:
> >Actually, I was reading in a newsgroup, the VMS newsgroup I think it was,
> >that the PA-RISC chip is on the Merced chip. Basically, Intel will sell
> >Merced's with the chip disabled (kind of like the math co-processor on the
> >486 SX
In article
you write:
>Actually, I was reading in a newsgroup, the VMS newsgroup I think it was,
>that the PA-RISC chip is on the Merced chip. Basically, Intel will sell
>Merced's with the chip disabled (kind of like the math co-processor on the
>486 SX's) and HP will sell it with the PA-RISC c
I was looking for followups to this thread and have searched the archives
for more information without luck. I have a few questions. Has this
project furthered any and where can one get the diffs / source??? Is
there a website that goes in depth about the project.
JOHN
> Following on the
On Fri, 27 Aug 1999, Nate Williams wrote:
> [ I'm nit-picking here, feel free to ignore ]
A) You're in really good company. :)
B) I expected a lot of nits to be picked on this project, which is
why I wanted to do a "first draft" and solicit comments. I'm not overly
concerned a
Raw pattern checker...less well polished...runs on a lot of platforms...
Avoids trashing disk labels...
Usage is a little less than obvious...
1. patchk RAWDISK TransferSize c
Create/Validate/Test patterns.. creates patterns in TransferSize
chunks..validates that they were correctly written, t
A bit of cleanup and filing off of serial numbers, etc...
test script && c program... very stupid test, except that in large doses
brings systems to their knees and very much exercises buffer ownership
issues. The test looks too stupid to catch things, but believe me, it
does.
#!/bin/sh
#
# Copy
On Fri, 27 Aug 1999, Doug wrote:
>
> Ok, revised diff attached. I made the case indentation change and some
> of
> sheldon's suggestions are incorporated. I also neglected to mention
> previously that I tuned up a few of the comments in the file, as well as
> error output. I also was more
In article
<[EMAIL PROTECTED]> you
write:
>Actually, I was reading in a newsgroup, the VMS newsgroup I think it was,
>that the PA-RISC chip is on the Merced chip. Basically, Intel will sell
>Merced's with the chip disabled (kind of like the math co-processor on the
>486 SX's) and HP will sell i
It seems that an interface configured with an address, which is then
deleted, and then set to a different address on the same network, the
machine continues to use the original address although all evidence of it
is gone.
examples.
ifconfig fxp0 207.252.1.31 netmask 255.255.255.0
ping something
I was looking for followups to this thread and have searched the archives
for more information without luck. I have a few questions. Has this
project furthered any and where can one get the diffs / source??? Is
there a website that goes in depth about the project.
JOHN
> Following on the
On Fri, 27 Aug 1999, Nate Williams wrote:
> [ I'm nit-picking here, feel free to ignore ]
A) You're in really good company. :)
B) I expected a lot of nits to be picked on this project, which is
why I wanted to do a "first draft" and solicit comments. I'm not overly
concerned
Raw pattern checker...less well polished...runs on a lot of platforms...
Avoids trashing disk labels...
Usage is a little less than obvious...
1. patchk RAWDISK TransferSize c
Create/Validate/Test patterns.. creates patterns in TransferSize
chunks..validates that they were correctly written,
1 - 100 of 169 matches
Mail list logo
