Re: Resolv.conf question
Jim Durham <[EMAIL PROTECTED]> wrote: > The 3.3 Box is a local server on a disconnected LAN talking > to a "remote" server that spools mail, which is grabbed by > fetchmail. We are running PPP on-demand to the external > server via a dial-up to an ISP. However, PPP only holds the > line up from 8am-8pm and this is happening at 1:59am, coinciding > with the "periodic daily" scripts from crontab. Try changing "netstat -i" to "netstat -ni" in the script /etc/periodic/daily/420.status-network Maybe the reverse dns lookup done by netstat -i tries to activate ppp which then wipes /etc/resolv.conf. Just a crazy idea... -- Björn Danielsson KTHNOC / Swedish University Network (mail me for my real e-mail address) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Resolv.conf question
On Thu, Dec 16, 1999 at 08:36:41PM -0500, Jim Durham wrote: > I posted this to -questions, but didn't really > get any answer that seemed to fit, so I thought > I would ask here. > > On a 3.3-RELEASE box, not realizing at first that > I didn't need an entry for the local nameserver, I > had it's IP in as the first line in resolv.conf, followed > by two more nameservers on the next two lines. > > Something in the daily scripts seemed to eliminate the > first line, containing the local nameserver. I say this > because the file date was 1:59am, the time that periodic/daily > runs. I put it back every day, and the next day, it was gone again. > > I hunted quite a while in the scripts, but couldn't > figure out what was doing this? > > Just for the sake of my curiosity, what was modifiying > resolv.conf? Is this a security feature? > Could be ppp(8). -- Ruslan Ermilov Sysadmin and DBA of the [EMAIL PROTECTED]United Commercial Bank, [EMAIL PROTECTED] FreeBSD committer, +380.652.247.647Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ATA w/ today's -CURRENT
> > ata_command: timeout waiting for interrupt > > ^^^ > > Thats an aritifact from the ATAPI probes, it should be of no harm... In that case, is there some way of getting rid of the message? Nick -- [EMAIL PROTECTED] [EMAIL PROTECTED] USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ATA w/ today's -CURRENT
It seems Nick Hibma wrote: > > > ata_command: timeout waiting for interrupt > > > ^^^ > > > > Thats an aritifact from the ATAPI probes, it should be of no harm... > > In that case, is there some way of getting rid of the message? Erhm well, I said harmless, but it indicates there is a problem with drive compliance -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Strange problem with NFS
> > Looks like a firewall to me. Either a firewall in a router > > sitting between the hosts, or an ipfw setup sitting on one or the > > other host. > > I set up the NFS server in question ages ago. I haven't looked at the > problem, but... The server does use ipfw. The broken client is on the same > subnet as the working ones and nothing in the server's ipfw ruleset refers > directly to the broken client. I can confirm this. The 1st 3 ipfw rules on server : 00100 allow ip from any to any via lo0 00200 deny ip from any to 127.0.0.0/8 02000 allow ip from 192.168.0.0/24 to 192.168.0.0/24 via fxp0 (192.168.0.0/24 is subnet both client and server are on and fxp0 is internal NIC) there is no ipfw/ipfilter setup on the client, everything is open.. Cillian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Resolv.conf question
On 17-Dec-99 Jim Durham wrote: > Mike Smith wrote: >> >> > Something in the daily scripts seemed to eliminate the >> > first line, containing the local nameserver. I say this >> > because the file date was 1:59am, the time that periodic/daily >> > runs. I put it back every day, and the next day, it was gone again. >> > >> > I hunted quite a while in the scripts, but couldn't >> > figure out what was doing this? >> >> Nothing should. >> >> > Just for the sake of my curiosity, what was modifiying >> > resolv.conf? Is this a security feature? >> >> No idea. Are you running DHCP there by any chance? >> > > Nope. There's an NT box on the LAN doing DHCP. > > The 3.3 Box is a local server on a disconnected LAN talking > to a "remote" server that spools mail, which is grabbed by > fetchmail. We are running PPP on-demand to the external > server via a dial-up to an ISP. However, PPP only holds the > line up from 8am-8pm and this is happening at 1:59am, coinciding > with the "periodic daily" scripts from crontab. > to mail the output of the periodic; sendmail is pulling up ppp > Seemed wierd to me.. me too. Regards, -- Don Read [EMAIL PROTECTED] EDP Manager [EMAIL PROTECTED] Calcasieu Lumber Co. Austin TX -- No Coffee No Peace To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ATA w/ today's -CURRENT
> It seems Nick Hibma wrote: > > > > ata_command: timeout waiting for interrupt > > > > ^^^ > > > > > > Thats an aritifact from the ATAPI probes, it should be of no harm... > > > > In that case, is there some way of getting rid of the message? > > Erhm well, I said harmless, but it indicates there is a problem with > drive compliance perhaps change the message to indicate that the drive is non-compliant. as it appears now, it seems to say that there it a problem that may affect the user. how about: "timeout waiting for interrupt, non-compliant drive, compensating". ;) jmb To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Upper <->Lower in shell script
This message was sent from Geocrawler.com by "Alex" <[EMAIL PROTECTED]> Be sure to reply to that address. Hello, I need in my shell script change upper case to lower case for characters. Cureently , I call c programm from script which do it. Is anybody did this inside script? Thank you Alex Geocrawler.com - The Knowledge Archive To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Upper <->Lower in shell script
In the last episode (Dec 17), Alex said:
> I need in my shell script change upper case to lower case for
> characters. Cureently , I call c programm from script which do it. Is
> anybody did this inside script?
#!/bin/sh
var=MixedCase
lvar=`echo $var | tr A-Z a-z`
echo $lvar
#!/usr/local/bin/zsh
var=MixedCase
lvar=${var:l}
echo $lvar
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: Upper <->Lower in shell script
On Fri, Dec 17, 1999, Alex wrote: > I need in my shell script change upper case to > lower case for characters. Cureently , I call c > programm from script which do it. > Is anybody did this inside script? Shells such as ksh (both PDKSH and AT&T KSH, available in ports, support this) and bash have a typeset command. To convert something to all upper-case is surprisingly easy: typeset -u variable Example: $ typeset -u f $ f=abc $ echo $f ABC -- |Chris Costello <[EMAIL PROTECTED]> |Beware of programmers who carry screwdrivers. - Leonard Brandwein `-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Upper <->Lower in shell script
On Fri, Dec 17, 1999, Alex wrote: > I need in my shell script change upper case to > lower case for characters. Cureently , I call c > programm from script which do it. > Is anybody did this inside script? Oops. That should be typeset -l. $ typeset -l var $ var=ABC $ echo $var abc -- |Chris Costello <[EMAIL PROTECTED]> |Random access is the optimum of the mass storages. `-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
IPFW Question
-BEGIN PGP SIGNED MESSAGE- Hi, We have a situation where we would like to drop packets based on the IP datagram length. I was wondering if this was possible with ipfw, and if not, how hard would this functionality be to implement into it. Thanks in advance... Corey - -- Corey Leopold E-Mail: Corey Leopold <[EMAIL PROTECTED]> Phone (210)-925-3459 - -- -BEGIN PGP SIGNATURE- Version: PGPfreeware 5.0i for non-commercial use Charset: noconv iQCVAwUBOFpWgD3+cS8MmLXZAQHVPQQAqvSZkGoJSpmDPnKkxESgNNqHWbtwkIum G5Vff+7GANvoBzCjw5oD6q1+6IdSnHh5ZjssCq8z0OAyCg9nvO3KnS3dpjtfGCWC wcSjZV/gOdxXlMtF8tp5TIce1WFJADP8L4s/7qp+VuYxXfr5Msoc8qtw72grwrzG o9TwK2bE+Bk= =T410 -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Resolv.conf question
Jim Durham wrote: > Something in the daily scripts seemed to eliminate the > first line, containing the local nameserver. I say this > because the file date was 1:59am, the time that periodic/daily > runs. I put it back every day, and the next day, it was gone again. > > I hunted quite a while in the scripts, but couldn't > figure out what was doing this? Are you running ppp (user, not kernel pppd)? I think it will modify /etc/resolv.conf if you specify ``enable dns'', but I'm not too sure (check the source if you want). -- Ben Smithurst| PGP: 0x99392F7D [EMAIL PROTECTED] | key available from keyservers and | [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
PRO/100+ DUAL PORT SERVER ADAPTER
Anybody have positive experience with this adapter? I will be using it in a router box. PRO/100+ DUAL PORT SERVER ADAPTER Thank you, Aaron To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: PRO/100+ DUAL PORT SERVER ADAPTER
On Fri, 17 Dec 1999, Aaron Sonntag wrote: > Anybody have positive experience with this adapter? > I will be using it in a router box. > > PRO/100+ DUAL PORT SERVER ADAPTER pcib3: at device 10.0 on pci2 pci3: on pcib3 fxp0: irq 10 at device 4.0 on pci3 fxp0: Ethernet address 00:90:27:2a:65:3e fxp1: irq 10 at device 5.0 on pci3 fxp1: Ethernet address 00:90:27:2a:65:3f Works perfectly over here. FreeBSD hawk.internal.chc-chimes.com 4.0-CURRENT FreeBSD 4.0-CURRENT #9: Mon Dec 13 22:07:08 EST 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/LOVEMACHINE i386 -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Per CPU timekeeping for SMP
Arun Sharma wrote: > > > Here's a reimplementation of my earlier per cpu time keeping patch > on SMP. The attached patch is against a 11/20/99 -current that I > cvsup'ed. Did anyone get a chance to review this ? Is everyone busy or sending patches to -hackers is frowned upon ? Or is this something that people aren't so excited about ? > 4. I've gotten sysctls working for sys_time - > > $ sysctl -A | grep kern.stats > kern.stats.systime.user: 25150 > kern.stats.systime.nice: 3878 > kern.stats.systime.sys: 14071 > kern.stats.systime.intr: 7395 > kern.stats.systime.idle: 5326029 > > I'm working on generating the per cpu sysctls. I've completed this work now. Here's the output of the new sysctl on my dual cpu box: $ sysctl -A | grep kern.stats kern.stats.systime.user: 13710 kern.stats.systime.nice: 552 kern.stats.systime.sys: 4296 kern.stats.systime.intr: 2602 kern.stats.systime.idle: 1878764 kern.stats.cpu.user.0: 7082 kern.stats.cpu.user.1: 7169 kern.stats.cpu.nice.0: 9 kern.stats.cpu.nice.1: 2 kern.stats.cpu.sys.0: 2120 kern.stats.cpu.sys.1: 2177 kern.stats.cpu.intr.0: 1309 kern.stats.cpu.intr.1: 1293 kern.stats.cpu.idle.0: 939407 kern.stats.cpu.idle.1: 939358 I have also figured out how to dynamically register sysctl nodes. The trick is to basically malloc a sysctl_oid and fill in the right fields and calling sysctl_register_oid. The code is in a kernel module available from: http://sharmas.dhs.org/~adsharma/projects/freebsd/sysctl.tar.gz It really needs to go into the base kernel. Also, I think sysctl_register_long and its yet to be written friends (register_int) etc, need to go into kern_sysctl - so that others can reuse the code to dynamically create sysctl nodes. I really don't want to spend my time on getting xosview and ktop to use these patches until I'm convinced that this code is going into the kernel. Again, the patches may not be perfect. But if people can review it I'll fix any issues. Also, Alpha guys need to make minor changes to keep things working. -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Upper <->Lower in shell script
> This message was sent from Geocrawler.com by "Alex" <[EMAIL PROTECTED]> > Be sure to reply to that address. > > Hello, > > I need in my shell script change upper case to > lower case for characters. Cureently , I call c > programm from script which do it. > Is anybody did this inside script? tr A-Z a-z -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
aout gdb in 3.x
How does one compile a version of GDB that can read a.out files? I know there is a way of doing it but I have totoally failed to work out how to do so. Julian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Per CPU timekeeping for SMP
At 11:41 AM -0800 12/17/99, Arun Sharma wrote: >Arun Sharma wrote: > > > > > > Here's a reimplementation of my earlier per cpu time keeping patch > > on SMP. The attached patch is against a 11/20/99 -current that I > > cvsup'ed. > >Did anyone get a chance to review this ? Is everyone busy or sending >patches to -hackers is frowned upon ? Or is this something that >people aren't so excited about ? Probably need to send this to -current instead of -hackers. Also, pick a subject that says something about "patches for review". Also note that people are in the middle of pushing out the 3.4-release, so they might not have time to read all of the articles in hackers right now. I'm interested in the idea of per-CPU timekeeping, but at the moment I don't have a 4.x-current system setup, so I can't try this... I know I've seen others ask for detail at the per-CPU level, although I obviously don't know if your patch does exactly what they were asking for. --- Garance Alistair Drosehn = [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Institute To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Dynamic sysctls (Re: Per CPU timekeeping for SMP)
On Fri, 17 Dec 1999, Arun Sharma wrote: > I have also figured out how to dynamically register sysctl nodes. > The trick is to basically malloc a sysctl_oid and fill in the right > fields and calling sysctl_register_oid. The code is in a kernel > module available from: > > http://sharmas.dhs.org/~adsharma/projects/freebsd/sysctl.tar.gz > > It really needs to go into the base kernel. Also, I think > sysctl_register_long and its yet to be written friends (register_int) > etc, need to go into kern_sysctl - so that others can reuse the code > to dynamically create sysctl nodes. I was thinking exactly about the same, and I was going to implement them myself... IMO these patches should go to the tree - without them the work that Mike Smith put into sysctl infrastructure is much less useful for average Joe Kernel Hacker... Andrzej Bialecki // <[EMAIL PROTECTED]> WebGiro AB, Sweden (http://www.webgiro.com) // --- // -- FreeBSD: The Power to Serve. http://www.freebsd.org // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Dynamic sysctls (Re: Per CPU timekeeping for SMP)
Andrzej Bialecki wrote: > On Fri, 17 Dec 1999, Arun Sharma wrote: > > > I have also figured out how to dynamically register sysctl nodes. > > The trick is to basically malloc a sysctl_oid and fill in the right > > fields and calling sysctl_register_oid. The code is in a kernel > > module available from: > > > > http://sharmas.dhs.org/~adsharma/projects/freebsd/sysctl.tar.gz > > > > It really needs to go into the base kernel. Also, I think > > sysctl_register_long and its yet to be written friends (register_int) > > etc, need to go into kern_sysctl - so that others can reuse the code > > to dynamically create sysctl nodes. > > I was thinking exactly about the same, and I was going to implement them > myself... IMO these patches should go to the tree - without them the work > that Mike Smith put into sysctl infrastructure is much less useful for > average Joe Kernel Hacker... Err.. That was Doug Rabson (dfr) who fixed the sysctl stuff to finish making it dynamic. sysctl_register_xxx() are wrappers around sysctl_register_oid(), but I guess it's ok to make some helper functions to make the existing functionality to make it easier to use. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Dynamic sysctls (Re: Per CPU timekeeping for SMP)
On Sat, 18 Dec 1999, Peter Wemm wrote: > Andrzej Bialecki wrote: > > On Fri, 17 Dec 1999, Arun Sharma wrote: > > > > > I have also figured out how to dynamically register sysctl nodes. > > > The trick is to basically malloc a sysctl_oid and fill in the right > > > fields and calling sysctl_register_oid. The code is in a kernel > > > module available from: > > > > > > http://sharmas.dhs.org/~adsharma/projects/freebsd/sysctl.tar.gz > > > > > > It really needs to go into the base kernel. Also, I think > > > sysctl_register_long and its yet to be written friends (register_int) > > > etc, need to go into kern_sysctl - so that others can reuse the code > > > to dynamically create sysctl nodes. > > > > I was thinking exactly about the same, and I was going to implement them > > myself... IMO these patches should go to the tree - without them the work > > that Mike Smith put into sysctl infrastructure is much less useful for > > average Joe Kernel Hacker... > > Err.. That was Doug Rabson (dfr) who fixed the sysctl stuff to finish > making it dynamic. sysctl_register_xxx() are wrappers around > sysctl_register_oid(), but I guess it's ok to make some helper functions to > make the existing functionality to make it easier to use. Oh... My sincere apologies then for wrong attribution. Anyway, I think this stuff (although it may seem redundant to you) is very helpful. It takes some time to figure out how to untangle the SYSCTL_*, SLIST_*, DATA_SET and linker sets (which are not really indispensable here) to really learn how the dynamic sysctls work. These functions provide useful and handy shortcuts. IMHO, of course. Andrzej Bialecki // <[EMAIL PROTECTED]> WebGiro AB, Sweden (http://www.webgiro.com) // --- // -- FreeBSD: The Power to Serve. http://www.freebsd.org // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Dynamic sysctls (Re: Per CPU timekeeping for SMP)
On Fri, 17 Dec 1999, Andrzej Bialecki wrote: > On Fri, 17 Dec 1999, Arun Sharma wrote: > > > I have also figured out how to dynamically register sysctl nodes. > > The trick is to basically malloc a sysctl_oid and fill in the right > > fields and calling sysctl_register_oid. The code is in a kernel > > module available from: > > > > http://sharmas.dhs.org/~adsharma/projects/freebsd/sysctl.tar.gz > > > > It really needs to go into the base kernel. Also, I think > > sysctl_register_long and its yet to be written friends (register_int) > > etc, need to go into kern_sysctl - so that others can reuse the code > > to dynamically create sysctl nodes. > Can this patch be applied to FreeBSD 3.3-Release? If so, is it difficult to do so? -Zhihui To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ATAPI tape support - how to format?
On Monday, 13 December 1999 at 12:55:20 -0600, Karl Denninger wrote: > > BTW, I have older HP DAT drives (4 & 8gb models) that have several YEARS > of active use on them, and other than using a cleaning tape when the front > panel "clean me" light flashes I've NEVER had ANY problem with them. This is in stark contrast with my experience. Which models? The 35480A DDS-1 drives I had had a life of about 8 months with daily backups. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ATAPI tape support - how to format?
C1533As, circa 1994. I have two of them and they are still working. They were in use at an *ISP* as primary backup devices for more than two years (read: had the shit beaten out of them nightly) until we outgrew them and went to Exabyte 8705s (which SUCKED reliability-wise, although they're better than the 8500s!). The final step was to go to two DLT IIIXTs (after that I have no idea; I don't run the place anymore) Their predecessors, two 35480As, were replaced ONLY for capacity reasons. As far as I know *those* are still working (I know where one of them is and its not broken) I've never had trouble with HP DAT drives. None whatsoever. -- -- Karl Denninger ([EMAIL PROTECTED]) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! On Sat, Dec 18, 1999 at 12:08:32PM +1030, Greg Lehey wrote: > On Monday, 13 December 1999 at 12:55:20 -0600, Karl Denninger wrote: > > > > BTW, I have older HP DAT drives (4 & 8gb models) that have several YEARS > > of active use on them, and other than using a cleaning tape when the front > > panel "clean me" light flashes I've NEVER had ANY problem with them. > > This is in stark contrast with my experience. Which models? The > 35480A DDS-1 drives I had had a life of about 8 months with daily > backups. > > Greg > -- > Finger [EMAIL PROTECTED] for PGP public key > See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Tape reliability (was: ATAPI tape support - how to format?)
On Friday, 17 December 1999 at 20:19:10 -0600, Karl Denninger wrote: > On Sat, Dec 18, 1999 at 12:08:32PM +1030, Greg Lehey wrote: >> On Monday, 13 December 1999 at 12:55:20 -0600, Karl Denninger wrote: >>> >>> BTW, I have older HP DAT drives (4 & 8gb models) that have several YEARS >>> of active use on them, and other than using a cleaning tape when the front >>> panel "clean me" light flashes I've NEVER had ANY problem with them. >> >> This is in stark contrast with my experience. Which models? The >> 35480A DDS-1 drives I had had a life of about 8 months with daily >> backups. > > C1533As, circa 1994. I have two of them and they are still working. I had one of them. In fact I still do, and it didn't fail on me; it got damaged in transit instead, and I never got it repaired. > They were in use at an *ISP* as primary backup devices for more than > two years (read: had the shit beaten out of them nightly) until we > outgrew them and went to Exabyte 8705s (which SUCKED > reliability-wise, although they're better than the 8500s!). I've never used an 8700. My 8505XL still seems to be working, the 8500 before it wore out. > The final step was to go to two DLT IIIXTs (after that I have no > idea; I don't run the place anymore) I'm having trouble with a Quantum DLT4000 right now, but it looks like a compatibility problem. > Their predecessors, two 35480As, were replaced ONLY for capacity reasons. > As far as I know *those* are still working (I know where one of them is and > its not broken) > > I've never had trouble with HP DAT drives. None whatsoever. Amazing. I certainly had your share of the trouble as well. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Tape reliability (was: ATAPI tape support - how to format?)
On Sat, Dec 18, 1999 at 12:54:42PM +1030, Greg Lehey wrote: > On Friday, 17 December 1999 at 20:19:10 -0600, Karl Denninger wrote: > > On Sat, Dec 18, 1999 at 12:08:32PM +1030, Greg Lehey wrote: > >> On Monday, 13 December 1999 at 12:55:20 -0600, Karl Denninger wrote: > >>> > >>> BTW, I have older HP DAT drives (4 & 8gb models) that have several YEARS > >>> of active use on them, and other than using a cleaning tape when the front > >>> panel "clean me" light flashes I've NEVER had ANY problem with them. > >> > >> This is in stark contrast with my experience. Which models? The > >> 35480A DDS-1 drives I had had a life of about 8 months with daily > >> backups. > > > > C1533As, circa 1994. I have two of them and they are still working. > > I had one of them. In fact I still do, and it didn't fail on me; it > got damaged in transit instead, and I never got it repaired. Ah. Well, they're good drives. I still have one in my production machine; its all original (still has a 9406 firmware stamp!) ;-) > > They were in use at an *ISP* as primary backup devices for more than > > two years (read: had the shit beaten out of them nightly) until we > > outgrew them and went to Exabyte 8705s (which SUCKED > > reliability-wise, although they're better than the 8500s!). > > I've never used an 8700. My 8505XL still seems to be working, the > 8500 before it wore out. I had 8505XLs too - they sucked badly as well. My luck with Exabytes has been somewhere between shit and worse. I could tell you horror stories from the early 90s on production machines that ate their tapes or worse, wrote tapes that couldn't be restored.. > > The final step was to go to two DLT IIIXTs (after that I have no > > idea; I don't run the place anymore) > > I'm having trouble with a Quantum DLT4000 right now, but it looks like > a compatibility problem. I still have the two IIIXTs - they're overkill for my network at the house but they work and the price was right. :-) > > Their predecessors, two 35480As, were replaced ONLY for capacity reasons. > > As far as I know *those* are still working (I know where one of them is and > > its not broken) > > > > I've never had trouble with HP DAT drives. None whatsoever. > > Amazing. I certainly had your share of the trouble as well. That's ok - I got your share of trouble with the Exabytes, so we're even ;-). -- -- Karl Denninger ([EMAIL PROTECTED]) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
New victim.. er.. committer
< said: > although I actually live near Amherst, Massachusetts much of the > time. Anyone up for a Southern New England FreeBSD ftf gtg? I can host. If you think you might be interested, please reply privately. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same [EMAIL PROTECTED] | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Sun4c as Xterminal - Problems
Here is a question that will test your memories! I'm trying to use a Sun ELC (sun4c) as an Xterminal on my FreeBSD system using Xkernel 2.0. I've used the old howto's from 1996 (Philippe Regnauld) as well as NetBSD diskless howto's to set this up. I've got it working up to a point: It finds it IP address via rarp loads the boot loader via tftp mounts it's root via nfs and boots the kernel. But then it freezes with the message: le0 at SBus slot 0 0xc0 pri 5 bwtwo0 at SBus slot 3 0x0 pri 7 No bootparam server responding; still trying whoami: pmap_rmtcall status 0x5 Looking at a tcpdump, I see: 22:45:09.936573 sun.wl.vg.1023 > 209.9.69.0.sunrpc: udp 100 repeated frequently. >From what I've seen in the mail archives, it's probably a networking issue, and several people asked about it in 1996. But I never found a solution in the archives, only questions. So, does anyone have a fix for this? Back in '96-97, Luigi Rizzo and Mike Smith (among others) seemed to be doing this, so I'm hoping someone still does. Patrick Gardella My setup: 4.0-CURRENT #2: Sun Dec 12 20:35:48 EST 1999 fxp0: flags=8943 mtu 1500 inet 209.9.69.194 netmask 0xffe0 broadcast 209.9.69.223 ether 00:90:27:cb:0f:32 media: autoselect (10baseT/UTP) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
