Re: Problems installing FreeBSD 4.0 20000125-CURRENT

>>> 3. On the first reboot after installing, the keyboard was in a funny >>> state. > >> Urk, can't reproduce it. I need a reproducible sequence of operations >> before we'll have any hope of tackling this one. > >>> Control-alt-del definitely didn't work, so I had to power off and >>> reboot. T

Re: Problems installing FreeBSD 4.0 20000125-CURRENT

>I seem to have this problem occasionaly, the keyboard keymap gets all screwed >up somehow, and the only way to get out is to hit the reset button. But I've >been having the problem for a long time, and with different boxes. It happens >about every 1 out of 15 reboots but randomly. I haven't been

Re: Errors compiling kernel...

On Thu, Jan 27, 2000 at 07:31:50PM -0500, Donn Miller wrote: > I recently cvsup'd the sources (around Thu Jan 27 19:30:48 EST 2000), and > I'm getting these errors compiling the kernel: > > cc -c -mpentium -O3 -pipe -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes -Wmissing-prototy

Re: buildworld failure in "===> makeinfo"

>>whereintheworld.pl (thanxs Bill Fenner) shows ... >What does this Perl script do? :-) See http://www.freebsd.org/~fenner/ - it parses "make world" output in a way that gives slightly better progress info than just a "tail". Bill To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscr

Re: Problems installing FreeBSD 4.0 20000125-CURRENT

>> In message <[EMAIL PROTECTED]> Mike Smith writes: >> : It doesn't do anything to the keyboard, it just calls the BIOS to find >> : out whether keys have been pressed. >> >> I've been seeing the hit twice fast problem for months. > >It's always been a problem; we don't understand the mechani

Re: Comments on this patch?

:On Thu, Jan 27, 2000 at 02:44:27PM -0700, Warner Losh wrote: :> I've been running this for a while. I reversed the normal order to :> make it easier to do the math w/o having to shift columns and flip :> things over. : :Thanks for the patch! It'd be nice to time the buildworld only. Is there :a

Re: Problems installing FreeBSD 4.0 20000125-CURRENT

< said: > citizen" these days without a resolvable hostname that also matches > your primary IP address or, among other things, you won't be able to > send mail directly to anyone who practices traditional spam filtering > techniques. However, there is no need to actually use the configured host

Re: Comments on this patch?

On Thu, Jan 27, 2000 at 04:00:40PM -0700, Warner Losh wrote: > So I'd say this is with 2.7.3 and the compiler in today's current. Ah. 2.95.2 is a known speed snail. The GCC developers took this to heart and 2.96 will compile much faster. To Unsubscribe: send mail to [EMAIL PROTECTED] with "un

Re: Problems installing FreeBSD 4.0 20000125-CURRENT

> < said: > > > citizen" these days without a resolvable hostname that also matches > > your primary IP address or, among other things, you won't be able to > > send mail directly to anyone who practices traditional spam filtering > > techniques. > > However, there is no need to actually use the

Re: Problems installing FreeBSD 4.0 20000125-CURRENT

On Thu, Jan 27, 2000 at 04:06:31PM -0800, Jordan K. Hubbard wrote: > > IMHO, that is the wrong assumption. Most DHCP servers I've seen aren't > > setup to provide hostnames to the requrestor. > > Seems they're set up incorrectly then. Not at all. > You can't be a good "network citizen" these d

-current is still broken as of 2000/01/27

===> libexec/getNAME cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -c /usr/src/libexec/getNAME/ge tNAME.c cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -o getNAME getNAME.o gzip -cn /usr/src/libexec/getNAME/getNAME.1 > getNAME.1.gz ===> libexec/getty cc -O -pipe -I/usr/obj/usr/src/i386/

Re: Problems installing FreeBSD 4.0 20000125-CURRENT

On Thu, Jan 27, 2000 at 04:20:54PM -0800, Mike Smith wrote: > > Actually, the problem here is that our dhclient doesn't pick the hostname > up the first time around. If it's set in an existing lease that is just > confirmed, it works, but if you're starting without a lease, you won't > get a h

Re: Problems installing FreeBSD 4.0 20000125-CURRENT

> That's not correct; your DHCP configuration should reflect the hostname. > > Sysinstall doesn't fill in the hostname field because the crunched binary > is missing the hostname(1) command. If we were to add that, it's just > possible that we'd get hostnames working too. Actually, that's not

Re: Problems installing FreeBSD 4.0 20000125-CURRENT

> On Thu, Jan 27, 2000 at 04:20:54PM -0800, Mike Smith wrote: > > > > Actually, the problem here is that our dhclient doesn't pick the hostname > > up the first time around. If it's set in an existing lease that is just > > confirmed, it works, but if you're starting without a lease, you won't

Re: Problems installing FreeBSD 4.0 20000125-CURRENT

> > That's not correct; your DHCP configuration should reflect the hostname. > > > > Sysinstall doesn't fill in the hostname field because the crunched binary > > is missing the hostname(1) command. If we were to add that, it's just > > possible that we'd get hostnames working too. > > Actual

Re: ColdFusion 4.5 RC3

On Thu, 27 Jan 2000, Brian Hechinger wrote: > yes. sorry about the confusion, i forgot to mention that. > Allaire off-record said that they aren't happy with Linux > and are seeking an alternative. i seem to be pushing > them towards FreeBSD. but, keep in mind, this will be a > huge shift in d

Re: Problems installing FreeBSD 4.0 20000125-CURRENT

On Thu, 27 Jan 2000, Bill Fenner wrote: > > >Right. I've seen this when I hit Enter rapidly twice at the first > >loader prompt. Doesn't ever happen if I wait for the second > >prompt. > > That's my impression too -- I've seen it on my laptop when I do > that (sometimes), and I may have hit e

Re: .bash_history and permissions

On Thu, Jan 27, 2000 at 05:24:16PM -0600, Dan Nelson wrote: > Delete permission comes from the directory, not the file. No amount of > chmod'ing the file will affect it. Hmm, so If I took out write permission for the directory, the user wouldn't be able to delete his .bash_history, correct? (or

Re: Comments on this patch?

On Fri, 28 Jan 2000, Peter Jeremy wrote: > On 2000-Jan-28 10:02:06 +1100, Warner Losh <[EMAIL PROTECTED]> wrote: > >In message <[EMAIL PROTECTED]> "David O'Brien" writes: > >: > BTW, I'm getting numbers that are 2x bigger than before :-(.I had > >: > makebuildworld down to around 1:20 at one

Re: Problems installing FreeBSD 4.0 20000125-CURRENT

< said: > That's not correct; your DHCP configuration should reflect the hostname. No, it shouldn't. As I keep on trying to explain, the DHCP addresses are: 1) Temporary. 2) Meaningless. 3) Temporary. 4) Temporary. 5) Temporary. -GAWollman -- Garrett A

Re: -current is still broken as of 2000/01/27

On Thu, Jan 27, 2000 at 06:09:17PM -0800, Jordan K. Hubbard wrote: > ===> libexec/getNAME > cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -c /usr/src/libexec/getNAME/ge > tNAME.c > cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -o getNAME getNAME.o > gzip -cn /usr/src/libexec/getNAME/getNA

Re: Problems installing FreeBSD 4.0 20000125-CURRENT

> < said: > > > That's not correct; your DHCP configuration should reflect the hostname. > > No, it shouldn't. As I keep on trying to explain, the DHCP addresses > are: > > 1) Temporary. > 2) Meaningless. > 3) Temporary. > 4) Temporary. > 5) Temporary. Since the

Re: Problems installing FreeBSD 4.0 20000125-CURRENT

On Thu, Jan 27, 2000 at 09:26:44PM -0500, Garrett Wollman wrote: > < said: > > > That's not correct; your DHCP configuration should reflect the hostname. > > No, it shouldn't. As I keep on trying to explain, the DHCP addresses > are: ^^ usually > 1) Temporary. > 2) Meaningl

Re: Comments on this patch?

On Thu, 27 Jan 2000, Warner Losh wrote: > I've been running this for a while. I reversed the normal order to > make it easier to do the math w/o having to shift columns and flip > things over. I plan to put timestamps on most of the "<<<" lines and remove all the ornation around the "<<" lines.

Re: Comments on this patch?

In message <[EMAIL PROTECTED]> Bruce Evans writes: : I plan to put timestamps on most of the "<<<" lines and remove all : the ornation around the "<<" lines. Almost every large target could : begin by (optionally of course) printing the time. Sounds more general than mine... Warner To Unsubs

Re: [PATCH] Please test the PS/2 mouse driver patch

>Do you have specs on the Trackpoint PS/2 mice found on Thinkpads? No. >The version on my 770X has a double click by "pushing hard on the >trackpoint" feature. It also has the ability to do the scroll >thing if you hold the middle mouse button and move the trackpoint. You mean, there feature

Re: Problems installing FreeBSD 4.0 20000125-CURRENT

On Thu, Jan 27, 2000 at 06:22:55PM -0800, Mike Smith wrote: > Correct behaviour would be not to set the hostname unless: > a) it is not already set > or > b) it was previously set by the DHCP client > > You could probably ignore b) and satisfy most people. At the moment, the > hostname is _ne

The Commit That Broke PCM

PCM has been broken for me since December 1999. I would very much appreciate if someone could help me fix it before the code freeze (cg, dfr and tanimura CC'd). I have an unknown MSS-compatible non-PnP ISA sound card, which identifies itself as a CS4231. Unknown, because it's inside a laptop.

Re: .bash_history and permissions

In the last episode (Jan 27), Emre said: > On Thu, Jan 27, 2000 at 05:24:16PM -0600, Dan Nelson wrote: > > Delete permission comes from the directory, not the file. No amount of > > chmod'ing the file will affect it. > > Hmm, so If I took out write permission for the directory, the user > wouldn

Re: pcm - stutters

Nick Hibma writes: > > The output of my ESS 1869 stutters whenever there is no new data fed to > it. For example pressing Ctrl-Z, or heavy disk usage (normally making > mpg123 jump). The stuttering is repetition of one short fragment of > about a quarter of a second, indefinitely > > An

Re: Speaking of ATAisms...

On Wed, 26 Jan 2000, Soren Schmidt wrote: > > zippy:~#dd if=/dev/afd0c bs=1k count=16 of=afd0c.output > > dd: /dev/afd0c: Input/output error > > zippy:~#Jan 26 00:38:32 zippy /kernel: afd0: error reading primary > > partition table reading fsbn 0 > > > > Hmm. I know this disk works with Windows

Re: Problems installing FreeBSD 4.0 20000125-CURRENT

On Thu, Jan 27, 2000 at 06:53:51PM -0800, Mike Smith wrote: > Since the hostname is simply a plain-text token for the IP address, it > has to remain bound to the IP address (whether that binding is fixed or > dynamic is outside the scope of this discussion). Having a hostname that > doesn't ma

Re: Problems installing FreeBSD 4.0 20000125-CURRENT

In message Alex Zepeda writes: : in a row quickly occasionally screw up. Also sometimes I'll be able to : catch the screwed up booter when I notice that it doesn't respond to me : hitting enter (In 9 seconds... hit enter.. 8 seconds.. hit enter..

Re: Problems installing FreeBSD 4.0 20000125-CURRENT

In message <[EMAIL PROTECTED]> Garrett Wollman writes: : < said: : : > That's not correct; your DHCP configuration should reflect the hostname. : : No, it shouldn't. As I keep on trying to explain, the DHCP addresses : are: : : 1) Temporary. : 2) Meaningless. : 3) Temporary.

That fix for the ^T crash

Hi, Brian! I'm concerned that your fix won't make it before the code freeze. Is there a problem with it? I admit I haven't actually tested it. :-( My excuse is that I assumed you had. Or should I just do a quick test on your patch (+ bde fixes) and commit it myself? Stephen. To Unsubscribe:

Re: ColdFusion 4.5 RC3

Ummm just tried to install it, and i get ./start Error: performing semget() on ColdFusion Registry semaphore:File exists Abort trap - core dumped FreeBSD angelsguardian.netquick.net 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Sat Jan 22 23:22:53 EST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/GUARDIAN

Re: Problems installing FreeBSD 4.0 20000125-CURRENT

> That reminds me. sysinstall *SHOULD*NOT* hard code the IP address > that it gets from dhcp into rc.conf. I've seen this in 3.2, but > haven't tried since then to reproduce this. It doesn't do that anymore; it was a nasty hack to work around not having been able to sell BPF in the kernel in t

Re: help! need kernel!

On Thu, 27 Jan 2000, Alexandr Listopad wrote: > there no tools/ dir in /usr/src - why? Because you didn't download it? > doc-all > src-base > src-bin > src-contrib > src-etc > src-gnu > src-include > src-lib > src-libexec > src-release > src-sbin > src-share > src-sys src-tools > src-usrbin > s

Re: Problems installing FreeBSD 4.0 20000125-CURRENT

In message <[EMAIL PROTECTED]> Mike Smith writes: : > That reminds me. sysinstall *SHOULD*NOT* hard code the IP address : > that it gets from dhcp into rc.conf. I've seen this in 3.2, but : > haven't tried since then to reproduce this. : : It doesn't do that anymore; it was a nasty hack to work

Re: newpcm (or newpnp?)

Cameron Grant wrote: > would everyone who currently has an issue outstanding with newpcm please > report it to me in the next few days directly, please, so i can get an idea > of what needs work before release. i need as much detail as possible. Well, since you asked... Since rebuilding -CURRE

Re: Problems installing FreeBSD 4.0 20000125-CURRENT

> < said: > > >> 3. On the first reboot after installing, the keyboard was in a funny > >> state. > > > Urk, can't reproduce it. I need a reproducible sequence of operations > > before we'll have any hope of tackling this one. > > >> Control-alt-del definitely didn't work, so I had to power of

Re: Problems installing FreeBSD 4.0 20000125-CURRENT

On 28-Jan-00 Warner Losh wrote: > In message <[EMAIL PROTECTED]> Garrett Wollman writes: >: < said: >: >: > That's not correct; your DHCP configuration should reflect the hostname. >: >: No, it shouldn't. As I keep on trying to explain, the DHCP addresses >: are: >: >: 1) Temporary. >:

Re: Problems installing FreeBSD 4.0 20000125-CURRENT

On 28-Jan-00 Mike Smith wrote: >> On Thu, Jan 27, 2000 at 04:20:54PM -0800, Mike Smith wrote: >> > >> > Actually, the problem here is that our dhclient doesn't pick the hostname >> > up the first time around. If it's set in an existing lease that is just >> > confirmed, it works, but if you're

Re: That fix for the ^T crash

On Fri, 28 Jan 2000, Stephen McKay wrote: > Hi, Brian! > > I'm concerned that your fix won't make it before the code freeze. Is > there a problem with it? I admit I haven't actually tested it. :-( > My excuse is that I assumed you had. > > Or should I just do a quick test on your patch (+ bde

Re: (FWD) Re: cvs commit: src/etc/periodic/daily 200.backup-pass

> > On 27-Jan-00 David O'Brien wrote: > > I would appreciate it if those that want things changed would please try > > Sheldon's `sed' expression below and report back how it worked for you. > > That will expose passwords of users whose entries are commented out, My awk script does not have tha

Re: Comments on this patch?

> In message <[EMAIL PROTECTED]> "David O'Brien" writes: > : > BTW, I'm getting numbers that are 2x bigger than before :-(.I had > : > makebuildworld down to around 1:20 at one point, but now it is 2:40. > : > : Which compilers for both times? > > What ever was on -current as of 2.5 years ag

Re: newpcm (or newpnp?)

Chris Giordano wrote: > Previous to newpnp, I forced the modem (sio2) to irq 15 and the soundcard to > irq 5 via pnp commands in my /boot/kernel.conf. I did this because I had > found by experimentation that this was the only combination of the supposedly > available PnP configurations wh

Re: MD5 Sigs on 3.4-20000124-STABLE

On Wed, 26 Jan 2000, Jorge Aldana wrote: > I checked the signatures on the files I downloaded from > current.freebsd.org/pub/FreeBSD/snapshots/i386/3.4-2124-STABLE/ > > and the following fail the MD5 check: > > < = from CHECKSUM.MD5 listing > > = downloaded file. These all check out for me

Re: MD5 Sigs on 3.4-20000124-STABLE

Yes, the ftp app (IglooFTP Alpha v0.6.1) I was using consistently corrupted/truncated the same files which made it difficult to pin point, basic ftp took care of it. Sorry for the worry. Jorge On Thu, 27 Jan 2000, Kris Kennaway wrote: > On Wed, 26 Jan 2000, Jorge Aldana wrote: > > > I checked

<    1   2