Re: About 5.0 and Nvidia drivers
| You want to say me that there is an ATI graphics card that is more powerful | than NVidia GeForce? | | Sorry, but FreeBSD is really good operating system. Good enough for use it | on servers. As a system programmer, I wish to have a copy of it on my home | desktop. And my son/daughter wish to play games on same desktop. | | What should I do? Change video cards every day? Whatever? It sounds like dual booting would be a better idea here. Boot into FreeBSD when you want to code, boot into Windows when your son/daughter wish to play games. -Dan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: randomdev entropy gathering is really weak
| | Gotcha - fix coming; I need to stash some randomness at shutdown time, and | | use that to reseed the RNG at reboot time. | | What about saving the state of the RNG and re-reading it on bootup? That | will allow Yarrow to continue right where it left off. :-) | | That's a bad thing. You don't want someone to be able to examine the exact | PRNG state at next boot by looking at your hard disk after the machine has | shut down. I don't see how. If the attacker has physical access to the machine, there are plenty worse things to be done than just reading the state of a PRNG. If the random device is initialized in single user mode, and the file is then unlink()ed, I don't see any problems with that. -Dan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: randomdev entropy gathering is really weak
| Gotcha - fix coming; I need to stash some randomness at shutdown time, and | use that to reseed the RNG at reboot time. What about saving the state of the RNG and re-reading it on bootup? That will allow Yarrow to continue right where it left off. :-) -Dan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: randomdev entropy gathering is really weak
| In fact, it would be rather interesting to have a configuration flag which | always forces something like an fsck on a file system in order to provide | some entropy to the random device. Or some other user-exposed way of | providing entropy. I might have some data on disk, or some network | operations which can be performed to help seed the entropy pool. | | What we really need is this: | | fetch -o http://entropy.freebsd.org/ /dev/random | | with a bunch of volounteers providing random bits to people in need. | | I have thought about adding a entropy server to my array of weird | servers in my lab. Something like a Geiger counter and a smokedetector | could do wonders. If you wanted to have some fun with this, you could do a rc5-like distributed client, feeding random bits to a server, and pulling down new bits every so often! -Dan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: randomdev entropy gathering is really weak
| DuH! | | NTP is the perfect way to gather entropy at bootup! | | Predicting the clock's offset from reality and the two way path to | the server of choice is impossible, plus if people enable authentication | later on the packets will be choke full of high-quality entropy. | | We need an enterprising soul to add an option (default on) to | ntpdate to write the received packets in toto to /dev/random | if it exists. | | If somebody does this, I will spear-head the effort of getting it | into the ntpv4 sources (Hmm, don't I have a commit bit there | already ? Can't remember...) Well, how many other OSs out there allow /dev/random to be written to? -Dan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: randomdev entropy gathering is really weak
| I think there are other practical issues too. Unless the new libfetch | fetch supports https this won't work. More to the point, I'd | guess https needs a working /dev/random to set up the secure | connection, but we're running fetch to set up /dev/random. | | How much entropy can we get from: | | (date; dmesg ; sysctl -X; vmstat -i ) /dev/random | | Just playing it looks like you might get 4 so bits from the | rtc and clk interupt count alone. None. Any data that is publically available via userland should not be used for cryptography. -Dan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XML driver config file to replace LINT
| I disagree. We're not Linux, where people can throw in code without thought | to the wider consequences -- one of the commitments you should make (that's | a generic "you" there, not you specifically) as a FreeBSD committer is to | maintain the documentation that's affected by your changes. A look at | HARDWARE.TXT shows that (with a few notable exceptions) the FreeBSD Developer | Community at large is *not* keeping it up to date. Perhaps it would be a good idea to assign someone the task of just maintaing the HARDWARE.TXT file, rather than expecting all developers to keep documentation up to date? Warner is the gatekeeper for UPDATING, and it seems to work rather well. If there is no one explicitly on the doc project that you'd like doing this, I'd take on the responsibility. -- Dan Moschuk ([EMAIL PROTECTED]) "Don't get even -- get odd!" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XML driver config file to replace LINT
| Perhaps it would be a good idea to assign someone the task of just maintaing | the HARDWARE.TXT file, rather than expecting all developers to keep | documentation up to date? | | That is what I am currently doing (at least trying to.. ;-) for | FreeBSD/alpha. But considering that the alpha community is considerably | smaller this might be a problem in the much bigger x86 world. Right, but as someone that reads all the commit messages, catching new driver support and updating is more of a mundane task than anything. If maintainers emailed when they added new support (like when an entry in UPDATING is needed) it's even easier. -- Dan Moschuk ([EMAIL PROTECTED]) "Don't get even -- get odd!" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: (thoughts on) the mktemp() patch.
| | Maybe the soltion is to think out of the box. Maybe temporary | filestore should be a more official OS service. Race conditions would | be far less common if the OS itself was managing the namespace. | | You might even expand the capability somewhat. Provide process local, | uid local and global namespaces. You'd even gain the ability to | specify the limits on temporary filestore. | | We have an out of the box solution. But there are other software out | there in the world that happens to use mktemp() and we have no control | of. So we are trying to improve mktemp(). I've avoided this conversation, but what would everyone think of a tmpfs type of solution with a security minded design? I took a brief look at phk's md driver, and it could be quite easily molded to do what I want to do. Things like a sysctl option to disallow symlinks in a tmpfs mounted directory I'm sure would make a few people happy. The downfall, for being memory backed, is it's wiped on a reboot (some people, however, consider this to be A Good Thing). -- Dan Moschuk ([EMAIL PROTECTED]) "Don't get even -- get odd!" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current, ep and fragment problems.
| Is anyone else seeing odd behaviour with a fairly recent -current, an ep | driver nic card and fragmented packets? | | If I understand things correctly, Matt Dillon and a cast of thousands | just committed a fix to this problem. Try cvsup'ing and make'ing world | and see if that helps. Different problems, I think. I downgraded if_ep.c to revision 1.95 and the problem went away. Matthew Dodd believes he knows where the problem is, so it should be fixed soon. -- Dan Moschuk ([EMAIL PROTECTED]) "Waste not fresh tears on old griefs." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NOUUCP knob and /etc/uucp
| I was just noticing that the files in /etc/uucp are installed anyway | if you set NOUUCP, whereas those in /etc/ssh and /etc/ssl are | affected by their respective knobs. Could /etc/uucp be wrapped | around the NOUUCP knob? | | I replied to Dan Moschuk's commit message for this with the additional | suggestion of including uucpd in src/libexec/Makefile too, but got no | response. I like the idea of wrapping the files in src/etc with the | NOUUCP (NO_UUCP maybe?) knob as well. Further research offers rmail in | src/bin/Makefile as a candidate as well. Oops! I've just committed the fix. It probably should be NO_UUCP, but no one seems to want to make a final decision on the NOFOO vs. NO_FOO argument, so I left it at NOUUCP for now. -- Dan Moschuk ([EMAIL PROTECTED]) "Waste not fresh tears on old griefs." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
-current, ep and fragment problems.
Is anyone else seeing odd behaviour with a fairly recent -current, an ep driver nic card and fragmented packets? -- Dan Moschuk ([EMAIL PROTECTED]) "Waste not fresh tears on old griefs." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: emu10k1 (SB Live!) support under FreeBSD?
| | I would love to help out, but I don't know where to start, and I have no | | kernel programming experience. There are reference drivers available for | | linux via http://opensource.creative.com or http://www.alsa-project.org | | (my preference). | | One is on the way... Cam's boredom out-weighed my initiative. 8) http://www.freebsd.org/~cg/current.diff.gz contains a partial emu10k1 driver (minus recording) which is need of debugging. Give it a try! -- Dan Moschuk ([EMAIL PROTECTED]) "Waste not fresh tears on old griefs." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: emu10k1 (SB Live!) support under FreeBSD?
| http://www.freebsd.org/~cg/current.diff.gz contains a partial emu10k1 | driver (minus recording) which is need of debugging. Give it a try! | | How current is this? Will it work against 4.0-STABLE? I haven't tested it, but I believe so. -- Dan Moschuk ([EMAIL PROTECTED]) "Waste not fresh tears on old griefs." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: emu10k1 (SB Live!) support under FreeBSD?
| Are there any plans to support the emu10k1 chip (SoundBlaster Live! and | SB512) under FreeBSD? | | I would love to help out, but I don't know where to start, and I have no | kernel programming experience. There are reference drivers available for | linux via http://opensource.creative.com or http://www.alsa-project.org | (my preference). One is on the way... -- Dan Moschuk ([EMAIL PROTECTED]) "Waste not fresh tears on old griefs." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why not gzip iso images?
| Alas, that is just not true for many of us who are in bandwidth-poor | countries. Over here, it can take 3 to BIGNUM hours to download an ISO | image (there aren't any up-to-date local mirrors), depending on time of | day and the phase of the moon. I think compression would definitely help. | | As much as I sympathize with the plight of people who have to pay | for slow b/w, we're talking about something that is a luxury, not a | necessity. Sure, having a gzip'ed version of the iso image avaiable is | probably a good idea, but if you want your stuff gzip'ed just do an ftp | install. Those bits are already gzip'ed for you. Of course, you can always be good little FreeBSD users and order the CD. -Dan -- Dan Moschuk ([EMAIL PROTECTED]) "Waste not fresh tears on old griefs." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Hardware for 4.0
| What SCSI card would people recommend? It doesn't need RAID. | Any particular SCSI tape drive? I like the Adapdec 2940 cards for low-medium end servers. | I'll probably buy a midrange Asus motherboard and a nice Intel fxp | NIC to go on it. Any other recommendations? The fxp cards are good, but I usually use the 3Com 905[BC] cards. -- Dan Moschuk ([EMAIL PROTECTED]) "Waste not fresh tears on old griefs." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/usr.sbin/pkg_install/delete main.c src/usr.sbin/pkg_install/info main.c
|Log:
|Fix a bug in previous commit where pkg_{delete,info} foo-1.0/ would segfault.
|
|Noticed first by: kris
|
| Is it just me, or does: 'pkg_delete foo-1.0/' now just spin in the
| while() loop around line 92 of src/usr.sbin/pkg_install/delete/main.c ?
spirit# pkg_delete jive-1.1/
spirit#
Just you. :)
--
Dan Moschuk ([EMAIL PROTECTED])
"Waste not fresh tears on old griefs."
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: cdrom mounting issue
| in my kernel config file i have: | | options CD9660 #ISO 9660 Filesystem | options CD9660_ROOT #CD-ROM usable as root, CD9660 | required Do you have device atapicd0 In your configuration as well? -- Dan Moschuk ([EMAIL PROTECTED]) "Waste not fresh tears on old griefs." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PNPBIOS + Dell PowerEdge = panic()
| The problem here is that the i386 nexus_alloc_resource() unconditionally | calls pmap_mapdev() to map any memory-type resource into the kernel. | This is definitely a bad idea; IMHO we should only do this when the | resource is actually activated (and obviously free it when deactivated). | | Commentary? Should I just commit the change and see what happens? 8) Commit and see what happens. I'll keep the pointy had warm for you. 8) -- Dan Moschuk ([EMAIL PROTECTED]) "Waste not fresh tears on old griefs." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Overflow in banner(1)
| sizeof() is an operator whose value is determined at compile time. | sizeof(*buf) gives the size of what buf points to. This would be `1' if | buf were a char*, or `4' if buf were an int* [on the i386]. Ahh, so I've probably seen this concept used only on structures then. -- Dan Moschuk ([EMAIL PROTECTED]) "Cure for global warming: One giant heatsink and dual fans!" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
whereis broken?
whereis anything yields.. Warning: couldn't stat file /usr/local/lib/perl5/5.00502/man! Warning: couldn't stat file /usr/local/lib/perl5/5.00502/man! Warning: couldn't stat file /usr/local/lib/perl5/5.00502/man! Warning: couldn't stat file /usr/local/lib/perl5/5.00502/man! Warning: couldn't stat file /usr/local/lib/perl5/5.00502/man! ad infinity. Cheers, Dan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Berkeley DB 1.85 -- 2.0
Out of curiosity, is there a reason we are still using Berkeley DB v1.85 as apposed to v2? --Dan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
aic
Any hope of the aic driver gracing -current anytime soon? I'm really itching to port my burning software over. Cheers, -- Dan Moschuk (tfreak...@globalserve.net) Senior Systems/Network Administrator Globalserve Communications Inc., a Primus Canada Company If at first you don't succeed, redefine success To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
