3.3-RELEASE -> 4-STABLE
I have a machine I want to upgrade from 3.3-RELEASE to 4-STABLE. UPDATING seems to indicate I can jump all the way to 4-STABLE, but I know folks have recommended a center step. If I'm hosting the compile on that box, what are the "stopover points" that should be hit on the way? Should I go to RELENG_3 and then jump to RELENG_4? Should I hit RELENG_4_0 on the way? Or can I jump straight from 3.3-RELEASE to 4-STABLE? How about if I have another -STABLE box that I can do the installworld from. Can I jump straight to -STABLE in that case? -- Charlie Watts [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Is FreeBSD more secure than Windows NT or Windows 2000?
On Sat, 21 Jul 2001, Sung Nae Cho wrote: > Windows NT is very secure in that matter. Simply reinstalling Windows > NT will not let you read someone else's file. Also, it won't let you > reinstall Windows NT without verifying that you're the right > administrator! During the reinstall, it asks for your root passwd. > If the passwd doesn't match, it won't let you reinstall unless you're > willing to reinstall from scratch (reformat or erase everything before > going on to installation procedure). Now I think that's being secure > all the way. Is there anyway I can do that with FreeBSD? For > example, attaching signature to all my files etc. There are any number of tools, both commercial and freely available, that can read NTFS filesystems without paying attention to the permissions on the drive. The difference here is this: Unix does not pretend to be secure when it isn't. If you want file security against folks with access to the hardware, you need strong crypto. This is true on literally any operating system. -- Charlie Watts [EMAIL PROTECTED] Frontier Internet http://www.frontier.net/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Filesystem missing space?
I've got a missing-space problem that is puzzling me. These don't line up: # df -h | grep usr /dev/da0s1e 2.9G 2.7G -5.5M 100%/usr # du -h /usr 580M/usr Doing an `lsof /usr` doesn't show any open files in /usr that I don't expect. (Bunch of libraries open, mostly.) I've killed almost everything on the system and restarted it, thinking that perhaps a large file was open but had been unlinked. I'm about to try re-booting the box and fsck'ing the disk. I deleted most everything in /usr/ports, which made a several-hundred MB difference in the "du" total, but only made a ~ 50MB difference in the "df" total. softupdates -is- on. Is there anywhere else I should be looking? The box has been up for a few months with no problems. I've been having some problems with Mailman today, though ... had a bunch of copies of it running with a bunch of locks open. I deleted the 0-byte lockfiles before I killed the programs. Are there any softupdates+lock related problems, or should I be looking elsewhere? -- Charlie Watts [EMAIL PROTECTED] Frontier Internet http://www.frontier.net/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Benchmarks from SysAdmin mag
On Thu, 12 Jul 2001, Paul wrote: > Hi all... it appears that after so many FreeBSD users (including > myself) sent sysadmin magazine messages regarding the benchmark article > previously discussed in this thread, they've posted a follow-up. They > sent me an email directly in respond to my message, giving me the new URL. > > So, everyone interested check out: > http://www.sysadminmag.com/articles/2001/0108/0108q/0108q.htm They claim to have both done: tunefs -n enable / tunefs -n enable /usr tunefs -n enable /var And: in /etc/fstab Add to options for all hard disk file systems ",async": Given this, which takes precedence? Or am I mis-understanding? I think of the three options as sync, async, and softupdates. If you turn async AND softupdates on, what is really happening? -- Charlie Watts [EMAIL PROTECTED]Frontier Internet Systems Janitor and Network Plumber http://www.frontier.net/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re[2]: soft update should be default
On Sun, 6 May 2001, Gabriel Ambuehl wrote: > -BEGIN PGP SIGNED MESSAGE- > > Hello Charlie, > > Sunday, May 06, 2001, 1:53:20 AM, you wrote: > >> IBM DLTA-307030 Ultra ATA drive (tags/no WC vs. no tags/WC). With > neither > >> option, it is terrible, of course. > > I see the same behaviour on one of those disks, too. But - aren't > IBM's > > DTLA-series disks the only IDE drives that support TCQ? > > [ It's a -very- SCSI-feeling feature, in my mind. ] > > > It was about time this was implemented in IDE disk as this takes them > nearer to the ridiculously overpriced SCSI stuff. While I've always > been a lover of IBM drives, this feature is really cool. > > Is it on by default if you use DTLA disks or do I need to activate it > specifically, BTW? Of course, I should read all of my E-mail before responding. From other messages on freebsd-stable today: TCQ also turns on a -form- of write caching, it may not be quite the same as normal, but it still does, and should probably be considered not-totally safe. Bah. Sorry. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re[2]: soft update should be default
On Sun, 6 May 2001, Gabriel Ambuehl wrote: > -BEGIN PGP SIGNED MESSAGE- > > Hello Charlie, > > Sunday, May 06, 2001, 1:53:20 AM, you wrote: > > I see the same behaviour on one of those disks, too. But - aren't IBM's > > DTLA-series disks the only IDE drives that support TCQ? > > [ It's a -very- SCSI-feeling feature, in my mind. ] > > It was about time this was implemented in IDE disk as this takes them > nearer to the ridiculously overpriced SCSI stuff. While I've always > been a lover of IBM drives, this feature is really cool. > > Is it on by default if you use DTLA disks or do I need to activate it > specifically, BTW? In /boot/loader.conf: hw.ata.tags="1" I have several other random stupid IDE drives in this machine, too, and don't notice any adverse behaviour. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
