Re: Bootstrapping issues with groff(1)

2000-12-09 Thread Marcel Moolenaar
"Thomas D. Dean" wrote: > > # cd /usr/src/gnu/usr.bin > # make clean > # cd /usr/src > # make -DNOCLEAN world > > fixed the problem. Before, I used 'make -j36 -DNOCLEAN world'. Could > it be a problem with the Makefile in man? -DNOCLEAN is not guaranteed to work. Especially when makefiles cha

Re: Bootstrapping issues with groff(1)

2000-12-09 Thread Thomas D. Dean
I have no environment settings that relate to groff and only MANPATH that relates to man. There are no local modifications. etc/make.conf only has CFLAGS= -O -pipe HAVE_MOTIF= yes MOTIF_STATIC= yes USA_RESIDENT= YES WRKDIRPREFIX= /usr/obj/ports NO_MODULES= NO I have always

Re: Confusing error messages from shell image activation

2000-12-09 Thread Brandon D. Valentine
On Sat, 9 Dec 2000, David O'Brien wrote: >On Sat, Dec 09, 2000 at 08:28:07PM +0100, [EMAIL PROTECTED] wrote: > >> like NetBSD (and the corresponding sources under /usr/pkgsrc). > >Please stick to reasonable ideas. To move the CVS repo from ports/ to >pkgsrc/ would be totally unreasonable. I've

Re: write(2) returns error saying read only filesystem when trying to write to a partition

2000-12-09 Thread Brian F. Feldman
Bruce Evans <[EMAIL PROTECTED]> wrote: > On Fri, 8 Dec 2000, Matthew Thyer wrote: > > > Mike Smith wrote: > > > > The program works on Compaq True64 UNIX v 4.0d > > > > It also works on Solaris 7 (only tested sparc). > > > > > > > > So it seems FreeBSD is broken here. > > > > > > FreeBSD just be

Re: Confusing error messages from shell image activation

2000-12-09 Thread Garrett Wollman
< said: > There are other places where FreeBSD doesn't comply with the > appropriate standard - packages vs. FHS I have never heard of ``FHS''. What is its ANSI, FIPS, IEEE, IEC, or ISO number? -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in t

Re: /usr/local misuse (Was: Confusing error messages from shell image activation)

2000-12-09 Thread Mike Meyer
David O'Brien <[EMAIL PROTECTED]> types: > On Sat, Dec 09, 2000 at 01:59:51PM -0600, Mike Meyer wrote: > > I know. Unfortunately, support for PREFIX seems to draw more lip > > service than actual service. > I disagree. If one of the ports I maintain isn't PREFIX-clean, let me > know and it _will_

panic: vm_pageout_flush: partially dirty page

2000-12-09 Thread Philipp Mergenthaler
Hi, ever since this commit: ... dillon 2000/11/18 15:06:27 PST Modified files: sys/kern vfs_bio.c vfs_cluster.c vfs_subr.c vfs_vnops.c sys/sys buf.h vnode.h sys/ufs/ffs ffs_inode.c ffs_softdep.c sys/ufs/ufs

Re: Bootstrapping issues with groff(1)

2000-12-09 Thread Marcel Moolenaar
"Thomas D. Dean" wrote: > > >> /usr/bin/groff -S -Wall -mtty-char -man -Tascii | ... > > > > should be -mandoc > > This was generated by 'man', not me. I understand that. > There appears to be a problem in m

Re: write(2) returns error saying read only filesystem when trying to write to a partition

2000-12-09 Thread Daniel C. Sobral
Poul-Henning Kamp wrote: > > >>| Partition table | Data| > >> | Slice 1 | Slice 2 | Slice 3 | Slice 4 | > >> | Disklabel | Data | > >> | c | > >>

Re: Bootstrapping issues with groff(1)

2000-12-09 Thread Marcel Moolenaar
David O'Brien wrote: > > On Sat, Dec 09, 2000 at 12:43:24PM -0800, Marcel Moolenaar wrote: > > On the other hand, I also don't want to use mtree. > > The only thing you don't like about mtree is it changing ownership + > modes, right? Not only that. Using mtree(1) creates busloads of unnecessar

Re: /usr/local misuse (Was: Confusing error messages from shell image activation)

2000-12-09 Thread David O'Brien
On Sat, Dec 09, 2000 at 01:59:51PM -0600, Mike Meyer wrote: > I know. Unfortunately, support for PREFIX seems to draw more lip > service than actual service. I disagree. If one of the ports I maintain isn't PREFIX-clean, let me know and it _will_ be fixed. If you know others, please open a PR,

Re: Bootstrapping issues with groff(1)

2000-12-09 Thread David O'Brien
On Sat, Dec 09, 2000 at 12:43:24PM -0800, Marcel Moolenaar wrote: > On the other hand, I also don't want to use mtree. The only thing you don't like about mtree is it changing ownership + modes, right? If so, what about a new flag to mtree to make it only create directories and nothing else? -

Re: Bootstrapping issues with groff(1)

2000-12-09 Thread Thomas D. Dean
>> /usr/bin/groff -S -Wall -mtty-char -man -Tascii | ... > > should be -mandoc This was generated by 'man', not me. There appears to be a problem in man. tomdean To Unsubscribe: send mail to [EMAIL PROTECTE

Re: Bootstrapping issues with groff(1)

2000-12-09 Thread Marcel Moolenaar
"Thomas D. Dean" wrote: > > trying command: (cd /usr/share/man ; /usr/bin/zcat > /usr/share/man/man8/zzz.8.gz | /usr/bin/tbl | > /usr/bin/groff -S -Wall -mtty-char -man -Tascii | ... should be -mandoc > tr

Re: Bootstrapping issues with groff(1)

2000-12-09 Thread Thomas D. Dean
# ls /usr/share/man/man*/zzz* /usr/share/man/man8/zzz.8.gz # ls /usr/share/man/cat*/zzz* ls: No match. Ok, so, man zzz should reformat the man page. I have attached the output of 'man -d zzz' and 'man zzz' After 'man zzz', I see # ls /usr/share/man/cat*/zzz* /usr/share/man/cat8/zzz.8.gz So, t

Re: Lucent Orinoco Gold PCCard?

2000-12-09 Thread Pete Carah
There is also a new access point (either just available or "RSN") from Zyxel (316); it is a combination of a 310 (cable modem/bridged DSL/PPPOE router) and single-card bridged access point. I'm using one at work (overkill since I'm not using the router) as a bridged access point; it works just f

Re: Confusing error messages from shell image activation

2000-12-09 Thread Jordan Hubbard
Not likely to happen - people have an investment in the current scheme and it would certainly mess with their heads if one day FreeBSD suddenly started doing something entirely different than what it's been doing for the last 7 years. For those who really want to track the NetBSD way of doing thi

Re: Bootstrapping issues with groff(1)

2000-12-09 Thread Marcel Moolenaar
"Thomas D. Dean" wrote: > > Is this the problem I see with mal-formatted man pages? Possibly. I don't know if we changed files to get our sources working with the new groff(1). If we did, we definitely have a bootstrapping problem, because that would mean that we can't reliably create manpages w

Re: Bootstrapping issues with groff(1)

2000-12-09 Thread Thomas D. Dean
Is this the problem I see with mal-formatted man pages? The pages appear as 1 block with no headers, tities, etc. tomdean To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: Bootstrapping issues with groff(1)

2000-12-09 Thread Marcel Moolenaar
Ruslan Ermilov wrote: > > On Fri, Dec 08, 2000 at 06:17:52PM -0800, Marcel Moolenaar wrote: > > Ruslan Ermilov wrote: > > > > > > The attached patches (p4 and p5) try to solve this bootstrapping > > > problem with groff(1). I have lightly tested this on my -stable > > > box, and would appreciate

Re: Bootstrapping issues with groff(1)

2000-12-09 Thread Marcel Moolenaar
Ruslan Ermilov wrote: > > On Fri, Dec 08, 2000 at 06:22:09PM -0800, Marcel Moolenaar wrote: > > Ruslan Ermilov wrote: > > > > > > The attached patches (p4 and p5) try to solve this bootstrapping > > > problem with groff(1). > > > > Sorry, I missed this statement before. What exactly are the > > b

/usr/local misuse (Was: Confusing error messages from shell image activation)

2000-12-09 Thread Mike Meyer
Will Andrews <[EMAIL PROTECTED]> types: > On Sat, Dec 09, 2000 at 08:21:28PM +0100, [EMAIL PROTECTED] wrote: > > Agreed. It would be nice if FreeBSD could use the same system as NetBSD, > > storing the packages/ports under /usr/pkg. > That's why PREFIX exists. I know. Unfortunately, support for P

Re: Problem With Man Formatting

2000-12-09 Thread Thomas D. Dean
I dropped off the list for a day, or so, during an ISP change. Did I miss a resolution? # ls -l `which groff` -r-xr-xr-x 1 root wheel 62860 Dec 7 00:01 /usr/bin/groff* # groff -v GNU troff version 1.16.1 #ls -l `which man` -r-sr-xr-x 1 man wheel 28576 Dec 7 00:01 /usr/bin/man* # man -

Re: Confusing error messages from shell image activation

2000-12-09 Thread David O'Brien
On Sat, Dec 09, 2000 at 08:28:07PM +0100, [EMAIL PROTECTED] wrote: > like NetBSD (and the corresponding sources under /usr/pkgsrc). Please stick to reasonable ideas. To move the CVS repo from ports/ to pkgsrc/ would be totally unreasonable. To Unsubscribe: send mail to [EMAIL PROTECTED] with

Re: Confusing error messages from shell image activation

2000-12-09 Thread Will Andrews
On Sat, Dec 09, 2000 at 08:28:07PM +0100, [EMAIL PROTECTED] wrote: > Okay, let me rephrase: It would be nice if FreeBSD *by default* stored > the packages/ports under /usr/pkg, like NetBSD (and the corresponding > sources under /usr/pkgsrc). Well, that is one tradition that we'll be breaking if o

Re: Confusing error messages from shell image activation

2000-12-09 Thread sthaug
> > Agreed. It would be nice if FreeBSD could use the same system as NetBSD, > > storing the packages/ports under /usr/pkg. > > That's why PREFIX exists. Okay, let me rephrase: It would be nice if FreeBSD *by default* stored the packages/ports under /usr/pkg, like NetBSD (and the corresponding s

Re: Confusing error messages from shell image activation

2000-12-09 Thread Will Andrews
On Sat, Dec 09, 2000 at 08:21:28PM +0100, [EMAIL PROTECTED] wrote: > Agreed. It would be nice if FreeBSD could use the same system as NetBSD, > storing the packages/ports under /usr/pkg. That's why PREFIX exists. -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-

Re: Confusing error messages from shell image activation

2000-12-09 Thread sthaug
> Rant second: FreeBSD *violates* years of traditions with it's > treatment of /usr/local. /usr/local is for *local* things, not add-on > software packages! Coopting /usr/local for non-local software creates > needless complexity and confusion, which of course leads to needless > pain. Agreed. It

Re: Lucent Orinoco Gold PCCard?

2000-12-09 Thread Warner Losh
In message <[EMAIL PROTECTED]> Christopher Masto writes: : > If you're only 10 feet from the base, save several hundred dollars and buy : > a 4 meter patch cable. : : Thanks, that hadn't occurred to me. It depends on the 10' :-) My laptop roams between 3' and 75' of my closest outlet. Usually

Re: Confusing error messages from shell image activation

2000-12-09 Thread Mike Meyer
Brandon D. Valentine <[EMAIL PROTECTED]> types: > >There are other places where FreeBSD doesn't comply with the > >appropriate standard - packages vs. FHS, for instance. I claim that > We don't seek to comply with the arbitrarily devised linux filesystem > standard. We comply with hier(5), a stan

Re: Confusing error messages from shell image activation

2000-12-09 Thread Brandon D. Valentine
On Sat, 9 Dec 2000, Brandon D. Valentine wrote: >On Sat, 9 Dec 2000, Mike Meyer wrote: > >>There are other places where FreeBSD doesn't comply with the >>appropriate standard - packages vs. FHS, for instance. I claim that > >We don't seek to comply with the arbitrarily devised linux filesystem >s

Re: Confusing error messages from shell image activation

2000-12-09 Thread Brandon D. Valentine
On Sat, 9 Dec 2000, Mike Meyer wrote: >There are other places where FreeBSD doesn't comply with the >appropriate standard - packages vs. FHS, for instance. I claim that We don't seek to comply with the arbitrarily devised linux filesystem standard. We comply with hier(5), a standard steeped in

Re: Confusing error messages from shell image activation

2000-12-09 Thread Mike Meyer
Garrett Wollman <[EMAIL PROTECTED]> types: > < said: > > Um - compliance with what, exactly? > IEEE Std.1003.1-1990 et seq. Since no one has bothered to close this PR with a note that this noncompliance is unacceptable, I'm assuming that no one considers it so. Further, it's not clear that FreeBS

Re: Lucent Orinoco Gold PCCard?

2000-12-09 Thread Christopher Masto
On Sat, Dec 09, 2000 at 11:10:05AM -0700, Wes Peters wrote: > > > They're the same thing in different cases, it's hard to see how one can > > > be superior in any way other than price. > > > > "The most stupid thing was that you couldn't set its network name to > > anything other than its serial

Re: Lucent Orinoco Gold PCCard?

2000-12-09 Thread Wes Peters
Christopher Masto wrote: > > On Fri, Dec 08, 2000 at 11:23:00PM -0700, Wes Peters wrote: > > > I am told that the Apple "AirPort Base Station", which is $399, works > > > well and can be configured with the Java-based thing in the ports > > > collection. I am further told that the Lucent/ORiNOCO

Re: Bootstrapping issues with groff(1)

2000-12-09 Thread Ruslan Ermilov
On Fri, Dec 08, 2000 at 06:22:09PM -0800, Marcel Moolenaar wrote: > Ruslan Ermilov wrote: > > > > The attached patches (p4 and p5) try to solve this bootstrapping > > problem with groff(1). > > Sorry, I missed this statement before. What exactly are the > bootstrapping problems you're seeing? >

$B%Q%A%s%3E9$N=P6L4IM}$NHkL)$G$9(B

2000-12-09 Thread mailtest
$B%Q%A%s%3E9$N=P6L4IM}$NHkL)$G$9(B$B%Q%A%s%3E9$G$N!VBgEv$?$j!W$O%7%^$NItJ,ItJ,$K=8CDH/@8$7$^$9!#!JK\Ev$G$9!#!K(B$B$"$J$?$O$=$N;v$B$J$   $B%Q%A%s%3$r$5$l$kJ}$O@'Hs!"$3$N%[!<%`%Z!<%8$r$4Mw$/$@$5$$!#(B$B!VBgEv$?$j$N;EAH$_!W$d!"%Q%A%s%3E9$N!V=P6L4IM}$N;EAH$_!W$NHkL)$rH=$j$d$9$/@b(B$BL@$7$

Re: Bootstrapping issues with groff(1)

2000-12-09 Thread Ruslan Ermilov
On Fri, Dec 08, 2000 at 06:17:52PM -0800, Marcel Moolenaar wrote: > Ruslan Ermilov wrote: > > > > The attached patches (p4 and p5) try to solve this bootstrapping > > problem with groff(1). I have lightly tested this on my -stable > > box, and would appreciate a feedback on them. > > Do not rem

Re: Progress report: Multilingual sysinstall for -current

2000-12-09 Thread Michael C . Wu
On Sat, Dec 09, 2000 at 11:36:26AM +0900, Tatsumi Hosokawa scribbled: | At Wed, 6 Dec 2000 18:18:50 -0600, | Michael C . Wu <[EMAIL PROTECTED]> wrote: | > | > Do you have Alpha boot floppies? Does kons25/big5con/korean compile | > on Alpha? Would this fit on our ever growing mfsroot.flp and kern