Re: Bad disk or kernel (ATA Driver) problem? - SOLVED
Karl Denninger <[EMAIL PROTECTED]> wrote:
> Seagate's have been getting very poor performance reviews of late.
Do you have any URLs? While I haven't been following disk drives
closely, I haven't seen anything that points at "very poor" performance
("average"/boring performance, yes, but nothing really bad).
Thanks.
--
Darryl Okahata
[EMAIL PROTECTED]
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Agilent Technologies, or
of the little green men that have been following him all day.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Very large directory
Oliver Fromme <[EMAIL PROTECTED]> wrote:
> I would suggest trying this simple hack:
>
> cd /var/spool/directory ; cat . | strings | xargs rm -f
Since the original poster was willing to use -rf, wouldn't it be
better to do:
cd /var/spool/directory ; find . -type f -print0 | xargs -0 rm -f
Slightly more typing, but more robust.
--
Darryl Okahata
[EMAIL PROTECTED]
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Agilent Technologies, or
of the little green men that have been following him all day.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Bad disk or kernel (ATA Driver) problem? - SOLVED
Karl Denninger <[EMAIL PROTECTED]> wrote: > These two are DiamondMax10s - let's hope that this doesn't apply to that > line as well. Out of curiosity, why didn't you consider Seagate ? The recent Maxtors that I have, if run 24x7, seem to die just after the warranty expires (for me, just over a year). I'm now switching back to Seagate, as they now have a nice 5-year warranty, but I don't have much experience with these new drives. -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: User's cron job creates zombie process on 5.3
Raymond Wiker <[EMAIL PROTECTED]> wrote:
> Hmm... Maybe this will work?
>
> /bin/sh -c "/usr/bin/ssh -n -f ${tunnel} &"
>
> --- the effect of this should (hopefully) be that init becomes the
> parent of the zombie process.
An easier-to-read way, assuming that a Bourne-compatible shell is
used (e.g., /bin/sh and not /bin/csh), would be:
( /usr/bin/ssh -n -f ${tunnel} & )
--
Darryl Okahata
[EMAIL PROTECTED]
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Agilent Technologies, or
of the little green men that have been following him all day.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Serious (ha-ha) bug in 4.9-RELEASE
Daniel Eischen <[EMAIL PROTECTED]> wrote:
> > Very critical indeed... And with such a huge userbase that it took six
> > months before anybody noticed this problem. :-)
>
> No, we noticed it here at work where we use Sun Solaris
> boxes as our development systems. I didn't know what the
> problem was until now. It is very very annoying to have
> man, more, less, etc, screw up your display when using
> them while remotely logged in to our FreeBSD boxes.
Oh, so THAT's the cause. I've been seeing this for quite a while,
but haven't been sufficiently annoyed to track it down. I just assumed
that either termcap or xterm was broken. I've just been using
"TERM=vt100" as a kludgearound.
> The
> symptoms are that everything gets highlighted and underlined
> and it stays that way forcing you to close the xterm and
> open another.
An easier fix is to run vi and exit, which resets the
highlighting.
--
Darryl Okahata
[EMAIL PROTECTED]
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Agilent Technologies, or
of the little green men that have been following him all day.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Problems with package repository
FYI, Where does one report problems with the package repository? On ftp.freebsd.org and ftp6.freebsd.org, there are a number of "truncated packages" (incomplete package .tgz files). I have a cron job that downloads selected new packages, and it's noticing that a number of new freebsd packages are MUCH smaller than before; spot-checking some from ftp.freebsd.org shows that these files are obviously truncated (and are thus unusable). Here's a partial list output from my cron job; the number before "(remote)" is the size on ftp.freebsd.org, and the number before "(local)" is the "old size" (the size of an older copy of the file on my local disk): Size diff: "dist/All/AbiWord-0.9.6.1_1.tgz": 8704 (remote) vs 7621132 (local) Size diff: "dist/All/ddd-3.3.tgz": 16896 (remote) vs 2495234 (local) Size diff: "dist/All/dictd-database-20010416_1.tgz": 80384 (remote) vs 29214892 (local) Size diff: "dist/All/emacs-21.1_5.tgz": 39424 (remote) vs 15567029 (local) Size diff: "dist/All/gcc30-3.0.2.tgz": 37376 (remote) vs 11245857 (local) Size diff: "dist/All/gimp-1.2.2_1,1.tgz": 6656 (remote) vs 7809660 (local) Size diff: "dist/All/lesstif-0.91.8.tgz": 80384 (remote) vs 2525874 (local) Size diff: "dist/All/qt-2.3.1_1.tgz": 8704 (remote) vs 9869728 (local) Size diff: "dist/All/qt-static-2.3.1_1.tgz": 27136 (remote) vs 7489599 (local) Size diff: "dist/All/teTeX-1.0.7.tgz": 18944 (remote) vs 38717508 (local) As much as I'd love to think that gcc and emacs can each be compressed to under 40KB, it's wishful thinking. ;-( For that matter, what happened to all of the kde and gnome packages (the main ones are missing)? Thanks, -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Recovering from clobbered boot manager?
Lamont Granquist <[EMAIL PROTECTED]> wrote: > So, whats the easist way to recover from a clobbered boot manager in > FreeBSD? I kind of naively assumed that this would be easy to do from an > installation CDROM (4.3-RELEASE) but I failed to get it to work. Going > Configure->Fdisk in sysinstall didn't work for me. For the basic procedure, see the FAQ. However, one important piece missing from the FAQ is that you may have to use the "boot0cfg" command to enable LBA booting (this is REQUIRED if your FreeBSD partition is above the 1024-cylinder/8GB limit, assuming your BIOS supports it, and virtually all recent BIOSes do). See the boot0cfg man page for more info. Note that the boot0cfg uses the term, "packet", to refer to LBA booting. Among other things, you need to use the boot0cfg option, "-o packet". Read the man page. -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Radeon + A7A266 + XFree86-4.1.0 + spontaneous reboot woes...
Troy Bowman <[EMAIL PROTECTED]> wrote: > This is a problem with the AMD761 chipset, because it kinda > non-standard. It seems like I read that it was their AGP > implementation. A fix in X's drivers to work with the 761 would help > greatly. I found a few mailng list discussions on it, and they said > that they're "working on it." You didn't look hard enough. A fix was discussed last week (right here, in fact, although the fix itself originated from the XFree86 DRI folks). -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: FreeBSD and Athlon Processors
"Juha Saarinen" <[EMAIL PROTECTED]> wrote: > Have a look at www.viahardware.com, where they test a variety of boards > for the data corruption bug. For the lazy, the URL is: http://www.viahardware.com/686b_1.shtm -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Ethernet Card Recommendation...
Tenebrae <[EMAIL PROTECTED]> wrote: > > One of the replies to my inquiry said that the Netgear network adapters do > > not work well with certain AMD-based motherboards. Considering that one of > > my future upgrades will be to build a multi-processor Athlon system, this > > caused me a bit of concern. > > Not sure about that... > I am using a Netgear FA310TX network card on my freeBSD 4.3-STABLE server > with an ASUS P5A Super Socket 7 motherboard (ALi chipset) and an AMD > K6-2/350 processor. I've been pretty happy with it. Only problems I've The Netgear card is definitely an issue with the ASUS A7M266 motherboard (AMD 760-based, single CPU however). Check out the alt.comp.periphs.mainboard.asus newsgroup for more info. -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: FreeBSD and Athlon Processors
Allen Landsidel <[EMAIL PROTECTED]> wrote: > > Yeah. As long as you avoid motherboards with the VIA KT133A/KT133 > >chipset and the VIA 686B Southbridge, you're probably fine (not all such > >motherboards supposedly have problems, but how do you tell the > >difference?). For more info, check out: > > This is total nonsense. Do a google groups search on "via chipset ide corruption". You might be surprised at what you find. Just because you don't have problems, doesn't mean that the problem doesn't exist. [ After scanning some of the hits, it seems that a new BIOS might fix the problem. ] > Some people may feel differently (As may I once the nForce is out and field > tested) in the future, but for now, I wouldn't even consider any Athlon > motherboard without a VIA chipset; The exception, of course, being AthlonMP Heh. I'm writing this on an Asus A7M266 (I didn't want to wait for the nForce). -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ast0: TAPE
Soren Schmidt <[EMAIL PROTECTED]> wrote: > Another thing is that for this to work, the drive has to be set into > a 32.5Kb block mode where the 32K carry userdata, and the 512bytes > carry block info, like blocknumber etc, since you have to have > that info when reading, since you must keep track of which blocks > you have read, since they might be repeated later due to bad spots > and the above hit'n'write strategy left one double block around... > > So, since I have not found a way to deal with this in a satisfactory > way (malloc'ing 1 Mbyte worth of buffer in the kernel is not fun), the > support we have can't handle tapes with bad spots on it... Does the ata device have something analogous to the SCSI passthrough device (e.g., /dev/pass0)? A long time ago, when I was looking at implementing a "driver" for the SCSI version of the Onstream drive, it was much easier to write a userland "driver" that used the passthrough device. This way, you can malloc() as much space as you want (the real reason I did it that way, was because it could be much easier to port to other operating systems). -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: affordable wireless
"Kevin Oberman" <[EMAIL PROTECTED]> wrote: > Even at 128 bits, WEP encryption is, at best, rather weak. The right > answer is to use strong encryption for everything. > > OpenSSH is now a standard part of FreeBSD. Use it and stop sending > clear passwords over the net. Then you don't care about the security > of the link, only the end nodes. Very true. If people want to know why, see: http://mail-index.netbsd.org/tech-net/2000/02/04/0001.html -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: affordable wireless
"Sameer R. Manek" <[EMAIL PROTECTED]> wrote: > Does anyone have any suggestions on how to have 802.11 wireless for home > users? Naturally it should be supported by FreeBSD. Configuruation can be > done on any pc os though. > > My only affordable solution so far is to use the Apple AirPort base station, > and wavelan pcmcia cards, but I don't know if they can co-exist, and the > AirPort needs a Macintosh to configure. My idea of affordable for this is > less then $500, the lucent wavelan solution works out to about $900 startup, > that's a little out of my budget. Just to let everyone know: I should be getting a TechWorks (Buffalo) AirStation in the next couple of days, and I'll be adding it to my FreeBSD Wireless documentation. A co-worker got one, and we played with it briefly; it doesn't look too bad. It's an actual base station (does not work in ad-hoc mode). I don't know if it supports NAT/DHCP though, although bridging appears to work fine. Other comments: * Configuration is done via a web browser (bleah). * Only supports 40-bit encryption. Don't know if it's like the AirPort when it comes to the 128-bit encryption upgrade, though. * Keys can be entered as hex (yes!). * The $279 model doesn't have a modem. With a modem, it's $299 (the same as the AirPort). * It works fine with my Lucent Orinoco (WaveLan) gold card (we didn't try enabling encryption, though). -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
