Question about msdosfs
In msdosfs_vfsops.c we have:
|| !pmp->pm_Heads || pmp->pm_Heads > 255
#ifdef PC98
|| !pmp->pm_SecPerTrack || pmp->pm_SecPerTrack > 255) {
#else
|| !pmp->pm_SecPerTrack || pmp->pm_SecPerTrack > 63) {
#endif
error = EINVAL;
What's so special about 63? Many scsi drives have more than 63
sectors per track. The only reason that we don't see problems with
this is that it appears that CAM appears to be using a geometry with
64 heads and 32 sectors and N cylendars. What's the justification
here?
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: JFS and IBM
According to Bill Pechter: > Is this as much of a surprise to all of you as to me... I thought jfs > would remain a tightly held OSF/1 component that would never see > "free" status. Note that the released version is the OS/2 one (maybe based on HPFS?) not the one in AIX. But I agree this is good news. IBM has been a rather nice player in this field for a long time now (Jikes, Postfix and such). -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 4.0-CURRENT #77: Thu Dec 30 12:49:51 CET 1999 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: how to compile without libc (so not static)
According to Marco van de Voort: > gcc -nostdlib empty.c /usr/lib/crti.o /usr/lib/crt0.o -o empty You mean crt1.o instead of crt0.o here right? crt0.o is the a.out version... > grep exit *.o nm(1) is your Dear Friend® here. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 4.0-CURRENT #77: Thu Dec 30 12:49:51 CET 1999 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FreeBSD Posix threads
"Zhihui Zhang" <[EMAIL PROTECTED]> wrote: > (1) Some people say "For I/O bound activity, kernel threads are a really > bad idea". But I read the following passage from else where: > > Kernel threads perform better in I/O-intensive applications because system > call can be blocking for kernel threads (so there is only one > user-to-kernel and kernel-to-user transition per I/O operation rather than > two). > > So which one is the correct answer? I know there is only userland thread > in FreeBSD, but I would like to know the answer. Both. All I/O is not created equal. For blockable I/O (sockets, both TCP and UNIX domain, ttys, pipes, etc), userland pthreads are excellent. For disk I/O, they're less excellent because disk I/O is always ready to go, and you'll always block waiting for it. Not having multiple pending disk I/O requests can be killer. OTOH, that doesn't apply if your working set fits in memory. > (2) User threads are supposed to be faster than kernel threads in context > switch. But since we poll devices during each context switch, it is > actually slower (poll() is the extra system call). Is this correct? That's hard to say. If you use a "standard" thread-per-connection, then only the threads waiting for input contribute to the poll(). Threads that are working do not. Furthermore, a system call is not necessarily a cause for alarm - yet, that's a prime location for the kernel to decide to switch to another process, but it's not _required_ to do so. Later, scott To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FreeBSD Posix threads
%
%I have searched the archive for a while and still have some confusions
%about this subjects:
%
%(1) Some people say "For I/O bound activity, kernel threads are a really
%bad idea". But I read the following passage from else where:
%
%Kernel threads perform better in I/O-intensive applications because system
%call can be blocking for kernel threads (so there is only one
%user-to-kernel and kernel-to-user transition per I/O operation rather than
%two).
%
%So which one is the correct answer? I know there is only userland thread
%in FreeBSD, but I would like to know the answer.
%
%(2) User threads are supposed to be faster than kernel threads in context
%switch. But since we poll devices during each context switch, it is
%actually slower (poll() is the extra system call). Is this correct?
%
%(3) Can I do cooperative thread scheduling on FreeBSD? I guess the
%constant SCHED_RR (round robin) means preemptive. How about SCHED_FIFO
%and SCHED_OTHER defined in posix4/sched.h? Can I choose from them? In
%the case of SCHED_RR, I still do part of scheduling by routines like
%yield(), cond_signal(). Am I right?
%
%Any help is appreciated.
Excellent questions.
However, what is not stated is perhaps the most important (to me,
and other people burning up and showering down $$$). C++ programmers
use threads to share class members. In that context, the POSIX
realtime scheduling classes (SCHED_*) are quite useful, albeit abstractly
for now.
IMNSHO, focusing on fine-grained benchmarks ("perform better") for
an execution model based on C processes may be misleading in the
realistic broader picture.
Russell
%-Zhihui
%
%
%
%
%To Unsubscribe: send mail to [EMAIL PROTECTED]
%with "unsubscribe freebsd-hackers" in the body of the message
%
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: Re/Fwd: freebsd specific search
On Thu, 3 Feb 2000, Mike Bristow wrote: > True; but linux has support for a bigger variety of soundcards > (my Win98^H^H^H^H^H^HEverQuest machine now has a Live! in it; supported > under Linux but not under FreeBSD AFAIK; so the other half of the disk > may turn turn into ext2 rather than ffs) Well if you buy esoteric or just cheap hardware... > I generally get the feeling that `Workstation Hardware'[1] has a better > chance of being supported under Linux than FreeBSD. I may be talking rubbish, > though ;-) Cheap hardware has a better chance of being supported. If you stick with the name brand stuff, you could piece together a box that'll work great and work great with FreeBSD. Me, I've got my Micron PC (which was a pretty good deal when I bought it), and the onboard sound is AFAIK supported by that comercial Linux sound driver, but nothing else. The box also came with an AWE64, therefore I'm happy. - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
FreeBSD Posix threads
I have searched the archive for a while and still have some confusions about this subjects: (1) Some people say "For I/O bound activity, kernel threads are a really bad idea". But I read the following passage from else where: Kernel threads perform better in I/O-intensive applications because system call can be blocking for kernel threads (so there is only one user-to-kernel and kernel-to-user transition per I/O operation rather than two). So which one is the correct answer? I know there is only userland thread in FreeBSD, but I would like to know the answer. (2) User threads are supposed to be faster than kernel threads in context switch. But since we poll devices during each context switch, it is actually slower (poll() is the extra system call). Is this correct? (3) Can I do cooperative thread scheduling on FreeBSD? I guess the constant SCHED_RR (round robin) means preemptive. How about SCHED_FIFO and SCHED_OTHER defined in posix4/sched.h? Can I choose from them? In the case of SCHED_RR, I still do part of scheduling by routines like yield(), cond_signal(). Am I right? Any help is appreciated. -Zhihui To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: JFS and IBM
[moved to -fs] On Friday, 4 February 2000 at 15:28:34 -0700, Wes Peters wrote: > Bill Pechter wrote: >> >> Folks, while some of us were at Linux expo talking about journaling file >> systems and *BSD, IBM released jfs to the GPL. >> >> Is there anyone working on this as a gpl'd add-in to *BSD? > > You apparently haven't noticed the war of words going on on > http://daily.daemonnews.org/ on this very topic? I think this is going > to be our most "popular", or at least commented on, article to date. There was also a discussion in -fs, so I'm following up there. > Greg Lehey has downloaded the code and looked at it. Despite my > cheering and enthusiasm, he reports that we should wait until he > actually produces something to pronounce him a hero. ;^) Damn it, you keep mentioning my name. I'm certainly no hero based on what I've done or propose to do. For an update, taking in what phk had to say the other day: this is the OS/2 version, which has had the dependencies on the VM system removed. I consider it likely that, as a result, performance will be disappointing. Also I haven't seen any documentation which explains how it works. Given the size of the code base, this would make it quite a challenge. Maybe somebody else more stupid^H^H^H^H^H^Hheroic than I wants to have a go. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: aio_read crashing certain kernels.
"Matthew Dillon" <[EMAIL PROTECTED]> wrote: > If you can reproduce the bug easily, can you post the program that > causes it plus instructions on how to reproduce the bug? If one of us > can reproduce it we may be able to squeeze more info out of the crash. Sorry I took so long to follow-up on this. The issue is definitely, definitely, definitely related to SMP. On a 3.3-RELEASE kernel compiled without SMP support, my various aio_read() based programs work fine, I've probably pushed terabytes through them by now. On a kernel with SMP support, it locks the entire system up. It might not happen on the first call to aio_read(), or the second, but it always happens relatively quickly. I speculate that if the data is already cached, then sometimes it works by virtue of being able to service the request from the same CPU, so the rfork VM-sharing bug isn't an issue. I saw the same symptoms, working on a uniprocessor kernel, not on an SMP kernel, on kernels based on 3.4-RELEASE. Unfortunately, I haven't had time to build kernels verified to be from the same sources for 3.4-RELEASE. I'm leaning towards not bothering, because I'm not sure what it would prove at this point. I should have some time next week to wrap this up into a solid test which will always invoke the crash. Thanks, scott To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Removing interfaces
Warner Losh writes: > : With all the PCMCIA card stuff going on, is it now possible to > : remove a networking interface in FreeBSD (from within the kernel)? > : > : If so could someone show me an example how. I'd like to implement > : this in the ng_iface(8) netgraph node type. > > if_detach() is supposed to do this, but there are theoretical problems > with our implementation of it. Also, there needs to be some way to > propigate the "gone"ness of the interface generically rather than the > ad-hoc way we do it now. Thanks, that works great (so far :-) -Archie ___ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: General lameness regarding exec()
On Fri, 4 Feb 2000, Michael Bacarella wrote: > > I patch my systems to log exec() calls because I think it's useful, but I > really don't know how to go about making it a general contribution. > > Anyone like this idea? Any Suggestions for how I should really implement > it? Have a look at: http://www.freebsd.org/~abial/spy/README Andrzej Bialecki // <[EMAIL PROTECTED]> WebGiro AB, Sweden (http://www.webgiro.com) // --- // -- FreeBSD: The Power to Serve. http://www.freebsd.org // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: JFS and IBM
Bill Pechter wrote: > > Folks, while some of us were at Linux expo talking about journaling file > systems and *BSD, IBM released jfs to the GPL. > > Is there anyone working on this as a gpl'd add-in to *BSD? You apparently haven't noticed the war of words going on on http://daily.daemonnews.org/ on this very topic? I think this is going to be our most "popular", or at least commented on, article to date. Greg Lehey has downloaded the code and looked at it. Despite my cheering and enthusiasm, he reports that we should wait until he actually produces something to pronounce him a hero. ;^) > Is this as much of a surprise to all of you as to me... I thought jfs > would remain a tightly held OSF/1 component that would never see > "free" status. It's released under GPL, so it's still not free. It is available, though. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC [EMAIL PROTECTED] http://softweyr.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Disposable PCs?
"Potts, Ross" wrote: > > Okay, here it is. It's dated today(4 Feb 2000). > > www.tomshardware.com/technews/index.html#0619. For the full scoop, see http://www.theregister.co.uk/000203-22.html If you post complete URLs, *some* of us can just click on them in our mailers. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC [EMAIL PROTECTED] http://softweyr.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: JFS and IBM
At 2:57 PM -0500 2/4/00, Bill Pechter wrote: >Folks, while some of us were at Linux expo talking about journaling >file systems and *BSD, IBM released jfs to the GPL. > >Is there anyone working on this as a gpl'd add-in to *BSD? People outside the expo heard about it too, and there has been an active thread in hackers about this already. Review that thread, so we don't have to go over all the same comments again. There is also something about it at http://daily.daemonnews.org/, which had some interesting pointers. >Is this as much of a surprise to all of you as to me... I thought jfs >would remain a tightly held OSF/1 component that would never see >"free" status. Actually it didn't surprise me too much. IBM realizes it makes it's money in selling hardware and services. They don't have a whole lot to lose by making this JFS source code available, and they might have a fair amount to gain, as they position themselves as a good company to contact for "linux support services". --- Garance Alistair Drosehn = [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Institute To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: how to compile without libc (so not static)
In message <[EMAIL PROTECTED]> Marco van de Voort writes: : /usr/lib/crt1.o: In function `_start': : /usr/lib/crt1.o(.text+0x4f): undefined reference to `atexit' : /usr/lib/crt1.o(.text+0x5c): undefined reference to `atexit' : /usr/lib/crt1.o(.text+0x6f): undefined reference to `exit' : in /usr/lib doesn't find me that label. : : What am I missing? nm /usr/lib/crt1.o | egrep exit U atexit U exit Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
General lameness regarding exec()
I patch my systems to log exec() calls because I think it's useful, but I really don't know how to go about making it a general contribution. Anyone like this idea? Any Suggestions for how I should really implement it? I basically have it end up in syslog, along with who called it and what their credentials were. This is in contrast to process accounting, which only records information on processes which have terminated. /* -- Michael Bacarella( [EMAIL PROTECTED] ) | (212) 293-2620 Administration / Development / Support | http://nyct.net/ [ N e w Y o r k C o n n e c t . N E T ] | [EMAIL PROTECTED] Bringing New York The Internet Service It Deserves! - */ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
how to compile without libc (so not static)
I finished the syscalls, so now I moved on the initialisation code.
To test that I try to create an empty binary, which doesn't link to libc:
I've put in an hour effort, and wrote the following C file:
int main (void) {
return 0;
}
gcc -nostdlib empty.c /usr/lib/crti.o /usr/lib/crt0.o -o empty
results in:
/usr/lib/crt1.o: In function `_start':
/usr/lib/crt1.o(.text+0x4f): undefined reference to `atexit'
/usr/lib/crt1.o(.text+0x5c): undefined reference to `atexit'
/usr/lib/crt1.o(.text+0x6f): undefined reference to `exit'
with a
grep exit *.o
in /usr/lib doesn't find me that label.
What am I missing?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: elf
Marco van de Voort wrote: > > How can I disassemble ELF programs? objdump --disassemble -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC [EMAIL PROTECTED] http://softweyr.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: elf
> > On 04-Feb-00 Marco van de Voort wrote: > > > > > > How can I disassemble ELF programs? > > > > I need to create my own startup code for FPC programs. > > (copying some variables before pascal code startup) > > Try 'objdump -d'. It's more readable if you don't strip the program. > You can also use this to disassemble object files as well, so you > could just 'objdump -d /usr/lib/crt0.o'. The question is not "how" but "why"? You already have access to the source... -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
JFS and IBM
Folks, while some of us were at Linux expo talking about journaling file systems and *BSD, IBM released jfs to the GPL. Is there anyone working on this as a gpl'd add-in to *BSD? Is this as much of a surprise to all of you as to me... I thought jfs would remain a tightly held OSF/1 component that would never see "free" status. We live in interesting times, indeed. Bill --- [EMAIL PROTECTED]|[EMAIL PROTECTED]|[EMAIL PROTECTED] Three things never anger: First, the one who runs your DEC, The one who does Field Service and the one who signs your check. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: mounting openbsd disks
In message <[EMAIL PROTECTED]> "Chris D. Faulhaber" writes: : root@earth:~# disklabel ad1 : disklabel: ioctl DIOCGDINFO: Invalid argument : root@earth:~# disklabel /dev/ad1s4 disklabel /dev/ad2s2 (which is the OpenBSD partition) fails with the same error. Mounting claims a bad magic number. This is an OpenBSD/arc disk which has a slightly different disklabel I think (since when I say disklabel on the OpenBSD/arc machine I get 16 partitions. Changing the id of the slice doesn't help either. :-( Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Disposable PCs?
Okay, here it is. It's dated today(4 Feb 2000). www.tomshardware.com/technews/index.html#0619. -Original Message- From: Einar Orn Eidsson [SMTP:[EMAIL PROTECTED]] Sent: Friday, February 04, 2000 9:23 AM To: Potts, Ross Cc: '[EMAIL PROTECTED]' Subject:Re: Disposable PCs? That's interesting, I can't find the link on Tom's page though, either I'm blind or I'm having a premature hangover. Could you post the URL? | Einar Orn Eidsson | Tel: +354-696-1352 | SMS: [EMAIL PROTECTED] | ICQ: 8818678 -- -- - - - - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: elf
On Fri, 4 Feb 2000, John Baldwin wrote: > > On 04-Feb-00 Marco van de Voort wrote: > > > > > > How can I disassemble ELF programs? > > > > I need to create my own startup code for FPC programs. > > (copying some variables before pascal code startup) > > Try 'objdump -d'. It's more readable if you don't strip the program. > You can also use this to disassemble object files as well, so you > could just 'objdump -d /usr/lib/crt0.o'. My favourite is 'objdump -dS' to include source code. This obviously requires debugging information in the disassembled thing. -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: elf
On 04-Feb-00 Marco van de Voort wrote: > > > How can I disassemble ELF programs? > > I need to create my own startup code for FPC programs. > (copying some variables before pascal code startup) Try 'objdump -d'. It's more readable if you don't strip the program. You can also use this to disassemble object files as well, so you could just 'objdump -d /usr/lib/crt0.o'. -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: elf
Marco van de Voort <[EMAIL PROTECTED]> wrote: >How can I disassemble ELF programs? Try IDA PRO : http://www.datarescue.com/ida.htm http://www.rosprombank.ru/~ig/ -- -=AV=- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Disposable PCs?
That's interesting, I can't find the link on Tom's page though, either I'm blind or I'm having a premature hangover. Could you post the URL? | Einar Orn Eidsson | Tel: +354-696-1352 | SMS: [EMAIL PROTECTED] | ICQ: 8818678 -- -- - - - - On Fri, 4 Feb 2000, Potts, Ross wrote: > I just rejoined the list after a couple years layoff, so I felt compelled to > submit this. > > I finished reading an article on www.tomshardware.com that said Samsung is > trying to make disposable PCs. > Cost would be around $200. When I followed the link to get more details it > finished with speculation that the could be on a level with or beyond PIIIs. > > CAN YOU SAY CHEAP CLUSTERING? (pardon me while I wipe the drool offin' my lip) > > Ross > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
elf
How can I disassemble ELF programs? I need to create my own startup code for FPC programs. (copying some variables before pascal code startup) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
No Subject
auth fcec1a83 subscribe freebsd-hackers [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Disposable PCs?
I just rejoined the list after a couple years layoff, so I felt compelled to submit this. I finished reading an article on www.tomshardware.com that said Samsung is trying to make disposable PCs. Cost would be around $200. When I followed the link to get more details it finished with speculation that the could be on a level with or beyond PIIIs. CAN YOU SAY CHEAP CLUSTERING? (pardon me while I wipe the drool offin' my lip) Ross To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: mounting openbsd disks
On Fri, 4 Feb 2000, Warner Losh wrote: > I have a need to mount a disk that was partitioned and labeled on > OpenBSD. I'm getting the following errors when I try: > > # disklabel ad2 > disklabel: ioctl DIOCGDINFO: Invalid argument > root@earth:~# disklabel ad1 disklabel: ioctl DIOCGDINFO: Invalid argument root@earth:~# disklabel /dev/ad1s4 *snip* 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 52409704.2BSD 1024 819216 # (Cyl.0 - 519*) b: 1048320 524097 swap# (Cyl. 519*- 1559) c: 164504970unused0 0 # (Cyl.0 - 16319*) e: 262080 15724174.2BSD 1024 819216 # (Cyl. 1559*- 1819) f: 4194288 18344974.2BSD 1024 819216 # (Cyl. 1819*- 5980) root@earth:~# mount /dev/ad1s4a /mnt root@earth:~# ls /mnt .cshrc bootemulroottmp .profilebsd etc sbinusr altroot bsd.old homestand var bin dev mnt sys root@earth:~# - Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Re/Fwd: freebsd specific search
On Thu, Feb 03, 2000 at 07:58:04PM -0700, Wes Peters wrote: > Mike Bristow wrote: > > > > True; but linux has support for a bigger variety of soundcards > > (my Win98^H^H^H^H^H^HEverQuest machine now has a Live! in it; supported > > under Linux but not under FreeBSD AFAIK; so the other half of the disk > > may turn turn into ext2 rather than ffs) > > > > The other 2 boxes will, of course, stay FreeBSD. > > You'd switch operating systems for the sake of a sound card? That seems > backwards to this correspondent. Just buy a reasonable sound card that > works under your system of choice; they're less expensive than a system > installation. You're right of course. But the system of choice is EverQuest[1], not FreeBSD. 98% of the time it's on, it's running Windows. Until Verant produce a linux or FreeBSD or BeOS or whatever client, I don't have any choice in the matter. [1] at the moment. It'll probably change to some other game later. -- Mike Bristow, Geek At Large ``Beware of Invisible Cows'' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Installing -current
> > Before I ran into trouble I want to ask if 4.0 supports the > > 3CCFE574BT NIC? (3com 3c574). > > It looks that way. I haven't had the occasion to try myself. It worked! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: IBM releases JFS for Linux.
In message <[EMAIL PROTECTED]>, Greg Lehey writes: >I've taken a look, and there's as good as no docco. It's an OS/2 >version, which suggests to me that it would be more difficult to port >than the original AIX version. I might get back to it again later on, >but don't hold your breath. No, in fact the AIX version was so hard to port that OSF eventually had to give up trying. It was rather closely married to the VM hardware on the Power CPU. -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Suggestions for Gigabit cards for -CURRENT
Of all the gin joints in all the towns in all the world, Kenneth D. Merry had to walk into mine and say: > > Talking of the XMAC II, there's one other thing I forgot to mention earlier. > > The FreeBSD sk driver does jumbo frames, but the SysKonnect drivers don't. > > At least, not yet. The XMAC II's receive FIFO is 8K. By default, the chip > > operates in 'store and forward' mode in order to perform error checking on > > received frames (it has to get the entire frame in the FIFO in order to > > do a CRC on it, I think). This is fine for normal frames, but if you want > > to handle jumbograms larger than 8192 bytes, you have to put the chip into > > 'streaming' mode, otherwise any frame larger than 8192 bytes will be truncated. > > To get 'streaming' mode to work, you have to disable all of the RX error > > checking. > > That is unfortunate, since it means you can't do checksum offloading with > jumbo frames. Uhm. I'm not sure about that. The 8K FIFO limitation is in the XMAC II, not in the GEnesis controller. And I believe it's the GEnesis that actually does the hardware checksumming stuff. Oh, and the XMAC appears to have a 4K TX FIFO, not 2K. My mistake. > FWIW, of the three gigabit ethernet implementations I've seen anything of > (Alteon, Intel, SysKonnect), none have implemented all of the hooks > necessary for a seamless zero copy receive implementation. > > Alteon comes the closest, but they don't support splitting out the headers > (yet), which is a requirement for us. The only way to do zero copy receive > with our VM architecture (that I know of) is page flipping, i.e. receive > the page in the kernel, and then trade it for the user's page. You can't > do it on anything less than page-sized granularity, and things have to be > page aligned. (The IO-Lite stuff from Rice is an exception to all this.) > > The nice thing about the Alteon boards, though, is that you can modify the > firmware, and so header splitting is an option there. It would even be > possible to split the headers off of IPv6 packets, or any other protocol > that you have knowlege of. If you can actually modify the firmware to do this then you have a lot more guru points than I do. :) I've looked at the Alteon firmware code but it's all quite opaque to me. -Bill -- = -Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu Work: [EMAIL PROTECTED] | Center for Telecommunications Research Home: [EMAIL PROTECTED] | Columbia University, New York City = "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
