Re: Cross builds and upgrade path from 4.x are broken in usr.bin/file

2001-08-14 Thread Ruslan Ermilov
On Mon, Aug 13, 2001 at 01:30:15PM -0700, David O'Brien wrote: On Fri, Aug 10, 2001 at 08:23:00PM +0300, Ruslan Ermilov wrote: Your solution does not work. You're creating binary files in HOST format during the build phase and expecting things such as alignment and endianness to be

Re: bash in /usr/local/bin?

2001-08-14 Thread Johann Visagie
Terry Lambert on 2001-08-11 (Sat) at 12:47:01 -0700: Garance A Drosihn wrote: As to Jason's situation, I also like to use bash as my shell even when I am root. However, I do not want to muck around with the port for 'bash', or do anything else to move where bash is or how it's

Re: bash in /usr/local/bin?

2001-08-14 Thread David O'Brien
On Tue, Aug 14, 2001 at 01:23:40PM +0200, Johann Visagie wrote: if ( $tty != ) then (There may be a more elegant way to check for shell interactivity in csh, and if there is I'd like to know about it, please. :-) I've used if ($?USER == 0 || $?prompt == 0) in the past. To Unsubscribe:

Re: bash in /usr/local/bin?

2001-08-14 Thread Garance A Drosihn
At 1:23 PM +0200 8/14/01, Johann Visagie wrote: You may also want to restrict it so that only interactive login sessions cause bash to be invoked. To summarise: if ( $tty != ) then if ( -x /usr/local/bin/bash ) then setenv SHELL /usr/local/bin/bash exec

Re: bash in /usr/local/bin?

2001-08-14 Thread Doug Ambrisko
David O'Brien writes: | On Tue, Aug 14, 2001 at 01:23:40PM +0200, Johann Visagie wrote: |if ( $tty != ) then | | (There may be a more elegant way to check for shell interactivity in csh, and | if there is I'd like to know about it, please. :-) | | I've used if ($?USER == 0 || $?prompt

Re: Cross builds and upgrade path from 4.x are broken in usr.bin/file

2001-08-14 Thread David O'Brien
On Tue, Aug 14, 2001 at 09:54:04AM +0300, Ruslan Ermilov wrote: They produce the same output, but in the general case they do not need to. What I hear? Hell, then my solution (or something similar) should be committed, as it at least unbreaks the 4.x - 5.0 upgrade path, which I am

Re: FreeBSD's aggressive keyboard probe/attach

2001-08-14 Thread Chris Dillon
On Mon, 13 Aug 2001, Terry Lambert wrote: Chris Dillon wrote: Occasionally I'll have mouse sync problems when I switch between FreeBSD and NT when the NT box has had difference mice (wheel vs. non-wheel MS mice, apparently) used on it via the dual-user KVM switch. NT seems to handle

Re: Cross builds and upgrade path from 4.x are broken in usr.bin/file

2001-08-14 Thread Ruslan Ermilov
On Tue, Aug 14, 2001 at 08:55:56AM -0700, David O'Brien wrote: On Tue, Aug 14, 2001 at 09:54:04AM +0300, Ruslan Ermilov wrote: They produce the same output, but in the general case they do not need to. What I hear? Hell, then my solution (or something similar) should be committed,

Re: driver writing newbie

2001-08-14 Thread Alexander Langer
Thus spake Kenneth Wayne Culver ([EMAIL PROTECTED]): SYS_RES_MEMORY instead of SYS_RES_IOPORT (all these combinations are for use in bus_alloc_resource). The thing is everything I've tried fails to work, so I can't attach my driver because it won't map the resources. Can anyone suggest other

Re: Last Words...(documentation)

2001-08-14 Thread Terry Lambert
Joe Kelsey wrote: However, I have one last comment to make. TWO people have written to me and said that the reason THEY write documentation in their day jobs is that they get PAID for it. So, excuse me! I guess real programmers only write documentation when they are PAID! Obviously,

any -current vinum problems?

2001-08-14 Thread Michael Lucas
Before I start generating crash dumps etc., are there any gotchas with Vinum -current? I'm using devfs on a SMP system, upgraded 3 days ago. I get a panic whenever I stripe something. Thanks, Michael -- Michael Lucas [EMAIL PROTECTED] http://www.blackhelicopters.org/~mwlucas/ Big Scary

devfs and Vinum (was: any -current vinum problems?)

2001-08-14 Thread Greg Lehey
On Tuesday, 14 August 2001 at 19:26:09 -0400, Michael Lucas wrote: Before I start generating crash dumps etc., are there any gotchas with Vinum -current? I'm using devfs on a SMP system, upgraded 3 days ago. I get a panic whenever I stripe something. Ah, now you say devfs. There was a

Re: devfs and Vinum (was: any -current vinum problems?)

2001-08-14 Thread Andrew Kenneth Milton
+---[ Greg Lehey ]-- | [snip] | whether it's been fixed. Basically, devfs as supplied in CURRENT had | a 16 character limit on device names, and it didn't understand | subdirectories: it treated the / as a part of the device name. The subdir part bit me about a week

Re: Cross builds and upgrade path from 4.x are broken in usr.bin/file

2001-08-14 Thread David O'Brien
On Tue, Aug 14, 2001 at 08:30:45PM +0300, Ruslan Ermilov wrote: Just to clarify. Nothing should be built in ${.OBJDIR} at install time, as it may be read-only. Correct. The build in ${DESTDIR} is allowed, we, for example, execute makewhatis(1) at the end of `installworld'. But this

Re: Cross builds and upgrade path from 4.x are broken in usr.bin/file

2001-08-14 Thread Bruce Evans
On Tue, 14 Aug 2001, Ruslan Ermilov wrote: On Tue, Aug 14, 2001 at 08:55:56AM -0700, David O'Brien wrote: From a correctness stand point, building the .mgc files at install time is the correct thing to do... or maybe we should do both -- doing the [re]creation of the .mgc files at install

Re: Cross builds and upgrade path from 4.x are broken in usr.bin/file

2001-08-14 Thread Bruce Evans
On Tue, 14 Aug 2001, David O'Brien wrote: On Tue, Aug 14, 2001 at 08:30:45PM +0300, Ruslan Ermilov wrote: The build in ${DESTDIR} is allowed, we, for example, execute makewhatis(1) at the end of `installworld'. But this build is implicit, i.e., it's not done by make dependencies. What

Re: devfs and Vinum (was: any -current vinum problems?)

2001-08-14 Thread Poul-Henning Kamp
In message [EMAIL PROTECTED], Andrew Kenneth Milton writes: +---[ Greg Lehey ]-- | [snip] | whether it's been fixed. Basically, devfs as supplied in CURRENT had | a 16 character limit on device names, and it didn't understand | subdirectories: it treated the / as a

Re: devfs and Vinum (was: any -current vinum problems?)

2001-08-14 Thread Greg Lehey
On Wednesday, 15 August 2001 at 7:16:02 +0200, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Andrew Kenneth Milton writes: +---[ Greg Lehey ]-- [snip] whether it's been fixed. Basically, devfs as supplied in CURRENT had a 16 character limit on device

Re: devfs and Vinum (was: any -current vinum problems?)

2001-08-14 Thread Poul-Henning Kamp
In message [EMAIL PROTECTED], Greg Lehey writes: I'm working on the 16char limit problem as well, but I want to avoid allocating memory in incovenient circumstances if at all possible. The problem is that I kept having problems with the devfs/vinum combination even after increasing the size