Re: d-link dwl520 wireless pci
In message: <[EMAIL PROTECTED]>
Brooks Davis <[EMAIL PROTECTED]> writes:
: If it's going to work the definition for the Linksys WMP11 will do it.
: It will have the wrong name in dmesg, but that doesn't do anything.
: This entry should be changed to reflect the fact that it's actually an
: Intersil Prism 2.5 ID that lazy vendors are using.
Comments on the following patch? It removes the extra IEEE 802.11
stuff (which is noise since wi is an 802.11b driver :-) and changes
Linksys WMP11 to the more generic Intersil Prism2.5 PCI.
Warner
Index: if_wi_pci.c
===
RCS file: /home/imp/FreeBSD/CVS/src/sys/dev/wi/if_wi_pci.c,v
retrieving revision 1.5
diff -u -r1.5 if_wi_pci.c
--- if_wi_pci.c 14 Apr 2002 22:08:58 - 1.5
+++ if_wi_pci.c 27 Apr 2002 07:06:57 -
@@ -94,13 +94,13 @@
int bus_type;
char *desc;
} pci_ids[] = {
- {0x1638, 0x1100, WI_BUS_PCI_PLX, "PRISM2STA PCI WaveLAN/IEEE 802.11"},
- {0x1385, 0x4100, WI_BUS_PCI_PLX, "Netgear MA301 PCI IEEE 802.11b"},
- {0x16ab, 0x1101, WI_BUS_PCI_PLX, "GLPRISM2 PCI WaveLAN/IEEE 802.11"},
- {0x16ab, 0x1102, WI_BUS_PCI_PLX, "Linksys WDT11 PCI IEEE 802.11b"},
- {0x1260, 0x3873, WI_BUS_PCI_NATIVE, "Linksys WMP11 PCI Prism2.5"},
- {0x10b7, 0x7770, WI_BUS_PCI_PLX, "3Com Airconnect IEEE 802.11b"},
- {0x111a, 0x1023, WI_BUS_PCI_PLX, "Siemens SpeedStream IEEE 802.11b"},
+ {0x1638, 0x1100, WI_BUS_PCI_PLX, "PRISM2STA PCI WaveLAN"},
+ {0x1385, 0x4100, WI_BUS_PCI_PLX, "Netgear MA301 PCI"},
+ {0x16ab, 0x1101, WI_BUS_PCI_PLX, "GLPRISM2 PCI WaveLAN"},
+ {0x16ab, 0x1102, WI_BUS_PCI_PLX, "Linksys WDT11 PCI"},
+ {0x1260, 0x3873, WI_BUS_PCI_NATIVE, "Intersil Prism2.5 PCI"},
+ {0x10b7, 0x7770, WI_BUS_PCI_PLX, "3Com Airconnect"},
+ {0x111a, 0x1023, WI_BUS_PCI_PLX, "Siemens SpeedStream"},
{0, 0, 0, NULL}
};
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Recent commit to sys/kern/kern_environment.c broke reading t
In message: <[EMAIL PROTECTED]> John Baldwin <[EMAIL PROTECTED]> writes: : : On 27-Apr-2002 Shizuka Kudo wrote: : > It seems the latest commit of : > sys/kern/kern_environment to current broke the reading : > of system tunables set by loader.conf. This is true at : > least for hw.cbb.start_mem of my cardbus bridge. With : > this latest commit, the hw.cbb.start_mem sysctl still : > shows the default value after boot up. : > : > Reverting back to version 1.22 solve my problem. Is : > this unique to me? : : No, it seems to be broken for all environment variables : on alpha. It is busted for me as well. I had some not too nice words to say when I discovered that :-( Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ipfilter not broken for me
In some email I received from Doug Barton, sie wrote: > On Fri, 26 Apr 2002, Ruslan Ermilov wrote: > > > I tested this on i386 only with 2 days old -CURRENT (today's is > > broken due to the import of latest IPFilter suite) > > I updated to the latest and greatest last night around midnight > and built/installed -current just fine. What about the ipfilter import is > broken, and have you let Darren know? I haven't seen anything on the lists > about it... I have not received any email about it. I tested building all the ipfilter binaries and kernel after the import and came up clean. if ref5 was a bit quicker Darren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Recent commit to sys/kern/kern_environment.c broke reading t
On 27-Apr-2002 Shizuka Kudo wrote: > It seems the latest commit of > sys/kern/kern_environment to current broke the reading > of system tunables set by loader.conf. This is true at > least for hw.cbb.start_mem of my cardbus bridge. With > this latest commit, the hw.cbb.start_mem sysctl still > shows the default value after boot up. > > Reverting back to version 1.22 solve my problem. Is > this unique to me? No, it seems to be broken for all environment variables on alpha. -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "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: cvs commit: src/sys/kern kern_tc.c src/sys/sys timepps.h timetc.h
On Fri, Apr 26, 2002 at 02:51:08PM -0700, Poul-Henning Kamp wrote: > phk 2002/04/26 14:51:08 PDT > > Modified files: > sys/kern kern_tc.c > sys/sys timepps.h timetc.h > Log: This commit causes the bento package cluster to hang at boot time: [...] Timecounters tick every 10.000 msec ad0: 29314MB [59560/16/63] at ata0-master UDMA66 Mounting root from nfs: And it hangs there forever. Backing out this commit fixes things. Kris msg37758/pgp0.pgp Description: PGP signature
RE: d-link dwl520 wireless pci
U using latest version of -current, in fact even the original 5.0 DR1
iso release supported the card, kernel needed some minor modification,
but I am using the dlink dwl 520 in my box right now without any
problems. And Brooks Davis was correct, with shows up as a linksys
device on my machines.
If the original poster wants, I can send him my kernal config file, but
I think I really only had to add options card which I think was
commented out, not too sure, it was a while back, and I had a lot of
other issues with the kernels and the machine taking a huge dump to
panic mode a lot on some other things, like smbfs and smp.
Snippet of dmesg below.
wi0: mem 0xfb80-0xfb800fff irq 2 at
device 10.0 on pci0
wi0: 802.11 address: 00:05:5d:da:5f:47
wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI)
wi0: Intersil Firmware: Primary 1.00.07, Station 1.03.05
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Brooks Davis
Sent: Friday, April 26, 2002 8:18 PM
To: . ten tacles . .
Cc: [EMAIL PROTECTED]
Subject: Re: d-link dwl520 wireless pci
On Fri, Apr 26, 2002 at 07:44:11PM -0400, . ten tacles . . wrote:
>
> recently acquired a dwl520 and i was wondering
> if there is freebsd support for this card.
> i looked through what appeared to be the pci-support
> portion of the wi driver (if_wi_pci.c ..checked out
> via cvs last night) and i couldn't find a definition of this card:
>
> pci_ids[] = {
> {0x1638, 0x1100, WI_BUS_PCI_PLX, "PRISM2STA PCI WaveLAN/IEEE
802.11"},
> {0x1385, 0x4100, WI_BUS_PCI_PLX, "Netgear MA301 PCI IEEE
802.11b"},
> {0x16ab, 0x1101, WI_BUS_PCI_PLX, "GLPRISM2 PCI WaveLAN/IEEE
802.11"},
> {0x16ab, 0x1102, WI_BUS_PCI_PLX, "Linksys WDT11 PCI IEEE
802.11b"},
> {0x1260, 0x3873, WI_BUS_PCI_NATIVE, "Linksys WMP11 PCI
Prism2.5"},
> {0x10b7, 0x7770, WI_BUS_PCI_PLX, "3Com Airconnect IEEE
802.11b"},
> {0x111a, 0x1023, WI_BUS_PCI_PLX, "Siemens SpeedStream IEEE
802.11b"},
> {0, 0, 0, NULL}
>
> this may or may not be indicative of support for this card as far as i
> know (which is not much regarding driver hacking). i compiled the
> driver into the kernel anyways and got this on bootup:
>
> pci0: (vendor=0x1260, dev=0x3873) at 11.0 irq 12
>
> so would anyone happen to know if this card is supported and if so, is
> there a diff/patch/revision that i should get or procedure i should
> follow?
If it's going to work the definition for the Linksys WMP11 will do it.
It will have the wrong name in dmesg, but that doesn't do anything. This
entry should be changed to reflect the fact that it's actually an
Intersil Prism 2.5 ID that lazy vendors are using.
-- Brooks
--
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Recent commit to sys/kern/kern_environment.c broke reading tunables
It seems the latest commit of sys/kern/kern_environment to current broke the reading of system tunables set by loader.conf. This is true at least for hw.cbb.start_mem of my cardbus bridge. With this latest commit, the hw.cbb.start_mem sysctl still shows the default value after boot up. Reverting back to version 1.22 solve my problem. Is this unique to me? Thanks. __ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
shutdown doesn't
It goes into background and nothing happens. Krzysztof To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
login coredumps
At the login prompt using the arrow keys to move the cursor up and down causes login to dump core. System was cvsupped today. Krzysztof To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: d-link dwl520 wireless pci
On Fri, Apr 26, 2002 at 07:44:11PM -0400, . ten tacles . . wrote:
>
> recently acquired a dwl520 and i was wondering
> if there is freebsd support for this card.
> i looked through what appeared to be the pci-support
> portion of the wi driver (if_wi_pci.c ..checked out
> via cvs last night) and i couldn't find a definition of this card:
>
> pci_ids[] = {
> {0x1638, 0x1100, WI_BUS_PCI_PLX, "PRISM2STA PCI WaveLAN/IEEE 802.11"},
> {0x1385, 0x4100, WI_BUS_PCI_PLX, "Netgear MA301 PCI IEEE 802.11b"},
> {0x16ab, 0x1101, WI_BUS_PCI_PLX, "GLPRISM2 PCI WaveLAN/IEEE 802.11"},
> {0x16ab, 0x1102, WI_BUS_PCI_PLX, "Linksys WDT11 PCI IEEE 802.11b"},
> {0x1260, 0x3873, WI_BUS_PCI_NATIVE, "Linksys WMP11 PCI Prism2.5"},
> {0x10b7, 0x7770, WI_BUS_PCI_PLX, "3Com Airconnect IEEE 802.11b"},
> {0x111a, 0x1023, WI_BUS_PCI_PLX, "Siemens SpeedStream IEEE 802.11b"},
> {0, 0, 0, NULL}
>
> this may or may not be indicative of support for this card as far as i
> know (which is not much regarding driver hacking). i compiled the driver
> into the kernel anyways and got this on bootup:
>
> pci0: (vendor=0x1260, dev=0x3873) at 11.0 irq 12
>
> so would anyone happen to know if this card is supported and if so,
> is there a diff/patch/revision that i should get or procedure i should
> follow?
If it's going to work the definition for the Linksys WMP11 will do it.
It will have the wrong name in dmesg, but that doesn't do anything.
This entry should be changed to reflect the fact that it's actually an
Intersil Prism 2.5 ID that lazy vendors are using.
-- Brooks
--
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4
msg37753/pgp0.pgp
Description: PGP signature
RE: xdm broken on current
On 26-Apr-2002 John Baldwin wrote: > Please back out revision 1.3 of src/etc/pam.d/xdm since it breaks xdm. > xdm core dumps with a signal 6 if there is no session management > configured for it in PAM. Obviously this commmit wasn't actually tested > with xdm (at least not on X 4). In revision 1.19 of pam.conf Mark > Murray changed the session management for xdm to use pam_unix instead of > pam_deny with no apparent reason why. (The log message doesn't say why > that change was made.) Erm, I should finish that thought: So perhaps it can use pam_deny or some such instead of pam_unix if using pam_unix is bad? -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "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: d-link dwl520 wireless pci
* . ten tacles . . <[EMAIL PROTECTED]> [020426 16:03] wrote:
>
> via cvs last night) and i couldn't find a definition of this card:
>
> pci_ids[] = {
...
> {0x1260, 0x3873, WI_BUS_PCI_NATIVE, "Linksys WMP11 PCI Prism2.5"},
...
> pci0: (vendor=0x1260, dev=0x3873) at 11.0 irq 12
I think you mucked up your kernel install. Are you positive?
Try sticking a printf in the driver's probe routine to make sure
it's being called at boot time.
--
-Alfred Perlstein [[EMAIL PROTECTED]]
'Instead of asking why a piece of software is using "1970s technology,"
start asking why software is ignoring 30 years of accumulated wisdom.'
Tax deductible donations for FreeBSD: http://www.freebsdfoundation.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
xdm broken on current
Please back out revision 1.3 of src/etc/pam.d/xdm since it breaks xdm. xdm core dumps with a signal 6 if there is no session management configured for it in PAM. Obviously this commmit wasn't actually tested with xdm (at least not on X 4). In revision 1.19 of pam.conf Mark Murray changed the session management for xdm to use pam_unix instead of pam_deny with no apparent reason why. (The log message doesn't say why that change was made.) -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "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: DRM in the sys/ tree: looking for testers
On Fri, 2002-04-26 at 01:03, moto kawasaki wrote: > > Thank you very much, Mr. Eric Anholt, > > I have been testing your code on my PC, and found that kernel cannot > initialize agpgart device so far. The i8x0 DRM drivers require AGP to be working. I took a look at your i830 patch today, and compared it to the linux kernel version. I added some more checks for invalid options (binding memory into offsets used by the stolen memory), and added the enabling of the gatt that linux does. The only difference that I see between our drivers after this diff is that linux forces enabling of the integrated graphics. The diff is at http://gladstone.uoregon.edu/~eanholt/dri/i810diff If we aren't sure how well the driver is working, testgart might help for debugging without using X. A copy of linux testgart from utah-glx is at http://gladstone.uoregon.edu/~eanholt/dri/testgart.c To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
d-link dwl520 wireless pci
recently acquired a dwl520 and i was wondering
if there is freebsd support for this card.
i looked through what appeared to be the pci-support
portion of the wi driver (if_wi_pci.c ..checked out
via cvs last night) and i couldn't find a definition of this card:
pci_ids[] = {
{0x1638, 0x1100, WI_BUS_PCI_PLX, "PRISM2STA PCI WaveLAN/IEEE 802.11"},
{0x1385, 0x4100, WI_BUS_PCI_PLX, "Netgear MA301 PCI IEEE 802.11b"},
{0x16ab, 0x1101, WI_BUS_PCI_PLX, "GLPRISM2 PCI WaveLAN/IEEE 802.11"},
{0x16ab, 0x1102, WI_BUS_PCI_PLX, "Linksys WDT11 PCI IEEE 802.11b"},
{0x1260, 0x3873, WI_BUS_PCI_NATIVE, "Linksys WMP11 PCI Prism2.5"},
{0x10b7, 0x7770, WI_BUS_PCI_PLX, "3Com Airconnect IEEE 802.11b"},
{0x111a, 0x1023, WI_BUS_PCI_PLX, "Siemens SpeedStream IEEE 802.11b"},
{0, 0, 0, NULL}
this may or may not be indicative of support for this card as far as i
know (which is not much regarding driver hacking). i compiled the driver
into the kernel anyways and got this on bootup:
pci0: (vendor=0x1260, dev=0x3873) at 11.0 irq 12
so would anyone happen to know if this card is supported and if so,
is there a diff/patch/revision that i should get or procedure i should
follow?
thanks a bunches!
--tents
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Minor things: swi_net: unregistered isr number
"Matthew N. Dodd" wrote: > On Thu, 25 Apr 2002, Peter Wemm wrote: > > This is well known. If we recieve an ARP frame before we sent one, then > > we print this. eg: a broadcast ARP packet will trigger it. dhclient > > etc use bpf etc so ARP isn't initialized at this point. > > We could just put this block of code from arp_rtrequest() into arp_init(). > > LIST_INIT(&llinfo_arp); > timeout(arptimer, (caddr_t)0, hz); > register_netisr(NETISR_ARP, arpintr); > > I'm not sure why it should to be in arp_rtrequest() in the first place. You do not want the timer running and using cpu if you are not using ARP (eg: ppp only). Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/kern kern_tc.c src/sys/sys timepps.h timetc.h
Please let me know if you see any changes in timekeeping behaviour as a result of this series of commits. >phk 2002/04/26 14:51:08 PDT > > Modified files: >sys/kern kern_tc.c >sys/sys timepps.h timetc.h > Log: > Now that the private parts of timecounters are no longer being fingered > by other bits of code, split struct timecounter into two. > > struct timecounter contains just the bits which pertains to the hardware > counter and the reading of it. > > struct timehands (as in "the hands on a clock") contains all the ugly bit > fidling stuff. Statically compile ten timehands. > > This commit is the functional part. A later cosmetic patch will rename > various variables and fieldnames. > > Revision ChangesPath > 1.126 +109 -143 src/sys/kern/kern_tc.c > 1.15 +3 -1 src/sys/sys/timepps.h > 1.51 +1 -12 src/sys/sys/timetc.h > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
elf/strip ???
I get this error when I'm trying to install some ports and /usr/src: (this is taken from /usr/src/libexec) make install ===> atrun install -c -s -o root -g wheel -m 555 atrun /usr/libexec strip: could not exec elf/strip in /usr/libexec: No such file or directory *** Error code 70 Stop in /usr/src/libexec/atrun. *** Error code 1 Stop in /usr/src/libexec. does anyone have any idea? /John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src Makefile Makefile.inc1 src/etc Makefile src/gnu/usr.bin/perl/library Makefile.inc src/release Makefile src/release/scripts catpages-make.sh doFS.sh manpages-make.sh src/secure/usr.bin/ssh Makefile src/secure/usr.sbin/sshd Makefile ...
On Fri, Apr 26, 2002 at 10:12:14PM +0300, Ruslan Ermilov wrote: > On Fri, Apr 26, 2002 at 11:59:21AM -0700, Marcel Moolenaar wrote: > > On Fri, Apr 26, 2002 at 09:26:34PM +0300, Ruslan Ermilov wrote: > > > > > I.e., if you built world a month ago, and didn't touch /usr/src > > > since, and /usr/obj has "buildworld" output for this /usr/src, > > > and you have booted with this world, it should be okay to start > > > building today's release. > > > > I share my src tree, so I almost always have a /usr/src that's not > > in sync with the /usr/obj for and on a particular machine. > > > > What goes wrong if /usr/src and /usr/obj are out of sync? > > > The prerequisite for a successful "make release" is to "installworld" > first the same world as you are currently running. This is done to > create a pristine environment (with an empty /etc/make.conf, etc.) > which is then chroot'ed into. I see. Doing a "make everything TARGET_ARCH=foo -DNOCLEAN" should probably be enough in most cases to sync the object tree, right? > Also, when I wrote "/usr/src" and "/usr/obj" I didn't mean them > literally. That's mostly academic :-) BTW: Do you have plans to remove the exception for non-cross builds to have the object tree rooted under /usr/obj/$TARGET_ARCH? The exception was created for make release, but from a pure cross-building point of view it's inconsistent and is one of the blockers to build, say, alpha on i386 and doing a native install on alpha (the other would be having an empty temproot). -- Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ipfilter not broken for me
On Fri, 26 Apr 2002, Ruslan Ermilov wrote: > I tested this on i386 only with 2 days old -CURRENT (today's is > broken due to the import of latest IPFilter suite) I updated to the latest and greatest last night around midnight and built/installed -current just fine. What about the ipfilter import is broken, and have you let Darren know? I haven't seen anything on the lists about it... -- "We have known freedom's price. We have shown freedom's power. And in this great conflict, ... we will see freedom's victory." - George W. Bush, President of the United States State of the Union, January 28, 2002 Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src Makefile Makefile.inc1 src/etc Makefile src/gnu/usr.bin/perl/library Makefile.inc src/release Makefile src/release/scripts catpages-make.sh doFS.sh manpages-make.sh src/secure/usr.bin/ssh Makefile src/secure/usr.sbin/sshd Makefile ...
On Fri, Apr 26, 2002 at 01:00:21PM -0700, Bruce A. Mah wrote: > If memory serves me right, Ruslan Ermilov wrote: > > > It's important to note that you no > > longer need to have a today's world to build a today's release. > > I.e., if you built world a month ago, and didn't touch /usr/src > > since, and /usr/obj has "buildworld" output for this /usr/src, > > and you have booted with this world, it should be okay to start > > building today's release. > > I'm not sure I understand this comment. Why was there a requirement to > have today's /usr/src and /usr/obj before starting a release? > > (Most of my release-building experience is with 4-STABLE, but so far it > seems like as long as there haven't been any major API changes or other > shufflings between what's on the machine and the release being built, it > Just Worked (TM).) > You're right, it wasn't required even before. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age msg37739/pgp0.pgp Description: PGP signature
Re: cvs commit: src Makefile Makefile.inc1 src/etc Makefile src/gnu/usr.bin/perl/library Makefile.inc src/release Makefile src/release/scripts catpages-make.sh doFS.sh manpages-make.sh src/secure/usr.bin/ssh Makefile src/secure/usr.sbin/sshd Makefile ...
If memory serves me right, Ruslan Ermilov wrote: > It's important to note that you no > longer need to have a today's world to build a today's release. > I.e., if you built world a month ago, and didn't touch /usr/src > since, and /usr/obj has "buildworld" output for this /usr/src, > and you have booted with this world, it should be okay to start > building today's release. I'm not sure I understand this comment. Why was there a requirement to have today's /usr/src and /usr/obj before starting a release? (Most of my release-building experience is with 4-STABLE, but so far it seems like as long as there haven't been any major API changes or other shufflings between what's on the machine and the release being built, it Just Worked (TM).) Thanks, Bruce. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src Makefile Makefile.inc1 src/etc Makefile src/gnu/usr.bin/perl/library Makefile.inc src/release Makefile src/release/scripts catpages-make.sh doFS.sh manpages-make.sh src/secure/usr.bin/ssh Makefile src/secure/usr.sbin/sshd Makefile ...
On Fri, Apr 26, 2002 at 09:26:34PM +0300, Ruslan Ermilov wrote: > I tested this on i386 only with 2 days old -CURRENT (today's is > broken due to the import of latest IPFilter suite), and just to > make sure I didn't screw other arches I'd appreciate a feedback > from Alpha hardware owners. It's important to note that you no > longer need to have a today's world to build a today's release. > I.e., if you built world a month ago, and didn't touch /usr/src > since, and /usr/obj has "buildworld" output for this /usr/src, > and you have booted with this world, it should be okay to start > building today's release. I even suspect that you can now use > the -STABLE box to build -CURRENT release (but still the same > arch). [...] Correction. Make sure you cd /usr/src/release && \ make -f /path/to/-CURRENT/usr/src/release/Makefile \ [re]release ... before trying to build -CURRENT release on your -STABLE box. -STABLE's release/Makefile has some incompatibilities, the most harmless of which is BUILDNAME. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age msg37737/pgp0.pgp Description: PGP signature
Re: passwd and PAM
bsd <[EMAIL PROTECTED]> writes:
> Great thanks!
You're welcome. The attached patch should fix the problem with passwd
asking root for the old password.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
//depot/user/des/pam/lib/libpam/modules/pam_unix/pam_unix.c#14 - /usr/src/lib/libpam/modules/pam_unix/pam_unix.c
--- /tmp/tmp.2741.0 Fri Apr 26 21:28:02 2002
+++ /usr/src/lib/libpam/modules/pam_unix/pam_unix.c Fri Apr 26 21:24:35 2002
@@ -313,6 +313,11 @@
PAM_LOG("PRELIM round");
+ if (getuid() == 0 &&
+ (pwd->pw_fields & _PWF_SOURCE) == _PWF_FILES)
+ /* root doesn't need the old password */
+ return (pam_set_item(pamh, PAM_OLDAUTHTOK, ""));
+
if (pwd->pw_passwd[0] == '\0'
&& pam_test_option(&options, PAM_OPT_NULLOK, NULL)) {
/*
@@ -338,7 +343,7 @@
PAM_LOG("UPDATE round");
retval = pam_get_authtok(pamh,
- PAM_AUTHTOK, &old_pass, NULL);
+ PAM_OLDAUTHTOK, &old_pass, NULL);
if (retval != PAM_SUCCESS)
return (retval);
PAM_LOG("Got old password");
Re: cvs commit: src Makefile Makefile.inc1 src/etc Makefile src/gnu/usr.bin/perl/library Makefile.inc src/release Makefile src/release/scripts catpages-make.sh doFS.sh manpages-make.sh src/secure/usr.bin/ssh Makefile src/secure/usr.sbin/sshd Makefile ...
On Fri, Apr 26, 2002 at 03:20:02PM -0400, Tom Rhodes wrote: > On Fri, 26 Apr 2002 11:59:21 -0700 > Marcel Moolenaar <[EMAIL PROTECTED]> wrote: > > > On Fri, Apr 26, 2002 at 09:26:34PM +0300, Ruslan Ermilov wrote: > > > > > I.e., if you built world a month ago, and didn't touch /usr/src > > > since, and /usr/obj has "buildworld" output for this /usr/src, > > > and you have booted with this world, it should be okay to start > > > building today's release. > > > > I share my src tree, so I almost always have a /usr/src that's not > > in sync with the /usr/obj for and on a particular machine. > > > > What goes wrong if /usr/src and /usr/obj are out of sync? > > > > -- > > Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED] > > > > Correct me if i'm wrong, but last time my obj and src was different, > and I tried a make installworld, the process returned errors of: > > file not found > > where filename was a missing file. After a cvsup and a makebuildworld, > make install world worked fine ;) > > In other words, I think you will get those errors. > That is the best scenario, but some of our share/mk targets are "broken" in that they attempt to "build" things at "install" time if they are not up-to-date. For example, SCRIPTS and FILES stuff in bsd.prog.mk suffers from this problem, and it can't be easily solved because we "abuse" the dependencies to get the correct source paths. I haven't (yet) found a way to do it "the other way". This is often reported on various mailing lists; the most frequent one is about "expr not found" while attempting to build groff fonts at "install" time. I answered this question a few zillion times. :-) Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age msg37736/pgp0.pgp Description: PGP signature
Re: cvs commit: src Makefile Makefile.inc1 src/etc Makefile src/gnu/usr.bin/perl/library Makefile.inc src/release Makefile src/release/scripts catpages-make.sh doFS.sh manpages-make.sh src/secure/usr.bin/ssh Makefile src/secure/usr.sbin/sshd Makefile ...
On Fri, Apr 26, 2002 at 11:59:21AM -0700, Marcel Moolenaar wrote: > On Fri, Apr 26, 2002 at 09:26:34PM +0300, Ruslan Ermilov wrote: > > > I.e., if you built world a month ago, and didn't touch /usr/src > > since, and /usr/obj has "buildworld" output for this /usr/src, > > and you have booted with this world, it should be okay to start > > building today's release. > > I share my src tree, so I almost always have a /usr/src that's not > in sync with the /usr/obj for and on a particular machine. > > What goes wrong if /usr/src and /usr/obj are out of sync? > The prerequisite for a successful "make release" is to "installworld" first the same world as you are currently running. This is done to create a pristine environment (with an empty /etc/make.conf, etc.) which is then chroot'ed into. Also, when I wrote "/usr/src" and "/usr/obj" I didn't mean them literally. "make world" in /my/src-5 with MAKEOBJDIRPREFIX=/his/obj and /his/obj/my/src-5 staffed with the "buildworld" output from the above should work too. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age msg37735/pgp0.pgp Description: PGP signature
Re: cvs commit: src Makefile Makefile.inc1 src/etc Makefile src/gnu/usr.bin/perl/library Makefile.inc src/release Makefile src/release/scripts catpages-make.sh doFS.sh manpages-make.sh src/secure/usr.bin/ssh Makefile src/secure/usr.sbin/sshd Makefile ...
On Fri, 26 Apr 2002 11:59:21 -0700
Marcel Moolenaar <[EMAIL PROTECTED]> wrote:
> On Fri, Apr 26, 2002 at 09:26:34PM +0300, Ruslan Ermilov wrote:
>
> > I.e., if you built world a month ago, and didn't touch /usr/src
> > since, and /usr/obj has "buildworld" output for this /usr/src,
> > and you have booted with this world, it should be okay to start
> > building today's release.
>
> I share my src tree, so I almost always have a /usr/src that's not
> in sync with the /usr/obj for and on a particular machine.
>
> What goes wrong if /usr/src and /usr/obj are out of sync?
>
> --
> Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED]
>
Correct me if i'm wrong, but last time my obj and src was different,
and I tried a make installworld, the process returned errors of:
file not found
where filename was a missing file. After a cvsup and a makebuildworld,
make install world worked fine ;)
In other words, I think you will get those errors.
--
Tom (Darklogik) Rhodes
www.FreeBSD.org -The Power To Serve
www.Pittgoth.com -Pittgoth Discussion Portal
trhodes@{Pittgoth.com, FreeBSD.org}
PGP key by www:
http://www.pittgoth.com/~darklogik/darklogik.key
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
passwd failed
I cant change my passwords anymore. $ passwd test the old password and compares the given but does not write anything to the master.passwd or somewhere else. Jan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: passwd and PAM
Great thanks! Chris On 26 Apr 2002, Dag-Erling Smorgrav wrote: > bsd <[EMAIL PROTECTED]> writes: > > My problem is that the passwd command isn't doing anything, at all. > > Already fixed, cvsup and rebuild libpam. > > > Also, if a user does have a password, with the stock setup not even root > > can change it without providing the correct previous password. This > > wasn't intentional was it? > > Yes and no. There are some complications regarding NIS. It's high on > my list of things to fix. > > DES > -- > Dag-Erling Smorgrav - [EMAIL PROTECTED] > > 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: passwd and PAM
bsd <[EMAIL PROTECTED]> writes: > My problem is that the passwd command isn't doing anything, at all. Already fixed, cvsup and rebuild libpam. > Also, if a user does have a password, with the stock setup not even root > can change it without providing the correct previous password. This > wasn't intentional was it? Yes and no. There are some complications regarding NIS. It's high on my list of things to fix. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src Makefile Makefile.inc1 src/etc Makefile src/gnu/usr.bin/perl/library Makefile.inc src/release Makefile src/release/scripts catpages-make.sh doFS.sh manpages-make.sh src/secure/usr.bin/ssh Makefile src/secure/usr.sbin/sshd Makefile ...
On Fri, Apr 26, 2002 at 09:26:34PM +0300, Ruslan Ermilov wrote: > I.e., if you built world a month ago, and didn't touch /usr/src > since, and /usr/obj has "buildworld" output for this /usr/src, > and you have booted with this world, it should be okay to start > building today's release. I share my src tree, so I almost always have a /usr/src that's not in sync with the /usr/obj for and on a particular machine. What goes wrong if /usr/src and /usr/obj are out of sync? -- Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src Makefile Makefile.inc1 src/etc Makefile src/gnu/usr.bin/perl/library Makefile.inc src/release Makefile src/release/scripts catpages-make.sh doFS.sh manpages-make.sh src/secure/usr.bin/ssh Makefile src/secure/usr.sbin/sshd Makefile ...
I tested this on i386 only with 2 days old -CURRENT (today's is
broken due to the import of latest IPFilter suite), and just to
make sure I didn't screw other arches I'd appreciate a feedback
from Alpha hardware owners. It's important to note that you no
longer need to have a today's world to build a today's release.
I.e., if you built world a month ago, and didn't touch /usr/src
since, and /usr/obj has "buildworld" output for this /usr/src,
and you have booted with this world, it should be okay to start
building today's release. I even suspect that you can now use
the -STABLE box to build -CURRENT release (but still the same
arch). doFS.sh appears to be smart enough to handle (the only
so far) incompatibility between -STABLE and -CURRENT, essential
for "make release" (vn(4) vs. md(4)). Another note. Make sure
that you kldload either vn.ko or md.ko before running "make
release", because chroot'ed environment does not have these
modules and can't autoload them. I will fix it with one line
patch to src/release/Makefile on Monday, by simply copying the
respective module from /boot/{kernel,modules}/{vn,md}.ko to
the respective place in ${CHROOTDIR}.
Make sure to "export NO_IPFILTER" before "make release" if you
want to release the today's -CURRENT. IOW, please don't spam
me with the initial "buildworld" failures -- my patch has
nothing to do with them. :-)
It also may be a real pain to use the recent -CURRENT to make
a release. "make release" with either WORLD_FLAGS=-j4 or
KERNEL_FLAGS=-j4 often fails, at random intervals and at
random places, with either SIGBUS or SIGSEGV. I even had to
restart the non-parallel "make release" three times on this
fast box. My slow box that was used as this patch's development
box (which ran "make release" stage by stage) didn't suffer from
this problem for some reason (perhaps, the breakage only shows
itself on relatively fast machines?).
On Fri, Apr 26, 2002 at 10:55:27AM -0700, Ruslan Ermilov wrote:
> ru 2002/04/26 10:55:27 PDT
>
> Modified files:
> .Makefile Makefile.inc1
> etc Makefile
> gnu/usr.bin/perl/library Makefile.inc
> release Makefile
> release/scripts catpages-make.sh doFS.sh manpages-make.sh
> secure/usr.bin/ssh Makefile
> secure/usr.sbin/sshd Makefile
> sys Makefile
> kerberos5Makefile Makefile.inc
> kerberos5/libMakefile
> kerberos5/lib/libkrb5 Makefile
> kerberos5/libexec/hprop Makefile
> kerberos5/libexec/hpropd Makefile
> kerberos5/libexec/ipropd-master Makefile
> kerberos5/libexec/ipropd-slave Makefile
> kerberos5/libexec/k5admind Makefile
> kerberos5/libexec/k5passwdd Makefile
> kerberos5/libexec/kdc Makefile
> kerberos5/usr.bin/k5admin Makefile
> kerberos5/usr.bin/k5destroy Makefile
> kerberos5/usr.bin/k5init Makefile
> kerberos5/usr.bin/k5list Makefile
> kerberos5/usr.bin/k5passwd Makefile
> kerberos5/usr.bin/k5su Makefile
> kerberos5/usr.sbin/k5stash Makefile
> kerberos5/usr.sbin/ktutil Makefile
> kerberosIV Makefile Makefile.inc
> share/mk bsd.subdir.mk
> Log:
> Milestone #1 in cross-arch make releases.
>
> Do not install games and profiled libraries to the ${CHROOTDIR}
> with the initial installworld.
>
> Eliminate the need in the second installworld. For that, make sure
> _everything_ is built in the "world" environment, using the right
> tool chain.
>
> Added SUBDIR_OVERRIDE helper stuff to Makefile.inc1. Split the
> buildworld process into stages, and skip some stages when
> SUBDIR_OVERRIDE is set (used to build crypto, krb4, and krb5
> dists).
>
> Added NO_MAKEDB_RUN knob to Makefile.inc1 to avoid running
> makewhatis(1) at the end of installworld (used when making crypto,
> krb4, and krb5 dists).
>
> In release/scripts/doFS.sh, ensure that the correct boot blocks are
> used.
>
> Moved the creation of the "crypto" dist from release.5 to
> release.2.
>
> In release.3 and doMFSKERN, build kernels in the "world"
> environment. KERNELS now means "additional" kernels, GENERIC is
> always built.
>
> Ensure we build crunched binaries in the "world" environment.
> Obfuscate release/Makefile some more (WMAKEENV) to achieve this.
>
> Inline createBOOTMFS target.
>
> Use already built GENERIC kernel modules to augment mfsfd's
> /stand/modules. GC doMODULES as such.
>
> Assorted fixes:
>
> Get rid of the "afterdistribute" target by moving the single use
> of it from sys/Makefile to etc/Makefile's "distribute".
>
> Makefile.inc1: apparently "etc" no longer needs to be last for
> "distribute" to succeed.
>
> gnu/usr.bin/perl/library/Makefile.inc: do not override the
> "install" and "distribute" targets, do it the "canonical" way.
>
> release/scripts/{man,cat}pages-mak
passwd and PAM
I realize this probably isn't a -current issue, but since I don't have any experience with PAM I don't know for sure if it's just me or not. My problem is that the passwd command isn't doing anything, at all. I have the stock pam setup (/etc/pam.d, /etc/pam.conf deleted after running mergemaster). Running adduser will add a user with a password in master.passwd, but running passwd will not change the password, regardless if a password exists or is null. Also, if a user does have a password, with the stock setup not even root can change it without providing the correct previous password. This wasn't intentional was it? Chris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: linux broken?
Julian Elischer wrote: > > > On Thu, 25 Apr 2002, John Baldwin wrote: > > > > > On 25-Apr-2002 Julian Elischer wrote: > > > > kldload sysvipc.ko or compile the SYSV stuff into your kernel. > > Perhaps the linux kld needs to have a module dependency on > > the sysvipc modules? > > there is no sysvipc module but this is what I tried.. > > jules# cd /boot/kernel > jules# ls sy* > sym.ko syscall_gate.ko sysvmsg.ko sysvsem.ko sysvshm.ko > jules# kldload sysvmsg > jules# kldload sysvsem > jules# kldload sysvshm > jules# kldload linux > link_elf: symbol semop undefined > kldload: can't load linux: Exec format error > jules# Like John said, there needs to be a module dependency. The dependency from linux to sysvsem (for example) is used for two things. 1) to prevent sysvsem being unloaded before linux, and 2) to add sysvsem to the symbol search order for linux. You cannot "see" symbols in other modules without registering a dependency for this reason. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[no subject]
To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
3com 3cxfe575bt
Hello – Does –CURRENT currently support the 3com 3cxfe575bt cardbus pc card? Thanks David
Re: DRM in the sys/ tree: looking for testers
Hi, It is minor problem but when I added "options DRM_DEBUG" in my kernel configuration file under /usr/src/sys/i386/conf/, I got the following error. cc -c -O -pipe -march=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstr ict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fform at-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -I../../contri b/ipfilter -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../dev/drm/i830_dma.c ../../dev/drm/i830_dma.c: In function `i830_getbuf': ../../dev/drm/i830_dma.c:1506: `current' undeclared (first use in this function) ../../dev/drm/i830_dma.c:1506: (Each undeclared identifier is reported only once ../../dev/drm/i830_dma.c:1506: for each function it appears in.) *** Error Code 1 Stop in /usr/src/sys/compile/KAWASAKI Thank you. moto kawasaki <[EMAIL PROTECTED]> From: moto kawasaki <[EMAIL PROTECTED]> Subject: Re: DRM in the sys/ tree: looking for testers Date: Fri, 26 Apr 2002 16:03:16 +0900 (JST) Message-ID: <[EMAIL PROTECTED]> kawasaki> kawasaki> Thank you very much, Mr. Eric Anholt, kawasaki> kawasaki> I have been testing your code on my PC, and found that kernel cannot kawasaki> initialize agpgart device so far. kawasaki> kawasaki> Environment: kawasaki> Dell Latitude C400 (w/ Intel 82830 aka I830MG) kawasaki> FreeBSD 4.5 STABLE (last cvsuped around 2002/Apr/24) kawasaki> XFree86 4.2.0 (using /usr/ports/x11/XFree86-4/, cvsuped on the same day) kawasaki> sysdrm-2002-04-21-tcldrm.tar.gz kawasaki> sysdrm-2002-04-20-tclmodules.tar.gz kawasaki> sysdrm-2002-04-20-tclstableconf.diff kawasaki> (following http://gladstone.uoregon.edu/~eanholt/dri/install.html) kawasaki> kawasaki> Also, please find attached several configuration files and logs. kawasaki> kawasaki> I myself am not an expert of neither FreeBSD kernel nor XFree86, kawasaki> but I am eager to become a test monkey for saving my life :-) kawasaki> kawasaki> kawasaki> Thank you very much. kawasaki> kawasaki> kawasaki> kawasaki> kawasaki> Yours, kawasaki> kawasaki> kawasaki> moto kawasaki <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Revision 1.88 of kern_linker.c breaks module loading for diskless
> On Fri, 26 Apr 2002, Brian Somers wrote: > > BS>The intent is to discover whether there's a filesystem yet (vn_open() > BS>will die horribly otherwise). > BS> > BS>My use of rootdev is (obviously) flawed. AFAICT, either rootvp > BS>or rootvnode should be used, but I can't tell the difference between > BS>the two at a glance and am lacking development resources right now > BS>(my development box seems to enjoy dropping cores too frequently to > BS>build a kernel at the moment). > BS> > BS>If somebody could test that rootvnode or rootvp are non-NULL after > BS>an NFS-mounted root is set up, I'd thankfully approve the quick > BS>fix... :*) > > dlc1# gdb -k /boot/kernel/kernel /dev/mem > (no debugging symbols found)... > IdlePTD at phsyical address 0x00392000 > initial pcb at physical address 0x082bdda0 > panic messages: > --- > --- > #0 0xc017b968 in mi_switch () > (kgdb) p rootdev > $1 = -1 > (kgdb) p rootvnode > $2 = -843452416 > (kgdb) p rootvp > $3 = -843452416 > (kgdb) > > They obviously point to the same thing and are non-NULL (root is NFS). Thanks. I've committed the change. > harti > -- > harti brandt, >http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private > [EMAIL PROTECTED] -- Brian <[EMAIL PROTECTED]><[EMAIL PROTECTED]> http://www.freebsd-services.com/ Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Revision 1.88 of kern_linker.c breaks module loading for diskless
On Fri, 26 Apr 2002, Brian Somers wrote: BS>The intent is to discover whether there's a filesystem yet (vn_open() BS>will die horribly otherwise). BS> BS>My use of rootdev is (obviously) flawed. AFAICT, either rootvp BS>or rootvnode should be used, but I can't tell the difference between BS>the two at a glance and am lacking development resources right now BS>(my development box seems to enjoy dropping cores too frequently to BS>build a kernel at the moment). BS> BS>If somebody could test that rootvnode or rootvp are non-NULL after BS>an NFS-mounted root is set up, I'd thankfully approve the quick BS>fix... :*) dlc1# gdb -k /boot/kernel/kernel /dev/mem (no debugging symbols found)... IdlePTD at phsyical address 0x00392000 initial pcb at physical address 0x082bdda0 panic messages: --- --- #0 0xc017b968 in mi_switch () (kgdb) p rootdev $1 = -1 (kgdb) p rootvnode $2 = -843452416 (kgdb) p rootvp $3 = -843452416 (kgdb) They obviously point to the same thing and are non-NULL (root is NFS). harti -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
