Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's
In reply: > On Wed, 21 Jul 1999, Kip Macy wrote: > > > My employer has gone through numerous motherboards, we have found the ASUS > > P2B (now the P2B-F) to be rock solid for Pentium II usage. > > This is probably more appropriate for -hardware or even just -chat.. > but anyway, I'll second that recommendation. I've found the ASUS P2B > series to be very solid. I've also used many ATrend BX boards for > Winblows95 boxes (simply because they were cheaper than the ASUS > boards), and haven't had a bit of trouble with them. YMMV. > > > -- Chris Dillon - cdil...@wolves.k12.mo.us - cdil...@inter-linc.net >FreeBSD: The fastest and most stable server OS on the planet. >For Intel x86 and Alpha architectures (SPARC under development). >( http://www.freebsd.org ) > >"One should admire Windows users. It takes a great deal of > courage to trust Windows with your data." don't leave out the tyan thunder2 and thunder100 boards. the only problem i even know of with the thunder2 is the sound chip still isn't recognized, and the id codes pnp returns on the sound chip may differ from board to board [others claim it works for them, but not here]. i have heard of no problems with the thunder100 board. jim -- All opinions expressed are mine, if you| "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" -- Inet: jbry...@tfs.netAX.25: kc5...@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant -- HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Anyone know how to dim and SGI flat panel?
: :I'd bet it's done using DPMS. See if the XFree86 4.x code can tell you :anything about the monitor's capabilities. It's up? Very cool, they actually put the prerelease up 2 days ago! 47MB download, yummy! DGA is going to be so cool. Unfortunately it looks like the DPMS stuff is still a bit primitive. Shoot. I'll check it out, though. The 3.3.3 I128 driver (that's the number 9 card) does not appear to support DPMS at all. SGI's site has a whitepaper on the flatpanel but it's a bit spare on control protocols. They do say something about an I2C bus but I dunno whether that is what DPMS uses or not. -Matt Matthew Dillon <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: System unique identifier.....
> > That's not quite true. It wouldn't be too hard to modify existant files, > > but writing new ones/truncating would take a lot of work. It's still not > > a great idea to try to use a file on the FS for storage of persistent > > data. Wouldn't it be possible to have the kernel itself read in persistent > > data (in some form such as getenv?) to be written to disk? That way, the > > boot loader could pass it easily, and not have to worry about storage. > > This may sound like a heresy to you, but... Why don't use the Forth blocks > for that? For what? Saving parametric data? That was always the plan, but the last thing I think anyone wants to do is rewrite the ffs code in Forth. > They were invented for that purpose. We can create the files > beforehand (under normal OS operation), then from the bootloader we can > read and modify them - I suppose writing to a disk block is much easier > than through the filesystem layer... Yes, that's what we've always discussed as being the most likely course of action. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msm...@freebsd.org \\-- Joseph Merrick \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's
In reply: > On Wed, 21 Jul 1999, Kip Macy wrote: > > > My employer has gone through numerous motherboards, we have found the ASUS > > P2B (now the P2B-F) to be rock solid for Pentium II usage. > > This is probably more appropriate for -hardware or even just -chat.. > but anyway, I'll second that recommendation. I've found the ASUS P2B > series to be very solid. I've also used many ATrend BX boards for > Winblows95 boxes (simply because they were cheaper than the ASUS > boards), and haven't had a bit of trouble with them. YMMV. > > > -- Chris Dillon - [EMAIL PROTECTED] - [EMAIL PROTECTED] >FreeBSD: The fastest and most stable server OS on the planet. >For Intel x86 and Alpha architectures (SPARC under development). >( http://www.freebsd.org ) > >"One should admire Windows users. It takes a great deal of > courage to trust Windows with your data." don't leave out the tyan thunder2 and thunder100 boards. the only problem i even know of with the thunder2 is the sound chip still isn't recognized, and the id codes pnp returns on the sound chip may differ from board to board [others claim it works for them, but not here]. i have heard of no problems with the thunder100 board. jim -- All opinions expressed are mine, if you| "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" -- Inet: [EMAIL PROTECTED]AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant -- HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Anyone know how to dim and SGI flat panel?
> This is the 1600x1024 one that comes w/ the Number-9 graphics card. > It has no dimmer control for the backlight but, apparently, there > is a way to do it from a control panel in windows. > > The question is: Is there a way to do it from FreeBSD? I've got it > up and running just dandy - except it's so bright it's burning holes > in my eyes at night :-( > > Anyone who has one of these things know how its done? I'd bet it's done using DPMS. See if the XFree86 4.x code can tell you anything about the monitor's capabilities. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msm...@freebsd.org \\-- Joseph Merrick \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: System unique identifier.....
> > That's not quite true. It wouldn't be too hard to modify existant files, > > but writing new ones/truncating would take a lot of work. It's still not > > a great idea to try to use a file on the FS for storage of persistent > > data. Wouldn't it be possible to have the kernel itself read in persistent > > data (in some form such as getenv?) to be written to disk? That way, the > > boot loader could pass it easily, and not have to worry about storage. > > This may sound like a heresy to you, but... Why don't use the Forth blocks > for that? For what? Saving parametric data? That was always the plan, but the last thing I think anyone wants to do is rewrite the ffs code in Forth. > They were invented for that purpose. We can create the files > beforehand (under normal OS operation), then from the bootloader we can > read and modify them - I suppose writing to a disk block is much easier > than through the filesystem layer... Yes, that's what we've always discussed as being the most likely course of action. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ [EMAIL PROTECTED] \\-- Joseph Merrick \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Anyone know how to dim and SGI flat panel?
This is the 1600x1024 one that comes w/ the Number-9 graphics card. It has no dimmer control for the backlight but, apparently, there is a way to do it from a control panel in windows. The question is: Is there a way to do it from FreeBSD? I've got it up and running just dandy - except it's so bright it's burning holes in my eyes at night :-( Anyone who has one of these things know how its done? Thanks! -Matt Matthew Dillon To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Anyone know how to dim and SGI flat panel?
> This is the 1600x1024 one that comes w/ the Number-9 graphics card. > It has no dimmer control for the backlight but, apparently, there > is a way to do it from a control panel in windows. > > The question is: Is there a way to do it from FreeBSD? I've got it > up and running just dandy - except it's so bright it's burning holes > in my eyes at night :-( > > Anyone who has one of these things know how its done? I'd bet it's done using DPMS. See if the XFree86 4.x code can tell you anything about the monitor's capabilities. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ [EMAIL PROTECTED] \\-- Joseph Merrick \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Anyone know how to dim and SGI flat panel?
This is the 1600x1024 one that comes w/ the Number-9 graphics card. It has no dimmer control for the backlight but, apparently, there is a way to do it from a control panel in windows. The question is: Is there a way to do it from FreeBSD? I've got it up and running just dandy - except it's so bright it's burning holes in my eyes at night :-( Anyone who has one of these things know how its done? Thanks! -Matt Matthew Dillon <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: KDE on FreeBSD (missing symbols)
On Wed, 21 Jul 1999, eT wrote: > Hi, I noticed that my ld path was using the old libqt in /usr/X11R6/lib and > not the new > one I have in /usr/local/qt/lib. That would do it too :^) > Problem I am getting now is libstdc++ problem: ld.elf complains: > > libstdc++.so.3: undefined symbol __ti9exception You're compiling something without exceptions (-fno-exceptions). Check again Qt, kdelibs, kdebase. And possibly if you built world recently, check the CFLAGS and CXXFLAGS that were used to build world too. - alex You wear guilt, like shackles on your feet, Like a halo in reverse - Depeche Mode To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Proposal for new syscall to close files
"John W. DeBoskey" wrote: > I like this approach. I have a number of often spawned daemon >processes that could benefit from this. I don't suppose that you have any statistics showing that the for (i = 3; i < getdtablesize(); i++) close(i); approach would be too slow? > For naming convention considerations, I might suggest 'closeall' >or 'closefdset' or something similar... at least have 'close' in >name... :-) I'm not really keen on the name either - but I couldn't think of anything better. `closeall' isn't really descriptive since it doesn't close all the FDs. `closefdset' suggests (to me, anyway) the opposite behaviour: ie closing the FDs specified in the passed fd_set, instead of closing everything else. Peter To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's
On Wed, 21 Jul 1999, Kip Macy wrote: > My employer has gone through numerous motherboards, we have found the ASUS > P2B (now the P2B-F) to be rock solid for Pentium II usage. This is probably more appropriate for -hardware or even just -chat.. but anyway, I'll second that recommendation. I've found the ASUS P2B series to be very solid. I've also used many ATrend BX boards for Winblows95 boxes (simply because they were cheaper than the ASUS boards), and haven't had a bit of trouble with them. YMMV. -- Chris Dillon - cdil...@wolves.k12.mo.us - cdil...@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures (SPARC under development). ( http://www.freebsd.org ) "One should admire Windows users. It takes a great deal of courage to trust Windows with your data." To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: poor ethernet performance?
Vincent Poy wrote: > > On Wed, 21 Jul 1999, Modred wrote: > > > On Wed, 21 Jul 1999, Vincent Poy wrote: > > > > > Speaking about Layer 2 and layer 3. Does the Cisco Catalyst > > > 2924XL and the HP ProCurve 2424M and 4000M switches fall under Layer 3 or > > > just layer 2? > > > > Cisco, yes... HP, no clue (perhaps you could check their website). > > > > IOW, RTFM. Wouldn't that be RTFW? ;^) > I did, it gets interesting though since if it was a true Level 3 > switch, it sure seems to perform more like a Level 2. Wait'll you see IP routing at 12,000,000 packets per second. ;^) Layer 3 switches are not inherently slower than Layer 2, if they're built right. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://softweyr.com/ w...@softweyr.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: KDE on FreeBSD (missing symbols)
On Wed, 21 Jul 1999, eT wrote: > Hi, I noticed that my ld path was using the old libqt in /usr/X11R6/lib and not the >new > one I have in /usr/local/qt/lib. That would do it too :^) > Problem I am getting now is libstdc++ problem: ld.elf complains: > > libstdc++.so.3: undefined symbol __ti9exception You're compiling something without exceptions (-fno-exceptions). Check again Qt, kdelibs, kdebase. And possibly if you built world recently, check the CFLAGS and CXXFLAGS that were used to build world too. - alex You wear guilt, like shackles on your feet, Like a halo in reverse - Depeche Mode To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Proposal for new syscall to close files
Hi,
I like this approach. I have a number of often spawned daemon
processes that could benefit from this. One of the last process
we debugged where we had unwanted open filedescriptors was in
programs invoked by the cvs loginfo script.
For naming convention considerations, I might suggest 'closeall'
or 'closefdset' or something similar... at least have 'close' in
name... :-)
Good Work,
John
> It's fairly common, when spawning new processes, to want to make sure
> all unwanted FDs are closed. Currently, the options for doing this are:
>
> 1) Use fcntl(fd, F_SETFD, FD_CLOEXEC) to set the close-on-exec flag
>when the file is opened/cloned. This may not be practical if the
>FD must remain open across some exec's, but not others. It is not
>possible to ensure that FDs implicitly opened within library
>functions have the close-on-exec flag set. It may be inefficient if
>there are lots of opens and few execs.
>
> 2) Explicitly close unwanted FDs in the child, before the exec().
>This suffers from the usual resource tracking problems (ie it's
>easy to forget to close one - especially in a maze of pipe()/
>dup()/dup2() calls designed to join the child's stdin/out/err
>to the parent). It also requires that the FD's be visible to the
>function - which may be difficult (the FD may be hidden within
>another function somewhere).
>
> 3) Close all FDs except the ones you explicitly want to keep. This
>is normally something like:
> for (i = getdtablesize(); --i > 2; )
> close(i);
>The advantage is that you are sure you don't miss any. The
>disadvantage is that it requires a system call for each potentially
>open FD - >600 on my system - whereas maybe only 4 or 5 are
>actually open.
>
> In the case of option 3, you only really need to attempt to close file
> descriptors less then curproc->p_fd->fd_lastfile or even
> curproc->p_fd->fd_nfiles, but these values aren't readily accessible
> from userland. (And this still suffers the overhead of a userland
> to kernel transition for each FD).
>
> I'd therefore like to propose a new syscall that closes _all_ file
> descriptors associated with a process, except for those passed as
> 1 bits in an fd_set. The proposed API is:
>
> int cleanup_files(int nfds, const fd_set *leavefds);
>
> where nfds specifies the number of fds in *leavefds to potentially
> keep open (ie all fds >= nfds will be closed).
>
> The function would return the number of FDs closed.
>
> The implementation would be along the lines of:
>
> struct cleanup_files_args {
> int nd;
> fd_set *leave;
> };
>
> int
> cleanup_files(p, uap)
> register struct proc *p;
> register struct cleanup_files_args *uap;
> {
> fd_set s_fdset;
> fd_set *lset;
> int error, nclosed = 0;
> u_int i, ncpbytes, nfdbits;
> struct filedesc *fdp = p->p_fd;
> struct file **fpp;
> char *fdfp;
>
> if (uap->nd < 0 || uap->leave = NULL)
> return (EINVAL);
>
> /* some daemons mught not have any file descriptors */
> if (fdp == NULL) {
> p->p_retval[0] = 0;
> return (0);
> }
>
> if (uap->nd > fdp->fd_lastfile)
> uap->nd = fdp->fd_lastfile + 1;
>
> /*
>* Allocate just enough bits for the passed fd_set. Use the
>* preallocated auto buffer if possible.
>*/
> nfdbits = roundup(uap->nd, NFDBITS);
> ncpbytes = nfdbits / NBBY;
> if (ncpbytes <= sizeof s_fdset)
> lset = &s_fdset;
> else
> lset = malloc(ncpbytes, M_SELECT, M_WAITOK);
>
> error = copyin(uap->leave, lbits, ncpbytes);
> if (error != 0)
> goto done;
>
> fpp = fdp->fd_ofiles;
> fdfp = fdp->fd_ofileflags;
> for (i = 0; i < uap->nd; i++, fpp++, fdfp++) {
> if (!FD_ISSET(i, lset) && *fpp != NULL) {
> if (*fdfp & UF_MAPPED)
> (void) munmapfd(p, i);
> error = closef(*fpp, p);
> if (error != 0)
> goto done;
> nclosed++;
> *fpp = NULL;
> *fdfp = 0;
> if (i < fdp->fd_freefile)
> fdp->fd_freefile = i;
> }
> }
>
> for (; i <= fdp->fd_lastfile; i++, fpp++, fdfp++)
> if (*fpp != NULL) {
> if (*fdfp & UF_MAPPED)
> (void) munmapfd(p, i);
> error = closef(*fpp, p);
> if (error != 0)
> goto done;
> nclosed++;
> *fpp = NULL;
> *fdfp = 0;
> if (i < fdp->fd_freefile)
> fdp->fd_freefile = i
Re: Proposal for new syscall to close files
"John W. DeBoskey" <[EMAIL PROTECTED]> wrote: > I like this approach. I have a number of often spawned daemon >processes that could benefit from this. I don't suppose that you have any statistics showing that the for (i = 3; i < getdtablesize(); i++) close(i); approach would be too slow? > For naming convention considerations, I might suggest 'closeall' >or 'closefdset' or something similar... at least have 'close' in >name... :-) I'm not really keen on the name either - but I couldn't think of anything better. `closeall' isn't really descriptive since it doesn't close all the FDs. `closefdset' suggests (to me, anyway) the opposite behaviour: ie closing the FDs specified in the passed fd_set, instead of closing everything else. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's
On Wed, 21 Jul 1999, Kip Macy wrote: > My employer has gone through numerous motherboards, we have found the ASUS > P2B (now the P2B-F) to be rock solid for Pentium II usage. This is probably more appropriate for -hardware or even just -chat.. but anyway, I'll second that recommendation. I've found the ASUS P2B series to be very solid. I've also used many ATrend BX boards for Winblows95 boxes (simply because they were cheaper than the ASUS boards), and haven't had a bit of trouble with them. YMMV. -- Chris Dillon - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures (SPARC under development). ( http://www.freebsd.org ) "One should admire Windows users. It takes a great deal of courage to trust Windows with your data." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's
I hope this helps. I'm running version 3.1 on ASUS Pentium III double processor. Just a Rocket! No problems at all on the installation all the SCSI ports were recognizedmy entire machine cost me 2000 USD...similar one of a famous brabd...at least 6,000 JB At 05:26 PM 21/07/99 -0700, you wrote: >Greetings everyone, > > What are the current good motherboards for FreeBSD for the pentium >II and III? I know on the Pentium, it was the ASUS board but for the >PII/PIII, is the Abit the better board? Also, I was wondering what is the >fastest Celeron chip that can be overclocked to run at 100Mhz FSB? Does >it matter if it's Slot 1 or PPGA based? Thanks. > > >Cheers, >Vince - vi...@mcestate.com - vi...@gaianet.net __ >Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] >GaiaNet Corporation - M & C Estate / / / / | / | __] ] >Beverly Hills, California USA 90210 / / / / / |/ / | __] ] >HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[] > > > >To Unsubscribe: send mail to majord...@freebsd.org >with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
1373 sound chip
I sent this to multimedia about a week ago and didn't get a response so I'm trying it here [hackers & hardware] (with minor mods): I'm setting up a new machine that has onboard sound in the form of an ES1373 Creative (Ensoniq, probably). Visual config shows an unknown device as ES0 and pcm0 doesn't find anything (tried various forms in the kernel config for that one, the last one was/is: device pcm0 Is there any driver for this chip? Under windows it uses the SoundBlaster AudioPCI 64V driver. So far I haven't found any specs on Creative's or Ensoniq's website. Can someone shed some light on possibly adapting the pcm driver to this chip (like how to ID, etc.) ? Vince. -- == Vince Vielhaber -- KA8CSH email: v...@michvhf.com flame-mail: /dev/null # includeTEAM-OS2 Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: poor ethernet performance?
Vincent Poy wrote: > > On Wed, 21 Jul 1999, Modred wrote: > > > On Wed, 21 Jul 1999, Vincent Poy wrote: > > > > > Speaking about Layer 2 and layer 3. Does the Cisco Catalyst > > > 2924XL and the HP ProCurve 2424M and 4000M switches fall under Layer 3 or > > > just layer 2? > > > > Cisco, yes... HP, no clue (perhaps you could check their website). > > > > IOW, RTFM. Wouldn't that be RTFW? ;^) > I did, it gets interesting though since if it was a true Level 3 > switch, it sure seems to perform more like a Level 2. Wait'll you see IP routing at 12,000,000 packets per second. ;^) Layer 3 switches are not inherently slower than Layer 2, if they're built right. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://softweyr.com/ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: poor ethernet performance?
On Wed, 21 Jul 1999, Modred wrote: > On Wed, 21 Jul 1999, Vincent Poy wrote: > > > Speaking about Layer 2 and layer 3. Does the Cisco Catalyst > > 2924XL and the HP ProCurve 2424M and 4000M switches fall under Layer 3 or > > just layer 2? > > Cisco, yes... HP, no clue (perhaps you could check their website). > > 2900XL Architecture Notes: > > http://www.cisco.com/warp/public/cc/cisco/mkt/switch/cat/2900xl \ > /tech/malbu_wp.htmhttp://www.cisco.com/warp/public/cc/cisco/mkt/ \ > switch/cat/2900xl/tech/malbu_wp.htm > > 2900XL Management Guide: > > http://www.cisco.com/univercd/cc/td/doc/product/lan/c2900xl/ \ > 29_35sa6/index.htm > > IOW, RTFM. I did, it gets interesting though since if it was a true Level 3 switch, it sure seems to perform more like a Level 2. Cheers, Vince - vi...@mcestate.com - vi...@gaianet.net __ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[] To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's
On Wed, 21 Jul 1999, Kip Macy wrote: Hmmm, we're using the ABIT BH-6 but that's all because we got the board for free so we can't complain... Cheers, Vince - vi...@mcestate.com - vi...@gaianet.net __ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[] > My employer has gone through numerous motherboards, we have found the ASUS > P2B (now the P2B-F) to be rock solid for Pentium II usage. > > > On Wed, 21 Jul 1999, Vincent Poy wrote: > > > Greetings everyone, > > > > What are the current good motherboards for FreeBSD for the pentium > > II and III? I know on the Pentium, it was the ASUS board but for the > > PII/PIII, is the Abit the better board? Also, I was wondering what is the > > fastest Celeron chip that can be overclocked to run at 100Mhz FSB? Does > > it matter if it's Slot 1 or PPGA based? Thanks. > > > > > > Cheers, > > Vince - vi...@mcestate.com - vi...@gaianet.net __ > > Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] > > GaiaNet Corporation - M & C Estate / / / / | / | __] > > ] > > Beverly Hills, California USA 90210 / / / / / |/ / | __] ] > > HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[] > > > > > > > > To Unsubscribe: send mail to majord...@freebsd.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > > > > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's
My employer has gone through numerous motherboards, we have found the ASUS P2B (now the P2B-F) to be rock solid for Pentium II usage. On Wed, 21 Jul 1999, Vincent Poy wrote: > Greetings everyone, > > What are the current good motherboards for FreeBSD for the pentium > II and III? I know on the Pentium, it was the ASUS board but for the > PII/PIII, is the Abit the better board? Also, I was wondering what is the > fastest Celeron chip that can be overclocked to run at 100Mhz FSB? Does > it matter if it's Slot 1 or PPGA based? Thanks. > > > Cheers, > Vince - vi...@mcestate.com - vi...@gaianet.net __ > Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] > GaiaNet Corporation - M & C Estate / / / / | / | __] ] > Beverly Hills, California USA 90210 / / / / / |/ / | __] ] > HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[] > > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-hackers" in the body of the message > > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: poor ethernet performance?
On Wed, 21 Jul 1999, Vincent Poy wrote: > Speaking about Layer 2 and layer 3. Does the Cisco Catalyst > 2924XL and the HP ProCurve 2424M and 4000M switches fall under Layer 3 or > just layer 2? Cisco, yes... HP, no clue (perhaps you could check their website). 2900XL Architecture Notes: http://www.cisco.com/warp/public/cc/cisco/mkt/switch/cat/2900xl \ /tech/malbu_wp.htmhttp://www.cisco.com/warp/public/cc/cisco/mkt/ \ switch/cat/2900xl/tech/malbu_wp.htm 2900XL Management Guide: http://www.cisco.com/univercd/cc/td/doc/product/lan/c2900xl/ \ 29_35sa6/index.htm IOW, RTFM. Later, --mike To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Proposal for new syscall to close files
Hi,
I like this approach. I have a number of often spawned daemon
processes that could benefit from this. One of the last process
we debugged where we had unwanted open filedescriptors was in
programs invoked by the cvs loginfo script.
For naming convention considerations, I might suggest 'closeall'
or 'closefdset' or something similar... at least have 'close' in
name... :-)
Good Work,
John
> It's fairly common, when spawning new processes, to want to make sure
> all unwanted FDs are closed. Currently, the options for doing this are:
>
> 1) Use fcntl(fd, F_SETFD, FD_CLOEXEC) to set the close-on-exec flag
>when the file is opened/cloned. This may not be practical if the
>FD must remain open across some exec's, but not others. It is not
>possible to ensure that FDs implicitly opened within library
>functions have the close-on-exec flag set. It may be inefficient if
>there are lots of opens and few execs.
>
> 2) Explicitly close unwanted FDs in the child, before the exec().
>This suffers from the usual resource tracking problems (ie it's
>easy to forget to close one - especially in a maze of pipe()/
>dup()/dup2() calls designed to join the child's stdin/out/err
>to the parent). It also requires that the FD's be visible to the
>function - which may be difficult (the FD may be hidden within
>another function somewhere).
>
> 3) Close all FDs except the ones you explicitly want to keep. This
>is normally something like:
> for (i = getdtablesize(); --i > 2; )
> close(i);
>The advantage is that you are sure you don't miss any. The
>disadvantage is that it requires a system call for each potentially
>open FD - >600 on my system - whereas maybe only 4 or 5 are
>actually open.
>
> In the case of option 3, you only really need to attempt to close file
> descriptors less then curproc->p_fd->fd_lastfile or even
> curproc->p_fd->fd_nfiles, but these values aren't readily accessible
> from userland. (And this still suffers the overhead of a userland
> to kernel transition for each FD).
>
> I'd therefore like to propose a new syscall that closes _all_ file
> descriptors associated with a process, except for those passed as
> 1 bits in an fd_set. The proposed API is:
>
> int cleanup_files(int nfds, const fd_set *leavefds);
>
> where nfds specifies the number of fds in *leavefds to potentially
> keep open (ie all fds >= nfds will be closed).
>
> The function would return the number of FDs closed.
>
> The implementation would be along the lines of:
>
> struct cleanup_files_args {
> int nd;
> fd_set *leave;
> };
>
> int
> cleanup_files(p, uap)
> register struct proc *p;
> register struct cleanup_files_args *uap;
> {
> fd_set s_fdset;
> fd_set *lset;
> int error, nclosed = 0;
> u_int i, ncpbytes, nfdbits;
> struct filedesc *fdp = p->p_fd;
> struct file **fpp;
> char *fdfp;
>
> if (uap->nd < 0 || uap->leave = NULL)
> return (EINVAL);
>
> /* some daemons mught not have any file descriptors */
> if (fdp == NULL) {
> p->p_retval[0] = 0;
> return (0);
> }
>
> if (uap->nd > fdp->fd_lastfile)
> uap->nd = fdp->fd_lastfile + 1;
>
> /*
>* Allocate just enough bits for the passed fd_set. Use the
>* preallocated auto buffer if possible.
>*/
> nfdbits = roundup(uap->nd, NFDBITS);
> ncpbytes = nfdbits / NBBY;
> if (ncpbytes <= sizeof s_fdset)
> lset = &s_fdset;
> else
> lset = malloc(ncpbytes, M_SELECT, M_WAITOK);
>
> error = copyin(uap->leave, lbits, ncpbytes);
> if (error != 0)
> goto done;
>
> fpp = fdp->fd_ofiles;
> fdfp = fdp->fd_ofileflags;
> for (i = 0; i < uap->nd; i++, fpp++, fdfp++) {
> if (!FD_ISSET(i, lset) && *fpp != NULL) {
> if (*fdfp & UF_MAPPED)
> (void) munmapfd(p, i);
> error = closef(*fpp, p);
> if (error != 0)
> goto done;
> nclosed++;
> *fpp = NULL;
> *fdfp = 0;
> if (i < fdp->fd_freefile)
> fdp->fd_freefile = i;
> }
> }
>
> for (; i <= fdp->fd_lastfile; i++, fpp++, fdfp++)
> if (*fpp != NULL) {
> if (*fdfp & UF_MAPPED)
> (void) munmapfd(p, i);
> error = closef(*fpp, p);
> if (error != 0)
> goto done;
> nclosed++;
> *fpp = NULL;
> *fdfp = 0;
> if (i < fdp->fd_freefile)
> fdp->fd_freefile =
Re: polling in device driver
[returning to -hackers]
On Wednesday, 21 July 1999 at 16:20:48 -0700, Jeff Hagendaz wrote:
> Hi,
>
> I asked this in -hackers, but didn't get an answer.
> Guess it is too simple to quanlify into -hackers,
> I am moving it here. Your help is highly appreciated.
No, -hackers is the right place. Just because you don't get an answer
doesn't mean that you posted in the wrong place :-)
> I am reading a Linux device driver. At some point it
> polls a device to check if it is ready. The timeout
> is set to 5 second. It uses the system jiffies to
> count the time:
>
> u32 time_out = jiffies + 5 * HZ;
> for (;;) {
> /* code to check if dev is ready */
>
> if (ready) break;
> if (intr_count == 0) schedule();
> if (jiffies > time_out) return ERROR;
> }
>
> How do I implement such polling in FreeBSD? Thanks.
If at all possible, you don't. If it's in the bottom half, you don't.
You should try to find a better way to find when the device is ready:
the driver appears to be counting interrupts, so you can probably
tsleep for 5 seconds and wakeup from the lower half when you get an
interrupt. It's difficult to give an example from the code you show.
Greg
--
When replying to this message, please copy the original recipients.
For more information, see http://www.lemis.com/questions.html
See complete headers for address, home page and phone numbers
finger g...@lemis.com for PGP public key
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
Re: Will FreeBSD ever see native IPv6 ??
On Wed, Jul 21, 1999 at 12:16:22PM -0700, Julian Elischer wrote: > > FreeBSD will have native IPV6 within a matter of weeks at this stage.. > the code is being readied as we speak. see www.kame.net . 3 sets of > developers for FreeBSD IPV6 have merged their efforts and the result of > this should be available by the end of summer (Northern). (which isn't > far away now..) Wicked. I can't wait to exercise our firewall's IPsec capabilities... Congratulations to all parties involved, and good luck with the final mile! -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator In Mountain View did Larry Wall Sedately launch a quiet plea: That DOS, the ancient system, shall On boxes pleasureless to all Run Perl though lack they C. -- ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ** To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
What good PII/PIII Motherboards for FreeBSD and Celeron CPU's
Greetings everyone, What are the current good motherboards for FreeBSD for the pentium II and III? I know on the Pentium, it was the ASUS board but for the PII/PIII, is the Abit the better board? Also, I was wondering what is the fastest Celeron chip that can be overclocked to run at 100Mhz FSB? Does it matter if it's Slot 1 or PPGA based? Thanks. Cheers, Vince - vi...@mcestate.com - vi...@gaianet.net __ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[] To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
What good Xeon boards are people using?
Need to build a good fast single processor server running FreeBSD 3.2. Uptime far more important than absolute maximum speed. However, pricing dell/compaq, etc, seems on the high side. What good boards are people using in the trenches? To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's
I hope this helps. I'm running version 3.1 on ASUS Pentium III double processor. Just a Rocket! No problems at all on the installation all the SCSI ports were recognizedmy entire machine cost me 2000 USD...similar one of a famous brabd...at least 6,000 JB At 05:26 PM 21/07/99 -0700, you wrote: >Greetings everyone, > > What are the current good motherboards for FreeBSD for the pentium >II and III? I know on the Pentium, it was the ASUS board but for the >PII/PIII, is the Abit the better board? Also, I was wondering what is the >fastest Celeron chip that can be overclocked to run at 100Mhz FSB? Does >it matter if it's Slot 1 or PPGA based? Thanks. > > >Cheers, >Vince - [EMAIL PROTECTED] - [EMAIL PROTECTED] __ >Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] >GaiaNet Corporation - M & C Estate / / / / | / | __] ] >Beverly Hills, California USA 90210 / / / / / |/ / | __] ] >HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[] > > > >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: poor ethernet performance?
> > > That's a option too... Only problem is that can take forever. :-) > > Yeah, I've noticed the 'sync-up time' takes quite awhile on a Catalyst > running 100Mbps. > that is due to the spanning tree algorithm being run. takes about 30 seconds. you can disable this with "spantree portfast" applied to the port. be careful. ;) jmb To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
1373 sound chip
I sent this to multimedia about a week ago and didn't get a response so I'm trying it here [hackers & hardware] (with minor mods): I'm setting up a new machine that has onboard sound in the form of an ES1373 Creative (Ensoniq, probably). Visual config shows an unknown device as ES0 and pcm0 doesn't find anything (tried various forms in the kernel config for that one, the last one was/is: device pcm0 Is there any driver for this chip? Under windows it uses the SoundBlaster AudioPCI 64V driver. So far I haven't found any specs on Creative's or Ensoniq's website. Can someone shed some light on possibly adapting the pcm driver to this chip (like how to ID, etc.) ? Vince. -- == Vince Vielhaber -- KA8CSH email: [EMAIL PROTECTED] flame-mail: /dev/null # includeTEAM-OS2 Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: poor ethernet performance?
On Wed, 21 Jul 1999, Modred wrote: > On Wed, 21 Jul 1999, Vincent Poy wrote: > > > Speaking about Layer 2 and layer 3. Does the Cisco Catalyst > > 2924XL and the HP ProCurve 2424M and 4000M switches fall under Layer 3 or > > just layer 2? > > Cisco, yes... HP, no clue (perhaps you could check their website). > > 2900XL Architecture Notes: > > http://www.cisco.com/warp/public/cc/cisco/mkt/switch/cat/2900xl \ > /tech/malbu_wp.htmhttp://www.cisco.com/warp/public/cc/cisco/mkt/ \ > switch/cat/2900xl/tech/malbu_wp.htm > > 2900XL Management Guide: > > http://www.cisco.com/univercd/cc/td/doc/product/lan/c2900xl/ \ > 29_35sa6/index.htm > > IOW, RTFM. I did, it gets interesting though since if it was a true Level 3 switch, it sure seems to perform more like a Level 2. Cheers, Vince - [EMAIL PROTECTED] - [EMAIL PROTECTED] __ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's
On Wed, 21 Jul 1999, Kip Macy wrote: Hmmm, we're using the ABIT BH-6 but that's all because we got the board for free so we can't complain... Cheers, Vince - [EMAIL PROTECTED] - [EMAIL PROTECTED] __ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[] > My employer has gone through numerous motherboards, we have found the ASUS > P2B (now the P2B-F) to be rock solid for Pentium II usage. > > > On Wed, 21 Jul 1999, Vincent Poy wrote: > > > Greetings everyone, > > > > What are the current good motherboards for FreeBSD for the pentium > > II and III? I know on the Pentium, it was the ASUS board but for the > > PII/PIII, is the Abit the better board? Also, I was wondering what is the > > fastest Celeron chip that can be overclocked to run at 100Mhz FSB? Does > > it matter if it's Slot 1 or PPGA based? Thanks. > > > > > > Cheers, > > Vince - [EMAIL PROTECTED] - [EMAIL PROTECTED] __ > > Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] > > GaiaNet Corporation - M & C Estate / / / / | / | __] ] > > Beverly Hills, California USA 90210 / / / / / |/ / | __] ] > > HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[] > > > > > > > > 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: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's
My employer has gone through numerous motherboards, we have found the ASUS P2B (now the P2B-F) to be rock solid for Pentium II usage. On Wed, 21 Jul 1999, Vincent Poy wrote: > Greetings everyone, > > What are the current good motherboards for FreeBSD for the pentium > II and III? I know on the Pentium, it was the ASUS board but for the > PII/PIII, is the Abit the better board? Also, I was wondering what is the > fastest Celeron chip that can be overclocked to run at 100Mhz FSB? Does > it matter if it's Slot 1 or PPGA based? Thanks. > > > Cheers, > Vince - [EMAIL PROTECTED] - [EMAIL PROTECTED] __ > Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] > GaiaNet Corporation - M & C Estate / / / / | / | __] ] > Beverly Hills, California USA 90210 / / / / / |/ / | __] ] > HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[] > > > > 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: poor ethernet performance?
On Wed, 21 Jul 1999, Vincent Poy wrote: > Speaking about Layer 2 and layer 3. Does the Cisco Catalyst > 2924XL and the HP ProCurve 2424M and 4000M switches fall under Layer 3 or > just layer 2? Cisco, yes... HP, no clue (perhaps you could check their website). 2900XL Architecture Notes: http://www.cisco.com/warp/public/cc/cisco/mkt/switch/cat/2900xl \ /tech/malbu_wp.htmhttp://www.cisco.com/warp/public/cc/cisco/mkt/ \ switch/cat/2900xl/tech/malbu_wp.htm 2900XL Management Guide: http://www.cisco.com/univercd/cc/td/doc/product/lan/c2900xl/ \ 29_35sa6/index.htm IOW, RTFM. Later, --mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: polling in device driver
[returning to -hackers]
On Wednesday, 21 July 1999 at 16:20:48 -0700, Jeff Hagendaz wrote:
> Hi,
>
> I asked this in -hackers, but didn't get an answer.
> Guess it is too simple to quanlify into -hackers,
> I am moving it here. Your help is highly appreciated.
No, -hackers is the right place. Just because you don't get an answer
doesn't mean that you posted in the wrong place :-)
> I am reading a Linux device driver. At some point it
> polls a device to check if it is ready. The timeout
> is set to 5 second. It uses the system jiffies to
> count the time:
>
> u32 time_out = jiffies + 5 * HZ;
> for (;;) {
> /* code to check if dev is ready */
>
> if (ready) break;
> if (intr_count == 0) schedule();
> if (jiffies > time_out) return ERROR;
> }
>
> How do I implement such polling in FreeBSD? Thanks.
If at all possible, you don't. If it's in the bottom half, you don't.
You should try to find a better way to find when the device is ready:
the driver appears to be counting interrupts, so you can probably
tsleep for 5 seconds and wakeup from the lower half when you get an
interrupt. It's difficult to give an example from the code you show.
Greg
--
When replying to this message, please copy the original recipients.
For more information, see http://www.lemis.com/questions.html
See complete headers for address, home page and phone numbers
finger [EMAIL PROTECTED] for PGP public key
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: Will FreeBSD ever see native IPv6 ??
On Wed, Jul 21, 1999 at 12:16:22PM -0700, Julian Elischer wrote: > > FreeBSD will have native IPV6 within a matter of weeks at this stage.. > the code is being readied as we speak. see www.kame.net . 3 sets of > developers for FreeBSD IPV6 have merged their efforts and the result of > this should be available by the end of summer (Northern). (which isn't > far away now..) Wicked. I can't wait to exercise our firewall's IPsec capabilities... Congratulations to all parties involved, and good luck with the final mile! -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator In Mountain View did Larry Wall Sedately launch a quiet plea: That DOS, the ancient system, shall On boxes pleasureless to all Run Perl though lack they C. -- ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ** To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
What good PII/PIII Motherboards for FreeBSD and Celeron CPU's
Greetings everyone, What are the current good motherboards for FreeBSD for the pentium II and III? I know on the Pentium, it was the ASUS board but for the PII/PIII, is the Abit the better board? Also, I was wondering what is the fastest Celeron chip that can be overclocked to run at 100Mhz FSB? Does it matter if it's Slot 1 or PPGA based? Thanks. Cheers, Vince - [EMAIL PROTECTED] - [EMAIL PROTECTED] __ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
What good Xeon boards are people using?
Need to build a good fast single processor server running FreeBSD 3.2. Uptime far more important than absolute maximum speed. However, pricing dell/compaq, etc, seems on the high side. What good boards are people using in the trenches? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: speed of file(1)
Matthew Dillon wrote: > > Nice rundown of the problem! > > I presume someone is going to commit this... OK, I've got it on freefall, ready to roll, and building on my 3.2-STABLE system here. I'll commit it as soon as *I've* seen it work, if somebody doesn't beat me to the punch. ;^) Thanks for the patch, Peter. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://softweyr.com/ w...@softweyr.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: poor ethernet performance?
> > > That's a option too... Only problem is that can take forever. :-) > > Yeah, I've noticed the 'sync-up time' takes quite awhile on a Catalyst > running 100Mbps. > that is due to the spanning tree algorithm being run. takes about 30 seconds. you can disable this with "spantree portfast" applied to the port. be careful. ;) jmb To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: UDMA broken in -CURRENT/-STABLE? *CRITICAL*!!!!!
Hi, On Wed, Jul 21, 1999 at 03:15:26PM -0700, Julian Elischer wrote: > try a -current but only reverting pci/ide_pci.c It'll have to wait for 18 hours or so... I'm moving the machine from -CURRENT to 3.2-RELEASE then -STABLE, so once my CDs are written and I can get da0 out then I'll play with the disk again... I only wanted a new network driver. Maybe revert -STABLE anyway if there's signs of smoke? > you can use the CVS web interface to fetch various versions... Never run current without a CVS repository is probably better advice. Regards, -Jeremy -- | "I could be anything I wanted to, but one things true --+-- Never gonna be as big as Jesus, never gonna hold the world in my hand |Never gonna be as big as Jesus, never gonna build a promised land |But that's, that's all right, OK with me..." -Audio Adrenaline To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: speed of file(1)
Matthew Dillon wrote: > > Nice rundown of the problem! > > I presume someone is going to commit this... > > -Matt > Matthew Dillon > > > :*** file/apprentice.c Wed Jan 28 07:36:21 1998 > :--- file.new/apprentice.c Wed Jul 21 12:35:21 1999 > :*** > :*** 50,55 > :--- 50,56 > : static void eatsize __P((char **)); > : > : static int maxmagic = 0; > :... I will, if nobody else has. Are there any other committers following this thread? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://softweyr.com/ w...@softweyr.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: speed of file(1)
Matthew Dillon wrote: > > Nice rundown of the problem! > > I presume someone is going to commit this... OK, I've got it on freefall, ready to roll, and building on my 3.2-STABLE system here. I'll commit it as soon as *I've* seen it work, if somebody doesn't beat me to the punch. ;^) Thanks for the patch, Peter. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://softweyr.com/ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: UDMA broken in -CURRENT/-STABLE? *CRITICAL*!!!!!
try a -current but only reverting pci/ide_pci.c you can use the CVS web interface to fetch various versions... julian On Thu, 22 Jul 1999, Jeremy Lea wrote: > Hi, > > On Wed, Jul 21, 1999 at 05:21:07PM -0400, David E. Cross wrote: > > > I was in the UDMA code yesterday > > > (but mostly in the CYRIX code... (changes elsewhere should have been > > > mostly cosmetic). > > > > > > > > > can you get the exact error message? > > > > > > julian > > > > I got it..., I happened to be working on something else at the time > > and I let it sit unattended for awhile.. it ate my disk partition rather > > badly. > > > > Here is the error I see: > > wd0: DMA failure, DMA status 5 > > > > Thank goodness I tested this -STABLE on my desk machine before I was going > > to > > place it on the home directory server for the department... > > Same error here, from 18h old -CURRENT. Asus TX97 MB and Quantum > Fireball SE (4.3GB). Thankfully my disk seems ok (I didn't write > anything to that disk with the bad kernel). > > My last kernel was from 5 July, so I can't narrow the gap any. I tried > a kernel with 0x80ff flags, and it wouldn't see my keyboard (although I > did a quick rebuild, so that might be pilot error.) > > Regards, > -Jeremy > > -- > | "I could be anything I wanted to, but one things true > --+-- Never gonna be as big as Jesus, never gonna hold the world in my hand > |Never gonna be as big as Jesus, never gonna build a promised land > |But that's, that's all right, OK with me..." -Audio Adrenaline > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: UDMA broken in -CURRENT/-STABLE? *CRITICAL*!!!!!
this looks like a hardware failure.. On Wed, 21 Jul 1999, David E. Cross wrote: > > I was in the UDMA code yesterday > > (but mostly in the CYRIX code... (changes elsewhere should have been > > mostly cosmetic). > > > > > > can you get the exact error message? > > > > julian > > I got it..., I happened to be working on something else at the time > and I let it sit unattended for awhile.. it ate my disk partition rather > badly. > > Here is the error I see: > wd0: DMA failure, DMA status 5 > > Thank goodness I tested this -STABLE on my desk machine before I was going to > place it on the home directory server for the department... > > -- > David Cross | email: cro...@cs.rpi.edu > Systems Administrator/Research Programmer | Web: > http://www.cs.rpi.edu/~crossd > Rensselaer Polytechnic Institute, | Ph: 518.276.2860 > Department of Computer Science| Fax: 518.276.4033 > I speak only for myself. | WinNT:Linux::Linux:FreeBSD > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: UDMA broken in -CURRENT/-STABLE? *CRITICAL*!!!!!
Hi, On Wed, Jul 21, 1999 at 03:15:26PM -0700, Julian Elischer wrote: > try a -current but only reverting pci/ide_pci.c It'll have to wait for 18 hours or so... I'm moving the machine from -CURRENT to 3.2-RELEASE then -STABLE, so once my CDs are written and I can get da0 out then I'll play with the disk again... I only wanted a new network driver. Maybe revert -STABLE anyway if there's signs of smoke? > you can use the CVS web interface to fetch various versions... Never run current without a CVS repository is probably better advice. Regards, -Jeremy -- | "I could be anything I wanted to, but one things true --+-- Never gonna be as big as Jesus, never gonna hold the world in my hand |Never gonna be as big as Jesus, never gonna build a promised land |But that's, that's all right, OK with me..." -Audio Adrenaline To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: UDMA broken in -CURRENT/-STABLE? *CRITICAL*!!!!!
Hi, On Wed, Jul 21, 1999 at 05:21:07PM -0400, David E. Cross wrote: > > I was in the UDMA code yesterday > > (but mostly in the CYRIX code... (changes elsewhere should have been > > mostly cosmetic). > > > > > > can you get the exact error message? > > > > julian > > I got it..., I happened to be working on something else at the time > and I let it sit unattended for awhile.. it ate my disk partition rather > badly. > > Here is the error I see: > wd0: DMA failure, DMA status 5 > > Thank goodness I tested this -STABLE on my desk machine before I was going to > place it on the home directory server for the department... Same error here, from 18h old -CURRENT. Asus TX97 MB and Quantum Fireball SE (4.3GB). Thankfully my disk seems ok (I didn't write anything to that disk with the bad kernel). My last kernel was from 5 July, so I can't narrow the gap any. I tried a kernel with 0x80ff flags, and it wouldn't see my keyboard (although I did a quick rebuild, so that might be pilot error.) Regards, -Jeremy -- | "I could be anything I wanted to, but one things true --+-- Never gonna be as big as Jesus, never gonna hold the world in my hand |Never gonna be as big as Jesus, never gonna build a promised land |But that's, that's all right, OK with me..." -Audio Adrenaline To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: speed of file(1)
Matthew Dillon wrote: > > Nice rundown of the problem! > > I presume someone is going to commit this... > > -Matt > Matthew Dillon > <[EMAIL PROTECTED]> > > :*** file/apprentice.c Wed Jan 28 07:36:21 1998 > :--- file.new/apprentice.c Wed Jul 21 12:35:21 1999 > :*** > :*** 50,55 > :--- 50,56 > : static void eatsize __P((char **)); > : > : static int maxmagic = 0; > :... I will, if nobody else has. Are there any other committers following this thread? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://softweyr.com/ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: speed of file(1)
I wrote: > Looking at ktrace with MALLOC_OPTIONS=U, it does do a lot of > realloc()ing (once for every 20 active lines in .../magic) and sbrk()s > to a maximum size of ~390KB - not really significant. and in a later message: > When I profile file in a slow system (like a 386 or 486), there is an > obvious performance bottleneck: The problem is the memcpy() invoked > from fgets(). Peter Edwards wrote: >A MAXMAGIS constant in file.h that estimates a limit of 1000 lines in >magic. (The real number is 4802) > >An array sized on MAXMAGIS, that is reallocated every ALLOC_INTR lines >of magic once MAXMAGIS is exceeded. That'll teach me to rely on the output from gprof. I thought that gprof's claim (repeated by me) that the apprentice_1() -> fgets() -> memcpy() chain was taking all the time looked dubious, but it was consistent across several systems (and it was late at night for me). (Anyone want to adapt the profiling code so that it correctly apportions time between callers, rather than just using number of calls?) My earlier statement about lots of realloc's, together with the (accurate) datapoint that memcpy() was very slow should have led me to Peter Edwards fix. It also explains why the 3.2/4.x magic file (which has only about 20% more lines) takes 50% longer to start up (continually reallocing to increase an array size is O(N^2)). Congratulations to Peter Edwards. Peter To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: UDMA broken in -CURRENT/-STABLE? *CRITICAL*!!!!!
try a -current but only reverting pci/ide_pci.c you can use the CVS web interface to fetch various versions... julian On Thu, 22 Jul 1999, Jeremy Lea wrote: > Hi, > > On Wed, Jul 21, 1999 at 05:21:07PM -0400, David E. Cross wrote: > > > I was in the UDMA code yesterday > > > (but mostly in the CYRIX code... (changes elsewhere should have been > > > mostly cosmetic). > > > > > > > > > can you get the exact error message? > > > > > > julian > > > > I got it..., I happened to be working on something else at the time > > and I let it sit unattended for awhile.. it ate my disk partition rather > > badly. > > > > Here is the error I see: > > wd0: DMA failure, DMA status 5 > > > > Thank goodness I tested this -STABLE on my desk machine before I was going to > > place it on the home directory server for the department... > > Same error here, from 18h old -CURRENT. Asus TX97 MB and Quantum > Fireball SE (4.3GB). Thankfully my disk seems ok (I didn't write > anything to that disk with the bad kernel). > > My last kernel was from 5 July, so I can't narrow the gap any. I tried > a kernel with 0x80ff flags, and it wouldn't see my keyboard (although I > did a quick rebuild, so that might be pilot error.) > > Regards, > -Jeremy > > -- > | "I could be anything I wanted to, but one things true > --+-- Never gonna be as big as Jesus, never gonna hold the world in my hand > |Never gonna be as big as Jesus, never gonna build a promised land > |But that's, that's all right, OK with me..." -Audio Adrenaline > > > 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: UDMA broken in -CURRENT/-STABLE? *CRITICAL*!!!!!
> I was in the UDMA code yesterday > (but mostly in the CYRIX code... (changes elsewhere should have been > mostly cosmetic). > > > can you get the exact error message? > > julian I got it..., I happened to be working on something else at the time and I let it sit unattended for awhile.. it ate my disk partition rather badly. Here is the error I see: wd0: DMA failure, DMA status 5 Thank goodness I tested this -STABLE on my desk machine before I was going to place it on the home directory server for the department... -- David Cross | email: cro...@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science| Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: UDMA broken in -CURRENT/-STABLE? *CRITICAL*!!!!!
this looks like a hardware failure.. On Wed, 21 Jul 1999, David E. Cross wrote: > > I was in the UDMA code yesterday > > (but mostly in the CYRIX code... (changes elsewhere should have been > > mostly cosmetic). > > > > > > can you get the exact error message? > > > > julian > > I got it..., I happened to be working on something else at the time > and I let it sit unattended for awhile.. it ate my disk partition rather > badly. > > Here is the error I see: > wd0: DMA failure, DMA status 5 > > Thank goodness I tested this -STABLE on my desk machine before I was going to > place it on the home directory server for the department... > > -- > David Cross | email: [EMAIL PROTECTED] > Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd > Rensselaer Polytechnic Institute, | Ph: 518.276.2860 > Department of Computer Science| Fax: 518.276.4033 > I speak only for myself. | WinNT:Linux::Linux:FreeBSD > > > 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: UDMA broken in -CURRENT/-STABLE? *CRITICAL*!!!!!
Hi, On Wed, Jul 21, 1999 at 05:21:07PM -0400, David E. Cross wrote: > > I was in the UDMA code yesterday > > (but mostly in the CYRIX code... (changes elsewhere should have been > > mostly cosmetic). > > > > > > can you get the exact error message? > > > > julian > > I got it..., I happened to be working on something else at the time > and I let it sit unattended for awhile.. it ate my disk partition rather > badly. > > Here is the error I see: > wd0: DMA failure, DMA status 5 > > Thank goodness I tested this -STABLE on my desk machine before I was going to > place it on the home directory server for the department... Same error here, from 18h old -CURRENT. Asus TX97 MB and Quantum Fireball SE (4.3GB). Thankfully my disk seems ok (I didn't write anything to that disk with the bad kernel). My last kernel was from 5 July, so I can't narrow the gap any. I tried a kernel with 0x80ff flags, and it wouldn't see my keyboard (although I did a quick rebuild, so that might be pilot error.) Regards, -Jeremy -- | "I could be anything I wanted to, but one things true --+-- Never gonna be as big as Jesus, never gonna hold the world in my hand |Never gonna be as big as Jesus, never gonna build a promised land |But that's, that's all right, OK with me..." -Audio Adrenaline To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: speed of file(1)
I wrote: > Looking at ktrace with MALLOC_OPTIONS=U, it does do a lot of > realloc()ing (once for every 20 active lines in .../magic) and sbrk()s > to a maximum size of ~390KB - not really significant. and in a later message: > When I profile file in a slow system (like a 386 or 486), there is an > obvious performance bottleneck: The problem is the memcpy() invoked > from fgets(). Peter Edwards <[EMAIL PROTECTED]> wrote: >A MAXMAGIS constant in file.h that estimates a limit of 1000 lines in >magic. (The real number is 4802) > >An array sized on MAXMAGIS, that is reallocated every ALLOC_INTR lines >of magic once MAXMAGIS is exceeded. That'll teach me to rely on the output from gprof. I thought that gprof's claim (repeated by me) that the apprentice_1() -> fgets() -> memcpy() chain was taking all the time looked dubious, but it was consistent across several systems (and it was late at night for me). (Anyone want to adapt the profiling code so that it correctly apportions time between callers, rather than just using number of calls?) My earlier statement about lots of realloc's, together with the (accurate) datapoint that memcpy() was very slow should have led me to Peter Edwards fix. It also explains why the 3.2/4.x magic file (which has only about 20% more lines) takes 50% longer to start up (continually reallocing to increase an array size is O(N^2)). Congratulations to Peter Edwards. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: UDMA broken in -CURRENT/-STABLE? *CRITICAL*!!!!!
> I was in the UDMA code yesterday > (but mostly in the CYRIX code... (changes elsewhere should have been > mostly cosmetic). > > > can you get the exact error message? > > julian I got it..., I happened to be working on something else at the time and I let it sit unattended for awhile.. it ate my disk partition rather badly. Here is the error I see: wd0: DMA failure, DMA status 5 Thank goodness I tested this -STABLE on my desk machine before I was going to place it on the home directory server for the department... -- David Cross | email: [EMAIL PROTECTED] Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science| Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: UDMA broken in -CURRENT/-STABLE?
I was in the UDMA code yesterday (but mostly in the CYRIX code... (changes elsewhere should have been mostly cosmetic). can you get the exact error message? julian On Wed, 21 Jul 1999, David E. Cross wrote: > I updated a system to -CURRENT last night and got a panic with alot of > messages about UDMA failing (I don't have the exact messages, I can get > them if need be). I backed down the wdc0/wdc1 controller flags from > 0xa0ffa0ff to 0x0 and everything is happy. I figured its -CURRENT, and that > is to be expected. > > I updated another system to -STABLE as of earlier today, and I got the same > thing... *eeak*. again backing down from 0xa0ffa0ff to 0x0 works like a > champ. > > The messages came right after init(8) started, and before any of the > filesystems were mounted r/w (it happened most during the fsck). > > I hope someone else has seen this (sorry I am so skimpy on the details, I > will be able to provide more soonish.) > > uname -a: > FreeBSD phoenix.cs.rpi.edu 3.2-STABLE FreeBSD 3.2-STABLE #0: Wed Jul 21 > 15:17:27 EDT 1999 r...@phoenix.cs.rpi.edu:/usr/src/sys/compile/PHOENIX > i386 > > dmesg: > [...] > ide_pci0: rev 0x00 on pci0.7.1 > [...] > > -- > David Cross | email: cro...@cs.rpi.edu > Systems Administrator/Research Programmer | Web: > http://www.cs.rpi.edu/~crossd > Rensselaer Polytechnic Institute, | Ph: 518.276.2860 > Department of Computer Science| Fax: 518.276.4033 > I speak only for myself. | WinNT:Linux::Linux:FreeBSD > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
UDMA broken in -CURRENT/-STABLE?
I updated a system to -CURRENT last night and got a panic with alot of messages about UDMA failing (I don't have the exact messages, I can get them if need be). I backed down the wdc0/wdc1 controller flags from 0xa0ffa0ff to 0x0 and everything is happy. I figured its -CURRENT, and that is to be expected. I updated another system to -STABLE as of earlier today, and I got the same thing... *eeak*. again backing down from 0xa0ffa0ff to 0x0 works like a champ. The messages came right after init(8) started, and before any of the filesystems were mounted r/w (it happened most during the fsck). I hope someone else has seen this (sorry I am so skimpy on the details, I will be able to provide more soonish.) uname -a: FreeBSD phoenix.cs.rpi.edu 3.2-STABLE FreeBSD 3.2-STABLE #0: Wed Jul 21 15:17:27 EDT 1999 r...@phoenix.cs.rpi.edu:/usr/src/sys/compile/PHOENIX i386 dmesg: [...] ide_pci0: rev 0x00 on pci0.7.1 [...] -- David Cross | email: cro...@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science| Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: any docs on how to use bus_dma_tag_create e.a. ?
As Justin T. Gibbs wrote ... Excellent help, thanks. Some more questions inserted below. > >shared memory stuff? I found some DMA stuff in ahc_pci.c: > > > > /* Allocate a dmatag for our SCB DMA maps */ > >/* XXX Should be a child of the PCI bus dma tag */ > >error = bus_dma_tag_create(/*parent*/NULL, > > A parent tag would indicate the restrictions of any parent bridge between > the device you are talking to and CPU memory. We haven't modified the > new bus code yet to pass through this information, so just leave it NULL > for now. > /*alignment*/1, > > Any alignment constraints on the target memory region of a DMA specified in > bytes. If the allocation must be 32bit aligned, you would specify 4. > > > /*boundary*/0, > > Any boundary constraints on the target memory region of a DMA, for instance > if the DMA cannot cross a 64k boundary, you would set this to 64K. > > > /*lowaddr*/BUS_SPACE_MAXADDR_32BIT, > > /*highaddr*/BUS_SPACE_MAXADDR, > > low and high address of the region that the DMA engine cannot access. Meaning e.g. the 16Mbyte barrier that ISA DMA has? For PCI this would be a 4Gb range(?). > > /*filter*/NULL, /*filterarg*/NULL, > > If the device's DMA constraints cannot be specified with a single region, > you must specify a region that encompasses all such regions and specify > a filter function to provide a finer level of control. > > > /*maxsize*/MAXBSIZE, > > Maximum DMA transfer size. > > >/*nsegments*/AHC_NSEG, > > Maximum number of discontinuities in the mapped region. Eh.. ? > > /*maxsegsz*/AHC_MAXTRANSFER_SIZE, > > Maximum size of a segment. maxsize <= nsegments * maxsegsz. Eh.. ? > > /*flags*/BUS_DMA_ALLOCNOW > > Allocate all necessary resources to handle a single mapping for this tag > at the time the tag is created. > > >Most (?) drivers seem to use the older framework (can I distinguish > >those by COMPAT_PCI_DRIVER() ?). > > You should use the new API if possible. That is what I'm planning to do. The amount of sample code in the various drivers is rather limited as most drivers use the old code. So I hope you don't mind me asking some more questions, Wilko -- | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Will FreeBSD ever see native IPv6 ??
FreeBSD will have native IPV6 within a matter of weeks at this stage..
the code is being readied as we speak. see www.kame.net . 3 sets of
developers for FreeBSD IPV6 have merged their efforts and the result of
this should be available by the end of summer (Northern). (which isn't
far away now..)
On Wed, 21 Jul 1999, David O'Brien wrote:
> So is FreeBSD *EVER* going to see native IPv6 ??
> I attended a talk by a group of Intrusion Detection researchers. They
> were basing their research on FreeBSD because they needed divert
> sockets and found FreeBSD worked perfectly for this in this respect.
> However, once they needed IPv6 and IPsec guess what happened??? They
> moved to Linux and now have such a time investment in their custom kernel
> hacks FreeBSD will never be an option for them again.
>
> NetBSD and OpenBSD get more and more coverage from IPv6/IPsec
> capabilities every day. FreeBSD has lost considerable ground if we want
> to be a platform of choice for network and security researchers.
>
> Now ever LSOF has IPv6 support for NetBSD and OpenBSD...
>
>
> - Forwarded message from Vic Abell -
> Date: Wed, 21 Jul 1999 10:53:51 -0500
> Subject: 64 bit lsof for Solaris 7; IPv6 support for {Net,Open}BSD
>
>
> IPv6 Support for {Net,Open}BSD
> ==
> ..snip..
>
> An lsof 4.45 pre-release distribution of the NetBSD and OpenBSD
> sources with the IPv6 updates is available at:
>
> ..snip..
>
> - End forwarded message -
>
> --
> -- David(obr...@nuxi.com -or- obr...@freebsd.org)
>
>
> To Unsubscribe: send mail to majord...@freebsd.org
> with "unsubscribe freebsd-hackers" in the body of the message
>
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
Re: UDMA problems on ALI chipsets
It seems Dag-Erling Smorgrav wrote: > Is anybody working on getting UltraDMA to work on ALI chipsets? I have > a scratch box with that chipset and an UDMA disks and can test patches > and perform minor debugging if anyone needs me to. > > ide_pci0: irq 0 at > device 15.0 on pci0 Use the ata driver, it has support for the aladdin chipset, and it works... -Søren To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
UDMA problems on ALI chipsets
Is anybody working on getting UltraDMA to work on ALI chipsets? I have a scratch box with that chipset and an UDMA disks and can test patches and perform minor debugging if anyone needs me to. ide_pci0: irq 0 at device 15.0 on pci0 DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: amandad zombies (fwd)
Snob Art Genre writes: > I've been beating my head against a mysterious problem for some > time now, and I'm hoping that you folks can help me out. When I run > amanda, seven out of my 16 hosts don't respond. Of these, some are > Solaris and some are FreeBSD 3.1-RELEASE, but it's the FreeBSD ones I'm > concerned with at the moment. I'm using Amanda 2.4.1. (Note that the > symptomology on the Solaris machines is different, which is why I'm > posting this to -hackers.) This was fixed in revision 1.49 of src/usr.sbin/inetd.c (1999/05/11). DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: UDMA broken in -CURRENT/-STABLE?
I was in the UDMA code yesterday (but mostly in the CYRIX code... (changes elsewhere should have been mostly cosmetic). can you get the exact error message? julian On Wed, 21 Jul 1999, David E. Cross wrote: > I updated a system to -CURRENT last night and got a panic with alot of > messages about UDMA failing (I don't have the exact messages, I can get > them if need be). I backed down the wdc0/wdc1 controller flags from > 0xa0ffa0ff to 0x0 and everything is happy. I figured its -CURRENT, and that > is to be expected. > > I updated another system to -STABLE as of earlier today, and I got the same > thing... *eeak*. again backing down from 0xa0ffa0ff to 0x0 works like a > champ. > > The messages came right after init(8) started, and before any of the > filesystems were mounted r/w (it happened most during the fsck). > > I hope someone else has seen this (sorry I am so skimpy on the details, I > will be able to provide more soonish.) > > uname -a: > FreeBSD phoenix.cs.rpi.edu 3.2-STABLE FreeBSD 3.2-STABLE #0: Wed Jul 21 15:17:27 EDT >1999 [EMAIL PROTECTED]:/usr/src/sys/compile/PHOENIX i386 > > dmesg: > [...] > ide_pci0: rev 0x00 on pci0.7.1 > [...] > > -- > David Cross | email: [EMAIL PROTECTED] > Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd > Rensselaer Polytechnic Institute, | Ph: 518.276.2860 > Department of Computer Science| Fax: 518.276.4033 > I speak only for myself. | WinNT:Linux::Linux:FreeBSD > > > 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: Base Kerberos 5 support?
:Howdy , : :I noticed this : : :http://www.microsoft.com/Windows/server/Deploy/security/MitKerb.asp : :Microsoft claims that they are going to be compatible with MIT Kerberos 5 :or so the story goes 8) : :I noticed that the based kerberized tools in FreeBSD are for Kerberos IV... : :I installed Kerberos 5 port on my system and it appears to work except :in multi-homed server: I get replay dispatch errors ... : :My work around was simply to start moving my network services to a :a box which I don't use often and it has a single interface which is okay :and right for internal network services such as kerberos . : : Cheers : Amancio Hasty Kerberos 5 is currently a port, /usr/ports/security/krb5. I would love to see krb 5 made part of the standard distribution. BEST has been using it for several years now with no problems and I believe that it is a whole lot easier to administrate then krb 4. -Matt Matthew Dillon To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: understanding code related to forced COW for debugger
On Wed, 21 Jul 1999, Matthew Dillon wrote: > > The VM_PROT_OVERRIDE_WRITE flag is only used for user-wired pages, so > it does not effect 'normal' page handling. Look carefully at the > vm_fault() code (vm/vm_fault.c line 212), that lookup only occurs > with VM_PROT_OVERRIDE_WRITE set if the normal lookup fails and the > user has wired the page. > > So if a normal lookup fails and this is a user-wired page, we try > the lookup again with VM_PROT_OVERRIDE_WRITE, presumably to handle > a faked copy-on-write fault for the debugger. This results in the > following: > > First, we temporarily increase the protections to make the page *appear* > writeable. Note: only 'appear' writeable, not actually be writeable. > > if (fault_type & VM_PROT_OVERRIDE_WRITE) > prot = entry->max_protection; > else > prot = entry->protection; To allow a debugger to write TEXT area of a program, the max_protection field must be set to include VM_PROT_WRITE by the loader. Am I right? > *wired = (entry->wired_count != 0); > if (*wired) > prot = fault_type = entry->protection; > > I'm pretty sure this piece is simply reverting the mess that the > copy-on-write stuff does for the debugger. entry->protection is what > we normally want to use. Since mlock(2) is used by user, these make sense to me. Both vm_fault_wire() and vm_fault_user_wire() have non-zero wired_count of the related map entry before calling vm_fault(). This is done by their caller vm_map_pageable() and vm_map_user_pageable(). Since you are talking about user wiring case, so for the kernel wiring case, the above code should prevent any further fault on the page after this simulated one. Therefore, a kernel-wired page will never cause protection-violation faults, while a user-wired page can, as said on the man pages of mlock(2). Since mlock(2) is used by user, these make sense to me. Thanks for your response. -Zhihui To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: poor ethernet performance?
On Tue, 20 Jul 1999, Jaye Mathisen wrote: > > Perhaps I'm missing something obvious, but since switches forward packets > selectively per port, I would think it would be hard to sniff packets on > any port, w/o administrative access to the switch to tell it to mirror > data to a different port. You can definitely do it with ARP games. I was playing with this and I ran into an interesting phenomena -- perhaps someone more familiar with the workings of switches could explain. What I was doing was having one machine send out bogus ARPs to all the machines on the network except the victim, telling them the victim was at a nonexistent MAC address. The switch would broadcast packets for this MAC address because it didn't know where it was. I would then rewrite the MAC address in the ethernet header and put the packet back on the wire so the victim would get it. Interesting part was, not only did traffic for my bogus MAC get broadcast, apparently so did ALL traffic. !! This brought the 100Mbit switch to its knees. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
UDMA broken in -CURRENT/-STABLE?
I updated a system to -CURRENT last night and got a panic with alot of messages about UDMA failing (I don't have the exact messages, I can get them if need be). I backed down the wdc0/wdc1 controller flags from 0xa0ffa0ff to 0x0 and everything is happy. I figured its -CURRENT, and that is to be expected. I updated another system to -STABLE as of earlier today, and I got the same thing... *eeak*. again backing down from 0xa0ffa0ff to 0x0 works like a champ. The messages came right after init(8) started, and before any of the filesystems were mounted r/w (it happened most during the fsck). I hope someone else has seen this (sorry I am so skimpy on the details, I will be able to provide more soonish.) uname -a: FreeBSD phoenix.cs.rpi.edu 3.2-STABLE FreeBSD 3.2-STABLE #0: Wed Jul 21 15:17:27 EDT 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/PHOENIX i386 dmesg: [...] ide_pci0: rev 0x00 on pci0.7.1 [...] -- David Cross | email: [EMAIL PROTECTED] Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science| Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: any docs on how to use bus_dma_tag_create e.a. ?
As Justin T. Gibbs wrote ... Excellent help, thanks. Some more questions inserted below. > >shared memory stuff? I found some DMA stuff in ahc_pci.c: > > > > /* Allocate a dmatag for our SCB DMA maps */ > >/* XXX Should be a child of the PCI bus dma tag */ > >error = bus_dma_tag_create(/*parent*/NULL, > > A parent tag would indicate the restrictions of any parent bridge between > the device you are talking to and CPU memory. We haven't modified the > new bus code yet to pass through this information, so just leave it NULL > for now. > /*alignment*/1, > > Any alignment constraints on the target memory region of a DMA specified in > bytes. If the allocation must be 32bit aligned, you would specify 4. > > > /*boundary*/0, > > Any boundary constraints on the target memory region of a DMA, for instance > if the DMA cannot cross a 64k boundary, you would set this to 64K. > > > /*lowaddr*/BUS_SPACE_MAXADDR_32BIT, > > /*highaddr*/BUS_SPACE_MAXADDR, > > low and high address of the region that the DMA engine cannot access. Meaning e.g. the 16Mbyte barrier that ISA DMA has? For PCI this would be a 4Gb range(?). > > /*filter*/NULL, /*filterarg*/NULL, > > If the device's DMA constraints cannot be specified with a single region, > you must specify a region that encompasses all such regions and specify > a filter function to provide a finer level of control. > > > /*maxsize*/MAXBSIZE, > > Maximum DMA transfer size. > > >/*nsegments*/AHC_NSEG, > > Maximum number of discontinuities in the mapped region. Eh.. ? > > /*maxsegsz*/AHC_MAXTRANSFER_SIZE, > > Maximum size of a segment. maxsize <= nsegments * maxsegsz. Eh.. ? > > /*flags*/BUS_DMA_ALLOCNOW > > Allocate all necessary resources to handle a single mapping for this tag > at the time the tag is created. > > >Most (?) drivers seem to use the older framework (can I distinguish > >those by COMPAT_PCI_DRIVER() ?). > > You should use the new API if possible. That is what I'm planning to do. The amount of sample code in the various drivers is rather limited as most drivers use the old code. So I hope you don't mind me asking some more questions, Wilko -- | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Base Kerberos 5 support?
Howdy , I noticed this : http://www.microsoft.com/Windows/server/Deploy/security/MitKerb.asp Microsoft claims that they are going to be compatible with MIT Kerberos 5 or so the story goes 8) I noticed that the based kerberized tools in FreeBSD are for Kerberos IV... I installed Kerberos 5 port on my system and it appears to work except in multi-homed server: I get replay dispatch errors ... My work around was simply to start moving my network services to a a box which I don't use often and it has a single interface which is okay and right for internal network services such as kerberos . Cheers -- Amancio Hasty ha...@rah.star-gate.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Will FreeBSD ever see native IPv6 ??
FreeBSD will have native IPV6 within a matter of weeks at this stage..
the code is being readied as we speak. see www.kame.net . 3 sets of
developers for FreeBSD IPV6 have merged their efforts and the result of
this should be available by the end of summer (Northern). (which isn't
far away now..)
On Wed, 21 Jul 1999, David O'Brien wrote:
> So is FreeBSD *EVER* going to see native IPv6 ??
> I attended a talk by a group of Intrusion Detection researchers. They
> were basing their research on FreeBSD because they needed divert
> sockets and found FreeBSD worked perfectly for this in this respect.
> However, once they needed IPv6 and IPsec guess what happened??? They
> moved to Linux and now have such a time investment in their custom kernel
> hacks FreeBSD will never be an option for them again.
>
> NetBSD and OpenBSD get more and more coverage from IPv6/IPsec
> capabilities every day. FreeBSD has lost considerable ground if we want
> to be a platform of choice for network and security researchers.
>
> Now ever LSOF has IPv6 support for NetBSD and OpenBSD...
>
>
> - Forwarded message from Vic Abell <[EMAIL PROTECTED]> -
> Date: Wed, 21 Jul 1999 10:53:51 -0500
> Subject: 64 bit lsof for Solaris 7; IPv6 support for {Net,Open}BSD
>
>
> IPv6 Support for {Net,Open}BSD
> ==
> ..snip..
>
> An lsof 4.45 pre-release distribution of the NetBSD and OpenBSD
> sources with the IPv6 updates is available at:
>
> ..snip..
>
> - End forwarded message -
>
> --
> -- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED])
>
>
> 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: UDMA problems on ALI chipsets
It seems Dag-Erling Smorgrav wrote: > Is anybody working on getting UltraDMA to work on ALI chipsets? I have > a scratch box with that chipset and an UDMA disks and can test patches > and perform minor debugging if anyone needs me to. > > ide_pci0: irq 0 at device 15.0 >on pci0 Use the ata driver, it has support for the aladdin chipset, and it works... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
UDMA problems on ALI chipsets
Is anybody working on getting UltraDMA to work on ALI chipsets? I have a scratch box with that chipset and an UDMA disks and can test patches and perform minor debugging if anyone needs me to. ide_pci0: irq 0 at device 15.0 on pci0 DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: amandad zombies (fwd)
Snob Art Genre <[EMAIL PROTECTED]> writes: > I've been beating my head against a mysterious problem for some > time now, and I'm hoping that you folks can help me out. When I run > amanda, seven out of my 16 hosts don't respond. Of these, some are > Solaris and some are FreeBSD 3.1-RELEASE, but it's the FreeBSD ones I'm > concerned with at the moment. I'm using Amanda 2.4.1. (Note that the > symptomology on the Solaris machines is different, which is why I'm > posting this to -hackers.) This was fixed in revision 1.49 of src/usr.sbin/inetd.c (1999/05/11). DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Base Kerberos 5 support?
:Howdy , : :I noticed this : : :http://www.microsoft.com/Windows/server/Deploy/security/MitKerb.asp : :Microsoft claims that they are going to be compatible with MIT Kerberos 5 :or so the story goes 8) : :I noticed that the based kerberized tools in FreeBSD are for Kerberos IV... : :I installed Kerberos 5 port on my system and it appears to work except :in multi-homed server: I get replay dispatch errors ... : :My work around was simply to start moving my network services to a :a box which I don't use often and it has a single interface which is okay :and right for internal network services such as kerberos . : : Cheers : Amancio Hasty Kerberos 5 is currently a port, /usr/ports/security/krb5. I would love to see krb 5 made part of the standard distribution. BEST has been using it for several years now with no problems and I believe that it is a whole lot easier to administrate then krb 4. -Matt Matthew Dillon <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: PAM & LDAP in FreeBSD
On Wed, Jul 21, 1999 at 10:57:24AM -0600, Oscar Bonilla wrote: > > I don't see where the modularized crypt would fit in then... > i totally agree that pam has this capability i was just trying to fit > in the crypt stuff people have been working on. (Mark Murray: jump in here if I get this wrong) The way I understand it, a PAM module (pam_unix?) would need to be able to look at the password hash and figure out which of the crypt functions to call. Ideally, the PAM configuration would be able to specify which crypt functions are valid for the system. That said, one of the very attractive features of specifying the crypt function in the login class is the ability to assign different crypt algorithms on a user by user basis. Regards, --Keith Stevenson-- -- Keith Stevenson System Programmer - Data Center Services - University of Louisville k.steven...@louisville.edu PGP key fingerprint = 4B 29 A8 95 A8 82 EA A2 29 CE 68 DE FC EE B6 A0 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: understanding code related to forced COW for debugger
On Wed, 21 Jul 1999, Matthew Dillon wrote: > > The VM_PROT_OVERRIDE_WRITE flag is only used for user-wired pages, so > it does not effect 'normal' page handling. Look carefully at the > vm_fault() code (vm/vm_fault.c line 212), that lookup only occurs > with VM_PROT_OVERRIDE_WRITE set if the normal lookup fails and the > user has wired the page. > > So if a normal lookup fails and this is a user-wired page, we try > the lookup again with VM_PROT_OVERRIDE_WRITE, presumably to handle > a faked copy-on-write fault for the debugger. This results in the > following: > > First, we temporarily increase the protections to make the page *appear* > writeable. Note: only 'appear' writeable, not actually be writeable. > > if (fault_type & VM_PROT_OVERRIDE_WRITE) > prot = entry->max_protection; > else > prot = entry->protection; To allow a debugger to write TEXT area of a program, the max_protection field must be set to include VM_PROT_WRITE by the loader. Am I right? > *wired = (entry->wired_count != 0); > if (*wired) > prot = fault_type = entry->protection; > > I'm pretty sure this piece is simply reverting the mess that the > copy-on-write stuff does for the debugger. entry->protection is what > we normally want to use. Since mlock(2) is used by user, these make sense to me. Both vm_fault_wire() and vm_fault_user_wire() have non-zero wired_count of the related map entry before calling vm_fault(). This is done by their caller vm_map_pageable() and vm_map_user_pageable(). Since you are talking about user wiring case, so for the kernel wiring case, the above code should prevent any further fault on the page after this simulated one. Therefore, a kernel-wired page will never cause protection-violation faults, while a user-wired page can, as said on the man pages of mlock(2). Since mlock(2) is used by user, these make sense to me. Thanks for your response. -Zhihui To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: poor ethernet performance?
On Tue, 20 Jul 1999, Jaye Mathisen wrote: > > Perhaps I'm missing something obvious, but since switches forward packets > selectively per port, I would think it would be hard to sniff packets on > any port, w/o administrative access to the switch to tell it to mirror > data to a different port. You can definitely do it with ARP games. I was playing with this and I ran into an interesting phenomena -- perhaps someone more familiar with the workings of switches could explain. What I was doing was having one machine send out bogus ARPs to all the machines on the network except the victim, telling them the victim was at a nonexistent MAC address. The switch would broadcast packets for this MAC address because it didn't know where it was. I would then rewrite the MAC address in the ethernet header and put the packet back on the wire so the victim would get it. Interesting part was, not only did traffic for my bogus MAC get broadcast, apparently so did ALL traffic. !! This brought the 100Mbit switch to its knees. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Base Kerberos 5 support?
Howdy , I noticed this : http://www.microsoft.com/Windows/server/Deploy/security/MitKerb.asp Microsoft claims that they are going to be compatible with MIT Kerberos 5 or so the story goes 8) I noticed that the based kerberized tools in FreeBSD are for Kerberos IV... I installed Kerberos 5 port on my system and it appears to work except in multi-homed server: I get replay dispatch errors ... My work around was simply to start moving my network services to a a box which I don't use often and it has a single interface which is okay and right for internal network services such as kerberos . Cheers -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Will FreeBSD ever see native IPv6 ??
So is FreeBSD *EVER* going to see native IPv6 ??
I attended a talk by a group of Intrusion Detection researchers. They
were basing their research on FreeBSD because they needed divert
sockets and found FreeBSD worked perfectly for this in this respect.
However, once they needed IPv6 and IPsec guess what happened??? They
moved to Linux and now have such a time investment in their custom kernel
hacks FreeBSD will never be an option for them again.
NetBSD and OpenBSD get more and more coverage from IPv6/IPsec
capabilities every day. FreeBSD has lost considerable ground if we want
to be a platform of choice for network and security researchers.
Now ever LSOF has IPv6 support for NetBSD and OpenBSD...
- Forwarded message from Vic Abell -
Date: Wed, 21 Jul 1999 10:53:51 -0500
Subject: 64 bit lsof for Solaris 7; IPv6 support for {Net,Open}BSD
IPv6 Support for {Net,Open}BSD
==
..snip..
An lsof 4.45 pre-release distribution of the NetBSD and OpenBSD
sources with the IPv6 updates is available at:
..snip..
- End forwarded message -
--
-- David(obr...@nuxi.com -or- obr...@freebsd.org)
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
Re: poor ethernet performance?
On Wed, 21 Jul 1999, Wes Peters wrote: > Matthew Dillon wrote: > > > > :Perhaps I'm missing something obvious, but since switches forward packets > > :selectively per port, I would think it would be hard to sniff packets on > > :any port, w/o administrative access to the switch to tell it to mirror > > :data to a different port. > > : > > :ie, if I'm plugged into port 1, I can't see traffic on a switch on port 2 > > :except for broadcast traffic... > > > > The switch routes traffic based on its ARP cache. While you cannot > > easily monitor another port's traffic, you can take over its MAC address > > and steal its traffic. > > Unmanaged layer 2 switches do that, but the "intelligent" layer 3 switches > certainly don't. Layer 3 switches can be configured to consider 2 physically > adjacent ports to be on completely different networks; they will not even > share broadcast traffic. If you shop carefully, you can even buy switches > where you can configure VLANs based on user authentication, any given > physical port can join a VLAN based on a user login program rather than > port number or MAC or IP address. Speaking about Layer 2 and layer 3. Does the Cisco Catalyst 2924XL and the HP ProCurve 2424M and 4000M switches fall under Layer 3 or just layer 2? Cheers, Vince - vi...@mcestate.com - vi...@gaianet.net __ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[] To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: PAM & LDAP in FreeBSD
On Wed, Jul 21, 1999 at 10:57:24AM -0600, Oscar Bonilla wrote: > > I don't see where the modularized crypt would fit in then... > i totally agree that pam has this capability i was just trying to fit > in the crypt stuff people have been working on. (Mark Murray: jump in here if I get this wrong) The way I understand it, a PAM module (pam_unix?) would need to be able to look at the password hash and figure out which of the crypt functions to call. Ideally, the PAM configuration would be able to specify which crypt functions are valid for the system. That said, one of the very attractive features of specifying the crypt function in the login class is the ability to assign different crypt algorithms on a user by user basis. Regards, --Keith Stevenson-- -- Keith Stevenson System Programmer - Data Center Services - University of Louisville [EMAIL PROTECTED] PGP key fingerprint = 4B 29 A8 95 A8 82 EA A2 29 CE 68 DE FC EE B6 A0 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: PAM & LDAP in FreeBSD
On Wed, Jul 21, 1999 at 06:22:39PM +, Niall Smart wrote: > [ CC list nuked ] good! :) >> Ok, here goes my understanding of how things should be, please correct me >> if i'm wrong. >> >> There are three parts to the problem: >> >> 1. Where do we get the databases from? I mean, where do we get passwd, group, >>hosts, ethers, etc from. >> >>This should be handled by a name service switch a la solaris. Basically >>we want to be able to tell the system for each individual database where >>to get the stuff from. We can add entries for each database in the system. > > Not so much as "where do we get the databases from" as "which databases > hold data for this particular service". For example DNS can store > information for the hosts service (i.e. nameserver service) but could > also > store crytographic keys which could be used for as host keys for ssh for > example. The service has a standard API (gethostbyname() for example, > or > getpwnam()) which can search through multiple disparate database types. > > (I may be mixing my terminology up here, it may be more conventional > to say "which services support this database", where the database > might be a load of struct pw for example, but hopefully its clear I > mean) > > Each particular database type might have its own configuration file. > Taking the "hosts" service for example, the configuration file for > the DNS database is /etc/resolv.conf and there is no configuration > for the files database (which uses /etc/hosts) Agreed. How would the sysadmin configure the stuff? I mean, our design should be flexible enough to allow for the kind of stuff you're talking about. I personally would like to be able to configure everything in the system the following way: $ cat /etc/nsswitch.conf passwd= ldap files hosts= dns files group= ldap files traditional service = where db to get it from here passwd means stuff that's in struct passwd hosts meand hostname to IP mapping, and so on. $ cat /etc/ldap.conf host= ldap.fisicc-ufm.edu basedn= ou=staff, dc=fisicc-ufm, dc=edu username= uid passwd= userPassword uid= userId gid= groupId home= userHome shell= defaultShell this would be all the ldap configuration stuff, for instance, how to map the struct passwd entries to the ldap records. $ cat /etc/resolv.conf usual dns configuration stuff so we would end up having a singe configuration file (nsswitch.conf) telling the system where to get the info from and then individual configuration files telling the system how to configure each individual service. now... would we want to be able to pull this individual configuration files from a certain service? could I have /etc/resolv.conf pulled from ldap for example? > >> 2. How to authorize the user? I mean, what sort of authentication should we >>use to decide if the user should be allowed in. >> >>This should be handled by PAM. > > Yes, although login programs would require that a) getpwnam returns > non-NULL and b) pam_authenticate returns PAM_SUCCESS. > this is what started the thread. I installed a pam_ldap module only to find out that login wouldn't let the user in because getpwnam returned NULL (not found on /etc/passwd). I then asked: "what would happen if login were to succeed, but once the user has logged in he/she doesn't have a username to uid mapping?" >> 3. What password hash should we use when we have the username and the >>password hash? >> >>This should be handled by the new modularized crypt. > > This is a function of the pam_unix module, a PAM module can > use smartcards, retina scanners, body odour detectors etc etc, > so it may not use password hashes at all. Each PAM module may > have its own configuration file to tell it which serial port the > smartcard reader is on for example. I don't see where the modularized crypt would fit in then... i totally agree that pam has this capability i was just trying to fit in the crypt stuff people have been working on. do I make sense? Regards, -Oscar -- For PGP Public Key: finger oboni...@fisicc-ufm.edu To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: cvs commit: src/usr.sbin/inetd inetd.c
>Can nohup really prevent processes from trapping SIGHUP? I thought it >just set the SIGUP handler to discard and hoped for the best. It's normally a bug to catch ignored signals. Daomons that reread config files when they receive a signal may be counterexamples. OTOH, they probably shouldn't be started with some signals ignored unless ignoring those signals is really wanted. >Xntpd in the base system explicitly requests its graceful termination >function, called finish(), be loaded as the SIGHUP handler. This seems to be just a bug. finish() is used for SIGHUP, SIGINT, SIGQUIT and SIGTERM. finish() just finishes (actually it has undefined behaviour since it calls exit()), so nothing except undefined behaviour is lost by ignoring these signals. Bruce To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: cvs commit: src/usr.sbin/inetd inetd.c
The point was who the heck sends the SIGHUP and why ? Poul-Henning In message <23428.932574...@axl.noc.iafrica.com>, Sheldon Hearn writes: > >[Hi-jacked from cvs-committers and cvs-all] > >On Wed, 21 Jul 1999 18:15:09 +0200, Poul-Henning Kamp wrote: > >> There is another one you may want to look at, I have not figured it >> out yet: >> >> I try to start a ntpd from /etc/rc.local this way: >> >> nohup /usr/local/bin/ntpd -d -d > /usr/ntp/x.ntpd 2>&1 & >> >>and it invariably ends up dead in a few seconds with: > >> Jul 17 12:26:39 bogon ntpd[248]: ntpd exiting on signal 1 > >Can nohup really prevent processes from trapping SIGHUP? I thought it >just set the SIGUP handler to discard and hoped for the best. > >Xntpd in the base system explicitly requests its graceful termination >function, called finish(), be loaded as the SIGHUP handler. > >What is it you'd like? > > 1) nohup should prevent processes from trapping SIGHUP. > 2) xntpd should reconfigure on SIGHUP. > 3) xntpd is getting a SIGHUP and you're not sure where from. > 4) xntpd is different from the port's ntpd in some way that > should change. > >Ciao, >Sheldon. > -- Poul-Henning Kamp FreeBSD coreteam member p...@freebsd.org "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: xmms port broken
[Hijacked from freebsd-hackers and freebsd-questions] Hi Chris, You've cross-posted this message to two inappropriate lists. The freebsd-ports mailing list is what you really wanted. A copy of this message (with your original question intact) has been sent to that list on your behalf. Ciao, Sheldon. --- Forwarded Message Message-ID: <3795f2a8.8d2e6...@thedial.com> Date: Wed, 21 Jul 1999 10:17:44 -0600 From: Christopher Taylor To: freebsd-hackers@FreeBSD.ORG, freebsd-questi...@feebsd.org Subject: xmms port broken Yesterday, I updated my ports tree with cvsup...I then attempted to make the audio/xmms port and received the following error... [r...@ezln23 xmms]# make ===> Extracting for xmms-0.9.1 >> Checksum OK for xmms-0.9.1.tar.gz. ===> xmms-0.9.1 depends on executable: libtool - found ===> xmms-0.9.1 depends on shared library: gtk12.2 - not found ===>Verifying install for gtk12.2 in /usr/ports/x11-toolkits/gtk12 ===> Returning to build of xmms-0.9.1 Error: shared library "gtk12.2" does not exist *** Error code 1 gtk12.2 _does_ exist on my system... after symlinking gtk-config and glib-config to gtk12-config and glib12-config, resectively, I was able to compile xmms by hand. However, it still gives me the same error if I try and install the xmms port. A side note...xmms plays audio fine, but the player is slow to respond to mouse clicks... - --Chris - -- Christopher Taylor Technical Director Earth Broadcasting Corporation (EBC) 415 East 200 South Salt Lake City, Utah 84111 phone: (801) 322-3949 cell: (801) 541-8287 email: ch...@thedial.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message --- End of Forwarded Message To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: understanding code related to forced COW for debugger
:I have tried to understand the following code in vm_map_lookup() without
:much success:
:
:if (fault_type & VM_PROT_OVERRIDE_WRITE)
:prot = entry->max_protection;
:else
:prot = entry->protection;
:
:
:if (entry->wired_count && (fault_type & VM_PROT_WRITE) &&
:(entry->eflags & MAP_ENTRY_COW) &&
:(fault_typea & VM_PROT_OVERRIDE_WRITE) == 0) {
:RETURN(KERN_PROTECTION_FAILURE);
:}
:
:At first, it seems to me that if you want to write a COW page, you must
:have OVERRIDE_WRITE set.
The VM_PROT_OVERRIDE_WRITE flag is only used for user-wired pages, so
it does not effect 'normal' page handling. Look carefully at the
vm_fault() code (vm/vm_fault.c line 212), that lookup only occurs
with VM_PROT_OVERRIDE_WRITE set if the normal lookup fails and the
user has wired the page.
So if a normal lookup fails and this is a user-wired page, we try
the lookup again with VM_PROT_OVERRIDE_WRITE, presumably to handle
a faked copy-on-write fault for the debugger. This results in the
following:
First, we temporarily increase the protections to make the page *appear*
writeable. Note: only 'appear' writeable, not actually be writeable.
if (fault_type & VM_PROT_OVERRIDE_WRITE)
prot = entry->max_protection;
else
prot = entry->protection;
Next we strip off only the fault bits that we care about. Note that
we have already adjusted 'prot' based on the VM_PROT_OVERRIDE_WRITE
flag so 'prot' is probably writeable. We will thus fall through this
conditional:
fault_type &= (VM_PROT_READ|VM_PROT_WRITE|VM_PROT_EXECUTE);
if ((fault_type & prot) != fault_type) {
RETURN(KERN_PROTECTION_FAILURE);
}
If this is part of a user wire and we have a write fault and the
page is copy-on-write, *AND* VM_PROT_OVERRIDE_WRITE was not set,
we return a failure. This is, in fact, the failure that is returned
when the vm_fault code initially attempts to do the lookup before
vm_fault falls through and makes a second attempt with
VM_PROT_OVERRIDE_WRITE.
if (entry->wired_count && (fault_type & VM_PROT_WRITE) &&
(entry->eflags & MAP_ENTRY_COW) &&
(fault_typea & VM_PROT_OVERRIDE_WRITE) == 0) {
RETURN(KERN_PROTECTION_FAILURE);
}
Now that we've gotten past this code we revert the protection bits
if the page is a user-wire, because it was because the page was a
user wire (indirectly, anyway) that the protections were increased in
the first place. We lose the entry->max_protection and
revert back to entry->protection. Essentially, we make the page
(probably) read-only again.
*wired = (entry->wired_count != 0);
if (*wired)
prot = fault_type = entry->protection;
... but we've already gotten past the conditionals that can cause
a failure to be returned, so the code that follows will *still* do
the copy-on-write for the debugger.
:But later I find that when wired_count is non zero, we are actually
:simulating a page fault, not a real one.
:Anyway, I do not know how the above code (1) prevents a debugger from
:writing a binary code, (2) forces
:a COW when a debugger write other data.
:
:I also have some questions on wiring a page:
:
:(1) According to the man pages of mlock(2), a wired page can still
:cause protection-violation faults.
:But in the same vm_map_lookup(), we have the following code:
:
:if (*wired)
:prot = fault_type = entry->protection;
:
:and the comment says "get it for all possible accesses". As I undersand
:it, we wire a page by simulating
:a page fault (no matter whether it is kernel or user who is wiring a
:page).
I'm pretty sure this piece is simply reverting the mess that the
copy-on-write stuff does for the debugger. entry->protection is what
we normally want to use.
The debugger copy-on-write junk is there so the debugger can modify a
program's TEXT area but the program itself *cannot* modify its own TEXT
area. It's a big mess and I don't fully understand how the structures
are faked up to handle the case.
:(2) Can the kernel wire a page of a user process without that user's
:request (by calling mlock)?
:
:Any help is appreciated.
Yes. The kernel can wire a page. It usually busies the page for the
duration, however, so vm_fault will block on the page and then retry
without actually noticing that the page has been wired. I'm probably
not entirely correct here, John may be able to say more about it.
-Matt
Matthew Dillon
To Unsubscribe: send mail to maj
Re: cvs commit: src/usr.sbin/inetd inetd.c
[Hi-jacked from cvs-committers and cvs-all] On Wed, 21 Jul 1999 18:15:09 +0200, Poul-Henning Kamp wrote: > There is another one you may want to look at, I have not figured it > out yet: > > I try to start a ntpd from /etc/rc.local this way: > > nohup /usr/local/bin/ntpd -d -d > /usr/ntp/x.ntpd 2>&1 & > >and it invariably ends up dead in a few seconds with: > Jul 17 12:26:39 bogon ntpd[248]: ntpd exiting on signal 1 Can nohup really prevent processes from trapping SIGHUP? I thought it just set the SIGUP handler to discard and hoped for the best. Xntpd in the base system explicitly requests its graceful termination function, called finish(), be loaded as the SIGHUP handler. What is it you'd like? 1) nohup should prevent processes from trapping SIGHUP. 2) xntpd should reconfigure on SIGHUP. 3) xntpd is getting a SIGHUP and you're not sure where from. 4) xntpd is different from the port's ntpd in some way that should change. Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Will FreeBSD ever see native IPv6 ??
So is FreeBSD *EVER* going to see native IPv6 ??
I attended a talk by a group of Intrusion Detection researchers. They
were basing their research on FreeBSD because they needed divert
sockets and found FreeBSD worked perfectly for this in this respect.
However, once they needed IPv6 and IPsec guess what happened??? They
moved to Linux and now have such a time investment in their custom kernel
hacks FreeBSD will never be an option for them again.
NetBSD and OpenBSD get more and more coverage from IPv6/IPsec
capabilities every day. FreeBSD has lost considerable ground if we want
to be a platform of choice for network and security researchers.
Now ever LSOF has IPv6 support for NetBSD and OpenBSD...
- Forwarded message from Vic Abell <[EMAIL PROTECTED]> -
Date: Wed, 21 Jul 1999 10:53:51 -0500
Subject: 64 bit lsof for Solaris 7; IPv6 support for {Net,Open}BSD
IPv6 Support for {Net,Open}BSD
==
..snip..
An lsof 4.45 pre-release distribution of the NetBSD and OpenBSD
sources with the IPv6 updates is available at:
..snip..
- End forwarded message -
--
-- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: xmms port broken
On Wed, 21 Jul 1999, Christopher Taylor wrote: > Date: Wed, 21 Jul 1999 10:17:44 -0600 > From: Christopher Taylor > To: freebsd-hackers@FreeBSD.ORG, freebsd-questi...@feebsd.org > Subject: xmms port broken You guessed wrong on both mailing lists. Problems with freebsd ports go to freebsd-ports ;-) Kris To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: PAM & LDAP in FreeBSD
[ CC list nuked ] > Ok, here goes my understanding of how things should be, please correct me > if i'm wrong. > > There are three parts to the problem: > > 1. Where do we get the databases from? I mean, where do we get passwd, group, >hosts, ethers, etc from. > >This should be handled by a name service switch a la solaris. Basically >we want to be able to tell the system for each individual database where >to get the stuff from. We can add entries for each database in the system. Not so much as "where do we get the databases from" as "which databases hold data for this particular service". For example DNS can store information for the hosts service (i.e. nameserver service) but could also store crytographic keys which could be used for as host keys for ssh for example. The service has a standard API (gethostbyname() for example, or getpwnam()) which can search through multiple disparate database types. (I may be mixing my terminology up here, it may be more conventional to say "which services support this database", where the database might be a load of struct pw for example, but hopefully its clear I mean) Each particular database type might have its own configuration file. Taking the "hosts" service for example, the configuration file for the DNS database is /etc/resolv.conf and there is no configuration for the files database (which uses /etc/hosts) > 2. How to authorize the user? I mean, what sort of authentication should we >use to decide if the user should be allowed in. > >This should be handled by PAM. Yes, although login programs would require that a) getpwnam returns non-NULL and b) pam_authenticate returns PAM_SUCCESS. > 3. What password hash should we use when we have the username and the >password hash? > >This should be handled by the new modularized crypt. This is a function of the pam_unix module, a PAM module can use smartcards, retina scanners, body odour detectors etc etc, so it may not use password hashes at all. Each PAM module may have its own configuration file to tell it which serial port the smartcard reader is on for example. Regards, Niall To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: poor ethernet performance?
On Wed, 21 Jul 1999, Wes Peters wrote: > Matthew Dillon wrote: > > > > :Perhaps I'm missing something obvious, but since switches forward packets > > :selectively per port, I would think it would be hard to sniff packets on > > :any port, w/o administrative access to the switch to tell it to mirror > > :data to a different port. > > : > > :ie, if I'm plugged into port 1, I can't see traffic on a switch on port 2 > > :except for broadcast traffic... > > > > The switch routes traffic based on its ARP cache. While you cannot > > easily monitor another port's traffic, you can take over its MAC address > > and steal its traffic. > > Unmanaged layer 2 switches do that, but the "intelligent" layer 3 switches > certainly don't. Layer 3 switches can be configured to consider 2 physically > adjacent ports to be on completely different networks; they will not even > share broadcast traffic. If you shop carefully, you can even buy switches > where you can configure VLANs based on user authentication, any given > physical port can join a VLAN based on a user login program rather than > port number or MAC or IP address. Speaking about Layer 2 and layer 3. Does the Cisco Catalyst 2924XL and the HP ProCurve 2424M and 4000M switches fall under Layer 3 or just layer 2? Cheers, Vince - [EMAIL PROTECTED] - [EMAIL PROTECTED] __ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
xmms port broken
Yesterday, I updated my ports tree with cvsup...I then attempted to make the audio/xmms port and received the following error... [r...@ezln23 xmms]# make ===> Extracting for xmms-0.9.1 >> Checksum OK for xmms-0.9.1.tar.gz. ===> xmms-0.9.1 depends on executable: libtool - found ===> xmms-0.9.1 depends on shared library: gtk12.2 - not found ===>Verifying install for gtk12.2 in /usr/ports/x11-toolkits/gtk12 ===> Returning to build of xmms-0.9.1 Error: shared library "gtk12.2" does not exist *** Error code 1 gtk12.2 _does_ exist on my system... after symlinking gtk-config and glib-config to gtk12-config and glib12-config, resectively, I was able to compile xmms by hand. However, it still gives me the same error if I try and install the xmms port. A side note...xmms plays audio fine, but the player is slow to respond to mouse clicks... --Chris -- Christopher Taylor Technical Director Earth Broadcasting Corporation (EBC) 415 East 200 South Salt Lake City, Utah 84111 phone: (801) 322-3949 cell: (801) 541-8287 email: ch...@thedial.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
MLINKS for select(2) FD_* macros
Hi folks, Would it be inappropriate to add select.2 MLINKS for FD_SET, FD_CLR, FD_ISSET and FD_ZERO? Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: PAM & LDAP in FreeBSD
On Thu, Jul 22, 1999 at 01:00:57AM +0900, Daniel C. Sobral wrote: > Oscar Bonilla wrote: >> >> There are three parts to the problem: >> >> 1. Where do we get the databases from? I mean, where do we get passwd, group, >>hosts, ethers, etc from. >> >>This should be handled by a name service switch a la solaris. Basically >>we want to be able to tell the system for each individual database where >>to get the stuff from. We can add entries for each database in the system. > > I perceive here an unfair biasing toward nss. Someone mentioned > defining where to get the passwords from based on the login class. > This is a very interesting option, that doesn't seem to be well > served by nss. > I was actually talking about the "other" entries. usename:uid:gid:gecos:home:shell where does PAM fit in the schema you talk about? would we need to make PAM login.conf aware then? Where do we get login.conf from? from nsswitch.conf? Regards, -Oscar -- For PGP Public Key: finger oboni...@fisicc-ufm.edu To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: linking question...
In article <199907210557.baa43...@cs.rpi.edu>, David E. Cross wrote: > > The problem indeed was conflicting libraries... (in /usr/X11R6/lib).. however > I did place on the line *immediately* before the -lwcs a -L/usr/local/lib, > however it appeared to take the /usr/X11R6/lib (which was in a previous -L > statement) version instead. Is this correct? Yes, it's correct. The -L options can appear anywhere relative to the -l options -- even after them -- and it doesn't make any difference. The relative ordering among the -L options with respect to *each other* is all ld cares about. That's been the traditional behavior on every Unix system I've ever used that supported -L at all. John -- John Polstra j...@polstra.com John D. Polstra & Co., Inc.Seattle, Washington USA "No matter how cynical I get, I just can't keep up."-- Nora Ephron To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: any docs on how to use bus_dma_tag_create e.a. ?
>> bus_dma related stuff is only required if the device has a DMA engine >> you wish to use. To access the shared memory on the card (e.g. map > >Eh, sorry, I was confused. It has *both* shared memory and a DMA engine. > >> it into the kernel's virtual address space), you will need to use >> the resource manager and bus space. > >Do you by chance have an example (maybe in -current somewhere) of the >shared memory stuff? I found some DMA stuff in ahc_pci.c: > > /* Allocate a dmatag for our SCB DMA maps */ >/* XXX Should be a child of the PCI bus dma tag */ >error = bus_dma_tag_create(/*parent*/NULL, A parent tag would indicate the restrictions of any parent bridge between the device you are talking to and CPU memory. We haven't modified the new bus code yet to pass through this information, so just leave it NULL for now. /*alignment*/1, Any alignment constraints on the target memory region of a DMA specified in bytes. If the allocation must be 32bit aligned, you would specify 4. > /*boundary*/0, Any boundary constraints on the target memory region of a DMA, for instance if the DMA cannot cross a 64k boundary, you would set this to 64K. > /*lowaddr*/BUS_SPACE_MAXADDR_32BIT, > /*highaddr*/BUS_SPACE_MAXADDR, low and high address of the region that the DMA engine cannot access. > /*filter*/NULL, /*filterarg*/NULL, If the device's DMA constraints cannot be specified with a single region, you must specify a region that encompasses all such regions and specify a filter function to provide a finer level of control. > /*maxsize*/MAXBSIZE, Maximum DMA transfer size. > /*nsegments*/AHC_NSEG, Maximum number of discontinuities in the mapped region. > /*maxsegsz*/AHC_MAXTRANSFER_SIZE, Maximum size of a segment. maxsize <= nsegments * maxsegsz. > /*flags*/BUS_DMA_ALLOCNOW Allocate all necessary resources to handle a single mapping for this tag at the time the tag is created. >Most (?) drivers seem to use the older framework (can I distinguish >those by COMPAT_PCI_DRIVER() ?). You should use the new API if possible. -- Justin To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: PAM & LDAP in FreeBSD
Oscar Bonilla wrote: > > There are three parts to the problem: > > 1. Where do we get the databases from? I mean, where do we get passwd, group, >hosts, ethers, etc from. > >This should be handled by a name service switch a la solaris. Basically >we want to be able to tell the system for each individual database where >to get the stuff from. We can add entries for each database in the system. I perceive here an unfair biasing toward nss. Someone mentioned defining where to get the passwords from based on the login class. This is a very interesting option, that doesn't seem to be well served by nss. -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org "Your usefulness to my realm ended the day you made it off Hustaing alive." -- Sun Tzu Liao to his ex-finacee, Isis Marik To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: PAM & LDAP in FreeBSD
On Wed, Jul 21, 1999 at 06:22:39PM +, Niall Smart wrote: > [ CC list nuked ] good! :) >> Ok, here goes my understanding of how things should be, please correct me >> if i'm wrong. >> >> There are three parts to the problem: >> >> 1. Where do we get the databases from? I mean, where do we get passwd, group, >>hosts, ethers, etc from. >> >>This should be handled by a name service switch a la solaris. Basically >>we want to be able to tell the system for each individual database where >>to get the stuff from. We can add entries for each database in the system. > > Not so much as "where do we get the databases from" as "which databases > hold data for this particular service". For example DNS can store > information for the hosts service (i.e. nameserver service) but could > also > store crytographic keys which could be used for as host keys for ssh for > example. The service has a standard API (gethostbyname() for example, > or > getpwnam()) which can search through multiple disparate database types. > > (I may be mixing my terminology up here, it may be more conventional > to say "which services support this database", where the database > might be a load of struct pw for example, but hopefully its clear I > mean) > > Each particular database type might have its own configuration file. > Taking the "hosts" service for example, the configuration file for > the DNS database is /etc/resolv.conf and there is no configuration > for the files database (which uses /etc/hosts) Agreed. How would the sysadmin configure the stuff? I mean, our design should be flexible enough to allow for the kind of stuff you're talking about. I personally would like to be able to configure everything in the system the following way: $ cat /etc/nsswitch.conf passwd= ldap files hosts= dns files group= ldap files traditional service = where db to get it from here passwd means stuff that's in struct passwd hosts meand hostname to IP mapping, and so on. $ cat /etc/ldap.conf host= ldap.fisicc-ufm.edu basedn= ou=staff, dc=fisicc-ufm, dc=edu username= uid passwd= userPassword uid= userId gid= groupId home= userHome shell= defaultShell this would be all the ldap configuration stuff, for instance, how to map the struct passwd entries to the ldap records. $ cat /etc/resolv.conf usual dns configuration stuff so we would end up having a singe configuration file (nsswitch.conf) telling the system where to get the info from and then individual configuration files telling the system how to configure each individual service. now... would we want to be able to pull this individual configuration files from a certain service? could I have /etc/resolv.conf pulled from ldap for example? > >> 2. How to authorize the user? I mean, what sort of authentication should we >>use to decide if the user should be allowed in. >> >>This should be handled by PAM. > > Yes, although login programs would require that a) getpwnam returns > non-NULL and b) pam_authenticate returns PAM_SUCCESS. > this is what started the thread. I installed a pam_ldap module only to find out that login wouldn't let the user in because getpwnam returned NULL (not found on /etc/passwd). I then asked: "what would happen if login were to succeed, but once the user has logged in he/she doesn't have a username to uid mapping?" >> 3. What password hash should we use when we have the username and the >>password hash? >> >>This should be handled by the new modularized crypt. > > This is a function of the pam_unix module, a PAM module can > use smartcards, retina scanners, body odour detectors etc etc, > so it may not use password hashes at all. Each PAM module may > have its own configuration file to tell it which serial port the > smartcard reader is on for example. I don't see where the modularized crypt would fit in then... i totally agree that pam has this capability i was just trying to fit in the crypt stuff people have been working on. do I make sense? Regards, -Oscar -- For PGP Public Key: finger [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
