Re: Seagate STT8000A (ATAPI/IDE) on FreeBSD? (fwd)
It seems David Krinsky wrote: > I posted this to -hardware a few days ago and haven't > gotten much in the way of feedback; since it sounds to me > like a driver bug this seems like an appropriate forum too. > > Is anyone here using -any- ATAPI drive for backup? Yup, I use one: ast0: tape drive at ata1 as slave ast0: Drive empty, readonly, reverse, qfa, ecc, 512b ast0: Max speed=600Kb/s, Transfer limit=52 blocks, Buffer size=728 blocks > When I try to tar up a usefully-sized directory or filesystem, > however, the drive will begin its work apparently correctly, but the > tar will exit with an I/O error at a variable point a few seconds to > minutes into the backup. The following goes to syslog: > > wst_done: wst0: nonrecovered data error I've seen this problem LOTS of times when using the old wd based atapi subsystem. I've never been able to find out why this is happening exactly. This was part of the reason I started out on the new ATA driver (only in -current now). I've never had this problem using the ATA driver, so I'm pretty sure its the old driver thats at fault, probably some delicate timing prob. Using the new driver I do routine backups every night on a couble of servers, not seen a signle problem yet... -Soren To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Dell PERC LVD card (Power Edge Raid Controller)
Through a mis-order I have aquired a PERC card (Actually an AMI megaRAID) which I am happy to make available to anyone genuinly interested in working on a driver (This is the PCI RAID card that goes into Dells Power Edge servers if ordered in a RAID configuration) -- Geoff Buckingham Systems Manager Netlink Internet Services To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RELENG_3 and diskless booting
please followup only in hackers. I've Just cvsuped freebsd RELENG_3 as of this evening (~21:00 mdt) and using a rom built with etherboot 4.1b9 which has worked flawlessly for the last couple of months. Tonight I getting Searching for server... My IP xxx.yyy.zzz.www Server IP aaa.bbb.ccc.ddd, GW IP fff.ggg.hhh.iii Loading /disklessroot/hostname/kernel... FreeBSD-elf Entry = 0xC01178A0 Segment -1, offset , read 0200, loadpoint text size 2 =0x001583fe c010 Segment 2, offset , read 0200, loadpoint 0010 Segment 2, offset , read 00158400, loadpoint 00258200 Write trailing bit data size 3= 0x00018780 00158400 C0259400 Segment 3, offset , read 00158400, loadpoint 00259400 Then the machine reboots previously it did . My IP xxx.yyy.zzz.www Server IP aaa.bbb.ccc.ddd, GW IP fff.ggg.hhh.iii Loading /disklessroot/hostname/kernel... FreeBSD-elf Entry = 0xC0117669 Segment -1, offset , read 0200, loadpoint text size 2 =0x001566c6 c010 Segment 2, offset , read 0200, loadpoint 0010 Segment 2, offset , read 00158400, loadpoint 00258200 Write trailing bit data size 3= 0x00018604 001566c8 c02576c8 Segment 3, offset 00c8, read 00156800, loadpoint 002576c8 then up comes the normal kernel boot messages to console I see a lot of changes have occured, the booting kernel is FreeBSD xx 3.2-STABLE FreeBSD 3.2-STABLE #9: Thu Aug 26 22: 00:55 MDT 1999 r...@:/usr/src/sys/compile/DISKLESS i386 and was cvsuped on Aug 26 around 21:00 MDT -- Email: ska...@worldgate.com Voice: +403 413 1910Fax: +403 421 4929 #575 Sun Life Place * 10123 99 Street * Edmonton, AB * Canada * T5J 3H1 ---- PGP 2.6.2 Key fingerprint = 42 9C 2C A8 4D 2B C9 C4 7D B6 00 B0 50 47 20 97 http://gras-varg.worldgate.com/~skafte/ http://www.worldgate.com/ ---- When things can't get any worse, they simplify themselves by getting a whole lot worse then complicated. A complete and utter disaster is the simplest thing in the world; it's preventing one that's complex. (Janet Morris) To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Seagate STT8000A (ATAPI/IDE) on FreeBSD? (fwd)
I posted this to -hardware a few days ago and haven't gotten much in the way of feedback; since it sounds to me like a driver bug this seems like an appropriate forum too. Is anyone here using -any- ATAPI drive for backup? Thanks in advance for any help you can provide...this is screwy, and I really would rather not have to go out and buy a different tape drive. :-/ Dave. - Forwarded message from David Krinsky - Date: Tue, 31 Aug 1999 22:26:21 -0400 From: David Krinsky To: freebsd-hardw...@freebsd.org Subject: Seagate STT8000A (ATAPI/IDE) on FreeBSD? X-Mailer: Mutt 0.95.4i Has anyone here successfully used a Seagate STT8000A (8 gig Travan) ATAPI/IDE tape drive with FreeBSD? With wst0 compiled into the kernel, the drive is recognized correctly, and even works properly with small amounts of data; I have been able to back up and restore (using tar) a small test directory. When I try to tar up a usefully-sized directory or filesystem, however, the drive will begin its work apparently correctly, but the tar will exit with an I/O error at a variable point a few seconds to minutes into the backup. The following goes to syslog: wst_done: wst0: nonrecovered data error total=337920 ERR=70 len=20 ASC=31 ASCQ=0 After this point, and until the next reboot, all attempts to access the drive cause the machine to hang for a few seconds, and then return to normal, but with the new tar process asleep, apparently uninterruptibly, on wstdsc. After the brief hang the following appears in the syslog: atapi1.1: controller not ready for cmd atapi1.1: controller not ready for cmd atapi1.1: controller not ready for cmd atapi1.1: controller not ready for cmd atapi1.1: controller not ready for cmd wst0: Sense media type failed Has anyone seen this problem? I am running 3.2-STABLE on a vanilla PIII-450. The filesystems being backed up are, in toto, quite large, but the disk space used is less than 3GB (and should thus fit on one tape with or without compression). Any help would be appreciated; I'm willing to go to -CURRENT if it'll fix the problem, but as this is my primary work machine I'd rather not do so unless I'm confident it will improve the situation. Many thanks! Dave. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hardware" in the body of the message - End forwarded message - To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Proposal: Add generic username for 3rd-party MTA's
Warner Losh wrote: > > In message <199909012256.paa01...@dingo.cdrom.com> Mike Smith writes: > : If we do this, I hope a more obvious name is chosen; something like > : "mailman" might be a start. Or "mailperson", or "postperson", or > : whatever. "mta" just feels a little obscure. > > postmanpete > > which is both obscure and descriptive. Sadly it may be sexist as > well... Hah! Try "mcfeely" for obscure and descriptive. Much better than the much-maligned "newman" or the out-of-date "cliffy". -- "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: Seagate STT8000A (ATAPI/IDE) on FreeBSD? (fwd)
It seems David Krinsky wrote: > I posted this to -hardware a few days ago and haven't > gotten much in the way of feedback; since it sounds to me > like a driver bug this seems like an appropriate forum too. > > Is anyone here using -any- ATAPI drive for backup? Yup, I use one: ast0: tape drive at ata1 as slave ast0: Drive empty, readonly, reverse, qfa, ecc, 512b ast0: Max speed=600Kb/s, Transfer limit=52 blocks, Buffer size=728 blocks > When I try to tar up a usefully-sized directory or filesystem, > however, the drive will begin its work apparently correctly, but the > tar will exit with an I/O error at a variable point a few seconds to > minutes into the backup. The following goes to syslog: > > wst_done: wst0: nonrecovered data error I've seen this problem LOTS of times when using the old wd based atapi subsystem. I've never been able to find out why this is happening exactly. This was part of the reason I started out on the new ATA driver (only in -current now). I've never had this problem using the ATA driver, so I'm pretty sure its the old driver thats at fault, probably some delicate timing prob. Using the new driver I do routine backups every night on a couble of servers, not seen a signle problem yet... -Soren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RELENG_3 and diskless booting
please followup only in hackers. I've Just cvsuped freebsd RELENG_3 as of this evening (~21:00 mdt) and using a rom built with etherboot 4.1b9 which has worked flawlessly for the last couple of months. Tonight I getting Searching for server... My IP xxx.yyy.zzz.www Server IP aaa.bbb.ccc.ddd, GW IP fff.ggg.hhh.iii Loading /disklessroot/hostname/kernel... FreeBSD-elf Entry = 0xC01178A0 Segment -1, offset , read 0200, loadpoint text size 2 =0x001583fe c010 Segment 2, offset , read 0200, loadpoint 0010 Segment 2, offset , read 00158400, loadpoint 00258200 Write trailing bit data size 3= 0x00018780 00158400 C0259400 Segment 3, offset , read 00158400, loadpoint 00259400 Then the machine reboots previously it did . My IP xxx.yyy.zzz.www Server IP aaa.bbb.ccc.ddd, GW IP fff.ggg.hhh.iii Loading /disklessroot/hostname/kernel... FreeBSD-elf Entry = 0xC0117669 Segment -1, offset , read 0200, loadpoint text size 2 =0x001566c6 c010 Segment 2, offset , read 0200, loadpoint 0010 Segment 2, offset , read 00158400, loadpoint 00258200 Write trailing bit data size 3= 0x00018604 001566c8 c02576c8 Segment 3, offset 00c8, read 00156800, loadpoint 002576c8 then up comes the normal kernel boot messages to console I see a lot of changes have occured, the booting kernel is FreeBSD xx 3.2-STABLE FreeBSD 3.2-STABLE #9: Thu Aug 26 22: 00:55 MDT 1999 root@:/usr/src/sys/compile/DISKLESS i386 and was cvsuped on Aug 26 around 21:00 MDT -- Email: [EMAIL PROTECTED] Voice: +403 413 1910Fax: +403 421 4929 #575 Sun Life Place * 10123 99 Street * Edmonton, AB * Canada * T5J 3H1 ---- PGP 2.6.2 Key fingerprint = 42 9C 2C A8 4D 2B C9 C4 7D B6 00 B0 50 47 20 97 http://gras-varg.worldgate.com/~skafte/ http://www.worldgate.com/ ---- When things can't get any worse, they simplify themselves by getting a whole lot worse then complicated. A complete and utter disaster is the simplest thing in the world; it's preventing one that's complex. (Janet Morris) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Seagate STT8000A (ATAPI/IDE) on FreeBSD? (fwd)
I posted this to -hardware a few days ago and haven't gotten much in the way of feedback; since it sounds to me like a driver bug this seems like an appropriate forum too. Is anyone here using -any- ATAPI drive for backup? Thanks in advance for any help you can provide...this is screwy, and I really would rather not have to go out and buy a different tape drive. :-/ Dave. - Forwarded message from David Krinsky <[EMAIL PROTECTED]> - Date: Tue, 31 Aug 1999 22:26:21 -0400 From: David Krinsky <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Seagate STT8000A (ATAPI/IDE) on FreeBSD? X-Mailer: Mutt 0.95.4i Has anyone here successfully used a Seagate STT8000A (8 gig Travan) ATAPI/IDE tape drive with FreeBSD? With wst0 compiled into the kernel, the drive is recognized correctly, and even works properly with small amounts of data; I have been able to back up and restore (using tar) a small test directory. When I try to tar up a usefully-sized directory or filesystem, however, the drive will begin its work apparently correctly, but the tar will exit with an I/O error at a variable point a few seconds to minutes into the backup. The following goes to syslog: wst_done: wst0: nonrecovered data error total=337920 ERR=70 len=20 ASC=31 ASCQ=0 After this point, and until the next reboot, all attempts to access the drive cause the machine to hang for a few seconds, and then return to normal, but with the new tar process asleep, apparently uninterruptibly, on wstdsc. After the brief hang the following appears in the syslog: atapi1.1: controller not ready for cmd atapi1.1: controller not ready for cmd atapi1.1: controller not ready for cmd atapi1.1: controller not ready for cmd atapi1.1: controller not ready for cmd wst0: Sense media type failed Has anyone seen this problem? I am running 3.2-STABLE on a vanilla PIII-450. The filesystems being backed up are, in toto, quite large, but the disk space used is less than 3GB (and should thus fit on one tape with or without compression). Any help would be appreciated; I'm willing to go to -CURRENT if it'll fix the problem, but as this is my primary work machine I'd rather not do so unless I'm confident it will improve the situation. Many thanks! Dave. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hardware" in the body of the message - End forwarded message - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Proposal: Add generic username for 3rd-party MTA's
Warner Losh wrote: > > In message <[EMAIL PROTECTED]> Mike Smith writes: > : If we do this, I hope a more obvious name is chosen; something like > : "mailman" might be a start. Or "mailperson", or "postperson", or > : whatever. "mta" just feels a little obscure. > > postmanpete > > which is both obscure and descriptive. Sadly it may be sexist as > well... Hah! Try "mcfeely" for obscure and descriptive. Much better than the much-maligned "newman" or the out-of-date "cliffy". -- "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: StarOffice giveaway of source code
> > Didn't they actually kinda do this when they announced the availability of > Solaris source code, and then that didn't really seem to materialize the > first time around? Maybe my recolection of events is somewhat blurred... > I remember this (under the community source code license). But never saw any details. But they do "give" away solaris for personal use (but I find it not something I want to use without source). Marty Leisner To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
Chris Costello wrote: > > On Thu, Sep 02, 1999, Robert Sexton wrote: > > I'd have to agree with the "Lets be more professional" crowd. > > > > How about as a LINT option? "If you need something so banal, you can > > turn it on yourself" > >No, since it would just be useless bloat in the source tree. I'm going to have to side with Chris on this one. I spent half of last night trying to cut and trim as much out of the kernel as I could so it would boot on a 386SX-20 with 3 MB of RAM. Needless bloat is just that. (And FWIW, I made it to 997K, with just wdc0, fdc0, sio(4), ppp(4), and MSDOS support. I just wish I had PCMCIA slots so I could BOOTP FreeBSD instead.) -- Kris Kirby --- TGIFreeBSD... 'Nuff said. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
Ollivier Robert wrote: > > According to Nick Sayer: > > Would anyone scream and projectile-vomit if I added this to identcpu.c? > > Yes. We are also FreeBSD users/developers because we don't follow the Linux > way. Bogomips are [as it says] bogus and many people acknoledge this but far > too often you see in some Linux list/newsgroup some dick sizing^W^Wbogomips > comparisons. Of course, that's what RC5DES is for. -- Kris Kirby --- TGIFreeBSD... 'Nuff said. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: StarOffice giveaway of source code
> > Didn't they actually kinda do this when they announced the availability of > Solaris source code, and then that didn't really seem to materialize the > first time around? Maybe my recolection of events is somewhat blurred... > I remember this (under the community source code license). But never saw any details. But they do "give" away solaris for personal use (but I find it not something I want to use without source). Marty Leisner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
Chris Costello wrote: > > On Thu, Sep 02, 1999, Robert Sexton wrote: > > I'd have to agree with the "Lets be more professional" crowd. > > > > How about as a LINT option? "If you need something so banal, you can > > turn it on yourself" > >No, since it would just be useless bloat in the source tree. I'm going to have to side with Chris on this one. I spent half of last night trying to cut and trim as much out of the kernel as I could so it would boot on a 386SX-20 with 3 MB of RAM. Needless bloat is just that. (And FWIW, I made it to 997K, with just wdc0, fdc0, sio(4), ppp(4), and MSDOS support. I just wish I had PCMCIA slots so I could BOOTP FreeBSD instead.) -- Kris Kirby <[EMAIL PROTECTED]> --- TGIFreeBSD... 'Nuff said. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
Ollivier Robert wrote: > > According to Nick Sayer: > > Would anyone scream and projectile-vomit if I added this to identcpu.c? > > Yes. We are also FreeBSD users/developers because we don't follow the Linux > way. Bogomips are [as it says] bogus and many people acknoledge this but far > too often you see in some Linux list/newsgroup some dick sizing^W^Wbogomips > comparisons. Of course, that's what RC5DES is for. -- Kris Kirby <[EMAIL PROTECTED]> --- TGIFreeBSD... 'Nuff said. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: MAC takeover
On Thu, 2 Sep 1999, Andrzej Bialecki wrote:
> Hi,
>
> IIRC some time ago there was a vivid discussion about ability to
> change/set MAC address of Ethernet cards. I'm faced with similar problem
> right now: when building high-availability configuration it would be very
> handy to do MAC takeover instead of IP takeover. So, my questions follow:
>
> * which cards support it (that have FreeBSD drivers of course)?
>
> * is there some way to set it (I couldn't find any code in the ifconfig
> nor in the kernel)?
>
> Thanks!
>
> Andrzej Bialecki
>
This is a bit off topic (not your post, but my reply), but
you could have the live and spare server have the same ip
on a loopback interface. This would avoid nasties with arp.
If the servers were participating in a routing protocol,
the routing protocol (can be done in BGP, OFPF or RIP)
would have to be configured such that the live server was
the preferred route to the ip address on the loopback.
If the live server goes down, the backup server becomes the
only available gateway to the ip in question.
-
Barrett Richardson (my name)
barr...@aye.net(my email address)
main(){} (my program)
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
Re: MAC takeover
On Thu, 2 Sep 1999, Andrzej Bialecki wrote:
> Hi,
>
> IIRC some time ago there was a vivid discussion about ability to
> change/set MAC address of Ethernet cards. I'm faced with similar problem
> right now: when building high-availability configuration it would be very
> handy to do MAC takeover instead of IP takeover. So, my questions follow:
>
> * which cards support it (that have FreeBSD drivers of course)?
>
> * is there some way to set it (I couldn't find any code in the ifconfig
> nor in the kernel)?
>
> Thanks!
>
> Andrzej Bialecki
>
This is a bit off topic (not your post, but my reply), but
you could have the live and spare server have the same ip
on a loopback interface. This would avoid nasties with arp.
If the servers were participating in a routing protocol,
the routing protocol (can be done in BGP, OFPF or RIP)
would have to be configured such that the live server was
the preferred route to the ip address on the loopback.
If the live server goes down, the backup server becomes the
only available gateway to the ip in question.
-
Barrett Richardson (my name)
[EMAIL PROTECTED](my email address)
main(){} (my program)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
In article you write: >> CPU: Pentium/P54C (132.73-MHz 586-class CPU) >> Origin = "GenuineIntel" Id = 0x52c Stepping=12 >> Features=0x1bf >> >> Seems more precise and informative. For 386/486 based hardware >> someone could adapt one of the numerous CPU speed detection routines >> out there. > >Indeed. In fact, if someone is truly motivated to go and find >something to do, rather than adding a BogoMIPS counter why not instead >figure out some way to add CPU speed detection to SMP machines? As >anyone with an SMP box knows, that speed information is disabled for >various reasons. What I want is a simple new readable sysctl, something like: hw.clockrate: 132 I think that this would be useful both for development (how fast is that stupid machine down in the bunker?), and system admininstration (who needs a cpu upgrade this year?). Doing this for Pentium and better systems should be trivial. Doing it for 486 and lower would just add a timing loop. Doing it for SMP would be harder. hw.cpu0.clockrate: 233 hw.cpu1.clockrate: 233 Possibly? The implementer gets to pick a better name than these. -- Jonathan To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Proposal: Add generic username for 3rd-party MTA's
sheld...@uunet.co.za said: :- Emotional arguments and matters of personal preference aren't :- helpful. The only emotional argumentation seems to be yours. A "technical" objection was made that it seems best for ports to create whatever resources they need, and not polute base distribution with them. To me that seems to be quite a compeling argument. A "technical" observation was made that many ports needing this specific kind of resource (a uid or gid) already do just this. This also seems pretty compelling. Another "technical" objection was made that in large environment, these "reserved" uid and gid things are very *very* problematic because each vendor does it a different way. This is often overlooked by developers, but it is a major interoperability problem for those of us who try to deploy Freebsd in shops with thousands of computers using NIS. Ports maintainers should try to remember to consider this. Finally, I'll add my own "technical" observatios: there is no reason why multiple ports chouldn't *choose* to use the same uid or gid or username or whatever, but that isn't a good reason to add it to the base system. Also, adding it to the base system unnecessarily complicates maintenance (because, should one of the ports be changed to require *another* uid or gid, you would either have to go back and modify the base system, or you would be back in the situation you are already in by requiring the port to add the new uid/gid). So, I'd suggest this proposal *not* be addopted. - Robert Withrow, R.W. Withrow Associates, Swampscott MA, w...@rwwa.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
In article you write: >> CPU: Pentium/P54C (132.73-MHz 586-class CPU) >> Origin = "GenuineIntel" Id = 0x52c Stepping=12 >> Features=0x1bf >> >> Seems more precise and informative. For 386/486 based hardware >> someone could adapt one of the numerous CPU speed detection routines >> out there. > >Indeed. In fact, if someone is truly motivated to go and find >something to do, rather than adding a BogoMIPS counter why not instead >figure out some way to add CPU speed detection to SMP machines? As >anyone with an SMP box knows, that speed information is disabled for >various reasons. What I want is a simple new readable sysctl, something like: hw.clockrate: 132 I think that this would be useful both for development (how fast is that stupid machine down in the bunker?), and system admininstration (who needs a cpu upgrade this year?). Doing this for Pentium and better systems should be trivial. Doing it for 486 and lower would just add a timing loop. Doing it for SMP would be harder. hw.cpu0.clockrate: 233 hw.cpu1.clockrate: 233 Possibly? The implementer gets to pick a better name than these. -- Jonathan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Proposal: Add generic username for 3rd-party MTA's
[EMAIL PROTECTED] said: :- Emotional arguments and matters of personal preference aren't :- helpful. The only emotional argumentation seems to be yours. A "technical" objection was made that it seems best for ports to create whatever resources they need, and not polute base distribution with them. To me that seems to be quite a compeling argument. A "technical" observation was made that many ports needing this specific kind of resource (a uid or gid) already do just this. This also seems pretty compelling. Another "technical" objection was made that in large environment, these "reserved" uid and gid things are very *very* problematic because each vendor does it a different way. This is often overlooked by developers, but it is a major interoperability problem for those of us who try to deploy Freebsd in shops with thousands of computers using NIS. Ports maintainers should try to remember to consider this. Finally, I'll add my own "technical" observatios: there is no reason why multiple ports chouldn't *choose* to use the same uid or gid or username or whatever, but that isn't a good reason to add it to the base system. Also, adding it to the base system unnecessarily complicates maintenance (because, should one of the ports be changed to require *another* uid or gid, you would either have to go back and modify the base system, or you would be back in the situation you are already in by requiring the port to add the new uid/gid). So, I'd suggest this proposal *not* be addopted. - Robert Withrow, R.W. Withrow Associates, Swampscott MA, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
> CPU: Pentium/P54C (132.73-MHz 586-class CPU) > Origin = "GenuineIntel" Id = 0x52c Stepping=12 > Features=0x1bf > > Seems more precise and informative. For 386/486 based hardware > someone could adapt one of the numerous CPU speed detection routines > out there. Indeed. In fact, if someone is truly motivated to go and find something to do, rather than adding a BogoMIPS counter why not instead figure out some way to add CPU speed detection to SMP machines? As anyone with an SMP box knows, that speed information is disabled for various reasons. - Jordan To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
On Thu, 2 Sep 1999, Ollivier Robert wrote: > According to Nick Sayer: > > Would anyone scream and projectile-vomit if I added this to identcpu.c? > > Yes. We are also FreeBSD users/developers because we don't follow the Linux > way. Bogomips are [as it says] bogus and many people acknoledge this but far > too often you see in some Linux list/newsgroup some dick sizing^W^Wbogomips > comparisons. oh, please... what do you call a "world-stone"? :) Seriously, I do agree with you that it's a bad idea. "Just say no to bogomips" -Alfred > > Here lies madness. > -- > Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr > FreeBSD keltia.freenix.fr 4.0-CURRENT #73: Sat Jul 31 15:36:05 CEST 1999 > > > > 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: CFD: "bogomips" CPU performance metric
"Matthew N. Dodd" wrote: > > On Thu, 2 Sep 1999, Julian Elischer wrote: > > There was such a thing in 386BSD and FreeBSD1.0 > > > > I certainly thing it was a worth-while thing. > > I'd try make the loop as similar to the Linux one so that they are > > comparable. > > My vote is to make the number printed in parity with the number printed by > a Netware server. I think we should just hack SPECint and SPECfp into the system startup and be done with it. That'll make us look professional! For those who don't want to add 10 or 15 minutes to their system we'll add an rc.conf knob to turn it off. This has got to be the dumbest discussion I've ever seen on -hackers. -- "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: CFD: "bogomips" CPU performance metric
According to Nick Sayer: > Would anyone scream and projectile-vomit if I added this to identcpu.c? Yes. We are also FreeBSD users/developers because we don't follow the Linux way. Bogomips are [as it says] bogus and many people acknoledge this but far too often you see in some Linux list/newsgroup some dick sizing^W^Wbogomips comparisons. Here lies madness. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #73: Sat Jul 31 15:36:05 CEST 1999 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
> CPU: Pentium/P54C (132.73-MHz 586-class CPU) > Origin = "GenuineIntel" Id = 0x52c Stepping=12 > Features=0x1bf > > Seems more precise and informative. For 386/486 based hardware > someone could adapt one of the numerous CPU speed detection routines > out there. Indeed. In fact, if someone is truly motivated to go and find something to do, rather than adding a BogoMIPS counter why not instead figure out some way to add CPU speed detection to SMP machines? As anyone with an SMP box knows, that speed information is disabled for various reasons. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: [mount.c]: Option "user"-patch
> This still doesn't entirely Oops. I didn't finish that thought again after the vi -r. I meant to say that even with a modifed kernel mount() call, there are difficulties getting all of the configuration possibities into the kernel propper. (Mount Options, What FS types to try, etc). - Steve -- WaterSpout Communications, Inc.c...@waterspout.com 427 North 6th Street http://www.waterspout.com/ Lafayette, IN 47901 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: [mount.c]: Option "user"-patch
On Fri, Sep 03, 1999 at 03:01:26AM +0800, adr...@freebsd.org wrote: > > The user would still have to know what type of filesystem is on > > the volume. My code tries filesystem types from a list, one by > > one, so the same command or desktop icon will mount a FAT, UFS, or > > EXT2FS floppy, for example. The system administrator can also > > specify default mount options on a device or filesystem-type basis. > > I like that idea, but that still doesn't need suid privs to do. But the mount call does. I agree that you need to specify the mount restrictions centrally. Otherwise what's to prevent me (the user) from making a floppy with a suid shell, and mounting it? It makes sense in some situations for only the user on the console to be able to perform mount operations, and to own the files once they get mounted. This is essential for a lab environment. If the options aren't appropriate for you, then configure things differently. Real configuration files are needed for this functionality. I don't buy that getting the config into/out-of the kernel is easier/better than a carefully crafted suid binary. If someone wants to propose an alternate mount API into the kernel that would provide for this functionality... that might be the best of both worlds... I've not looked at the problem in much detail though, but it would seem to address some concerns and keep the features that Mr. Korty has implemented and contributed. This still doesn't entirely - Steve -- WaterSpout Communications, Inc.c...@waterspout.com 427 North 6th Street http://www.waterspout.com/ Lafayette, IN 47901 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
RE: Using UDMA
On 02-Sep-99 smc...@aol.com wrote: > Im currently using FreeBSD-3.2 stable. How do you get UDMA support working > under FreeBSD? Do I need FreeBSD 4-Current? > > > Thanks, > Sam > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-questions" in the body of the message Actually, if you just want to probe for DMA capability on a drive use the flag 0x2000. example: diskwd0 at wdc0 drive 0 flags 0x2000 (this option will probe for DMA capability on device wd0, which corresponds to the master IDE device on the first IDE controller, I believe) Like Mark, I'm not sure if this extends to UDMA support. type 'man 4 wd' for a better explanation of the wd drivers and their capabilities. --Justin Hays To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
On Thu, 2 Sep 1999, Ollivier Robert wrote: > According to Nick Sayer: > > Would anyone scream and projectile-vomit if I added this to identcpu.c? > > Yes. We are also FreeBSD users/developers because we don't follow the Linux > way. Bogomips are [as it says] bogus and many people acknoledge this but far > too often you see in some Linux list/newsgroup some dick sizing^W^Wbogomips > comparisons. oh, please... what do you call a "world-stone"? :) Seriously, I do agree with you that it's a bad idea. "Just say no to bogomips" -Alfred > > Here lies madness. > -- > Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] > FreeBSD keltia.freenix.fr 4.0-CURRENT #73: Sat Jul 31 15:36:05 CEST 1999 > > > > 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: CFD: "bogomips" CPU performance metric
"Matthew N. Dodd" wrote: > > On Thu, 2 Sep 1999, Julian Elischer wrote: > > There was such a thing in 386BSD and FreeBSD1.0 > > > > I certainly thing it was a worth-while thing. > > I'd try make the loop as similar to the Linux one so that they are > > comparable. > > My vote is to make the number printed in parity with the number printed by > a Netware server. I think we should just hack SPECint and SPECfp into the system startup and be done with it. That'll make us look professional! For those who don't want to add 10 or 15 minutes to their system we'll add an rc.conf knob to turn it off. This has got to be the dumbest discussion I've ever seen on -hackers. -- "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: CFD: "bogomips" CPU performance metric
On Thu, 2 Sep 1999, Julian Elischer wrote: > There was such a thing in 386BSD and FreeBSD1.0 > > I certainly thing it was a worth-while thing. > I'd try make the loop as similar to the Linux one so that they are > comparable. My vote is to make the number printed in parity with the number printed by a Netware server. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | win...@jurai.net | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
According to Nick Sayer: > Would anyone scream and projectile-vomit if I added this to identcpu.c? Yes. We are also FreeBSD users/developers because we don't follow the Linux way. Bogomips are [as it says] bogus and many people acknoledge this but far too often you see in some Linux list/newsgroup some dick sizing^W^Wbogomips comparisons. Here lies madness. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 4.0-CURRENT #73: Sat Jul 31 15:36:05 CEST 1999 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: syslogd -a (fwd)
On Thu, Sep 02, 1999 at 12:51:49PM -0400, Wayne Cuddy wrote: > I had a configuration where I was logging from linux to linux which was > working. Now I have replaced the logging system with FreeBSD 3.2. > > I started the FreeBSD syslogd like this: > syslogd -a XXX.XXX.XXX.XXX > > But I see no log messages from the linux system. You may need something like this: syslogd_flags="-a XXX.XXX.XXX.XXX/32:* -a XXX.XXX.XXX.XXY/32:*" > > Thanks for the help. > > Wayne > > On Thu, 2 Sep 1999, Ben Rosengart wrote: > > > Date: Thu, 2 Sep 1999 11:57:33 -0400 (EDT) > > From: Ben Rosengart > > To: Wayne Cuddy > > Cc: FreeBSD Hackers List > > Subject: Re: syslogd -a (fwd) > > > > On Thu, 2 Sep 1999, Wayne Cuddy wrote: > > > > > I am attempting to use syslogd on FreeBSD to log messages from a linux > > > syslogd > > > with little success. Is it possible to use the FBSD syslogd to log > > > messages > > > from other unix flavors? > > > > Yes, absolutely. What is the problem you're experiencing? > > > > -- > > Ben > > > > UNIX Systems Engineer, Skunk Group > > StarMedia Network, Inc. > > > > > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-hackers" in the body of the message /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. Network Manager, Tele Danmark NET, IP-section. "Hey, are any of you guys out there actually *using* RFC 2549?" To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: [mount.c]: Option "user"-patch
> This still doesn't entirely Oops. I didn't finish that thought again after the vi -r. I meant to say that even with a modifed kernel mount() call, there are difficulties getting all of the configuration possibities into the kernel propper. (Mount Options, What FS types to try, etc). - Steve -- WaterSpout Communications, Inc.[EMAIL PROTECTED] 427 North 6th Street http://www.waterspout.com/ Lafayette, IN 47901 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Proposal: Add generic username for 3rd-party MTA's
Sheldon Hearn wrote: >I plan to add a user ``smtp'' with UID 25 and a member of group >``mail'', for use in running non-priveledged MTA's in FreeBSD. I'd support this. I think the GID should be 25 as well. David Wolfskill wrote: >I think the overall idea is good, though my tendency has been to use >somewhat higher numbers (like 65532 or 65533). I prefer 25 because it's mnemonic - since SMTP is on port 25. (And since commonality has been raised, it's worthwhile noting that Solaris refuses to accept UID's and GIDs muvh above 6). > And I do it with sendmail. So do I. Warner Losh wrote: >postmanpete Maybe postmanpat - which isn't sexist, though the ANAL types[*] may have conniptions. :-) [*] As in `IANAL, but...'. Peter To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: [mount.c]: Option "user"-patch
On Fri, Sep 03, 1999 at 03:01:26AM +0800, [EMAIL PROTECTED] wrote: > > The user would still have to know what type of filesystem is on > > the volume. My code tries filesystem types from a list, one by > > one, so the same command or desktop icon will mount a FAT, UFS, or > > EXT2FS floppy, for example. The system administrator can also > > specify default mount options on a device or filesystem-type basis. > > I like that idea, but that still doesn't need suid privs to do. But the mount call does. I agree that you need to specify the mount restrictions centrally. Otherwise what's to prevent me (the user) from making a floppy with a suid shell, and mounting it? It makes sense in some situations for only the user on the console to be able to perform mount operations, and to own the files once they get mounted. This is essential for a lab environment. If the options aren't appropriate for you, then configure things differently. Real configuration files are needed for this functionality. I don't buy that getting the config into/out-of the kernel is easier/better than a carefully crafted suid binary. If someone wants to propose an alternate mount API into the kernel that would provide for this functionality... that might be the best of both worlds... I've not looked at the problem in much detail though, but it would seem to address some concerns and keep the features that Mr. Korty has implemented and contributed. This still doesn't entirely - Steve -- WaterSpout Communications, Inc.[EMAIL PROTECTED] 427 North 6th Street http://www.waterspout.com/ Lafayette, IN 47901 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Using UDMA
On 02-Sep-99 [EMAIL PROTECTED] wrote: > Im currently using FreeBSD-3.2 stable. How do you get UDMA support working > under FreeBSD? Do I need FreeBSD 4-Current? > > > Thanks, > Sam > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message Actually, if you just want to probe for DMA capability on a drive use the flag 0x2000. example: diskwd0 at wdc0 drive 0 flags 0x2000 (this option will probe for DMA capability on device wd0, which corresponds to the master IDE device on the first IDE controller, I believe) Like Mark, I'm not sure if this extends to UDMA support. type 'man 4 wd' for a better explanation of the wd drivers and their capabilities. --Justin Hays To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
We have this for 586+ class machines: CPU: Pentium/P54C (132.73-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf Seems more precise and informative. For 386/486 based hardware someone could adapt one of the numerous CPU speed detection routines out there. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
On Thu, 2 Sep 1999, Oliver Fromme wrote: > Nick Sayer wrote in list.freebsd-hackers: > > Linux generates a meric of CPU performance as a byproduct of calibrating > > a delay loop. > > It's not a metric of CPU performance. It's just a meaningless number, > and its relation to the actual performance of the machine is very > questionable. It is not as meaningless as it seems. The computed value is used for some driver timing. It can also detect some CPU misconfigurations. Quite valuable thing. Milan Kopacka To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Using UDMA
Im currently using FreeBSD-3.2 stable. How do you get UDMA support working under FreeBSD? Do I need FreeBSD 4-Current? Thanks, Sam To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
On Thu, 2 Sep 1999, Julian Elischer wrote: > There was such a thing in 386BSD and FreeBSD1.0 > > I certainly thing it was a worth-while thing. > I'd try make the loop as similar to the Linux one so that they are > comparable. My vote is to make the number printed in parity with the number printed by a Netware server. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
> If we must have it, how about a port? - I'm definitely for the "this isn't a > good idea" crowd, When I was using Linux, I thought it was 'cute'... I've > grown up a bit since then... Create /usr/ports/useless_linux_utils Add this and code for making the keyboard lights blink in time to whatever audio CD is playing ;-) I agree with what seems to be the consenus: not only are BogoMIPS useless in themselves, but it does detract from the 'professional' feel of FreeBSD. -marc To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: syslogd -a (fwd)
On Thu, Sep 02, 1999 at 12:51:49PM -0400, Wayne Cuddy wrote: > I had a configuration where I was logging from linux to linux which was > working. Now I have replaced the logging system with FreeBSD 3.2. > > I started the FreeBSD syslogd like this: > syslogd -a XXX.XXX.XXX.XXX > > But I see no log messages from the linux system. You may need something like this: syslogd_flags="-a XXX.XXX.XXX.XXX/32:* -a XXX.XXX.XXX.XXY/32:*" > > Thanks for the help. > > Wayne > > On Thu, 2 Sep 1999, Ben Rosengart wrote: > > > Date: Thu, 2 Sep 1999 11:57:33 -0400 (EDT) > > From: Ben Rosengart <[EMAIL PROTECTED]> > > To: Wayne Cuddy <[EMAIL PROTECTED]> > > Cc: FreeBSD Hackers List <[EMAIL PROTECTED]> > > Subject: Re: syslogd -a (fwd) > > > > On Thu, 2 Sep 1999, Wayne Cuddy wrote: > > > > > I am attempting to use syslogd on FreeBSD to log messages from a linux syslogd > > > with little success. Is it possible to use the FBSD syslogd to log messages > > > from other unix flavors? > > > > Yes, absolutely. What is the problem you're experiencing? > > > > -- > > Ben > > > > UNIX Systems Engineer, Skunk Group > > StarMedia Network, Inc. > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. Network Manager, Tele Danmark NET, IP-section. "Hey, are any of you guys out there actually *using* RFC 2549?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
On Thu, Sep 02, 1999, Karl Pielorz wrote: > Chris Costello wrote: > >No, since it would just be useless bloat in the source tree. > > If we must have it, how about a port? - I'm definitely for the "this isn't a > good idea" crowd, When I was using Linux, I thought it was 'cute'... I've > grown up a bit since then... I don't think the local Ports Wraith would be amazingly happy with a port which modifies identcpu.c, which is part of the kernel. > -Kp -- |Chris Costello |Base 8 is just like base 10, if you are missing two fingers. - Tom Lehrer `-- To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
It was there... when I added the code to calibrate the delay loops originally and added the DELAY macro, it printed out the callibration factor.. (DELAY was originally a spin loop) It wasn't called 'BOGOMIPS...' On Thu, 2 Sep 1999, Nate Williams wrote: > > There was such a thing in 386BSD and FreeBSD1.0 > > I remember no such thing doing a 'bogomips' to compare against Linux. > Certainly not in 386BSD. > > > > Nate > > > > > I certainly thing it was a worth-while thing. > > I'd try make the loop as similar to the Linux one so that they are > > comparable. > > > > On Thu, 2 Sep 1999, Nick Sayer wrote: > > > > > Linux generates a meric of CPU performance as a byproduct of calibrating > > > a delay loop. > > > We don't require doing any such thing, and so adding it would be purely > > > cosmetic. > > > However, I allege that cosmetic things aren't in and of themselves evil, > > > so long as > > > they don't break anything in the process. > > > > > > I would like to generate a number that will hopefully be reasonably > > > compatible with > > > the one Linux spits out. The best method I have come up with is to have > > > a similar > > > (the same?) count down loop in assembler. Have it count down from > > > 1,000,000 and > > > see how much nanotime() has gone by. NANSPERSEC/nansused = bogomips. > > > A 1 bogomips machine will take an extra second to do this (anything > > > likely to be > > > even able to run FreeBSD should exceed 1 BM - yes, ha ha), and a kBM CPU > > > > > > can do it in 1 ms. Perhaps in the future a prescaler might be required, > > > but > > > this whole thing is just really chrome anyway. > > > > > > Would anyone scream and projectile-vomit if I added this to identcpu.c? > > > > > > > > > > > > > > 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: CFD: "bogomips" CPU performance metric
Chris Costello wrote: > >No, since it would just be useless bloat in the source tree. > If we must have it, how about a port? - I'm definitely for the "this isn't a good idea" crowd, When I was using Linux, I thought it was 'cute'... I've grown up a bit since then... -Kp To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
On Thu, Sep 02, 1999, Nick Sayer wrote: > Would anyone scream and projectile-vomit if I added this to identcpu.c? Yes, I would. The way I interpret it, along with "useless blinking light", is as follows: BogoMIPS is but the combination of "Bogus" and an acronym for "Meaningless Indicator of Processor Speed." :) -- |Chris Costello |You might have mail. `-- To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
On Thu, Sep 02, 1999, Robert Sexton wrote: > I'd have to agree with the "Lets be more professional" crowd. > > How about as a LINT option? "If you need something so banal, you can > turn it on yourself" No, since it would just be useless bloat in the source tree. -- |Chris Costello |Supercomputer: Turns a CPU-bound problem into |an I/O-bound problem. - Ken Batcher `--- To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Proposal: Add generic username for 3rd-party MTA's
Sheldon Hearn <[EMAIL PROTECTED]> wrote: >I plan to add a user ``smtp'' with UID 25 and a member of group >``mail'', for use in running non-priveledged MTA's in FreeBSD. I'd support this. I think the GID should be 25 as well. David Wolfskill <[EMAIL PROTECTED]> wrote: >I think the overall idea is good, though my tendency has been to use >somewhat higher numbers (like 65532 or 65533). I prefer 25 because it's mnemonic - since SMTP is on port 25. (And since commonality has been raised, it's worthwhile noting that Solaris refuses to accept UID's and GIDs muvh above 6). > And I do it with sendmail. So do I. Warner Losh <[EMAIL PROTECTED]> wrote: >postmanpete Maybe postmanpat - which isn't sexist, though the ANAL types[*] may have conniptions. :-) [*] As in `IANAL, but...'. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Linux StarOffice51 runs on -stable
According to Vince Vielhaber: > There was a patch posted on the freebsd.misc newsgroup the other day for I re-posted the patch for people not running -STABLE yes. > procfs that eliminates the need for the "hackery". It's supposed to be > already in -current and I don't recall if it's supposed to be in -stable > now or just apply cleanly to -stable. I got it to apply to 3.2-CD but > had to do some of it manually. It is now included in -STABLE & -CURRENT (thanks to Marcel). -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #73: Sat Jul 31 15:36:05 CEST 1999 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Proposal: Add generic username for 3rd-party MTA's
According to Mike Smith: > If we do this, I hope a more obvious name is chosen; something like > "mailman" might be a start. Or "mailperson", or "postperson", or > whatever. "mta" just feels a little obscure. "smtp", the first proposal is a better idea then. "mailman" (like it is used on hub) is more for a human. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #73: Sat Jul 31 15:36:05 CEST 1999 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
> There was such a thing in 386BSD and FreeBSD1.0 I remember no such thing doing a 'bogomips' to compare against Linux. Certainly not in 386BSD. Nate > > I certainly thing it was a worth-while thing. > I'd try make the loop as similar to the Linux one so that they are > comparable. > > On Thu, 2 Sep 1999, Nick Sayer wrote: > > > Linux generates a meric of CPU performance as a byproduct of calibrating > > a delay loop. > > We don't require doing any such thing, and so adding it would be purely > > cosmetic. > > However, I allege that cosmetic things aren't in and of themselves evil, > > so long as > > they don't break anything in the process. > > > > I would like to generate a number that will hopefully be reasonably > > compatible with > > the one Linux spits out. The best method I have come up with is to have > > a similar > > (the same?) count down loop in assembler. Have it count down from > > 1,000,000 and > > see how much nanotime() has gone by. NANSPERSEC/nansused = bogomips. > > A 1 bogomips machine will take an extra second to do this (anything > > likely to be > > even able to run FreeBSD should exceed 1 BM - yes, ha ha), and a kBM CPU > > > > can do it in 1 ms. Perhaps in the future a prescaler might be required, > > but > > this whole thing is just really chrome anyway. > > > > Would anyone scream and projectile-vomit if I added this to identcpu.c? > > > > > > > > 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: CFD: "bogomips" CPU performance metric
As Nick Sayer wrote ... > so long as > they don't break anything in the process. > > I would like to generate a number that will hopefully be reasonably > compatible with > the one Linux spits out. The best method I have come up with is to have > a similar > (the same?) count down loop in assembler. Have it count down from > 1,000,000 and > see how much nanotime() has gone by. NANSPERSEC/nansused = bogomips. > A 1 bogomips machine will take an extra second to do this (anything > likely to be > even able to run FreeBSD should exceed 1 BM - yes, ha ha), and a kBM CPU > > can do it in 1 ms. Perhaps in the future a prescaler might be required, > but > this whole thing is just really chrome anyway. > > Would anyone scream and projectile-vomit if I added this to identcpu.c? I really don't see any merit in adding Linux-isms like this. Sounds a bit like the 'hack of the day' to me. I feel FreeBSD is well respected for it's stability etc. Not for it's 'me too' Linux-isms without any practical use. Mind you, I don't say Linux does not have stuff that is useful for inclusion in FreeBSD. I just stay BogoMips is what it calls itself: bogus, and should be kept from the FreeBSD kernel. Just my Dfl 0.02 W/ -- | / 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: CFD: "bogomips" CPU performance metric
We have this for 586+ class machines: CPU: Pentium/P54C (132.73-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf Seems more precise and informative. For 386/486 based hardware someone could adapt one of the numerous CPU speed detection routines out there. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
On Thu, 2 Sep 1999, Oliver Fromme wrote: > Nick Sayer wrote in list.freebsd-hackers: > > Linux generates a meric of CPU performance as a byproduct of calibrating > > a delay loop. > > It's not a metric of CPU performance. It's just a meaningless number, > and its relation to the actual performance of the machine is very > questionable. It is not as meaningless as it seems. The computed value is used for some driver timing. It can also detect some CPU misconfigurations. Quite valuable thing. Milan Kopacka To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Using UDMA
Im currently using FreeBSD-3.2 stable. How do you get UDMA support working under FreeBSD? Do I need FreeBSD 4-Current? Thanks, Sam To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
> If we must have it, how about a port? - I'm definitely for the "this isn't a > good idea" crowd, When I was using Linux, I thought it was 'cute'... I've > grown up a bit since then... Create /usr/ports/useless_linux_utils Add this and code for making the keyboard lights blink in time to whatever audio CD is playing ;-) I agree with what seems to be the consenus: not only are BogoMIPS useless in themselves, but it does detract from the 'professional' feel of FreeBSD. -marc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
Nick Sayer wrote in list.freebsd-hackers: > Linux generates a meric of CPU performance as a byproduct of calibrating > a delay loop. It's not a metric of CPU performance. It's just a meaningless number, and its relation to the actual performance of the machine is very questionable. > We don't require doing any such thing, and so adding it would be purely > cosmetic. > However, I allege that cosmetic things aren't in and of themselves evil, > so long as > they don't break anything in the process. It would break user's confidence in the seriousness of the system. > Would anyone scream and projectile-vomit if I added this to identcpu.c? I would, FWIW. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:o...@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
On Thu, Sep 02, 1999, Karl Pielorz wrote: > Chris Costello wrote: > >No, since it would just be useless bloat in the source tree. > > If we must have it, how about a port? - I'm definitely for the "this isn't a > good idea" crowd, When I was using Linux, I thought it was 'cute'... I've > grown up a bit since then... I don't think the local Ports Wraith would be amazingly happy with a port which modifies identcpu.c, which is part of the kernel. > -Kp -- |Chris Costello <[EMAIL PROTECTED]> |Base 8 is just like base 10, if you are missing two fingers. - Tom Lehrer `-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
It was there... when I added the code to calibrate the delay loops originally and added the DELAY macro, it printed out the callibration factor.. (DELAY was originally a spin loop) It wasn't called 'BOGOMIPS...' On Thu, 2 Sep 1999, Nate Williams wrote: > > There was such a thing in 386BSD and FreeBSD1.0 > > I remember no such thing doing a 'bogomips' to compare against Linux. > Certainly not in 386BSD. > > > > Nate > > > > > I certainly thing it was a worth-while thing. > > I'd try make the loop as similar to the Linux one so that they are > > comparable. > > > > On Thu, 2 Sep 1999, Nick Sayer wrote: > > > > > Linux generates a meric of CPU performance as a byproduct of calibrating > > > a delay loop. > > > We don't require doing any such thing, and so adding it would be purely > > > cosmetic. > > > However, I allege that cosmetic things aren't in and of themselves evil, > > > so long as > > > they don't break anything in the process. > > > > > > I would like to generate a number that will hopefully be reasonably > > > compatible with > > > the one Linux spits out. The best method I have come up with is to have > > > a similar > > > (the same?) count down loop in assembler. Have it count down from > > > 1,000,000 and > > > see how much nanotime() has gone by. NANSPERSEC/nansused = bogomips. > > > A 1 bogomips machine will take an extra second to do this (anything > > > likely to be > > > even able to run FreeBSD should exceed 1 BM - yes, ha ha), and a kBM CPU > > > > > > can do it in 1 ms. Perhaps in the future a prescaler might be required, > > > but > > > this whole thing is just really chrome anyway. > > > > > > Would anyone scream and projectile-vomit if I added this to identcpu.c? > > > > > > > > > > > > > > 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: CFD: "bogomips" CPU performance metric
Chris Costello wrote: > >No, since it would just be useless bloat in the source tree. > If we must have it, how about a port? - I'm definitely for the "this isn't a good idea" crowd, When I was using Linux, I thought it was 'cute'... I've grown up a bit since then... -Kp To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
On Thu, Sep 02, 1999, Nick Sayer wrote: > Would anyone scream and projectile-vomit if I added this to identcpu.c? Yes, I would. The way I interpret it, along with "useless blinking light", is as follows: BogoMIPS is but the combination of "Bogus" and an acronym for "Meaningless Indicator of Processor Speed." :) -- |Chris Costello <[EMAIL PROTECTED]> |You might have mail. `-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
On Thu, Sep 02, 1999, Robert Sexton wrote: > I'd have to agree with the "Lets be more professional" crowd. > > How about as a LINT option? "If you need something so banal, you can > turn it on yourself" No, since it would just be useless bloat in the source tree. -- |Chris Costello <[EMAIL PROTECTED]> |Supercomputer: Turns a CPU-bound problem into |an I/O-bound problem. - Ken Batcher `--- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
On Thu, Sep 02, 1999 at 10:40:30AM -0700, Nick Sayer wrote: > Linux generates a meric of CPU performance as a byproduct of calibrating > a delay loop. > We don't require doing any such thing, and so adding it would be purely > cosmetic. > However, I allege that cosmetic things aren't in and of themselves evil, > so long as > they don't break anything in the process. I'd have to agree with the "Lets be more professional" crowd. How about as a LINT option? "If you need something so banal, you can turn it on yourself" -- Robert Sexton, rob...@kudra.com "Imagine if every Thursday your shoes exploded if you tied them the usual way. This happens to us all the time with computers, and nobody thinks of complaining." -- Jeff Raskin, interviewed in Doctor Dobb's Journal To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Linux StarOffice51 runs on -stable
According to Vince Vielhaber: > There was a patch posted on the freebsd.misc newsgroup the other day for I re-posted the patch for people not running -STABLE yes. > procfs that eliminates the need for the "hackery". It's supposed to be > already in -current and I don't recall if it's supposed to be in -stable > now or just apply cleanly to -stable. I got it to apply to 3.2-CD but > had to do some of it manually. It is now included in -STABLE & -CURRENT (thanks to Marcel). -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 4.0-CURRENT #73: Sat Jul 31 15:36:05 CEST 1999 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Proposal: Add generic username for 3rd-party MTA's
According to Mike Smith: > If we do this, I hope a more obvious name is chosen; something like > "mailman" might be a start. Or "mailperson", or "postperson", or > whatever. "mta" just feels a little obscure. "smtp", the first proposal is a better idea then. "mailman" (like it is used on hub) is more for a human. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 4.0-CURRENT #73: Sat Jul 31 15:36:05 CEST 1999 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
> There was such a thing in 386BSD and FreeBSD1.0 I remember no such thing doing a 'bogomips' to compare against Linux. Certainly not in 386BSD. Nate > > I certainly thing it was a worth-while thing. > I'd try make the loop as similar to the Linux one so that they are > comparable. > > On Thu, 2 Sep 1999, Nick Sayer wrote: > > > Linux generates a meric of CPU performance as a byproduct of calibrating > > a delay loop. > > We don't require doing any such thing, and so adding it would be purely > > cosmetic. > > However, I allege that cosmetic things aren't in and of themselves evil, > > so long as > > they don't break anything in the process. > > > > I would like to generate a number that will hopefully be reasonably > > compatible with > > the one Linux spits out. The best method I have come up with is to have > > a similar > > (the same?) count down loop in assembler. Have it count down from > > 1,000,000 and > > see how much nanotime() has gone by. NANSPERSEC/nansused = bogomips. > > A 1 bogomips machine will take an extra second to do this (anything > > likely to be > > even able to run FreeBSD should exceed 1 BM - yes, ha ha), and a kBM CPU > > > > can do it in 1 ms. Perhaps in the future a prescaler might be required, > > but > > this whole thing is just really chrome anyway. > > > > Would anyone scream and projectile-vomit if I added this to identcpu.c? > > > > > > > > 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: Linux StarOffice51 runs on -stable
On Thu, 2 Sep 1999, Marcel Moolenaar wrote: > jack wrote: > > > > -rw-r--r-- 1 marcel marcel 72192512 Jul 23 11:47 so51_lnx_01.tar > > > MD5 (so51_lnx_01.tar) = 347ffa68be6c1d7b89fd843591afb0d3 > > > > so51a_lnx_01.tar > > -rw-r--r-- 1 jacko user 70393856 Aug 31 15:47 so51a_lnx_01.tar > > (libs are all libxxx517x.so) > > requires jumping throught the hoops (unzip setup.zip, etc.) to > > install but runs OOTB after that. I havn't tried to do a > > 'network' install. > > Sigh... > > For the record, I'm running the same version as jack and after looking at procfs_status.c in -stable (and current), this version should run with either version. -RELEASE, however, requires the patch. 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: Linux StarOffice51 runs on -stable
jack wrote: > > Today Marcel Moolenaar wrote: > > > bro...@one-eyed-alien.net wrote: > > > > > > On Thu, 2 Sep 1999, Marcel Moolenaar wrote: > > > > > > > SO5.1 installs OOTB on both -current and -stable. I suspect your > > > > -stable is > > > > not recent? The fact that soffice runs setup again and again depend to a missing file... add in the home of the user that make the install this missing file (2 lines): seaside:/usr/local/www/data/neuro/admin# less /home/gmarco/.sversionrc [Versions] StarOffice 5.1=/usr/local/Office51 -- Regards... Gianmarco "Unix expert since yesterday" http://www.giovannelli.it To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
UCB removes advertising clause
This is apparently old news, but I don't recall seeing anything about it
on the lists, and didn't hear about it until it hit Slashdot a short while
ago.
ftp://ftp.cs.berkeley.edu/pub/4bsd/README.Impt.License.Change:
July 22, 1999
To All Licensees, Distributors of Any Version of BSD:
As you know, certain of the Berkeley Software Distribution ("BSD") source
code files require that further distributions of products containing all or
portions of the software, acknowledge within their advertising materials
that such products contain software developed by UC Berkeley and its
contributors.
Specifically, the provision reads:
" * 3. All advertising materials mentioning features or use of this software
*must display the following acknowledgement:
*This product includes software developed by the University of
*California, Berkeley and its contributors."
Effective immediately, licensees and distributors are no longer required to
include the acknowledgement within advertising materials. Accordingly, the
foregoing paragraph of those BSD Unix files containing it is hereby deleted
in its entirety.
William Hoskins
Director, Office of Technology Licensing
University of California, Berkeley
--
Brian Buchanan br...@csua.berkeley.edu
--
FreeBSD - The Power to Serve! http://www.freebsd.org
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
As Nick Sayer wrote ... > so long as > they don't break anything in the process. > > I would like to generate a number that will hopefully be reasonably > compatible with > the one Linux spits out. The best method I have come up with is to have > a similar > (the same?) count down loop in assembler. Have it count down from > 1,000,000 and > see how much nanotime() has gone by. NANSPERSEC/nansused = bogomips. > A 1 bogomips machine will take an extra second to do this (anything > likely to be > even able to run FreeBSD should exceed 1 BM - yes, ha ha), and a kBM CPU > > can do it in 1 ms. Perhaps in the future a prescaler might be required, > but > this whole thing is just really chrome anyway. > > Would anyone scream and projectile-vomit if I added this to identcpu.c? I really don't see any merit in adding Linux-isms like this. Sounds a bit like the 'hack of the day' to me. I feel FreeBSD is well respected for it's stability etc. Not for it's 'me too' Linux-isms without any practical use. Mind you, I don't say Linux does not have stuff that is useful for inclusion in FreeBSD. I just stay BogoMips is what it calls itself: bogus, and should be kept from the FreeBSD kernel. Just my Dfl 0.02 W/ -- | / 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
Re: Linux StarOffice51 runs on -stable
"Andrew J. Korty" wrote: > If it helps, I don't think you really need to unzip setup.zip. I > found that setting LD_LIBRARY_PATH=. makes the setup program run > just fine (because it actually does unzip setup.zip, but into a > subdirectory of /tmp). Exactly what I always needed to do. It can't find the shared object because it simply is not in a searchable place. Setting LD_LIBRARY_PATH solves it. I always thought it was related to setting TMP to /var/tmp because I don't have enough space on /. -- Marcel Moolenaarmailto:mar...@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD projectmailto:mar...@freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: [mount.c]: Option "user"-patch
> The user would still have to know what type of filesystem is on > the volume. My code tries filesystem types from a list, one by > one, so the same command or desktop icon will mount a FAT, UFS, or > EXT2FS floppy, for example. The system administrator can also > specify default mount options on a device or filesystem-type basis. I like that idea, but that still doesn't need suid privs to do. Adrian To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
Nick Sayer wrote in list.freebsd-hackers: > Linux generates a meric of CPU performance as a byproduct of calibrating > a delay loop. It's not a metric of CPU performance. It's just a meaningless number, and its relation to the actual performance of the machine is very questionable. > We don't require doing any such thing, and so adding it would be purely > cosmetic. > However, I allege that cosmetic things aren't in and of themselves evil, > so long as > they don't break anything in the process. It would break user's confidence in the seriousness of the system. > Would anyone scream and projectile-vomit if I added this to identcpu.c? I would, FWIW. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:[EMAIL PROTECTED]) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Linux StarOffice51 runs on -stable
> Today Marcel Moolenaar wrote: > > > bro...@one-eyed-alien.net wrote: > > > > > > On Thu, 2 Sep 1999, Marcel Moolenaar wrote: > > > > > > > SO5.1 installs OOTB on both -current and -stable. I suspect your -stabl > e is > > > > not recent? > > > > > > Is this true for BOTH versions of the tarball? Changes where made to the > > > distribution without any apparent changes to the website. The new change > s > > > broke things. > > > > I wouldn't know. I'm not aware of any changes to the distribution. This is > > the distribution I have: > > -rw-r--r-- 1 marcel marcel 72192512 Jul 23 11:47 so51_lnx_01.tar > > MD5 (so51_lnx_01.tar) = 347ffa68be6c1d7b89fd843591afb0d3 > > so51a_lnx_01.tar > -rw-r--r-- 1 jacko user 70393856 Aug 31 15:47 so51a_lnx_01.tar > (libs are all libxxx517x.so) > requires jumping throught the hoops (unzip setup.zip, etc.) to > install but runs OOTB after that. I havn't tried to do a > 'network' install. If it helps, I don't think you really need to unzip setup.zip. I found that setting LD_LIBRARY_PATH=. makes the setup program run just fine (because it actually does unzip setup.zip, but into a subdirectory of /tmp). If you need to run setup after StarOffice has been installed, set LD_LIBRARY_PATH=/usr/local/Office51/lib, depending on where you installed it. ajk To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
On Thu, Sep 02, 1999 at 10:40:30AM -0700, Nick Sayer wrote: > Linux generates a meric of CPU performance as a byproduct of calibrating > a delay loop. > We don't require doing any such thing, and so adding it would be purely > cosmetic. > However, I allege that cosmetic things aren't in and of themselves evil, > so long as > they don't break anything in the process. I'd have to agree with the "Lets be more professional" crowd. How about as a LINT option? "If you need something so banal, you can turn it on yourself" -- Robert Sexton, [EMAIL PROTECTED] "Imagine if every Thursday your shoes exploded if you tied them the usual way. This happens to us all the time with computers, and nobody thinks of complaining." -- Jeff Raskin, interviewed in Doctor Dobb's Journal To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: [mount.c]: Option "user"-patch
> On Thu, Sep 02, 1999, Andrew J. Korty wrote: > > > > > You realise that this kind of stuff can be done in kernelspace, > > > > without needing yet another setuid binary/binaries.. > > > > > > Well, sysctl with list of pathes for user mounts looks good. > > > Configuration is simple and can be easliy changed at runtime. It is > > > always better to avoid setuid'ed binaries, this is more worse that > > > mount(8) can execute other mount_* binaries. > > > > My code provides needed features that all implementations I've seen > > of the sysctl approach do not. Our users need to mount removable > > volumes just by clicking on a KDE icon, without having to know what > > type of filesystem is present on the media. Non-console users > > should not be permitted to mount removable volumes. Both of these > > features are provided by my patch, which I have had in production > > since I submitted it. > > There are saner ways than using a suid binary. > Countering your arguement.. > > sysctl -w vfs.usermount="/floppy:/cdrom" > > And they can mount/umount at whim if they own the mountpoint/have done the > mount (and the permission checking can be extended to suit..) > > Then all you need to do is think of a sane way to chown console devices > (floppy, cdrom, etc..) to the user when they login? Perhaps an extension > to login/xdm/whatever kde uses ? The user would still have to know what type of filesystem is on the volume. My code tries filesystem types from a list, one by one, so the same command or desktop icon will mount a FAT, UFS, or EXT2FS floppy, for example. The system administrator can also specify default mount options on a device or filesystem-type basis. ajk To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Linux StarOffice51 runs on -stable
On Thu, 2 Sep 1999, Marcel Moolenaar wrote: > jack wrote: > > > > -rw-r--r-- 1 marcel marcel 72192512 Jul 23 11:47 so51_lnx_01.tar > > > MD5 (so51_lnx_01.tar) = 347ffa68be6c1d7b89fd843591afb0d3 > > > > so51a_lnx_01.tar > > -rw-r--r-- 1 jacko user 70393856 Aug 31 15:47 so51a_lnx_01.tar > > (libs are all libxxx517x.so) > > requires jumping throught the hoops (unzip setup.zip, etc.) to > > install but runs OOTB after that. I havn't tried to do a > > 'network' install. > > Sigh... > > For the record, I'm running the same version as jack and after looking at procfs_status.c in -stable (and current), this version should run with either version. -RELEASE, however, requires the patch. 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: Linux StarOffice51 runs on -stable
jack wrote: > > Today Marcel Moolenaar wrote: > > > [EMAIL PROTECTED] wrote: > > > > > > On Thu, 2 Sep 1999, Marcel Moolenaar wrote: > > > > > > > SO5.1 installs OOTB on both -current and -stable. I suspect your -stable is > > > > not recent? The fact that soffice runs setup again and again depend to a missing file... add in the home of the user that make the install this missing file (2 lines): seaside:/usr/local/www/data/neuro/admin# less /home/gmarco/.sversionrc [Versions] StarOffice 5.1=/usr/local/Office51 -- Regards... Gianmarco "Unix expert since yesterday" http://www.giovannelli.it To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
UCB removes advertising clause
This is apparently old news, but I don't recall seeing anything about it
on the lists, and didn't hear about it until it hit Slashdot a short while
ago.
ftp://ftp.cs.berkeley.edu/pub/4bsd/README.Impt.License.Change:
July 22, 1999
To All Licensees, Distributors of Any Version of BSD:
As you know, certain of the Berkeley Software Distribution ("BSD") source
code files require that further distributions of products containing all or
portions of the software, acknowledge within their advertising materials
that such products contain software developed by UC Berkeley and its
contributors.
Specifically, the provision reads:
" * 3. All advertising materials mentioning features or use of this software
*must display the following acknowledgement:
*This product includes software developed by the University of
*California, Berkeley and its contributors."
Effective immediately, licensees and distributors are no longer required to
include the acknowledgement within advertising materials. Accordingly, the
foregoing paragraph of those BSD Unix files containing it is hereby deleted
in its entirety.
William Hoskins
Director, Office of Technology Licensing
University of California, Berkeley
--
Brian Buchanan [EMAIL PROTECTED]
--
FreeBSD - The Power to Serve! http://www.freebsd.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
> >> >> Would anyone scream and projectile-vomit if I added this to identcpu.c? >> > >I might. :-) Why exactly, except to keep up with the Linux kidz, do we need >this? I recognize that this is solely a cosmetic change, but one of the >things I hold over the heads of the Linux folks I deal with is the fact that >FreeBSD is a professional quality operating system which doesn't need useless >blinking lights like BogoMIPS. > >Chalk me up as one of the people who considers "Linux works like that" as a >negative. I'm with you on this, Keith. I'd rather that we kept the professional FreeBSD look and feel. If we look too much like Linux, then people will just use Linux. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Linux StarOffice51 runs on -stable
"Andrew J. Korty" wrote: > If it helps, I don't think you really need to unzip setup.zip. I > found that setting LD_LIBRARY_PATH=. makes the setup program run > just fine (because it actually does unzip setup.zip, but into a > subdirectory of /tmp). Exactly what I always needed to do. It can't find the shared object because it simply is not in a searchable place. Setting LD_LIBRARY_PATH solves it. I always thought it was related to setting TMP to /var/tmp because I don't have enough space on /. -- Marcel Moolenaarmailto:[EMAIL PROTECTED] SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD projectmailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
There was such a thing in 386BSD and FreeBSD1.0 I certainly thing it was a worth-while thing. I'd try make the loop as similar to the Linux one so that they are comparable. On Thu, 2 Sep 1999, Nick Sayer wrote: > Linux generates a meric of CPU performance as a byproduct of calibrating > a delay loop. > We don't require doing any such thing, and so adding it would be purely > cosmetic. > However, I allege that cosmetic things aren't in and of themselves evil, > so long as > they don't break anything in the process. > > I would like to generate a number that will hopefully be reasonably > compatible with > the one Linux spits out. The best method I have come up with is to have > a similar > (the same?) count down loop in assembler. Have it count down from > 1,000,000 and > see how much nanotime() has gone by. NANSPERSEC/nansused = bogomips. > A 1 bogomips machine will take an extra second to do this (anything > likely to be > even able to run FreeBSD should exceed 1 BM - yes, ha ha), and a kBM CPU > > can do it in 1 ms. Perhaps in the future a prescaler might be required, > but > this whole thing is just really chrome anyway. > > Would anyone scream and projectile-vomit if I added this to identcpu.c? > > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
On Thu, Sep 02, 1999 at 10:40:30AM -0700, Nick Sayer wrote: > > Would anyone scream and projectile-vomit if I added this to identcpu.c? > I might. :-) Why exactly, except to keep up with the Linux kidz, do we need this? I recognize that this is solely a cosmetic change, but one of the things I hold over the heads of the Linux folks I deal with is the fact that FreeBSD is a professional quality operating system which doesn't need useless blinking lights like BogoMIPS. Chalk me up as one of the people who considers "Linux works like that" as a negative. 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: [mount.c]: Option "user"-patch
> The user would still have to know what type of filesystem is on > the volume. My code tries filesystem types from a list, one by > one, so the same command or desktop icon will mount a FAT, UFS, or > EXT2FS floppy, for example. The system administrator can also > specify default mount options on a device or filesystem-type basis. I like that idea, but that still doesn't need suid privs to do. Adrian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Linux StarOffice51 runs on -stable
> Today Marcel Moolenaar wrote: > > > [EMAIL PROTECTED] wrote: > > > > > > On Thu, 2 Sep 1999, Marcel Moolenaar wrote: > > > > > > > SO5.1 installs OOTB on both -current and -stable. I suspect your -stabl > e is > > > > not recent? > > > > > > Is this true for BOTH versions of the tarball? Changes where made to the > > > distribution without any apparent changes to the website. The new change > s > > > broke things. > > > > I wouldn't know. I'm not aware of any changes to the distribution. This is > > the distribution I have: > > -rw-r--r-- 1 marcel marcel 72192512 Jul 23 11:47 so51_lnx_01.tar > > MD5 (so51_lnx_01.tar) = 347ffa68be6c1d7b89fd843591afb0d3 > > so51a_lnx_01.tar > -rw-r--r-- 1 jacko user 70393856 Aug 31 15:47 so51a_lnx_01.tar > (libs are all libxxx517x.so) > requires jumping throught the hoops (unzip setup.zip, etc.) to > install but runs OOTB after that. I havn't tried to do a > 'network' install. If it helps, I don't think you really need to unzip setup.zip. I found that setting LD_LIBRARY_PATH=. makes the setup program run just fine (because it actually does unzip setup.zip, but into a subdirectory of /tmp). If you need to run setup after StarOffice has been installed, set LD_LIBRARY_PATH=/usr/local/Office51/lib, depending on where you installed it. ajk To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: [mount.c]: Option "user"-patch
> On Thu, Sep 02, 1999, Andrew J. Korty wrote: > > > > > You realise that this kind of stuff can be done in kernelspace, > > > > without needing yet another setuid binary/binaries.. > > > > > > Well, sysctl with list of pathes for user mounts looks good. > > > Configuration is simple and can be easliy changed at runtime. It is > > > always better to avoid setuid'ed binaries, this is more worse that > > > mount(8) can execute other mount_* binaries. > > > > My code provides needed features that all implementations I've seen > > of the sysctl approach do not. Our users need to mount removable > > volumes just by clicking on a KDE icon, without having to know what > > type of filesystem is present on the media. Non-console users > > should not be permitted to mount removable volumes. Both of these > > features are provided by my patch, which I have had in production > > since I submitted it. > > There are saner ways than using a suid binary. > Countering your arguement.. > > sysctl -w vfs.usermount="/floppy:/cdrom" > > And they can mount/umount at whim if they own the mountpoint/have done the > mount (and the permission checking can be extended to suit..) > > Then all you need to do is think of a sane way to chown console devices > (floppy, cdrom, etc..) to the user when they login? Perhaps an extension > to login/xdm/whatever kde uses ? The user would still have to know what type of filesystem is on the volume. My code tries filesystem types from a list, one by one, so the same command or desktop icon will mount a FAT, UFS, or EXT2FS floppy, for example. The system administrator can also specify default mount options on a device or filesystem-type basis. ajk To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
CFD: "bogomips" CPU performance metric
Linux generates a meric of CPU performance as a byproduct of calibrating a delay loop. We don't require doing any such thing, and so adding it would be purely cosmetic. However, I allege that cosmetic things aren't in and of themselves evil, so long as they don't break anything in the process. I would like to generate a number that will hopefully be reasonably compatible with the one Linux spits out. The best method I have come up with is to have a similar (the same?) count down loop in assembler. Have it count down from 1,000,000 and see how much nanotime() has gone by. NANSPERSEC/nansused = bogomips. A 1 bogomips machine will take an extra second to do this (anything likely to be even able to run FreeBSD should exceed 1 BM - yes, ha ha), and a kBM CPU can do it in 1 ms. Perhaps in the future a prescaler might be required, but this whole thing is just really chrome anyway. Would anyone scream and projectile-vomit if I added this to identcpu.c? smime.p7s Description: S/MIME Cryptographic Signature
Re: CFD: "bogomips" CPU performance metric
> >> >> Would anyone scream and projectile-vomit if I added this to identcpu.c? >> > >I might. :-) Why exactly, except to keep up with the Linux kidz, do we need >this? I recognize that this is solely a cosmetic change, but one of the >things I hold over the heads of the Linux folks I deal with is the fact that >FreeBSD is a professional quality operating system which doesn't need useless >blinking lights like BogoMIPS. > >Chalk me up as one of the people who considers "Linux works like that" as a >negative. I'm with you on this, Keith. I'd rather that we kept the professional FreeBSD look and feel. If we look too much like Linux, then people will just use Linux. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
There was such a thing in 386BSD and FreeBSD1.0 I certainly thing it was a worth-while thing. I'd try make the loop as similar to the Linux one so that they are comparable. On Thu, 2 Sep 1999, Nick Sayer wrote: > Linux generates a meric of CPU performance as a byproduct of calibrating > a delay loop. > We don't require doing any such thing, and so adding it would be purely > cosmetic. > However, I allege that cosmetic things aren't in and of themselves evil, > so long as > they don't break anything in the process. > > I would like to generate a number that will hopefully be reasonably > compatible with > the one Linux spits out. The best method I have come up with is to have > a similar > (the same?) count down loop in assembler. Have it count down from > 1,000,000 and > see how much nanotime() has gone by. NANSPERSEC/nansused = bogomips. > A 1 bogomips machine will take an extra second to do this (anything > likely to be > even able to run FreeBSD should exceed 1 BM - yes, ha ha), and a kBM CPU > > can do it in 1 ms. Perhaps in the future a prescaler might be required, > but > this whole thing is just really chrome anyway. > > Would anyone scream and projectile-vomit if I added this to identcpu.c? > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: CFD: "bogomips" CPU performance metric
On Thu, Sep 02, 1999 at 10:40:30AM -0700, Nick Sayer wrote: > > Would anyone scream and projectile-vomit if I added this to identcpu.c? > I might. :-) Why exactly, except to keep up with the Linux kidz, do we need this? I recognize that this is solely a cosmetic change, but one of the things I hold over the heads of the Linux folks I deal with is the fact that FreeBSD is a professional quality operating system which doesn't need useless blinking lights like BogoMIPS. Chalk me up as one of the people who considers "Linux works like that" as a negative. 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: Linux StarOffice51 runs on -stable
jack wrote: > > -rw-r--r-- 1 marcel marcel 72192512 Jul 23 11:47 so51_lnx_01.tar > > MD5 (so51_lnx_01.tar) = 347ffa68be6c1d7b89fd843591afb0d3 > > so51a_lnx_01.tar > -rw-r--r-- 1 jacko user 70393856 Aug 31 15:47 so51a_lnx_01.tar > (libs are all libxxx517x.so) > requires jumping throught the hoops (unzip setup.zip, etc.) to > install but runs OOTB after that. I havn't tried to do a > 'network' install. Sigh... -- Marcel Moolenaarmailto:mar...@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD projectmailto:mar...@freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: L440GX+ Server Board
On Wed, 1 Sep 1999, Bill Fumerola wrote: > On Wed, 1 Sep 1999, Luiz Morte da Costa Junior wrote: > > > > The onboard NIC works like any other Intel 10/100 using fxp0, adding a > > > asecond nic makes the onboard fxp1 (for failover purposes, I assume) > > > > I think that I don't have problem with my NIC (Intel 10/100). > > The bus that the onboard NIC is on probably gets probed later then > then the expansion bus. I'm using only the onboard NIC. I didn't add any other NIC in my server. []s, Luiz Morte da Costa Junior Analista de RedesE-mail: mo...@correionet.com.br Telefone: +55 19 754-2532Fax: +55 19 255-7576 CorreioNet - Correio Popular Campinas - SP - Brazil To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: [mount.c]: Option "user"-patch
On Fri, 3 Sep 1999 adr...@freebsd.org wrote: :Then all you need to do is think of a sane way to chown console devices :(floppy, cdrom, etc..) to the user when they login? Perhaps an extension :to login/xdm/whatever kde uses ? You can do this in /etc/fbtab. You already chown the console for X logging (you should be anyway). I don't like the idea of restricting access to the console user. That assumes that the removable media device in question is present on every machine in the room. This is not always the case. It may not even be the dominant case. Jamie Bowden -- If we've got to fight over grep, sign me up. But boggle can go. -Ted Faber (on Hasbro's request for removal of /usr/games/boggle) To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: L440GX+ Server Board
On Wed, 1 Sep 1999, Pete Mckenna wrote: ... > > > I have also put an adaptec 2940 in them and it works as well. > > > > What is the adaptec transfer rate? I have tested with a adaptec 80Mb, and > > it didn't work too. The chipset is the same the AIC 7896. > > I'm not sure what you are asking. I havn't put an Adaptec 7896 into this > motherboard, just added a 2940 to the built in 7896 and didn't have any > problems. We use LVD drives on the A or 0 channel and they need external > termination. I don't have transfer rate numbers handy but could generate > some if that's what your asking ? Ok. I try to explain again. The L440GX+ Server board has a AIC 7896 onboard (I haven't put), whith 2 SCSI interfaces: one with 80Mb transfer rate and one with 40Mb. I have 2 SCSI disk (with 80Mb transfer rate) and did the following tests: . I put the SCSI disk in 80Mb interface; . I put the SCSI disk in 40Mb interface; . I added a 2940 (with 80Mb transfer rate) and I put the disck SCSI. All tests didn't work, so my server stays very slow. > > Another test that I have done with my kernel was to put the flags below: > > This only refers to IDE drives not SCSI drives. We don't use anything > other than SCSI in these boxes. Which are you using ? > > > > controller wdc0at isa? port "IO_WD1" bio irq 14 > > diskwd0 at wdc0 drive 0 flags 0xb0ff > > diskwd1 at wdc0 drive 1 flags 0xb0ff > > controller wdc1at isa? port "IO_WD2" bio irq 15 > > diskwd2 at wdc1 drive 0 flags 0xb0ff > > diskwd3 at wdc1 drive 1 flags 0xb0ff Ok. I don't use IDE disk. What is your BIOS and BMC firmware version? I called to Intel support and they told me that my version BIOS is out of date. I have to upgrade to 1.05 (BMC firmware) and 7.3 (BIOS). Could it be this my problem? Thanks. []s, Luiz Morte da Costa Junior Analista de RedesE-mail: mo...@correionet.com.br Telefone: +55 19 754-2532Fax: +55 19 255-7576 CorreioNet - Correio Popular Campinas - SP - Brazil To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Linux StarOffice51 runs on -stable
Today Marcel Moolenaar wrote: > bro...@one-eyed-alien.net wrote: > > > > On Thu, 2 Sep 1999, Marcel Moolenaar wrote: > > > > > SO5.1 installs OOTB on both -current and -stable. I suspect your -stable > > > is > > > not recent? > > > > Is this true for BOTH versions of the tarball? Changes where made to the > > distribution without any apparent changes to the website. The new changes > > broke things. > > I wouldn't know. I'm not aware of any changes to the distribution. This is > the distribution I have: > -rw-r--r-- 1 marcel marcel 72192512 Jul 23 11:47 so51_lnx_01.tar > MD5 (so51_lnx_01.tar) = 347ffa68be6c1d7b89fd843591afb0d3 so51a_lnx_01.tar -rw-r--r-- 1 jacko user 70393856 Aug 31 15:47 so51a_lnx_01.tar (libs are all libxxx517x.so) requires jumping throught the hoops (unzip setup.zip, etc.) to install but runs OOTB after that. I havn't tried to do a 'network' install. -- Jack O'NeillSystems Administrator / Systems Analyst j...@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger j...@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -- To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: [mount.c]: Option "user"-patch
On Thu, Sep 02, 1999, Andrew J. Korty wrote: > > > You realise that this kind of stuff can be done in kernelspace, > > > without needing yet another setuid binary/binaries.. > > > > Well, sysctl with list of pathes for user mounts looks good. > > Configuration is simple and can be easliy changed at runtime. It is > > always better to avoid setuid'ed binaries, this is more worse that > > mount(8) can execute other mount_* binaries. > > My code provides needed features that all implementations I've seen > of the sysctl approach do not. Our users need to mount removable > volumes just by clicking on a KDE icon, without having to know what > type of filesystem is present on the media. Non-console users > should not be permitted to mount removable volumes. Both of these > features are provided by my patch, which I have had in production > since I submitted it. There are saner ways than using a suid binary. Countering your arguement.. sysctl -w vfs.usermount="/floppy:/cdrom" And they can mount/umount at whim if they own the mountpoint/have done the mount (and the permission checking can be extended to suit..) Then all you need to do is think of a sane way to chown console devices (floppy, cdrom, etc..) to the user when they login? Perhaps an extension to login/xdm/whatever kde uses ? All I'm saying is there has to be a better way to solve a problem using an iron pole, regardless of whether its first stuck inside a nerf dart. Adrian To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
CFD: "bogomips" CPU performance metric
Linux generates a meric of CPU performance as a byproduct of calibrating a delay loop. We don't require doing any such thing, and so adding it would be purely cosmetic. However, I allege that cosmetic things aren't in and of themselves evil, so long as they don't break anything in the process. I would like to generate a number that will hopefully be reasonably compatible with the one Linux spits out. The best method I have come up with is to have a similar (the same?) count down loop in assembler. Have it count down from 1,000,000 and see how much nanotime() has gone by. NANSPERSEC/nansused = bogomips. A 1 bogomips machine will take an extra second to do this (anything likely to be even able to run FreeBSD should exceed 1 BM - yes, ha ha), and a kBM CPU can do it in 1 ms. Perhaps in the future a prescaler might be required, but this whole thing is just really chrome anyway. Would anyone scream and projectile-vomit if I added this to identcpu.c? S/MIME Cryptographic Signature
Re: [mount.c]: Option "user"-patch
> On Wed, 1 Sep 1999 adr...@freebsd.org wrote: > > > On Tue, Aug 31, 1999, Doug Rabson wrote: > > > On Mon, 30 Aug 1999, Andrew J. Korty wrote: > > > > > > > I provided a solution via send-pr (bin/11031) over four months ago, > > > > which is, in my opinion, superior in many ways to this sysctl > > > > approach. The patch contains an amendment to the mount(1) manual > > > > page. > > > > > > I have not reviewed this pr myself but it seems like a well thought out > > > change to the system. Would the people who are involved with the current > > > (more limited) proposed change like to review this and possibly use it > > > instead. I don't want to lose anyones work here if it could be useful. > > > > You realise that this kind of stuff can be done in kernelspace, > > without needing yet another setuid binary/binaries.. > > Well, sysctl with list of pathes for user mounts looks good. > Configuration is simple and can be easliy changed at runtime. It is > always better to avoid setuid'ed binaries, this is more worse that > mount(8) can execute other mount_* binaries. My code provides needed features that all implementations I've seen of the sysctl approach do not. Our users need to mount removable volumes just by clicking on a KDE icon, without having to know what type of filesystem is present on the media. Non-console users should not be permitted to mount removable volumes. Both of these features are provided by my patch, which I have had in production since I submitted it. The possibility of executing undesired mount_* binaries is precluded by the ability to list in the configuration file what filesystem types should be tried for each device. Andrew J. Korty, Director http://www.physics.purdue.edu/~ajk/ Physics Computer Network85 73 1F 04 63 D9 9D 65 Purdue University 65 2E 7A A8 81 8C 45 75 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
