Re: cd writer recommendation?

1999-08-18 Thread John R. LoVerso
> One thing www.buy.com is really good for, ... > is to get pricing information on a general search. You can then use it > to do comparison shopping. Or, just use one of the pricing web servers. I use (and in the order I prefer) Pricescan, KillerApp, and Shopper (web pages are s/.*/

Re: [re]writable cdrom drive

1999-08-19 Thread John R. LoVerso
> > This does not actually erase the data, so if you have used say 100MB > > you will only have 550MB left. You can actually erase the media using > > 'cdrecord blank=all', which takes a while. > In my experience, this is not true. I have used blank=fast on a CDRW > that has over 500 MB written,

Re: T/TCP in FreeBSD-3.x

1999-01-22 Thread John R. LoVerso
> Why I'm asking about this, is because I recently read an advice in one > of the FreeBSD mailing lists, > about "Why my dial-up PPP connection from a FreeBSD box is so slow > comparing with Windows NT > (about ten times slower)?" > > And the advice was (without explanations): "Try to switch off t

Re: EGCS breaks what(1)

1999-04-06 Thread John R. LoVerso
> 'what' is broken. C does not impose any sort of address ordering > restriction on globals or autos that are declared next to each other. Right, except that 'what' isn't broken. It is vers.c (and conf/newvers.sh) that is broken, believing that the two variables will be allocating in co

Re: ATTENTION PLEASE: g77 in base system.

1999-04-09 Thread John R. LoVerso
> Right or wrong, you forgot: > > 5. BSD tradition. > > Case 5 justifies Fortran. By that logic, you'd also have to add a Pascal compiler to the base system. Neither makes much sense when they can both be ports (or packages) easily addable at install or compile time by the small % of the FreeB

Re: Berkeley DB 1.85 --> 2.0

1999-05-14 Thread John R. LoVerso
Of course, DB 2 is still available as an easily installed port/package. John To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message

Re: net.inet.tcp.always_keepalive on as default ?

1999-06-04 Thread John R. LoVerso
> "32bit is enought for everthing" Just mention the horrible header offset field. Lots of good TCP nits. Anyway, can't this argument be settled by separating the mechanism and policy. Adding a simple rc.conf tweak to enable them should be enough. But, consider going back to the discu