Re: ATACD issues slowly coming back...
Bruce Cran wrote: Your CD drive should indeed support UDMA33 - my DVD drive supports UDMA33, and my CDRW supports multi-word DMA, even though my BIOS only ever configures it for PIO4, and my DVD for UDMA33. FreeBSD only ever configures them for PIO during bootup, but, using the atacontrol program, it configures them both for maximum speed, even knowing they _can_ only do UDMA33,WDMA2. If you have a look at sysctl hw.ata tree, it'll give you the clue on how to overcome this behaviuor. In simple words, what you need is to poot hw.ata.atapi_dma=1 in your /boot/loader.conf and have the nirvana of automatic DMA detection... -- /Voland Vadim Belman http://www.lflat.org http://www.lflat.net To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Syscalls.master broken on -CURRENT?
On Sat, 2002-06-15 at 18:03, Robert Watson wrote:
During the compilation of usr.bin/truss this error stops world:
syscalls.master: line 55: syscall number out of sync at 7
line is:
struct rusage * rusage ) ; } wait4 wait_args int
The error is actually produced by the execution of
'/usr/src/sys/kern/makesyscalls.sh syscalls.master'
What I don't understand is why this same error breaks world
on one of my -CURRENT machines but not on the other machine...
Try this:
# cd /usr/src/usr.bin/truss
# make clean
# make
I think you will see the error appear.
s/appear/disappear/? It basically looks like the generated include files
aren't in sync, but it's not something I can reproduce locally. Lots of
make cleaning and make includes should clear this up. If it doesn't, let
me know, and I'll do more chasing.
I just have found source of the problem. It's broken sed, again. Having
a look into syscalls.master it's easy to spot that error take place
where lines are broken like this one:
7 MSTDBSD { int wait4(int pid, int *status, int options, \
struct rusage *rusage); } wait4 wait_args int
As they're joned back with sed, it's easy to guess the cause...
# cd /usr/src/usr.bin/sed
# make
# make install
And it works.
--
/Voland Vadim Belman
http://www.lflat.org
http://www.lflat.net
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: /etc/shells #include syntax support patch
On Sun, Jan 28, 2001 at 11:53:50PM -0500, Louis A. Mamakos wrote: Does this capability really need to exist (e.g., supporting many files)? It would seem like the additional complexity would be not what you want for what's essentially a security policy mechansim. Who gets to own these included files? What should their permissions be allowed to be? It doesn't seem unreasonable to have a single file with a list of allowable shells. It does if you think of mergemaster, for example. With any upgrade it consider /etc/shells as changed and prompts for replacing/merging/etc. -- /Voland Vadim Belman E-mail: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: randomdev entropy gathering is really weak
On Mon, Jul 17, 2000 at 04:14:50PM +0200, Poul-Henning Kamp wrote: NTP is the perfect way to gather entropy at bootup! Only if in reach of an NTP server ? Obviously :-) And what if no network at all? -- /Voland Vadim Belman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: randomdev entropy gathering is really weak
On Tue, Jul 18, 2000 at 06:43:40PM +0200, Poul-Henning Kamp wrote: And what if no network at all? Your need for random bits are quite a bit less urgent in that case. Remember: This is not about getting industry strength unbeatable crypto. If you want that, you buy a hardware solution. This is about making a FreeBSD machine as good as we can in the standard case. I mostly agree, but let's put it other way. A rare situation with a local network with no external connection, no NTP servers. Just a server(s) plus several clients. At least some of the clients are being treated as untrusted (consider public terminals) and server has some critical information on it. -- /Voland Vadim Belman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: randomdev entropy gathering is really weak
On Tue, Jul 18, 2000 at 07:03:37PM +0200, Poul-Henning Kamp wrote: I mostly agree, but let's put it other way. A rare situation with a local network with no external connection, no NTP servers. Just a server(s) plus several clients. At least some of the clients are being treated as untrusted (consider public terminals) and server has some critical information on it. Nobody talked about relying on *only* NTP for entropy, quite the contrary in fact. This I understand. 8) Ok, I've gotten the answer from the thread, somehow missed it before. -- /Voland Vadim Belman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make buildworld failed...
On Wed, Jun 21, 2000 at 02:39:55AM +0200, Mikko Tyolajarvi wrote: Same for me (fresh cvsup)... From the FAQ : "You can try to config OpenSSL so as not to use IDEA by using './config no-idea'". But i've no idea (what's a joke...) on how to do that with 'make buildworld'. Me too. I would very much appreciate a hint here. Thx! Try this as a workaround: cp /usr/src/crypto/openssl/crypto/idea/idea.h /usr/include/openssl Another one would be `make clean' in /usr/src. It worked for me (despite of failure during `make installworld' where it didn't locate osrelease.h). -- /Voland Vadim Belman E-mail: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
