Re: GRE Support in 4.X ???

2000-03-03 Thread sthaug

 I believe you can also configure policy based routing on the Cisco to ship
 the traffic to your caching server - without GRE encapsulation - and
 achieve the same results.

You can achieve *almost* the same results. What the policy based routing
doesn't give you is detection of a dead cache server. I believe WCCP has
some support for this (keepalives/polling).

Steinar Haug, Nethelp consulting, [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



C shell scripts (was: Re: which(1), rewritten in C?)

2000-03-03 Thread Patrick M. Hausen

Hi all!

 On Thu, Mar 02, 2000 at 08:47:19PM -0500, Dan Papasian wrote:
  While this may sound crazy, I was tired of 'which' taking a long
  time to complete on my 486 dx4/100 when it was under extereme
  pressure, so I rewrote it in C :)
  
  I don't think that it is worthwhile replacing this perl script
  with one written in C, but if anyone is interested...
 
 Why in the world isn't ``which'' written as a csh shell script??

Most probably because C shell scripts should be avoided at any
cost.

See: http://www.faqs.org/faqs/unix-faq/shell/csh-whynot/

Regards,
Patrick
-- 
WEB Internet Services Systemhaus GmbH   Scheffelstr. 17a76135 Karlsruhe
 phone +49 721 9109 0   fax +49 721 9109 100   http://www.punkt.de/
   Patrick M. Hausen   Technical Director   email [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



tunefs -p doesn't work for read-write mounts

2000-03-03 Thread Sheldon Hearn


Hi folks,

Shouldn't I be able to show the current tuneables for a given filesystem?

# tunefs -p /usr
tunefs: cannot work on read-write mounted file system

This is on a recent CURRENT.

Ciao,
Sheldon.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



4.0-CURRENT hangs in ex_isa_identify() (was: current hangs during boot if ET/5025-16 card is installed)

2000-03-03 Thread Don Lewis

On Mar 2,  4:09am, Don Lewis wrote:
} Subject: current hangs during boot if ET/5025-16 card is installed
} 
} I happened to try to install 4.0-CURRENT on a box that has an
} Emerging Technologies ET/5025-16 ISA card installed and found that
} the kernel wedges during boot.  It hangs hard and won't respond to
} anything except the reset switch.  The motherboard is an Asus P3B-F
} and I believe I have the BIOS propery configured with the correct
} settings to match the IRQ and memory addresses used by the ET card.
} 
} I also discovered that older versions of -CURRENT will boot correctly
} on this box.  I did a binary search on the -CURRENT snapshots and found
} that the floppies from the January 12th and earlier snapshots boot,
} while the floppies from the January 14th and later snapshots hang.

By adding a whole bunch of printf statements to the code, I was able
to track this problem to ex_isa_identify().  The ET card is jumpered
to I/O address 0x240, and it appears to consume 32 bytes starting at
this address.  When the ioport loop in ex_isa_identify() gets to 0x250,
look_for_card() appears to wedge.  I don't see how that can happen
unless the CPU gets stuck in inb().  I haven't looked at ISA hardware
in ages, can an ISA I/O read really hang forever?

What really sucks is that there is no way to disable the ex driver
at boot time, so the standard install floppies can no longer be used
to boot a box that contains one of these ET cards.

Should the ex driver be doing all this stuff at identify time, or was
the older method of doing this at probe time more correct?


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Kernel hangs booting fresh -current

2000-03-03 Thread Nik Clayton

How do,

I just tried to go from -stable (built on Feb 24th) to -current, fresh
yesterday (Thursday).

"make buildworld" completed cleanly, and following /usr/src/UPDATING I
made and installed a fresh kernel, and updated /dev (by running
"MAKEDEV da0s1a" and "MAKEDEV da1s1a" with a -current mknod).

Then I rebooted (without doing an "installworld", UPDATING says you do
this *after* the reboot).

The new kernel boots, but fails to mount the disks.  Thinking this was 
just a mismatch between the kernel and the mount binary, I dug out my
fixit floppy, got back in to the system, installed the new mount binaries
(including the mount_* ones), and tried to reboot.  This time, the system
froze after the last kernel message was printed, but before the "swapon"
message appears.  This was a complete lock, the LED keys didn't work, 
neither did CTRL-ALT-DEL.

Thinking there was something odd in my kernel config file, I recovered the
system again, got back in, and built a -current GENERIC kernel, figuring
that it should definitely work.  I tried rebooting with this, and got an
error message from the npx probe and an immediate reboot.  That happened
so quickly I couldn't get a good look at it, but the word "nexus" was
in there somewhere.  I stress this was with a stock GENERIC -current
kernel (but built on a 3.4 system).

Have I just hit a bad patch?  I've been following the -current list for 
years, and watch for problems religiously -- I figured with the OpenSSL
stuff out of the way, this was as good a time as any.

On a related note, why does UPDATING say to build and install the kernel,
and then reboot, before doing the "installworld"?  That contradicts the
advice in the Handbook (which I wrote), and I would've thought it's wrong
precisely because it allows for things like kernel/mount mismatches to
occur.

I'd be very surprised if this is hardware failure.  This system has been
rock solid on all versions of 3.x, and gets stressed quite highly most
days.

I realise I haven't been able to provide a great deal of information about
this, but I hope it rings bells with someone.

N
-- 
If you want to imagine the future, imagine a tennis shoe stamping
on a penguin's face forever.
--- with apologies to George Orwell


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Crash in currtprio, after dumping no operating system..

2000-03-03 Thread Vallo Kallaste

On Fri, Mar 03, 2000 at 03:23:17PM +1100, Bruce Evans [EMAIL PROTECTED] wrote:

  8 partitions:
  #size   offsetfstype   [fsize bsize bps/cpg]
a:   131072   5242884.2BSD 1024  819216   # (Cyl.   32*- 40*)
b:   5242880  swap# (Cyl.0 - 32*)
c:  88999470unused0 0 # (Cyl.0 - 553*)
e:  8244587   655360 vinum# (Cyl.   40*- 553*)
 
 The dump fills up precisely the entire 'b' partition.  Since the
 partition begins at offset 0, the dump overwrites the label at sector
 offset 1 and any bootblocks at sector offsets 0-15.  This misconfiguration
 is handled for swapping but not for dumping.
 
 This shouldn't lose any data.  Just restore the label from a backup and
 write new bootblocks.

Thanks for clarifying, but now I have next question. Why sysinstall
allows such misconfiguration? As I understand now the right way is
start the disk with root partition not swap. The disklabel shown here
was created with 4.0-2228-CURRENT sysinstall. It seems now I'm wrong
but I always thought the best place for swap is the beginning of disk.
Can you please confirm that the common practise is disklabel with root
partition in the beginning of disk?

Thanks
-- 

Vallo Kallaste
[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: tunefs -p doesn't work for read-write mounts

2000-03-03 Thread David Malone

On Fri, Mar 03, 2000 at 11:23:33AM +0200, Sheldon Hearn wrote:

 Shouldn't I be able to show the current tuneables for a given filesystem?
 
 # tunefs -p /usr
 tunefs: cannot work on read-write mounted file system

Tunefs seems to have had trouble with being given filesystem names
for a bit. Giving the device name works in 3.4, but not in 4.0.

David.

4.0-CURRENT:

10:04:gonzo 3# df /usr
Filesystem   1024-blocks UsedAvail Capacity  Mounted on
/dev/ad1s1f   858367   783550 614899%/usr
10:04:gonzo 4# tunefs -p /usr
tunefs: cannot work on read-write mounted file system
10:04:gonzo 5# tunefs -p /dev/ad1s1f
tunefs: cannot open /dev/ad1s1f: Device busy
10:04:gonzo 6# tunefs -p /dev/rad1s1f
tunefs: cannot open /dev/rad1s1f: Device busy


3.4-STABLE:

10:05:walton 1# df /usr
Filesystem   1024-blocks UsedAvail Capacity  Mounted on
/dev/da0s1f   762223   6732362801096%/usr
10:05:walton 2# tunefs -p /usr
tunefs: cannot work on read-write mounted file system
10:05:walton 3# tunefs -p /dev/rda0s1f
tunefs: soft updates:  (-n)disabled
tunefs: maximum contiguous block count: (-a)   15
tunefs: rotational delay between contiguous blocks: (-d)   0 ms
tunefs: maximum blocks per file in a cylinder group: (-e)  2048
tunefs: minimum percentage of free space: (-m) 8%
tunefs: optimization preference: (-o)  time




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Patch for usr.sbin/ntp/... (adds pcfclock)

2000-03-03 Thread Sheldon Hearn



On Sun, 27 Feb 2000 17:21:21 +0100, Alexander Leidinger wrote:

 attached is a patch for usr.sbin/ntp/config.h and
 usr.sbin/ntp/ntpd/Makefile. It adds reflock_pcf to the compiled in
 drivers (current has support in the kernel for it).

I think we should hold off on this until Sascha has fixed pcfclock for
the Alpha.

Ciao,
Sheldon.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: tunefs -p doesn't work for read-write mounts

2000-03-03 Thread Peter Edwards

I just send-pr'ed a patch for this: misc/17143

David Malone wrote:
 
 On Fri, Mar 03, 2000 at 11:23:33AM +0200, Sheldon Hearn wrote:
 
  Shouldn't I be able to show the current tuneables for a given filesystem?
 
  # tunefs -p /usr
  tunefs: cannot work on read-write mounted file system
 
 Tunefs seems to have had trouble with being given filesystem names
 for a bit. Giving the device name works in 3.4, but not in 4.0.
 
 David.
 
 4.0-CURRENT:
 
 10:04:gonzo 3# df /usr
 Filesystem   1024-blocks UsedAvail Capacity  Mounted on
 /dev/ad1s1f   858367   783550 614899%/usr
 10:04:gonzo 4# tunefs -p /usr
 tunefs: cannot work on read-write mounted file system
 10:04:gonzo 5# tunefs -p /dev/ad1s1f
 tunefs: cannot open /dev/ad1s1f: Device busy
 10:04:gonzo 6# tunefs -p /dev/rad1s1f
 tunefs: cannot open /dev/rad1s1f: Device busy
 
 3.4-STABLE:
 
 10:05:walton 1# df /usr
 Filesystem   1024-blocks UsedAvail Capacity  Mounted on
 /dev/da0s1f   762223   6732362801096%/usr
 10:05:walton 2# tunefs -p /usr
 tunefs: cannot work on read-write mounted file system
 10:05:walton 3# tunefs -p /dev/rda0s1f
 tunefs: soft updates:  (-n)disabled
 tunefs: maximum contiguous block count: (-a)   15
 tunefs: rotational delay between contiguous blocks: (-d)   0 ms
 tunefs: maximum blocks per file in a cylinder group: (-e)  2048
 tunefs: minimum percentage of free space: (-m) 8%
 tunefs: optimization preference: (-o)  time
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-current" in the body of the message


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: tunefs -p doesn't work for read-write mounts

2000-03-03 Thread Devin Butterfield

Sheldon Hearn wrote:
 
 Hi folks,
 
 Shouldn't I be able to show the current tuneables for a given filesystem?
 
 # tunefs -p /usr
 tunefs: cannot work on read-write mounted file system
 
 This is on a recent CURRENT.

AFAIK, you always need to do this with unmounted file systems. Unless of
course this was fixed in current?


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



BIOS settings (was Instrallation floppies and USB)

2000-03-03 Thread Navan Carson

 Plug and Play OS   [Yes]

 Should be No.


How does this setting effect traditional ISA, PNP ISA, PCI cards.


__
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: tunefs -p doesn't work for read-write mounts

2000-03-03 Thread Jeffrey J. Mountin

At 03:14 AM 3/3/00 -0800, Devin Butterfield wrote:
Sheldon Hearn wrote:
 
 Hi folks,
 
 Shouldn't I be able to show the current tuneables for a given filesystem?
 
 # tunefs -p /usr
 tunefs: cannot work on read-write mounted file system
 
 This is on a recent CURRENT.

AFAIK, you always need to do this with unmounted file systems. Unless of
course this was fixed in current?

Why so to only view the values?


Jeff Mountin - [EMAIL PROTECTED]
Systems/Network Administrator
FreeBSD - the power to serve



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: BIOS settings (was Instrallation floppies and USB)

2000-03-03 Thread Takanori Watanabe

In message [EMAIL PROTECTED], Navan Carson wrote:
 Plug and Play OS   [Yes]

 Should be No.


How does this setting effect traditional ISA, PNP ISA, PCI cards.


This setting tells BIOS not to set any PnP setting,
because OS itself want to  set it arbitary.
And any version FreeBSD ever have been released expects BIOS to
set PnP setting.

Takanori Watanabe
a href="http://www.planet.sci.kobe-u.ac.jp/~takawata/key.html"
Public Key/a
Key fingerprint =  2C 51 E2 78 2C E1 C5 2D  0F F1 20 A3 11 3A 62 2A 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: which(1), rewritten in C?

2000-03-03 Thread Dan Papasian

Can you please give an example of where multiple arguments
doesn't work as expected?

It works fine over here.

-Dan Papasian

On Thu, Mar 02, 2000 at 07:59:37PM -0800, Alfred Perlstein wrote:
 --snip--
 
 It doesn't seem to handle multiple arguments.  File a PR and fix
 the issues and I'll look at getting it into post 4.0.
 
 -Alfred


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: BIOS settings (was Instrallation floppies and USB)

2000-03-03 Thread Nikolai Saoukh

On Fri, Mar 03, 2000 at 08:50:07PM +0900, Takanori Watanabe wrote:

 In message [EMAIL PROTECTED], Navan Carson wrote:
  Plug and Play OS   [Yes]
 
  Should be No.
 
 
 How does this setting effect traditional ISA, PNP ISA, PCI cards.
 
 
 This setting tells BIOS not to set any PnP setting,
 because OS itself want to  set it arbitary.
 And any version FreeBSD ever have been released expects BIOS to
 set PnP setting.

Well,
what then pnp stuff (/usr/src/sys/isa/pnp*) do in -current?


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Kernel hangs booting fresh -current

2000-03-03 Thread Jim Bloom

Nik Clayton wrote:
 
 On a related note, why does UPDATING say to build and install the kernel,
 and then reboot, before doing the "installworld"?  That contradicts the
 advice in the Handbook (which I wrote), and I would've thought it's wrong
 precisely because it allows for things like kernel/mount mismatches to
 occur.

Because the signal interface changed several months ago.  If you ran
installworld on an old kernel, the machine would panic part way through
the install.  It is almost impossible to do forward compatibility on
major changes.  I guess you need to update the handbook to reflect this
change.

Jim Bloom
[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Ensoniq Soundscape

2000-03-03 Thread Systems Administrator

afaik, Ensoniq has their own chipset, they dont use ESS's.. I will try
this though :).. up for anything right now .. thanks :).. Any more
suggestions are welcome as well

On Fri, 3 Mar 2000, Donn Miller wrote:

 Systems Administrator wrote:
  
  Has anyone gotten a regular Ensoniq Soundscape (Not AudioPCI) to work with
  pcm0 or anything BUT snd0? :).. I would really love to know as snd0 gives
  me a lot of static feedback in 4.0 for some reason.. I figure pcm wouldn't
 
 Does that have an ESS chip in it, like an ESS 1868?  Did you put
 
 device  sbc0
 device  pcm0
 
 in your kernel config file?  Also, make sure you've done a make world
 recently, and did a mergemaster in single user maode.  Remake your
 audio device with ./MAKEDEV snd0.
 
 - Donn
 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: BIOS settings (was Instrallation floppies and USB)

2000-03-03 Thread takawata

In message [EMAIL PROTECTED], Nikolai Saoukh wrote:
 And any version FreeBSD ever have been released expects BIOS to
 set PnP setting.

Well,
what then pnp stuff (/usr/src/sys/isa/pnp*) do in -current?

They can 
1. reads PnP setting from ISA PnP system.
2. write PnP setting as User specified.

And there is no *automatic* PnP setting capability yet ,as far as I know.

Takanori Watanabe
a href="http://www.planet.kobe-u.ac.jp/~takawata/key.html"
Public Key/a
Key fingerprint =  2C 51 E2 78 2C E1 C5 2D  0F F1 20 A3 11 3A 62 2A 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: which(1), rewritten in C?

2000-03-03 Thread Alfred Perlstein

* Dan Papasian [EMAIL PROTECTED] [000303 04:39] wrote:
 Can you please give an example of where multiple arguments
 doesn't work as expected?
 
 It works fine over here.

~ % which ls ln sh
/bin/ls
/bin/ln
/bin/sh
~ % ./a.out ls ln sh
/bin/sh

-- 
-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: BIOS settings (was Instrallation floppies and USB)

2000-03-03 Thread Nikolai Saoukh

On Fri, Mar 03, 2000 at 11:29:11PM +0900, [EMAIL PROTECTED] 
wrote:

 In message [EMAIL PROTECTED], Nikolai Saoukh wrote:
  And any version FreeBSD ever have been released expects BIOS to
  set PnP setting.
 
 Well,
 what then pnp stuff (/usr/src/sys/isa/pnp*) do in -current?
 
 They can 
 1. reads PnP setting from ISA PnP system.
 2. write PnP setting as User specified.
 
 And there is no *automatic* PnP setting capability yet ,as far as I know.

There is such capability, limited with bugs, but it is.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: BIOS settings (was Instrallation floppies and USB)

2000-03-03 Thread Dan Nelson

In the last episode (Mar 03), Nikolai Saoukh said:
 On Fri, Mar 03, 2000 at 08:50:07PM +0900, Takanori Watanabe wrote:
  In message [EMAIL PROTECTED], Navan Carson wrote:
   Plug and Play OS   [Yes]
  
   Should be No.
  
  How does this setting effect traditional ISA, PNP ISA, PCI cards.
  
  This setting tells BIOS not to set any PnP setting, because OS
  itself want to set it arbitary. And any version FreeBSD ever have
  been released expects BIOS to set PnP setting.
 
 Well, what then pnp stuff (/usr/src/sys/isa/pnp*) do in -current?

It lets the kernel scan for pnp hardware and assign drivers to it based
on PnP ID (see sio.c, the sio_ids[] array for an example).  It does not
do conflict resolution.

-- 
Dan Nelson
[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: C shell scripts (was: Re: which(1), rewritten in C?)

2000-03-03 Thread David O'Brien

On Fri, Mar 03, 2000 at 10:09:17AM +0100, Patrick M. Hausen wrote:
 Most probably because C shell scripts should be avoided at any
 cost.
 
 See: http://www.faqs.org/faqs/unix-faq/shell/csh-whynot/

I do know about this FAQ, however for a very simple script that is just
passing arguments to a built-in function.
 
-- 
-- David([EMAIL PROTECTED])


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: C shell scripts (was: Re: which(1), rewritten in C?)

2000-03-03 Thread Assar Westerlund

"David O'Brien" [EMAIL PROTECTED] writes:
 I do know about this FAQ, however for a very simple script that is just
 passing arguments to a built-in function.

There's a real reason for not writing this in csh.  Because the
built-in function will return results for csh, which might not be the
right ones for other shells.

What result do you get with `which which' for example?

/assar


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: C shell scripts (was: Re: which(1), rewritten in C?)

2000-03-03 Thread Assar Westerlund

Garrett Wollman [EMAIL PROTECTED] writes:
 The error is in using `which' with another shell.  The correct command
 to use with POSIX-ish shells (sh, ksh, bash, etc.) is `type'.

Sure, but there's a /usr/bin/which program.  Do you suggest we should
remove it?  I don't have any problems with that...

/assar


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: which(1), rewritten in C?

2000-03-03 Thread Garance A Drosihn

At 10:36 PM -0500 3/2/00, Laurence Berland wrote:
Which is also a perl script, which sh uses (since it's not a builtin
there).  It does the same thing as the 'which' that's built in to bash
and tcsh and csh

If you do a 'type -a which' or 'help which' in bash, you'll find that
'which' is not a built-in function in bash either.  Sh/bash people
would be more likely to use 'type blah' or 'type -a blah' instead
of 'which blah'.

(at least, it isn't a built-in function on my machine...)

Having used csh for awhile before switching to bash, and also not
thrilled with /usr/bin/which, I have a function for it in my bashrc:

function which {
local which_temp
while [ "$1" ]; do
   which_temp=`type -type $1`
   if [ "$which_temp" = "file" ]; then
  type -path $1
   else
  if [ "$which_temp" ]; then
 type -all $1
  else
 echo no $1 in $PATH
  fi
   fi
   shift
done
}

That's just included for amusement purposes (and I'm not sure it
behaves exactly the way 'which' would in csh).  I do like the idea
of /usr/bin/which being rewritten into C...


---
Garance Alistair Drosehn   =   [EMAIL PROTECTED]
Senior Systems Programmer  or  [EMAIL PROTECTED]
Rensselaer Polytechnic Institute


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: 4.0-CURRENT hangs in ex_isa_identify() (was: current hangs duringboot if ET/5025-16 card is installed)

2000-03-03 Thread Matthew N. Dodd

On Fri, 3 Mar 2000, Don Lewis wrote:
 What really sucks is that there is no way to disable the ex driver
 at boot time, so the standard install floppies can no longer be used
 to boot a box that contains one of these ET cards.
 
 Should the ex driver be doing all this stuff at identify time, or was
 the older method of doing this at probe time more correct?

Thats really the only place for such a routine.  What needs to happen is
for if_ex to a little more selective about which addresses it
probes.  While it is using a non-destructive probe (see
look_for_card()) it should also use the resource manager to check and see
if a port is assigned before it does anything else.

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| [EMAIL PROTECTED] |   2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter | This Space For Rent  | ISO8802.5 4ever |



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: C shell scripts (was: Re: which(1), rewritten in C?)

2000-03-03 Thread Garrett Wollman

On 03 Mar 2000 17:03:05 +0100, Assar Westerlund [EMAIL PROTECTED] said:

 Sure, but there's a /usr/bin/which program.  Do you suggest we should
 remove it?  I don't have any problems with that...

The original `which' was a C shell script.  Its purpose was
specifically to explain how the C shell would locate a particular
command.  That's why the Korn shell introduced `type'.  This
functionality *needs* to be a shell builtin -- the only reason an
external C shell script worked (most of the time) was that csh insists
on reading .cshrc even for non-interactive shells.

-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-current" in the body of the message



Re: BIOS settings (was Instrallation floppies and USB)

2000-03-03 Thread Nick Hibma


  Plug and Play OS   [Yes]
 
  Should be No.
 
 
 How does this setting effect traditional ISA, PNP ISA, PCI cards.

Some might not be initiased. The basic point is that FreeBSD does not do
the device enumeration and therefore any device that has not been
configured by the BIOS or the previous OS (like Windows) is not
accessable.

Sometimes the BIOS wipes the configuration upon reboot and in that case
the settings Windows has left behind are no longer available.

Nick

--
[EMAIL PROTECTED]
[EMAIL PROTECTED]  USB project
http://www.etla.net/~n_hibma/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



RE: make release - usr.bin/ssh error

2000-03-03 Thread John Baldwin


On 02-Mar-00 John W. DeBoskey wrote:
 Hi,
 
I'm running a make release with sources current as of 7pm EST.
 I'm in the process of trying to figure out the following failure.

I'm getting this error as well. :(

At this rate RC#3 isn't going to be going out the door anytime soon.

 === usr.sbin/ktutil
 install -c -s -o root -g wheel -m 555   ktutil /usr/sbin
 install -c -o root -g wheel -m 444 ktutil.8.gz  /usr/share/man/man8
 cd /pub/FreeBSD/usr.bin/ssh; make   MAKE_KERBEROS5=yes cleandir   make   
MAKE_KERBEROS5=yes obj  
 make   MAKE_KERBEROS5=yes depend all install
 cd: can't cd to /pub/FreeBSD/usr.bin/ssh
 *** Error code 2
 
I'm in the process of tracking this down. If anyone has any
 pointers, I'd appreciate the help.
 
If this has already been fixed and I haven't seen the mail/cvs
 commit yet, please let me know that too... :-)
 
 Thanks!
 John

-- 

John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: make release - usr.bin/ssh error

2000-03-03 Thread John Hay

 
 I'm getting this error as well. :(
 
 At this rate RC#3 isn't going to be going out the door anytime soon.
 
  === usr.sbin/ktutil
  install -c -s -o root -g wheel -m 555   ktutil /usr/sbin
  install -c -o root -g wheel -m 444 ktutil.8.gz  /usr/share/man/man8
  cd /pub/FreeBSD/usr.bin/ssh; make   MAKE_KERBEROS5=yes cleandir   make   
MAKE_KERBEROS5=yes obj  
  make   MAKE_KERBEROS5=yes depend all install
  cd: can't cd to /pub/FreeBSD/usr.bin/ssh
  *** Error code 2
  
 I'm in the process of tracking this down. If anyone has any
  pointers, I'd appreciate the help.
  

This set of patches got make release going for me. I sent them to Mark
a little earlier this afternoon, because most of it is in his area.

John
-- 
John Hay -- [EMAIL PROTECTED]


Index: kerberos5/Makefile
===
RCS file: /home/ncvs/src/kerberos5/Makefile,v
retrieving revision 1.7
diff -u -r1.7 Makefile
--- kerberos5/Makefile  2000/03/02 11:16:25 1.7
+++ kerberos5/Makefile  2000/03/03 04:16:17
@@ -2,7 +2,7 @@
 
 SUBDIR=lib libexec usr.bin usr.sbin
 
-SDIR= ${.CURDIR}/..
+SDIR= ${.CURDIR}/../secure
 
 bootstrap: cleandir obj depend all install kprog
 
Index: secure/usr.bin/ssh/Makefile
===
RCS file: /home/ncvs/src/secure/usr.bin/ssh/Makefile,v
retrieving revision 1.3
diff -u -r1.3 Makefile
--- secure/usr.bin/ssh/Makefile 2000/02/28 19:27:31 1.3
+++ secure/usr.bin/ssh/Makefile 2000/03/03 07:52:28
@@ -29,8 +29,8 @@
((${MAKE_KERBEROS5} == "yes") || (${MAKE_KERBEROS5} == "YES"))
 DISTRIBUTION=krb5
 CFLAGS+= -DKRB5
-LDADD+= -lkrb5 -lkafs -lasn1 -lcom_err -lmd 
-L${.OBJDIR}/../../../kerberos5/lib/libroken -lroken
-DPADD+= ${LIBKRB5} ${LIBCOM_ERR} ${LIBKAFS} ${LIBASN1} ${LIBMD}
+LDADD+= -lkrb5 -lasn1 -lcom_err -lmd 
+-L${.OBJDIR}/../../../kerberos5/lib/libroken -lroken -lcrypt
+DPADD+= ${LIBKRB5} ${LIBCOM_ERR} ${LIBASN1} ${LIBMD} ${LIBCRYPT}
 .endif # MAKE_KERBEROS5
 
 .include bsd.prog.mk
Index: secure/usr.sbin/sshd/Makefile
===
RCS file: /home/ncvs/src/secure/usr.sbin/sshd/Makefile,v
retrieving revision 1.3
diff -u -r1.3 Makefile
--- secure/usr.sbin/sshd/Makefile   2000/02/28 19:27:31 1.3
+++ secure/usr.sbin/sshd/Makefile   2000/03/03 07:55:41
@@ -31,8 +31,8 @@
 DISTRIBUTION=krb5
 CFLAGS+= -DKRB5
 SRCS+= auth-krb5.c
-LDADD+= -lkrb5 -lkafs -lasn1 -lcom_err -lmd 
-L${.OBJDIR}/../../../kerberos5/lib/libroken -lroken
-DPADD+= ${LIBKRB5} ${LIBCOM_ERR} ${LIBKAFS} ${LIBASN1} ${LIBMD}
+LDADD+= -lkrb5 -lasn1 -lcom_err -lmd 
+-L${.OBJDIR}/../../../kerberos5/lib/libroken -lroken
+DPADD+= ${LIBKRB5} ${LIBCOM_ERR} ${LIBASN1} ${LIBMD}
 .endif # MAKE_KERBEROS5
 
 .include bsd.prog.mk
Index: crypto/openssh/auth-krb5.c
===
RCS file: /home/ncvs/src/crypto/openssh/auth-krb5.c,v
retrieving revision 1.1
diff -u -r1.1 auth-krb5.c
--- crypto/openssh/auth-krb5.c  2000/02/28 19:03:51 1.1
+++ crypto/openssh/auth-krb5.c  2000/03/03 07:54:18
@@ -240,7 +240,7 @@
}
   
if (!cleanup_registered) {
-  fatal_add_cleanup(krb4_cleanup_proc, NULL);
+  fatal_add_cleanup(krb5_cleanup_proc, NULL);
  cleanup_registered = 1;
}
return 0;
Index: release/Makefile
===
RCS file: /home/ncvs/src/release/Makefile,v
retrieving revision 1.534
diff -u -r1.534 Makefile
--- release/Makefile2000/02/29 11:26:24 1.534
+++ release/Makefile2000/03/03 12:05:47
@@ -430,8 +430,8 @@
if [ -d ${RD}/dists/crypto ] ; then ( cd ${RD}/dists/src  \
if [ -f ssecure.aa ] ; then mv ssecure.* ../crypto ; fi  \
if [ -f scrypto.aa ] ; then mv scrypto.* ../crypto ; fi  \
-   if [ -f skrb4.aa ] ; then mv skrb4.* ../crypto ; fi ; ) ; fi
-   if [ -f skrb5.aa ] ; then mv skrb5.* ../crypto ; fi ; ) ; fi
+   if [ -f skrb4.aa ] ; then mv skrb4.* ../crypto ; fi  \
+   if [ -f skrb5.aa ] ; then mv skrb5.* ../crypto ; fi ; ) fi
@echo "src distribution is finished."
 .endif
touch release.7


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: C shell scripts (was: Re: which(1), rewritten in C?)

2000-03-03 Thread Peter Edwards

Assar Westerlund wrote:

 There's a real reason for not writing this in csh.  Because the
 built-in function will return results for csh, which might not be the
 right ones for other shells.
 
I got bitten by this by HP-UX 10's csh-based "which". My solaris-hosted
NFS home directory had the default Solaris .cshrc that changes $path.
Needless to say, "which" was somewhat misleading :-)
Ugh.
--
Peter.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



ETA on RC3?

2000-03-03 Thread Andrew Gallatin


I'm just wondering -- when is RC3 expected? ?  A lot has happened
since the 2/14 snap..

Thanks,

Drew
--
Andrew Gallatin, Sr Systems Programmer  http://www.cs.duke.edu/~gallatin
Duke University Email: [EMAIL PROTECTED]
Department of Computer Science  Phone: (919) 660-6590







To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Kde2pre: is it FreeBSD or Kde fault?

2000-03-03 Thread Ilmar S. Habibulin

On Thu, 2 Mar 2000, Theo van Klaveren wrote:

  I have the same problem. Try to delete compile flag "-fno-builtin" while
  compiling libkhtml and konqueror.
 You actually get as far as kdebase? My builds quit in kdelibs in
 arts/flow/stereofftscope.cpp with the following message (verbatim):
 
 stereofftscope.cpp:~80: sorry, not implemented. (something about symbol
 to big for symbol table). Recompile all your sources with -fhuge-objects.
So recompile with -fhuge-objects and all will be fine.

 I finished the build with make -k, but I have no arts :( I suspect this to
 be a FreeBSD problem, as the Linux guys don't seem to have this (or it
 would have been fixed in the previous two/three weeks).
 
 I noticed the same problem with libkhtml, b.t.w.
I don't have problems with libkhtml except exception handling. But linux
guys have such a mish-mash (?) like -frtti and -fno-rtti, -fexceptions
and -fno-exceptions. And this works for them. :(



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Kde2pre: is it FreeBSD or Kde fault?

2000-03-03 Thread Ilmar S. Habibulin

On Thu, 2 Mar 2000, Vallo Kallaste wrote:

  I have the same problem. Try to delete compile flag "-fno-builtin" while
  compiling libkhtml and konqueror.
 
 I've recompiled the whole thing without -fno-builtin but no difference
 at all. What's the problem, then? Is it some kind of Linuxism as I
 believe most KDE developers are Linux based or ..?
I was sure, that -fno-builtins helped. Maybe they fixed this error and
i cvsuped errorfree source. I'll try to investigate it, cause i want to
use something differ from netscape.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: tunefs -p doesn't work for read-write mounts

2000-03-03 Thread Luoqi Chen

 Hi folks,
 
 Shouldn't I be able to show the current tuneables for a given filesystem?
 
 # tunefs -p /usr
 tunefs: cannot work on read-write mounted file system
 
 This is on a recent CURRENT.
 
 Ciao,
 Sheldon.
 
You were supposed to use a raw device for a mounted fs, but that no longer
works after the elimination of block device. I have a quick fix for this
problem: open the device read-only to read the superblock and later re-open
it read-write before writing back.

-lq

Index: tunefs.c
===
RCS file: /home/ncvs/src/sbin/tunefs/tunefs.c,v
retrieving revision 1.11
diff -u -r1.11 tunefs.c
--- tunefs.c2000/01/30 05:24:55 1.11
+++ tunefs.c2000/03/03 16:04:04
@@ -75,9 +75,10 @@
 int fi;
 long dev_bsize = 1;
 
-void bwrite(daddr_t, char *, int);
-int bread(daddr_t, char *, int);
-void getsb(struct fs *, char *);
+void bwrite __P((daddr_t, char *, int));
+int bread __P((daddr_t, char *, int));
+void getsb __P((struct fs *, char *));
+void putsb __P((struct fs *, char *, int));
 void usage __P((void));
 void printfs __P((void));
 
@@ -103,9 +104,6 @@
if (fs) {
if (statfs(special, stfs) == 0 
strcmp(special, stfs.f_mntonname) == 0) {
-   if ((stfs.f_flags  MNT_RDONLY) == 0) {
-   errx(1, "cannot work on read-write mounted file 
system");
-   }
active = 1;
}
special = fs-fs_spec;
@@ -251,12 +249,7 @@
}
if (argc != 1)
usage();
-   bwrite((daddr_t)SBOFF / dev_bsize, (char *)sblock, SBSIZE);
-   if (Aflag)
-   for (i = 0; i  sblock.fs_ncg; i++)
-   bwrite(fsbtodb(sblock, cgsblock(sblock, i)),
-   (char *)sblock, SBSIZE);
-   close(fi);
+   putsb(sblock, special, Aflag);
if (active) {
bzero(args, sizeof(args));
if (mount("ufs", fs-fs_file,
@@ -283,7 +276,7 @@
char *file;
 {
 
-   fi = open(file, 2);
+   fi = open(file, 0);
if (fi  0)
err(3, "cannot open %s", file);
if (bread((daddr_t)SBOFF, (char *)fs, SBSIZE))
@@ -291,6 +284,30 @@
if (fs-fs_magic != FS_MAGIC)
err(5, "%s: bad magic number", file);
dev_bsize = fs-fs_fsize / fsbtodb(fs, 1);
+}
+
+void
+putsb(fs, file, all)
+   register struct fs *fs;
+   char *file;
+   int all;
+{
+   int i;
+
+   /*
+* Re-open the device read-write. Use the read-only file
+* descriptor as an interlock to prevent the device from
+* being mounted while we are switching mode.
+*/
+   i = fi; fi = open(file, 2); close(i);
+   if (fi  0)
+   err(3, "cannot open %s", file);
+   bwrite((daddr_t)SBOFF / dev_bsize, (char *)fs, SBSIZE);
+   if (all)
+   for (i = 0; i  fs-fs_ncg; i++)
+   bwrite(fsbtodb(fs, cgsblock(fs, i)),
+   (char *)fs, SBSIZE);
+   close(fi);
 }
 
 void


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



RE: GRE Support in 4.X ???

2000-03-03 Thread Alejandro Ramirez

  I believe you can also configure policy based routing on the Cisco to
ship
  the traffic to your caching server - without GRE encapsulation - and
  achieve the same results.

 You can achieve *almost* the same results. What the policy based routing
 doesn't give you is detection of a dead cache server. I believe WCCP has
 some support for this (keepalives/polling).

Thanks but, also with policy routing the squid will work as a transparent
proxy, and in that way I cant have load balancing betwen several Cache
Engines, like the one that WCCP provides.

Greetings...
Ales





To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: ETA on RC3?

2000-03-03 Thread Wilko Bulte

On Fri, Mar 03, 2000 at 12:24:30PM -0500, Andrew Gallatin wrote:
 
 I'm just wondering -- when is RC3 expected? ?  A lot has happened
 since the 2/14 snap..

I don't think this is going to happen before sometime next week.
Jordan is currently visiting the Netherlands and will subsequently go to the
UK for a couple of days.

W/
-- 
Wilko Bulte Arnhem, The Netherlands   
http://www.tcja.nl  The FreeBSD Project: http://www.freebsd.org


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: ETA on RC3?

2000-03-03 Thread Kris Kennaway

On Fri, 3 Mar 2000, Andrew Gallatin wrote:

 I'm just wondering -- when is RC3 expected? ?  A lot has happened
 since the 2/14 snap..

As soon as Jordan gets the chance, I guess. The Plan was to do it on
Monday night but he ran out of time before leaving for Europe.

Kris


In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe [EMAIL PROTECTED]



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Patch for usr.sbin/ntp/... (adds pcfclock)

2000-03-03 Thread Ollivier Robert

According to Sheldon Hearn:
 I think we should hold off on this until Sascha has fixed pcfclock for
 the Alpha.

Agreed. It is too late for 4.0-RELEASE IMO and I won't have time next
week... (holidays :-)
-- 
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED]
FreeBSD keltia.freenix.fr 4.0-CURRENT #78: Sun Feb 27 15:32:39 CET 2000



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Ensoniq Soundscape

2000-03-03 Thread Ollivier Robert

According to Systems Administrator:
 afaik, Ensoniq has their own chipset, they dont use ESS's.. I will try
 this though :).. up for anything right now .. thanks :).. Any more
 suggestions are welcome as well

Add

options PNPBIOS

as well. Even if you card is not recognised, it will give us the various IDs
to be added in the proper file :)
-- 
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED]
FreeBSD keltia.freenix.fr 4.0-CURRENT #78: Sun Feb 27 15:32:39 CET 2000



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



fdisk -s, post 4.0

2000-03-03 Thread Warner Losh


I'd like to add a fdisk -s command after 4.0.  What -s would do is
produce a much boiled down fdisk output, for two consumers.  First,
for people who don't want to wade through a whole screen of stuff, and
second for scripts.  Here's the current output.  Lemme know what you
think.

BTW, I'm also in the middle of writing a prepdisk script that uses
fdisk and disklabel to properly and easily label a disk for use under
FreeBSD.  I'll post that later and would like to include that in
FreeBSD as well, given how restricted disklabel auto's intended
purpose is.  I may also do a gui, but that will likely take more time
than I have to devote to this.

# fdisk -s da2
/dev/rda2: 555 cyl 255 hd 63 sec
PartStartSize Type Flags
   1:  63 8916012 0xa5 0x80
# fdisk da2
*** Working on device /dev/rda2 ***
parameters extracted from in-core disklabel are:
cylinders=555 heads=255 sectors/track=63 (16065 blks/cyl)

parameters to be used for BIOS calculations are:
cylinders=555 heads=255 sectors/track=63 (16065 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165,(FreeBSD/NetBSD/386BSD)
start 63, size 8916012 (4353 Meg), flag 80 (active)
beg: cyl 0/ sector 1/ head 1;
end: cyl 554/ sector 63/ head 254
The data for partition 2 is:
UNUSED
The data for partition 3 is:
UNUSED
The data for partition 4 is:
UNUSED

Comments?

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: fdisk -s, post 4.0

2000-03-03 Thread Poul-Henning Kamp

In message [EMAIL PROTECTED], Warner Losh writes:

I'd like to add a fdisk -s command after 4.0.  What -s would do is
produce a much boiled down fdisk output, for two consumers.  First,
for people who don't want to wade through a whole screen of stuff, and
second for scripts.  Here's the current output.  Lemme know what you
think.

BTW, I'm also in the middle of writing a prepdisk script that uses
fdisk and disklabel to properly and easily label a disk for use under
FreeBSD.

Please look at the script I wrote for the doc2k device, it is in
src/sys/contrib/dev/fla

--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED]   "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: which(1), rewritten in C?

2000-03-03 Thread Matthew Hunt

On Fri, Mar 03, 2000 at 11:13:23AM -0500, Garance A Drosihn wrote:

 If you do a 'type -a which' or 'help which' in bash, you'll find that
 'which' is not a built-in function in bash either.  Sh/bash people
 would be more likely to use 'type blah' or 'type -a blah' instead
 of 'which blah'.

For what little it's worth, I'm a bash user and always use "which".
Probably because half the time, it's in backquotes:

$ less `which which`

and the "type" builtin is too verbose, saying "which is hashed
(/usr/bin/which)."  (It seems "type -p which" will do what I
want, but it's easier to type "which which", especially since that
is my habit already.)

As I have a slow machine by modern standards, I'm all for a faster
which(1) as well.

-- 
Matthew Hunt [EMAIL PROTECTED] * Stay close to the Vorlon.
http://www.pobox.com/~mph/   *


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: pcm on Thinkpad 600E

2000-03-03 Thread Sean O'Connell

Christopher T. Griffiths stated:
 Hello,
 
 I am trying to get the pcm device to work under current on my Thinkpad
 600e.
 
 Here is my kernel line:
 
 # Sound card support
 device  pcm0at isa? port ? irq 5 drq 1 flags 0x10
 
 
 I also made the device in /dev with:
 ./MAKEDEV snd0
 
 Here is the kernel output that I am getting:
 
 csa0: Crystal Semiconductor CS4610/4611 Audio accelerator mem
 0x5000-0x500
 f,0x5010-0x50100fff irq 11 at device 6.0 on pci0
 pcm0: CS461x PCM Audio on csa0
 pcm0: ac97 codec reports dac not ready
 
 
 Any Ideas??

Chris-

This a PCI card all you should need is:

device pcm0
device csa0

and you may want/need to add 

options PNPBIOS

I have installed -current on a Thinkpad 570.  This seems to
work fine for audio cd's (the mixer portion); however, I get
nothing but silence from the /dev/audio or /dev/dsp (things
like waveplay and realaudio are noops for me :( )

S
---
Sean O'ConnellEmail: [EMAIL PROTECTED]
Institute of Statistics and Decision Sciences Phone: (919) 684-5419
Duke University   Fax:   (919) 684-8594


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: fdisk -s, post 4.0

2000-03-03 Thread Warner Losh

In message [EMAIL PROTECTED] Poul-Henning Kamp writes:
: In message [EMAIL PROTECTED], Warner Losh writes:
: 
: I'd like to add a fdisk -s command after 4.0.  What -s would do is
: produce a much boiled down fdisk output, for two consumers.  First,
: for people who don't want to wade through a whole screen of stuff, and
: second for scripts.  Here's the current output.  Lemme know what you
: think.
: 
: BTW, I'm also in the middle of writing a prepdisk script that uses
: fdisk and disklabel to properly and easily label a disk for use under
: FreeBSD.
: 
: Please look at the script I wrote for the doc2k device, it is in
: src/sys/contrib/dev/fla

This is a second generation of that script.  It will work for scsi
devices, where your script won't.  It will also work for removable
media not present at /var/run/demsg.boot time.

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: which(1), rewritten in C?

2000-03-03 Thread Oliver Fromme

I'd like to add my 2 cents, too.

I agree that "which" should be a shell-builtin, because it is
dependant on how the shell will search and performe a command
(it might be an alias, a shell function, or a shell-builtin,
or a "normal" program).

Personally, I use the zsh, and its "which" builtin has served
me very well (zsh also supports "type" according to POSIX).
Another useful command is "where", which prints all possible
locations of a command, in order of preference (not just the
first one like "which" does).

Finally, I like the "path expansion" feature very much:  an
equal sign followed by a command name will expand to the full
path of the command.  For example, "vi =foo" is an easy way to
edit the foo script, no matter where it is and where my cwd is,
and "file =bar" tells me if bar is a binary, a shell script, a
perl hack or whatever, without having to know where it is.

Regards
   Oliver

-- 
Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany
(Info: finger userinfo:[EMAIL PROTECTED])

"In jedem Stück Kohle wartet ein Diamant auf seine Geburt"
 (Terry Pratchett)


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: sysinstall mistake

2000-03-03 Thread Jordan K. Hubbard

Whoops, you are correct!  Fixed.

 Hello!
 
 Sure, I'm tracking. 
 There are two lines with USA_RESIDENT. First used when creating new
 make.conf. Second one is used when updating existing make.conf.
 You've fixed it only in first case.
 Please look at the patch properly :) 
 
 Dmitry.
 
 On Thu, 2 Mar 2000, Jordan K. Hubbard wrote:
 
  Date: Thu, 02 Mar 2000 03:12:09 -0800
  From: "Jordan K. Hubbard" [EMAIL PROTECTED]
  To: Dmitry Valdov [EMAIL PROTECTED]
  Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
  Subject: Re: sysinstall mistake 
  
  You need to track -current.  I fixed this on:
  
  revision 1.155
  date: 2000/02/24 08:28:06;  author: jkh;  state: Exp;  lines: +2 -2
  Do USA_RESIDENT properly.
  
  
   Hi!
   
   Please commit it:
   
   
   
   --- release/sysinstall/config.c.old   Tue Feb 29 23:56:47 2000
   +++ release/sysinstall/config.c   Tue Feb 29 23:56:55 2000
   @@ -386,7 +386,7 @@
 if (!strncmp(lines[i], "USA_RESIDENT", 12)) {
 free(lines[i]);
 lines[i] = malloc(21);  /* big enough */
   - sprintf(lines[i], "USA_RESIDENT=\"%s\"\n", USAResident ? "YES" 
  : "NO");
   + sprintf(lines[i], "USA_RESIDENT=%s\n", USAResident ? "YES" : "N
  O");
 }
 }
}
   
   
   
  
  
 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



vmware stopped working?

2000-03-03 Thread David Gilbert

I just cvsup'd today (and I did also recompile the vmware modules,
just in case)... and the vmware binary started failing with the
message:

[2:18:318]dgilbert@strike:/u7/dgilbert/vmware/FreeBSD vmware
(USER) Dictionary_Create: unable to allocate memoryPanic without a VM
Segmentation fault

Any ideas?

Dave.

-- 

|David Gilbert, Velocet Communications.   | Two things can only be |
|Mail:   [EMAIL PROTECTED] |  equal if and only if they |
|http://www.velocet.net/~dgilbert |   are precisely opposite.  |
=GLO


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: 4.0-CURRENT hangs in ex_isa_identify() (was: current hangs during boot if ET/5025-16 card is installed)

2000-03-03 Thread Don Lewis

On Mar 3, 11:16am, "Matthew N. Dodd" wrote:
} Subject: Re: 4.0-CURRENT hangs in ex_isa_identify() (was: current hangs du
} On Fri, 3 Mar 2000, Don Lewis wrote:
}  What really sucks is that there is no way to disable the ex driver
}  at boot time, so the standard install floppies can no longer be used
}  to boot a box that contains one of these ET cards.
}  
}  Should the ex driver be doing all this stuff at identify time, or was
}  the older method of doing this at probe time more correct?
} 
} Thats really the only place for such a routine.  What needs to happen is
} for if_ex to a little more selective about which addresses it
} probes.  While it is using a non-destructive probe (see
} look_for_card()) it should also use the resource manager to check and see
} if a port is assigned before it does anything else.

Unfortunately the GENERIC kernel doesn't have a driver that could claim
the ET card.  Also ex_isa_identify() is called before the legacy ISA
probes are done.

IMHO, the best way to fix this would be for the dual-mode PnP/legacy
drivers to identify any cards in PnP mode, then do legacy ISA probes
using the old hard-wired port numbers, where legacy ISA probes can
be controlled by userconfig.  This is really ugly, but then we all
agree that ISA sucks.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Kernel hangs booting fresh -current

2000-03-03 Thread Nik Clayton

On Fri, Mar 03, 2000 at 07:38:33AM -0500, Jim Bloom wrote:
 Nik Clayton wrote:
  On a related note, why does UPDATING say to build and install the kernel,
  and then reboot, before doing the "installworld"?  That contradicts the
  advice in the Handbook (which I wrote), and I would've thought it's wrong
  precisely because it allows for things like kernel/mount mismatches to
  occur.
 
 Because the signal interface changed several months ago.  If you ran
 installworld on an old kernel, the machine would panic part way through
 the install.  

OK.  That just about makes sense.

 It is almost impossible to do forward compatibility on
 major changes.  I guess you need to update the handbook to reflect this
 change.

Not sure.  As a corner case it should probably stay in UPDATING.

N
-- 
If you want to imagine the future, imagine a tennis shoe stamping
on a penguin's face forever.
--- with apologies to George Orwell


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: 4.0-CURRENT hangs in ex_isa_identify() (was: current hangs duringboot if ET/5025-16 card is installed)

2000-03-03 Thread Matthew N. Dodd

On Fri, 3 Mar 2000, Don Lewis wrote:
 Unfortunately the GENERIC kernel doesn't have a driver that could claim
 the ET card.  Also ex_isa_identify() is called before the legacy ISA
 probes are done.
 
 IMHO, the best way to fix this would be for the dual-mode PnP/legacy
 drivers to identify any cards in PnP mode, then do legacy ISA probes
 using the old hard-wired port numbers, where legacy ISA probes can
 be controlled by userconfig.  This is really ugly, but then we all
 agree that ISA sucks.

I think the best solution is to rip broken hardware out of your computer.

There isn't any reason that the ET should lock up the system when its IO
ports are read.

The 'ex' driver is about the most non-destructive probe we've got.

It no longer uses the ISA compat shims; its a fully newbus'ed driver.

I agree that we need some way to enable/disable newbus drivers in the
visual userconfig though.  This isn't likely to happen until after 4.0.

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| [EMAIL PROTECTED] |   2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter | This Space For Rent  | ISO8802.5 4ever |



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



diskprep beta -- comments wanted.

2000-03-03 Thread Warner Losh


OK.  I've written a simple diskprep program.  It will take a disk, put
slice information (fdisk) and partition information (disklabel) onto
the disk.  By default, it will create one slice (1) and one partition
on that (a).  It will also newfs all partitions that are on the disk.
It supports reading in a config file which can change this behavior.

I've not written a man page yet.

diskprep disk

is all you should need.  I've tested this on a scsi drive, as well as
couple of different compact flash/pccard flash cards that I have
kicking around the office.

WARNING: While I've taken all the usual steps to ensure that this
doesn't do bad things.  It has been tested on exactly two machines,
one with a SCSI disk, and one with a CF card plugged into a pccard
bus.  I've tried to put good error checking, but I'm not positive I've
caught all the possible problems.

It doesn't work with vn devices.

You will need the fdisk patches from
http://people.freebsd.org/~imp/fdisk-patch  [*]
and you can get diskprep from
http://people.freebsd.org/~imp/diskprep

It is based on a similar idea that pkh did with his prep.fla.sh.  The
only thing that is left from that is the beerware license, which I
figured was good to rip off from phk :-).

Please let me know how this works.  I'd like to see this in FreeBSD in
the fullness of time.  It will be a useful tool and end a lot of the
frustration I've seen in connection with the setting up of disks.

Comments?

Warner

[*] -e - -I and -s talked about in other posts.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



How to crash FreeBSD w/ mpg123 and XFree86

2000-03-03 Thread Donn Miller

First, start up XFree86.  Next, play an mp3 clip in an xterm with
mpg123.  Next, hit cntrol+alt+F3 (or whatever) to switch to a VC while the
clip is playing.  Stau there for about 3 seconds.  Then, switch back to X
with alt+F9, or whichever VC X is running on.  On my machine, the monitor
goes blank, my display goes black, and the machine is
unresponsive.  However, I didn't try to see if I could still log in via a
serial terminal.

The version of XFree86 I'm running:

$ X -showconfig
XFree86 Version 3.9.18 / X Window System

Do all of this while the clip is playing.

- Donn



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: diskprep beta -- comments wanted.

2000-03-03 Thread Sheldon Hearn



On Fri, 03 Mar 2000 16:45:36 MST, Warner Losh wrote:

 Please let me know how this works.  I'd like to see this in FreeBSD in
 the fullness of time.  It will be a useful tool and end a lot of the
 frustration I've seen in connection with the setting up of disks.

As an aside, 4.0-RELEASE's sysinstall looks set to kick ass in this
area.  Of course, your solution will provide something more useful for
folks who don't want to interact with anything after typing the command.
Well, it will once it takes command-line options instead of / as well as
parsing a config file. :-)

Ciao,
Sheldon.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: diskprep beta -- comments wanted.

2000-03-03 Thread Warner Losh

In message [EMAIL PROTECTED] Sheldon Hearn writes:
: As an aside, 4.0-RELEASE's sysinstall looks set to kick ass in this
: area.  Of course, your solution will provide something more useful for
: folks who don't want to interact with anything after typing the command.
: Well, it will once it takes command-line options instead of / as well as
: parsing a config file. :-)

sysinstall doesn't work at all for me.  On three different machines,
it tells me that it found no disks.  So I can't comment on this.

It is about 1000x easier to use than sysinstall.  One simple command,
and you are good to go.  It won't add anything to /etc/fstab, but I
consider that to be a feature.

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



IPSec in 4.0-current questions..

2000-03-03 Thread Louis A. Mamakos


I've been messing about with IPSEC in 4.0-current, and have observed some
unexpected behavior.  Is there someone I can swap some email with off
the list to determine if what I'm seeing is a bug, or I'm just confused?

It has to do with security policy specifications and what SAID is being
selected when a TCP connection is being opened.

Thanks!

louie



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: BIOS settings (was Instrallation floppies and USB)

2000-03-03 Thread Warner Losh

In message [EMAIL PROTECTED] Nikolai Saoukh writes:
: what then pnp stuff (/usr/src/sys/isa/pnp*) do in -current?

That just deals with the isa pnp expansion cards.  the PnP BIOS
setting to "no" means that the BIOS will enable all the PnP (not just
ISA add on cards) devices before passing control to the os.  With it
set to yes, the OS has to do this activation, and FreeBSD doesn't do
that yet.

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: diskprep beta -- comments wanted.

2000-03-03 Thread Jonathan Smith

 
 It is about 1000x easier to use than sysinstall.  One simple command,
 and you are good to go.  It won't add anything to /etc/fstab, but I
 consider that to be a feature.
 

For what it's worth, one man's feature is another man's, er, wait, isn't
that treasure?  Never mind.  Point being, make it an option to do
so.  Further, make an option to specify the file to write to instead of
/etc/fstab.  Ie. '-F' writes to the _standard_ file (/etc/fstab), and then
'-f /saving/someother/computer/etc/fstab' would modify the alternate file
instead of the /etc/fstab.  Then again, neither '-F' nor '-f file' means
it wouldn't do it all.  Another suggestion might be to define '-f -' to do
the usual of throwing it to the stdout.

Just a penny and a half...

Jon Smith



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: which(1), rewritten in C?

2000-03-03 Thread Dan Papasian

Ah, well, I hadn't picked up that that was the desired behavoir.

Well, it is fixed: http://bugg.strangled.net/which.c 

-Dan Papasian
[EMAIL PROTECTED]

On Fri, Mar 03, 2000 at 07:09:29AM -0800, Alfred Perlstein wrote:
 * Dan Papasian [EMAIL PROTECTED] [000303 04:39] wrote:
  Can you please give an example of where multiple arguments
  doesn't work as expected?
  
  It works fine over here.
 
 ~ % which ls ln sh
 /bin/ls
 /bin/ln
 /bin/sh
 ~ % ./a.out ls ln sh
 /bin/sh
 
 -- 
 -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



current.freebsd.org

2000-03-03 Thread Bill Swingle

current.freebsd.org is currently down due to a hardware failure. I don't
have an ETA on when it will be back up again, due to it being offsite.
I'll post more info as it becomes available.

-Bill

-- 
-=| --- B i l l   S w i n g l e --- http://www.dub.net/
-=| [EMAIL PROTECTED]  - [EMAIL PROTECTED] - [EMAIL PROTECTED] 
-=| Different all twisty a of in maze are you, passages little




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: things I noticed w/ 4.0

2000-03-03 Thread Joseph Jacobson


Sorry for the late reply on this.

Ok, cvsup'ed and loaded the most up-to-date bios for my motherboard.
(That was tale of woe, but I'll hold off on that telling).

 Joseph Jacobson wrote:
  
  Kernel option VESA fails (see dmesg below).  Is this a problem with my
  graphics card?
 
 Are you, by any chance, both compiling in VESA _and_ loading it with
 loader?

VESA is compiled into the kernel.  I don't have a /boot/loader.conf
file.  Is there any other way for the VESA module to be loaded at boot,
before /etc/rc runs?  Also, none of the vidcontrol VESA modes work for
me.  (All this isn't a big deal, but the error message is weird).

 
  Kernel option PNPBIOS causes the mouse to stop working.  A pointer is
  visible at boot (w/ moused) until the mouse is moved, then it disappears
  forever.  Maybe I'm misunderstanding what PNPBIOS does
 
 Weird. Are you sure your BIOS is set to PnP OS = No?

My bios has settings "PnP OS", "Use ICU" (run-time software utility),
and "Use Setup" (you specify what IRQs and DMAs are available to PnP).
I get the above behavior with all three of these settings, (although I
believe "Use Setup" is the correct one).  I even tried removing my one
ISA card (which I don't use anyway, so I can live without PNPBIOS).

 
  'halt -p' still doesn't turn my computer off :).  Haven't tested any other
  functionality of apm though.  I usually disable apm in the bios since
  it makes turning the system power off w/ the button on the case a problem
  under FreeBSD.  Any ideas?
 
 Yep. Try turning apm in BIOS on. :-)
 

I didn't express myself very well in the above paragraph. :)  Here is the
behavior exhibited by my box with apm.  When apm is enabled in the bios,
and 'apm -e enable' is run, 'halt -p' causes the system to reboot.  'zzz'
causes the system to hang (unresponsive to keyboard and mouse input).
(I didn't try all permutations of my apm bios settings with 'zzz' to see
if I can work around the hang, but I don't think that's the cause).
Pushing my power button during the hang state caused the system to reboot.
Also, when apm is enabled, after a regular 'halt' or 'shutdown', pushing
the power button causes the machine to reset, not turn off.


None of this is stopping me from useful work w/ FreeBSD 4.0.

--Joe

Pertinent parts of dmesg follow:

FreeBSD 4.0-CURRENT #1: Thu Mar  2 09:27:11 EST 2000
root@home:/usr/src/sys/compile/new
...
Preloaded elf kernel "kernel" at 0xc0341000.
Intel Pentium detected, installing workaround for F00F bug
module_register_init: MOD_LOAD (vesa, c0246c6c, 0) error 6
md0: Malloc disk
...
chip1: Intel 82371AB Power management controller port 0xff40-0xff4f at device 7.3 on 
pci0
...
pci0: Number Nine model 493d graphics accelerator at 18.0 irq 11
...
psm0: PS/2 Mouse irq 12 on atkbdc0
psm0: model IntelliMouse, device ID 3
vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
sc0: System console on isa0
sc0: VGA 16 virtual consoles, flags=0x200



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: things I noticed w/ 4.0

2000-03-03 Thread Mike Smith

 VESA is compiled into the kernel.  I don't have a /boot/loader.conf
 file.  Is there any other way for the VESA module to be loaded at boot,
 before /etc/rc runs?  Also, none of the vidcontrol VESA modes work for
 me.  (All this isn't a big deal, but the error message is weird).
...
 module_register_init: MOD_LOAD (vesa, c0246c6c, 0) error 6

Sounds like the VESA BIOS initialisation failed; either the card doesn't 
have a VESA BIOS, or there are no supported modes.

-- 
\\ 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-current" in the body of the message



Shared IRQs

2000-03-03 Thread Sean-Paul Rees

I have a FreeBSD 4.0-CURRENT (cvsup'ed as of tonight) machine. It has a USB
controller (PIIX3) and an ethernet controller sharing irq 10. I'm not
much in the way of a hardware expert, so I'm wondering if this is safe or
if I should reroute the ethernet card or the usb to another irq.

In case it matters (don't think it would), this machine is an IBM
PC Server 325 with an Intel 440FX motherboard.
-- 
Cheers,
Sean



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Shared IRQs

2000-03-03 Thread Brooks Davis

On Fri, Mar 03, 2000 at 07:25:26PM -0800, Sean-Paul Rees wrote:
 I have a FreeBSD 4.0-CURRENT (cvsup'ed as of tonight) machine. It has a USB
 controller (PIIX3) and an ethernet controller sharing irq 10. I'm not
 much in the way of a hardware expert, so I'm wondering if this is safe or
 if I should reroute the ethernet card or the usb to another irq.

It's fine, PCI can share interupts.  It might perform somewhat
sub-optimaly under very heavy load, but it will work just fine.

-- Brooks

-- 
Any statement of the form "X is the one, true Y" is FALSE.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: current.freebsd.org

2000-03-03 Thread Louis A. Mamakos

 current.freebsd.org is currently down due to a hardware failure. I don't
 have an ETA on when it will be back up again, due to it being offsite.
 I'll post more info as it becomes available.

Usually hardware and software craps out when the "demo detector" kicks
in.  It seems that the we've got our own version, the "Jordan travel
detector."

louie



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Make world error.....

2000-03-03 Thread William Woods

Running 4.0-CURRENT FreeBSD 4.0-CURRENT #10: Wed Mar  1 10:25:09 PST 2000  on a
IBM thinkpad 600E, 128 megs. while doing a make world of todays CVSUP I get
this:

--
sys/sem.h - sys/sem.ph
sys/shm.h - sys/shm.ph
sys/signal.h - sys/signal.ph
sys/signalvar.h - sys/signalvar.ph
sys/snoop.h - sys/snoop.ph
sys/socket.h - sys/socket.ph
sys/socketvar.h - sys/socketvar.ph
sys/sockio.h - sys/sockio.ph
sys/soundcard.h - sys/soundcard.ph
sys/stat.h - sys/stat.ph
sys/syscall-hide.h - sys/syscall-hide.ph
sys/syscall.h - sys/syscall.ph
sys/sysctl.h - sys/sysctl.ph
sys/sysent.h - sys/sysent.ph
sys/syslimits.h - sys/syslimits.ph
sys/syslog.h - sys/syslog.ph
sys/sysproto.h - sys/sysproto.ph
sys/systm.h - sys/systm.ph
sys/termios.h - sys/termios.ph
sys/time.h - sys/time.ph
sys/timeb.h - sys/timeb.ph
sys/timepps.h - sys/timepps.ph
sys/timers.h - sys/timers.ph
sys/times.h - sys/times.ph
sys/timex.h - sys/timex.ph
sys/tprintf.h - sys/tprintf.ph
sys/tty.h - sys/tty.ph
sys/ttychars.h - sys/ttychars.ph
sys/ttycom.h - sys/ttycom.ph
sys/ttydefaults.h - sys/ttydefaults.ph
sys/ttydev.h - sys/ttydev.ph
sys/types.h - sys/types.ph
sys/ucontext.h - sys/ucontext.ph
sys/ucred.h - sys/ucred.ph
sys/uio.h - sys/uio.ph
sys/un.h - sys/un.ph
sys/unistd.h - sys/unistd.ph
sys/unpcb.h - sys/unpcb.ph
sys/user.h - sys/user.ph
sys/utsname.h - sys/utsname.ph
sys/vmmeter.h - sys/vmmeter.ph
sys/vnioctl.h - sys/vnioctl.ph
sys/vnode.h - sys/vnode.ph
sys/wait.h - sys/wait.ph   
sys/wormio.h - sys/wormio.ph
sys/xrpuio.h - sys/xrpuio.ph
vm/pmap.h - vm/pmap.ph
vm/swap_pager.h - vm/swap_pager.ph
vm/vm.h - vm/vm.ph
vm/vm_extern.h - vm/vm_extern.ph
vm/vm_kern.h - vm/vm_kern.ph
vm/vm_map.h - vm/vm_map.ph
vm/vm_object.h - vm/vm_object.ph
vm/vm_page.h - vm/vm_page.ph
vm/vm_pageout.h - vm/vm_pageout.ph
vm/vm_pager.h - vm/vm_pager.ph
vm/vm_param.h - vm/vm_param.ph
vm/vm_zone.h - vm/vm_zone.ph
vm/vnode_pager.h - vm/vnode_pager.ph
*** Error code 1

Stop in /usr/src/gnu/usr.bin/perl/utils/h2ph.
*** Error code 1

Stop in /usr/src/gnu/usr.bin/perl/utils.
*** Error code 1

Stop in /usr/src/gnu/usr.bin/perl.
*** Error code 1

Stop in /usr/src/gnu/usr.bin.
*** Error code 1

Stop in /usr/src/gnu.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1
1 error   


Ideas about what died and why?


--
E-Mail: [EMAIL PROTECTED]
Date: 03-Mar-00
Time: 21:54:08l
--


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



cvsup'ing 4.0 SNAPs

2000-03-03 Thread Nathan Sheeley


Is it possible to cvsup the source for the 4.0-SNAP
snapshot release?  I don't want to go completely current,
but I'd like to try 4.0 to see if the support for my SB PCI128
sound card is better.

I tried using "HEAD" as the tag,
but that didn't result in anything changing... perhaps
because current.freebsd.org is down?

Nate



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: diskprep beta -- comments wanted.

2000-03-03 Thread Warner Losh

In message [EMAIL PROTECTED] Jonathan Smith 
writes:
: Just a penny and a half...

Hmmm.  Maybe in the featuritis phase of development I may add this.
Right now there's no way to give a mount point...

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: IPSec in 4.0-current questions..

2000-03-03 Thread itojun


I've been messing about with IPSEC in 4.0-current, and have observed some
unexpected behavior.  Is there someone I can swap some email with off
the list to determine if what I'm seeing is a bug, or I'm just confused?
It has to do with security policy specifications and what SAID is being
selected when a TCP connection is being opened.

could you try sending details to [EMAIL PROTECTED] (KAME users
mailing list, you may want to subscribe it - see www.kam.enet).

itojun


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Make world error.....

2000-03-03 Thread Doug Barton

William Woods wrote:
 
 Running 4.0-CURRENT FreeBSD 4.0-CURRENT #10: Wed Mar  1 10:25:09 PST 2000  on a
 IBM thinkpad 600E, 128 megs. while doing a make world of todays CVSUP I get
 this:

What command line did you use? This looks to me like 'make -jN'
breakage. I would try the following:

cd /usr/src
make cleandir
cd /usr/obj
rm -r *
cvsup/cvs latest src
cd /usr/src
make -DNOCLEAN buildworld

Good luck,

Doug
-- 
"Welcome to the desert of the real." 

- Laurence Fishburne as Morpheus, "The Matrix"


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message