Re: What's new with xdm and 4.2 ? [FINAL]
Hi! I just want to let you know that I have solved my problem by means of tcpdump. I have an old attempt in my Xservers file. As my DNS server was cleaned and I totally forget this attempt I was trying to reach a very old machine which is not part of my network anymore. Thanks. Phil. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ports
Original Message On 1/19/01, 11:16:50 AM, Dominic Mitchell [EMAIL PROTECTED] wrote regarding Re: ports: On Thu, Jan 18, 2001 at 10:02:23PM -0500, Christopher K Davis wrote: W Gerald Hicks [EMAIL PROTECTED] writes: This syndrome is often caused when one uses CVSup to update their ports tree a long time after installing from a release. CVSup will not normally delete any file it didn't create. Sometimes this will cause a stale patch file to be left in a port. Would a reasonable test/fix for this be deleting the entire port directory in question and re-cvsupping? (This should make cvsup recreate everything and update its file lists, right?) Even better would be to use the cvsupchk tool that comes with cvsup (in the contrib directory) to get a list of files that shouldn't be there anyway. Then you can just pass a list to "xargs rm -f". It isn't installed by default, but if you still have a copy of the cvsup tarball in /usr/ports/distfiles, it will be in there. Even the "binary" distributions. You may wish to take a look at the cvsup FAQ found on http://www.polstra.com, and pay attention to the discussion in Q12, Q13. Mutatis mutandis, the same holds for the ports tree. Since ports are tagged "." (ie -CURRENT), one can correctly "sync" them for the first time by adding the *date* keyword (cf cvsup(1) for the exact format): one should specify a date as close as possible to that of "shipping" of one's ports tree. After cvsup has correctly created the ports checkouts file, which is precisely the goal of this first special synch operation, the date field must be removed; all subsequent updates will (ahem, should :-) be performed smoothly. Both approaches (the tool and the correct synching procedure) have been discussed countless times on these lists but, as the saying goes, few people read man pages, and fewer still the mailing list archives... :-) Best regards, Salvo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Problem with -stable and ata drives
I've got a problem that, because of the nature of the problem and the environment I can't give better details on. When I cvsup'ed to -stable last week, (I was at 4.2 stable as of sometime in December at that point) I rebooted after installing the new kernel and when attempting to mount the filesystems it would time out on read. After a few such attempts it would fall back to PIO mode (which happens anyway eventually on my machine) and it could read, but then it would timeout on write while (I'm guessing here) fsck was running. I could boot the old kernel just fine. For some reason the new ipfw did not like diverting to natd and my networking was a bit of a mess. In any case, I could get the machine back to 4.2-release, which is where I sit for now. I didn't find anything about this type of a problem in the research I did. I'm curious if this is a known issue before I try to take my router apart to get chip set and drive information to debug. -- Groove on Dude Michael Conlen [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
TTY console
I have a Dell PowerEdge server. Using FreeBSD-4.2 (recently built and updated), I can only force the serial console IF I have a keyboard plugged in. It doesn't matter what flags I use -P -D -h or just -h. Is this a bug, or? _F To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: RE: Weird sporadic DNS resolution problems
:Short term, though, I liked the suggestion about stuffing an entry in :/etc/hosts to work around the broken domains' DNS problems, and that does :work for me for now. So at least I have an ugly workaround.. much less :ugly than restarted named every few hours though. Next, I'm going to :start comparing the sendmail.cf files built from my old 8.9.3 .mc file and :my current 8.11.x .mc file and see if any big differences jump out at :me... : :Mike Andrews * [EMAIL PROTECTED] * [EMAIL PROTECTED] * http://www.bit0.com Don't do that! If the broken hosts have at least one working name server, then you can use options in named.conf to make bind ignore the broken servers. The bind documentation has all the information you need to make this work. This is a whole lot safer then creating static entries in /etc/hosts. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: RE: Weird sporadic DNS resolution problems
At 11:48 AM 1/19/01 -0800, Matt Dillon wrote: Don't do that! If the broken hosts have at least one working name server, then you can use options in named.conf to make bind ignore the broken servers. The bind documentation has all the information you need to make this work. This is a whole lot safer then creating static entries in /etc/hosts. Are you referring to auth-nxdomain ? Or something else ? ---Mike -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: RE: Weird sporadic DNS resolution problems
: :At 11:48 AM 1/19/01 -0800, Matt Dillon wrote: : : Don't do that! : : If the broken hosts have at least one working name server, then you : can use options in named.conf to make bind ignore the broken servers. : The bind documentation has all the information you need to make this : work. This is a whole lot safer then creating static entries in : /etc/hosts. : :Are you referring to auth-nxdomain ? Or something else ? : : ---Mike Let me find it... ah, here, look at the 'server' option. file:/usr/share/doc/bind/html/server.html And also the 'blackhole' option: file:/usr/share/doc/bind/html/options.html -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Intel PRO/1000F NIC wx driver
The Intel PRO/1000F NIC does not seem to be fully supported by the wx driver. I have directly connected two of these cards with a fiber patch cable, link lights are on, and the driver tells me "wx0: gigabit link now up". However, pings across the link fail, because packets are simply swallowed: For a ping, I can see the ARP request go out in tcpdump, the TX light flickers, but the remote end never receives anything. We're using FreeBSD 4.2-RELEASE. The same setup works fine under Windows 2000, so I doubt it's hardware-related. [larse@hbo: ~] dmesg | grep wx wx0: Intel GigaBit Ethernet (LIVENGOOD_SC) mem 0xfafd-0xfafd,0xfafe-0xfaff irq 16 at device 4.0 on pci3 wx0: Ethernet address 00:03:47:07:e8:10 bpf: wx0 attached wx0: gigabit link now up [larse@hbo: ~] ifconfig -L wx0 wx0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::203:47ff:fe07:e810%wx0 prefixlen 64 scopeid 0x1 inet 128.9.112.174 netmask 0xf000 broadcast 128.9.127.255 ether 00:03:47:07:e8:10 media: 1000baseSX full-duplex (autoselect full-duplex) status: active supported media: 1000baseSX full-duplex 1000baseSX Please let me know how I can help to track this down! Lars -- Lars Eggert [EMAIL PROTECTED] Information Sciences Institute http://www.isi.edu/larse/University of Southern California S/MIME Cryptographic Signature
Re: Intel PRO/1000F NIC wx driver
Lars Eggert wrote: The Intel PRO/1000F NIC does not seem to be fully supported by the wx driver. Sorry for not mentioning this in the original post: This card uses the Intel 82543GC chip. -- Lars Eggert [EMAIL PROTECTED] Information Sciences Institute http://www.isi.edu/larse/University of Southern California S/MIME Cryptographic Signature
Re: ports
Salvo Bartolotta [EMAIL PROTECTED] writes: You may wish to take a look at the cvsup FAQ found on http://www.polstra.com, and pay attention to the discussion in Q12, Q13. [...] Both approaches (the tool and the correct synching procedure) have been discussed countless times on these lists but, as the saying goes, few people read man pages, and fewer still the mailing list archives... :-) The tool isn't in the cvsupit package, nor is the "pump priming sync" technique in the Handbook (under any of current, synching, or cvsup). (Admittedly a link to the cvsup home page is there, so I could have found the FAQ that way. Mea culpa on that bit.) WIBNI the cvsupit package would do the pump priming for you? But then, it'd have to figure out what version of the source you were starting with (probably easy) *and* the date of the ports collection you're working with (probably not as easy). Hmm -- Christopher Davis * [EMAIL PROTECTED] * URL:http://www.ckdhr.com/ckd/ Put location information in your DNS! URL:http://www.ckdhr.com/dns-loc/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Intel PRO/1000F NIC wx driver
Lars Eggert [EMAIL PROTECTED] probably said: Lars Eggert wrote: The Intel PRO/1000F NIC does not seem to be fully supported by the wx driver. Sorry for not mentioning this in the original post: This card uses the Intel 82543GC chip. I realise this isn't very useful to you for getting that card working, but if you need gig ether working sooner than a fix I've been using the Netgear GA620, both fibre and copper versions; ti0: Netgear GA620 1000baseT Gigabit Ethernet mem 0xf400-0xf4003fff irq 10 at device 15.0 on pci0 ti0: gigabit link up ti0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 130.64.1.222 netmask 0xff00 broadcast 130.64.1.255 ether 00:02:e3:00:3d:a0 media: autoselect (1000baseTX full-duplex) status: active supported media: autoselect 1000baseTX full-duplex 1000baseTX 100baseTX full-duplex 100baseTX 10baseT/UTP full-duplex 10baseT/UTP Negotiates fine with the Foundry kit we use, at 100bT fdx and gbit fdx. P. -- pir [EMAIL PROTECTED][EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Intel PRO/1000F NIC wx driver
I'll look at it when I next spend a couple of days on this NIC (hopefully next week). To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
sshd with ssh -t problems
Not sure if someone else has run into this, but with 4.2-STABLE circa 1/16/2000's sshd I get the following behavior: othermachine% ssh -t 4.2stable-box ls login behavior 4.2stable-box% That is, from any other machine (running ssh-1.2.27 or various versions of openssh), trying to run a command via ssh while using the -t flag (particularly useful for, say, screen), causes you to log in, instead of merely executing the command and exiting (it seems to ignore the command, in fact) Is this a known problem? (I'm using the stock sshd_config) --David Bushong To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
