Re: Problems in VM structure ?

1999-02-16 Thread Matthew Dillon
:maxusers   256

Try reducing maxusers to 128.  Another person reported similar behavior
to me and after a bunch of work he tried going back to a basic 
distribution -- and everything started working again.

It turned out that a maxusers value of 256 and 512 were causing his machine
to go poof, but a maxusers value of 128 worked fine.

I haven't tracked the problem down yet.  Please try reducing your maxusers
to 128 and email the results to current.

-Matt


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message


sysinstall - ALT F2 black screen

1999-02-16 Thread Christoph Kukulies

I'm installing on a ASUS P55T2P4 again on an IBM DHEA 38451 with the
3.0 STABLE install floppies. 

Making filesystem on wd0s1f took quite long and did not end. Trying to
switch to the DEBUG screen (ALT F2) gives me a black screen.

Anyone seen this?

Or is my hardware still screwed? Not finding the wdc controllers
in previous efforts was caused by some special wiring the colleague added
to disable the hard disks by a switch on the front panel (which took
off power from the hard drive while leaving it cabled to the controller).


-- 
Chris Christoph P. U. Kukulies k...@gil.physik.rwth-aachen.de


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message


CTM deltas have stopped 3 days ago

1999-02-16 Thread Matthew Thyer
Is something broken or is there a reason for this ?

I normally get src-cur and ports-cur.

/=\
|Work: matthew.th...@dsto.defence.gov.au | Home: thy...@camtech.net.au|
\=/
If it is true that our Universe has a zero net value for all conserved
quantities, then it may simply be a fluctuation of the vacuum of some
larger space in which our Universe is imbedded. In answer to the
question of why it happened, I offer the modest proposal that our
Universe is simply one of those things which happen from time to time.
 E. P. Tryon   from Nature Vol.246 Dec.14, 1973



To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message


Re: Problems in VM structure ?

1999-02-16 Thread Brian Feldman
On Tue, 16 Feb 1999, Matthew Dillon wrote:

 :maxusers 256
 
 Try reducing maxusers to 128.  Another person reported similar behavior
 to me and after a bunch of work he tried going back to a basic 
 distribution -- and everything started working again.
 
 It turned out that a maxusers value of 256 and 512 were causing his 
 machine
 to go poof, but a maxusers value of 128 worked fine.
 
 I haven't tracked the problem down yet.  Please try reducing your maxusers
 to 128 and email the results to current.

For what it's worth, my maxusers is 250 and my system is quite stable, even
during a make -j25 buildworld.

 
   -Matt
 
 
 To Unsubscribe: send mail to majord...@freebsd.org
 with unsubscribe freebsd-current in the body of the message
 

 Brian Feldman_ __  ___ ___ ___  
 gr...@unixhelp.org   _ __ ___ | _ ) __|   \ 
 http://www.freebsd.org/ _ __ ___  | _ \__ \ |) |
 FreeBSD: The Power to Serve!  _ __ ___  _ |___/___/___/ 


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message


Re: Problems in VM structure ?

1999-02-16 Thread Khetan Gajjar
On Tue, 16 Feb 1999, Matthew Dillon wrote:

MD  Try reducing maxusers to 128.  Another person reported similar behavior
MD  to me and after a bunch of work he tried going back to a basic 
MD  distribution -- and everything started working again.

Hmmm, ok.

MD  It turned out that a maxusers value of 256 and 512 were causing his 
machine
MD  to go poof, but a maxusers value of 128 worked fine.

Ok. I'm glad, in a way, that I'm not the only one seeing
this.

The really weird thing though is that since reporting the problem,
it hasn't re-occured. If it occurs again, I'll mail the results of
the gdb -core /var/crash/blah, a trace and then try reducing the
number of maxusers.

This is the longest uptime I've had in almost two weeks - 14 hours.
Here's hoping :)

MD  I haven't tracked the problem down yet.  Please try reducing your 
maxusers
MD  to 128 and email the results to current.

If the problem re-occurs, I'll do so :)
---
Khetan Gajjar   (!kg1779) * khe...@iafrica.com ; khe...@os.org.za
http://www.os.org.za/~khetan  * Talk/Finger khe...@chain.freebsd.os.org.za
FreeBSD enthusiast* http://www2.za.freebsd.org/
Security-wise, NT is a OS with a kick me sign taped to it


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message


/etc/defaults/rc.conf

1999-02-16 Thread Luoqi Chen
Initially I though /etc/defaults/rc.conf stored the default settings and then
we could override some of the settings in /etc/rc.conf, but after a close
look at how they are used in /etc/rc*, I am confused:

if [ -f /etc/defaults/rc.conf ]; then
. /etc/defaults/rc.conf
elif [ -f /etc/rc.conf ]; then
. /etc/rc.conf
fi

If I have a /etc/defaults/rc.conf, then my /etc/rc.conf won't be consulted.
So what is the purpose of /etc/defaults/rc.conf?

-lq

To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message


Re: Suggestion for elf upgrade

1999-02-16 Thread Chris Costello
On Sun, Feb 14, 1999, Stephen Montgomery-Smith put this into my mailbox:
 Yesterday I did an upgrade from 3.0-Release to 3.1-beta.  I did
 make world, then I made the kernel.  At the end of the make kernel,
 I got a message about the kernel being elf!!!  Bad timing to find
 out about this - I was told to look at
 http://www.freebsd.org/~peter/elfday.html
 and by this time, the code mismatch between the binary executables
 and the kernel made netscape unusable.  Good thing I
 wasn't upgrading from 2.2.x, maybe then I could not have even installed
 lynx or Mosaic to get the info I needed.

   Odd.  Netscape runs for me.  I have an ELF kernel and the new bootblocks,
and obviously a new ELF world.

[ch...@holly ~] $ uname -srm
FreeBSD 3.1-RELEASE i386

 
 Well, I did get it figured out.  But I have one suggestion for the
 web page
 http://www.freebsd.org/~peter/elfday.html
 
 It told me that I needed new bootblocks.  I think a paragraph explanation
 of what bootblocks is would have helped a very great deal.  As it was
 it was like telling me to wear a nuffle on my head when it is cold.
 Like, what is a nuffle?  So what is a bootblock?  I did figure
 out enough to get it to work  (I am guessing that a bootblock is
 some code at the beginning of each slice that is loaded by booteasy).

   I believe the boot blocks contain the software required to access the disk
and boot the kernel.  Obviously you'd need new boot blocks if you'll be
trying to run a kernel that the 2.2 blocks don't understand.

-- 
SIGBUS Bus error (passengers dumped)

To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message


Re: /etc/defaults/rc.conf

1999-02-16 Thread sthaug
 Initially I though /etc/defaults/rc.conf stored the default settings and then
 we could override some of the settings in /etc/rc.conf, but after a close
 look at how they are used in /etc/rc*, I am confused:
 
   if [ -f /etc/defaults/rc.conf ]; then
   . /etc/defaults/rc.conf
   elif [ -f /etc/rc.conf ]; then
   . /etc/rc.conf
   fi

Check out the tail end of /etc/defaults/rc.conf - you'll find it sources
/etc/rc.conf (or /etc/rc.conf.local).

Steinar Haug, Nethelp consulting, sth...@nethelp.no

To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message


Re: CTM deltas have stopped 3 days ago

1999-02-16 Thread Mark Murray
Matthew Thyer wrote:
 Is something broken or is there a reason for this ?
 
 I normally get src-cur and ports-cur.

This normally happens after a tagging operation; sites take a _helluva_ long
time to catch up and create the diffs.

M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org

To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message


Re: Suggestion for elf upgrade

1999-02-16 Thread Stephen Montgomery-Smith
I think that you misunderstood my message.  The problems I was having
were not with the final state of the machine, but with the intermediate
stages.

Chris Costello wrote:
 
 On Sun, Feb 14, 1999, Stephen Montgomery-Smith put this into my mailbox:
  ...
  and by this time, the code mismatch between the binary executables
  and the kernel made netscape unusable.  
 
Odd.  Netscape runs for me.  I have an ELF kernel and the new bootblocks,
 and obviously a new ELF world.

The problem was I was stuck with 3.1 code, but an old 3.0 kernel.  I needed
netscape or some other browser to get to the web site to figure out how
to get the new 3.1 kernel going, and the mismatch meant that I could not
use netscape.  My point was that if I had known about this web site BEFORE
I started the make world, then it would have been much easier to extract the
needed info.

Now I finally got the 3.1 kernel going, netscape works fine.

  It told me that I needed new bootblocks.  I think a paragraph explanation
  of what bootblocks is would have helped a very great deal.  As it was
  it was like telling me to wear a nuffle on my head when it is cold.
  Like, what is a nuffle?  So what is a bootblock?  I did figure
  out enough to get it to work  (I am guessing that a bootblock is
  some code at the beginning of each slice that is loaded by booteasy).
 
I believe the boot blocks contain the software required to access the disk
 and boot the kernel.  Obviously you'd need new boot blocks if you'll be
 trying to run a kernel that the 2.2 blocks don't understand.

Yes, I did figure out that much.  But without understanding bootblocks in
context, I was unsure what exactly I was looking for.  I think that the
web page http://www.freebsd.org/~peter/elfday.html
would have been better if the link to http://www.freebsd.org/~rnordier/boot.txt
had been somewhere prominent at the top of
http://www.freebsd.org/~peter/elfday.html ,
and a small paragraph explaining what bootblocks is would have helped put the
whole thing in context.

My issue is not with the final product, which is fantastic.  Rather I am
making some suggested changes to the way the information is being put out.
Really, they are only suggestions.  I think that the FreeBSD team do a very good
job.  I just wanted to offer my feedback on the technical writing aspect.


-- 

Stephen Montgomery-Smith  step...@math.missouri.edu
307 Math Science Building step...@showme.missouri.edu
Department of Mathematics step...@missouri.edu
University of Missouri-Columbia
Columbia, MO 65211
USA

Phone (573) 882 4540
Fax   (573) 882 1869

http://math.missouri.edu/~stephen

To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message


Re: Problems in VM structure ?

1999-02-16 Thread John Fieber
On Tue, 16 Feb 1999, Matthew Dillon wrote:

 Try reducing maxusers to 128.  Another person reported similar behavior
 to me and after a bunch of work he tried going back to a basic 
 distribution -- and everything started working again.
 
 It turned out that a maxusers value of 256 and 512 were causing his 
 machine
 to go poof, but a maxusers value of 128 worked fine.

Another datapoint, Sybase goes poof with maxusers set to 64 or
higher.  This has been the case since before 3.0 was released.

-john


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message


Re: /etc/defaults/rc.conf

1999-02-16 Thread Richard Seaman, Jr.
On Tue, Feb 16, 1999 at 09:04:11AM -0500, Luoqi Chen wrote:
 Initially I though /etc/defaults/rc.conf stored the default settings and then
 we could override some of the settings in /etc/rc.conf, but after a close
 look at how they are used in /etc/rc*, I am confused:
 
   if [ -f /etc/defaults/rc.conf ]; then
   . /etc/defaults/rc.conf
   elif [ -f /etc/rc.conf ]; then
   . /etc/rc.conf
   fi
 
 If I have a /etc/defaults/rc.conf, then my /etc/rc.conf won't be consulted.
 So what is the purpose of /etc/defaults/rc.conf?

Doesn't /etc/defaults/rc.conf pull in /etc/rc.conf ?  It appears to here.

-- 
Richard Seaman, Jr.   email: d...@tar.com
5182 N. Maple Lanephone: 414-367-5450
Chenequa WI 53058 fax:   414-367-5852

To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message


Re: Suggestion for elf upgrade

1999-02-16 Thread Chris Costello
On Tue, Feb 16, 1999, Stephen Montgomery-Smith put this into my mailbox:

 My issue is not with the final product, which is fantastic.  Rather I am
 making some suggested changes to the way the information is being put out.
 Really, they are only suggestions.  I think that the FreeBSD team do a very 
 good
 job.  I just wanted to offer my feedback on the technical writing aspect.

   Oh.  Sorry.  Yeah, it had me kinda confused and lost for a while, until I
really read each and every word about 3 million times.  Perhaps, sometime soon,
it should be edited and put in the handbook.

   Just my $19.99 ($15.99 if you order by mail).

-Chris

To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: Problesm w/ 4.0-current wine

1999-02-16 Thread Mike Smith
  Wrong again.  boot0 is in the MBR, boot1 and boot2 are the bootstrap; 
  all by Robert.  The loader, OTOH, uses Robert's BTX code, Ficl, and a 
  lot of code derived by me from the NetBSD standalone loader.
 
 Boot2 is, as you say, correctly identified as the bootstrap, however you
 cannot deny that boot2 is a kernel loader as it can load a pure executable
 (a.out kernel or /boot/loader) or an ELF kernel.

It's the bootstrap.  Yes, it can load kernels, but it is not referred 
to as the kernel loader (that's what the loader is).

   The BTX loader does have a prompt by default and if you interrupt the
   countdown. The prompt is, of course, Forth :)
  
  The BTX loader doesn't have a prompt at all.  The kernel loader has a 
  prompt, and the prompt is not written in Forth (yet).
 
 By BTX loader I refer to the BTX kernel and system which can bootstrap
 a kernel and load modules.

There's already a perfectly good piece of code called the BTX Loader 
(btxldr); it's not appropriate to misapply this name to the loader 
proper.

 The prompt isn't OF Forth, I stated that the prompt TAKES Forth; perhaps I
 could have said that better.

You meant that the prompt takes Forth, perhaps. 8)

-- 
\\  Sometimes you're ahead,   \\  Mike Smith
\\  sometimes you're behind.  \\  m...@smith.net.au
\\  The race is long, and in the  \\  msm...@freebsd.org
\\  end it's only with yourself.  \\  msm...@cdrom.com



To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Buildworld fails on today 3.1-STABLE!

1999-02-16 Thread Maxim Sobolev
Here is output (checked 2 times) :(
?

=== share/doc/psd/title
touch _stamp.extraobjs
(cd /usr/obj/src/share/doc/psd/title; groff -mtty-char -Tascii -ms -o1-
/usr/obj/src/share/doc/psd/title/Title) |? gzip -cn  Title.ascii.gz
groff: can't find `DESC' file
groff:fatal error: invalid device `ascii'
=== share/doc/psd/contents
touch _stamp.extraobjs
(cd /usr/obj/src/share/doc/psd/contents; groff -mtty-char -Tascii -ms
-o1- /usr/obj/src/share/doc/psd/contents/contents.ms) |? gzip -cn 
contents.ascii.gz
groff: can't find `DESC' file
groff:fatal error: invalid device `ascii'
=== share/doc/psd/05.sysman
touch _stamp.extraobjs
(cd /usr/obj/src/share/doc/psd/05.sysman; groff -mtty-char -Tascii -t
-ms -o1- /usr/obj/src/share/doc/psd/05.sysman/0.t
/usr/obj/src/share/doc/psd/05.sysman/1.0.t
/usr/obj/src/share/doc/psd/05.sysman/1.1.t
/usr/obj/src/share/doc/psd/05.sysman/1.2.t
/usr/obj/src/share/doc/psd/05.sysman/1.3.t
/usr/obj/src/share/doc/psd/05.sysman/1.4.t
/usr/obj/src/share/doc/psd/05.sysman/1.5.t
/usr/obj/src/share/doc/psd/05.sysman/1.6.t
/usr/obj/src/share/doc/psd/05.sysman/1.7.t
/usr/obj/src/share/doc/psd/05.sysman/2.0.t
/usr/obj/src/share/doc/psd/05.sysman/2.1.t
/usr/obj/src/share/doc/psd/05.sysman/2.2.t
/usr/obj/src/share/doc/psd/05.sysman/2.3.t
/usr/obj/src/share/doc/psd/05.sysman/2.4.t
/usr/obj/src/share/doc/psd/05.sysman/2.5.t
/usr/obj/src/share/doc/psd/05.sysman/a.t) |? gzip -cn  paper.ascii.gz
groff: can't find `DESC' file
groff:fatal error: invalid device `ascii'
=== share/doc/psd/12.make
touch _stamp.extraobjs
(cd /usr/obj/src/share/doc/psd/12.make/../../../../usr.bin/make/PSD.doc;
groff -mtty-char -Tascii -ms -o1-
/usr/obj/src/share/doc/psd/12.make/../../../../usr.bin/make/PSD.doc/tutorial.ms)
|? gzip -cn  paper.ascii.gz
groff: can't find `DESC' file
groff:fatal error: invalid device `ascii'
=== share/doc/psd/13.rcs
=== share/doc/psd/13.rcs/rcs
touch _stamp.extraobjs
(cd
/usr/obj/src/share/doc/psd/13.rcs/rcs/../../../../../gnu/usr.bin/rcs/doc;
groff -mtty-char -Tascii -p -ms -o1-
/usr/obj/src/share/doc/psd/13.rcs/rcs/../../../../../gnu/usr.bin/rcs/doc/rcs.ms)
|? gzip -cn  paper.ascii.gz
groff: can't find `DESC' file
groff:fatal error: invalid device `ascii'
=== share/doc/psd/13.rcs/rcs_func
touch _stamp.extraobjs
(cd
/usr/obj/src/share/doc/psd/13.rcs/rcs_func/../../../../../gnu/usr.bin/rcs/doc;
groff -mtty-char -Tascii -ms -o1-
/usr/obj/src/share/doc/psd/13.rcs/rcs_func/../../../../../gnu/usr.bin/rcs/doc/rcs_func.ms)
|? gzip -cn  rcs_func.ascii.gz
groff: can't find `DESC' file
groff:fatal error: invalid device `ascii'
=== share/doc/psd/18.gprof
touch _stamp.extraobjs
(cd
/usr/obj/src/share/doc/psd/18.gprof/../../../../usr.bin/gprof/PSD.doc;
groff -mtty-char -Tascii -e -t -p -s -me -o1-
/usr/obj/src/share/doc/psd/18.gprof/../../../../usr.bin/gprof/PSD.doc/header.me
/usr/obj/src/share/doc/psd/18.gprof/../../../../usr.bin/gprof/PSD.doc/abstract.me
/usr/obj/src/share/doc/psd/18.gprof/../../../../usr.bin/gprof/PSD.doc/intro.me
/usr/obj/src/share/doc/psd/18.gprof/../../../../usr.bin/gprof/PSD.doc/profiling.me
/usr/obj/src/share/doc/psd/18.gprof/../../../../usr.bin/gprof/PSD.doc/gathering.me
/usr/obj/src/share/doc/psd/18.gprof/../../../../usr.bin/gprof/PSD.doc/postp.me
/usr/obj/src/share/doc/psd/18.gprof/../../../../usr.bin/gprof/PSD.doc/present.me
/usr/obj/src/share/doc/psd/18.gprof/../../../../usr.bin/gprof/PSD.doc/refs.me)
|? gzip -cn  paper.ascii.gz
groff: can't find `DESC' file
groff:fatal error: invalid device `ascii'
=== share/doc/psd/19.curses
/usr/libexec/vfontedpr
/usr/obj/src/share/doc/psd/19.curses/../../../../lib/libcurses/PSD.doc/ex1.c
| grep -v ^'wh  ex1.gr
/usr/libexec/vfontedpr
/usr/obj/src/share/doc/psd/19.curses/../../../../lib/libcurses/PSD.doc/twinkle1.c
| grep -v ^'wh  twinkle1.gr
tbl
/usr/obj/src/share/doc/psd/19.curses/../../../../lib/libcurses/PSD.doc/intro.2
 intro.2.tbl
tbl:/usr/obj/src/share/doc/psd/19.curses/../../../../lib/libcurses/PSD.doc/intro.2:40:
`tab' option requires argument in parentheses
touch _stamp.extraobjs
sed -e\ 's:\(\.so[\ \ ][\ \
]*\)\(Master\)$:\1/usr/obj/src/share/doc/psd/19.curses/../../../../lib/libcurses/PSD.doc/\2:'
-e\ 's:\(\.so[\ \ ][\ \
]*\)\(intro.0\)$:\1/usr/obj/src/share/doc/psd/19.curses/../../../../lib/libcurses/PSD.doc/\2:'
-e\ 's:\(\.so[\ \ ][\ \
]*\)\(intro.1\)$:\1/usr/obj/src/share/doc/psd/19.curses/../../../../lib/libcurses/PSD.doc/\2:'
-e\ 's:\(\.so[\ \ ][\ \
]*\)\(intro.3\)$:\1/usr/obj/src/share/doc/psd/19.curses/../../../../lib/libcurses/PSD.doc/\2:'
-e\ 's:\(\.so[\ \ ][\ \
]*\)\(intro.4\)$:\1/usr/obj/src/share/doc/psd/19.curses/../../../../lib/libcurses/PSD.doc/\2:'
-e\ 's:\(\.so[\ \ ][\ \
]*\)\(intro.5\)$:\1/usr/obj/src/share/doc/psd/19.curses/../../../../lib/libcurses/PSD.doc/\2:'
-e\ 's:\(\.so[\ \ ][\ \
]*\)\(intro.6\)$:\1/usr/obj/src/share/doc/psd/19.curses/../../../../lib/libcurses/PSD.doc/\2:'
-e\ 's:\(\.so[\ \ ][\ \
]*\)\(macros\)$:\1/usr/obj/src/share/doc/psd/19.curses/../../../../lib/libcurses/PSD.doc/\2:'
-e\ 's:\(\.so[\ \ ][\ \

Re: Problems in VM structure ?

1999-02-16 Thread John S. Dyson
Matthew Dillon said:
 :maxusers 256
 
 Try reducing maxusers to 128.  Another person reported similar behavior
 to me and after a bunch of work he tried going back to a basic 
 distribution -- and everything started working again.
 
 It turned out that a maxusers value of 256 and 512 were causing his 
 machine
 to go poof, but a maxusers value of 128 worked fine.
 
 I haven't tracked the problem down yet.  Please try reducing your maxusers
 to 128 and email the results to current.
 
Likely because data structures are getting too big.  The kernel is limited
to (I forget) how big in VA space.

-- 
John  | Never try to teach a pig to sing,
dy...@iquest.net  | it makes one look stupid
jdy...@nc.com | and it irritates the pig.

To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: /etc/defaults/rc.conf

1999-02-16 Thread Jordan K. Hubbard
 If I have a /etc/defaults/rc.conf, then my /etc/rc.conf won't be consulted.

Wrong.  You need to read just a bit FURTHER into that file before
jumping to such conclusions. :-)

- Jordan

To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



RE: Buildworld fails on today 3.1-STABLE!

1999-02-16 Thread Luke
 === share/doc/psd/title
 touch _stamp.extraobjs
 (cd /usr/obj/src/share/doc/psd/title; groff -mtty-char -Tascii -ms -o1-
 /usr/obj/src/share/doc/psd/title/Title) |_ gzip -cn  Title.ascii.gz
 groff: can't find `DESC' file
 groff:fatal error: invalid device `ascii'

This has happened to me many times with various versions of current and
3.x , and its always fixed by lowering the -O# # , I don't know why I just know
it works :). I re cvsupped several times once, and erased obj, and it always
did it until i lowered the -O.

---

E-Mail: Luke l...@aus.org
Sent by XFMail
--

To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: Buildworld fails on today 3.1-STABLE!

1999-02-16 Thread Karl Pielorz
Luke wrote:

  === share/doc/psd/title
 [snip]
  groff: can't find `DESC' file
  groff:fatal error: invalid device `ascii'
 
 This has happened to me many times with various versions of current 
 and
 3.x , and its always fixed by lowering the -O# # , I don't know why I just 
 know
 it works :). I re cvsupped several times once, and erased obj, and it always
 did it until i lowered the -O.

Thanks! - That just fixed my problem... I was going to post a similar message
along the lines of -current broken? - but you just saved me the
embarassment! :)...

I usually keep -O to just '-O' - I had been upping it recently, but then it
started breaking even some of my simple programs, so leasson learn't, it's
staying at just '-O' from now on in... (safety first? :-)

-Kp

To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: sysinstall - ALT F2 black screen

1999-02-16 Thread Mike Smith
 
 I'm installing on a ASUS P55T2P4 again on an IBM DHEA 38451 with the
 3.0 STABLE install floppies. 
 
 Making filesystem on wd0s1f took quite long and did not end. Trying to
 switch to the DEBUG screen (ALT F2) gives me a black screen.
 
 Anyone seen this?

Works fine here on an 8GB Western Digital.

 Or is my hardware still screwed? Not finding the wdc controllers
 in previous efforts was caused by some special wiring the colleague added
 to disable the hard disks by a switch on the front panel (which took
 off power from the hard drive while leaving it cabled to the controller).

Yuck. That's extra-bad.

-- 
\\  Sometimes you're ahead,   \\  Mike Smith
\\  sometimes you're behind.  \\  m...@smith.net.au
\\  The race is long, and in the  \\  msm...@freebsd.org
\\  end it's only with yourself.  \\  msm...@cdrom.com




To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: sysinstall - ALT F2 black screen

1999-02-16 Thread Christoph Kukulies
On Tue, Feb 16, 1999 at 12:26:46PM -0800, Mike Smith wrote:
  
  I'm installing on a ASUS P55T2P4 again on an IBM DHEA 38451 with the
  3.0 STABLE install floppies. 
  
  Making filesystem on wd0s1f took quite long and did not end. Trying to
  switch to the DEBUG screen (ALT F2) gives me a black screen.
  
  Anyone seen this?

Second boot and doing it all over again didn't show the black screen
and the system got installed fine fed from ftp.freebsd.org.

Thanks.

 
 Works fine here on an 8GB Western Digital.
 

-- 
Chris Christoph P. U. Kukulies k...@gil.physik.rwth-aachen.de


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: Buildworld fails on today 3.1-STABLE!

1999-02-16 Thread Mikhail Teterin
 I usually keep -O to just '-O' - I had been upping it recently, but then it
 started breaking even some of my simple programs, so leasson learn't, it's
 staying at just '-O' from now on in... (safety first? :-)

-O2 works fine too. -O3 does not. We'll probably see the newer version
of compiler before this is fixed.

-mi


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



UID for SMTP daemon

1999-02-16 Thread Sheldon Hearn

Hi folks,

I can think of two applications that offer smtp daemon services and like
to run under their own uid -- postfix and exim.

While I appreciate that Mr Bresler's import of postfix into the base
system was shot down fair and square (or perhaps just square, don't go
there), it does seem a pity that the user and group ids that he proposed
to add didn't make it.

There is already a precedent in the realm of creating users for
applications that aren't distributed with the base system -- pop (uid
68).

I couldn't give a sideways  at a rolling doughnut what the actual
name of the uid and gid are -- mta, mail, smtp, billsux, whatever. All I
want is a username that the exim port (and other ports, once there's a
trend) can assume will be present on the box.

PLEASE NOTE: I'm not interested in folks' opinions on this. I don't want
to have a discussion. I just want the uid and gid committed. I'll take
no comment as objection enough if nobody wants to commit this. Anything
else is just going to be more noise on a noisy list. :-)

Thanks,
Sheldon.


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: UID for SMTP daemon

1999-02-16 Thread Sheldon Hearn


On Wed, 17 Feb 1999 00:12:41 +0200, Sheldon Hearn wrote:

 PLEASE NOTE: I'm not interested in folks' opinions on this. I don't want
 to have a discussion. I just want the uid and gid committed.

So much for not discussing this. Sorry, all I want is the user
committed. Group mail already exists and will suffice.

Thanks,
Sheldon.


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Staroffice 5.0 under 4.0-current

1999-02-16 Thread Adhir




I'm running 4.0-current as of late last week, elf kernel.  Everything works
great - no problems.  I understand that the Linux kernel threads stuff is now in
my system by default, so I should be able to download and install StarOffice
5.0.  Others on the list have confirmed that it works.

I, however, am unable to get it running.  The setup program continually
complains about not finding the glibc2 libraries, even after I extracted them
into /compat/linux/lib and reran /compat/linux/sbin/ldconfig.

Any help would be greatly appreciated.

FWIW - Linux Wp7, and several others work just fine

Al





To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: Aladdin chipset SMBus support available!

1999-02-16 Thread Nicolas Souchu
On Sun, Feb 14, 1999 at 11:09:45PM +0100, Nicolas Souchu wrote:

On Sun, Feb 14, 1999 at 04:30:27PM -0500, Brian Feldman wrote:
 

On spd I would get an error message, and if I ever did spd 1 it got as far
as printing 128 bytes used, then erred out...

 rm alpm.o ; make CC=cc -DDEBUG

I'll rm alpm.o; CC='cc -DDEBUG' make alpm.o; make, if that's what you mean.

any difference?

I meant any difference between the two command lines?

-- 
nso...@teaser.fr / nso...@freebsd.org
FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: Aladdin chipset SMBus support available!

1999-02-16 Thread Nicolas Souchu
On Sun, Feb 14, 1999 at 07:41:25PM -0500, Brian Feldman wrote:

On Sun, 14 Feb 1999, Nicolas Souchu wrote:

 On Sun, Feb 14, 1999 at 04:30:27PM -0500, Brian Feldman wrote:
  
 
 On spd I would get an error message, and if I ever did spd 1 it got as far
 as printing 128 bytes used, then erred out...
 
  rm alpm.o ; make CC=cc -DDEBUG
 
 I'll rm alpm.o; CC='cc -DDEBUG' make alpm.o; make, if that's what you mean.
 
 any difference?

Yes:
Feb 14 17:12:16 green /kernel: alpm: idle? STS=0x0
Feb 14 17:12:48 green last message repeated 380 times
Feb 14 17:13:14 green last message repeated 5 times


The controller seems to stick on the bus. The Linux
team has reported such problems with there own driver and couldn't do
anything (reset of controller, SMBus abort...). The problem seem to have
disappeared with an additional device plugged on the bus. I'll dig into
your problem, but yet, I have no problem with the ASUS. I'll browse the
datasheets..


 
 -- 
 nso...@teaser.fr / nso...@freebsd.org
 FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org
 
 To Unsubscribe: send mail to majord...@freebsd.org
 with unsubscribe freebsd-current in the body of the message
 

 Brian Feldman   _ __  ___ ___ ___  
 gr...@unixhelp.org  _ __ ___ | _ ) __|   \ 
http://www.freebsd.org/ _ __ ___  | _ \__ \ |) |
 FreeBSD: The Power to Serve! _ __ ___  _ |___/___/___/ 



-- 
nso...@teaser.fr / nso...@freebsd.org
FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: Buildworld fails on today 3.1-STABLE!

1999-02-16 Thread Karl Pielorz


Maxim Sobolev wrote:
 
 Here is output (checked 2 times) :(

 groff: can't find `DESC' file
 groff:fatal error: invalid device `ascii'
 [super-snip]
 |  groff -mtty-char -Tascii -t -s -me -o1-  /dev/null
 groff: can't find `DESC' file
 groff:fatal error: invalid device `ascii'

Ugh, did you have to send so much output? :-) - What -O setting are you
using to build with? - Someone reported (and I've seen myself) - upping it
will cause the problems above... (I'm not saying it's the only cause, but it
got me :)

-Kp


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: Network Cards

1999-02-16 Thread Igor Nikolaev
On Thu, Feb 04, 1999 at 06:01:52AM -0500, Rod Taylor wrote:

 Suppose you have xl and vr in your computer. They are named eth0
 and eth1, respectively. You then replace your vr by a ed. Mark

 But then if I added another say ed0, it wouldn't get eth2 :)
 But yeah, I understand where you're going...

Not fully.

I service fbsd routers with up to 12 ethernet cards.
8 isa cards + 4 pci on advantech prompc computer.

And when a cableman add card to a router, 
(ctrl-alt-del, poweroff, screw card, power on)
he install card corresponded to driver name,
and set io/irq/mem corresponded to number.

-- 
Igor Nikolaev


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



RE: Problems in VM structure ?

1999-02-16 Thread tcobb
I'm seeing different responses depending on hardware.

On regular Pentium 166 machines, I almost NEVER get
a panic.  On brand-new Pentium II 350s, I get a panic
every 6-9 hours.  This happens when both kernels are
configured the same for maxusers.  It happens when
both machines are under the same load level -- the
P5 stays rock solid, the P6 flakes out.

What's the chance that our kernel adaptations for PIIs
is partly at fault?


-Troy Cobb
 Circle Net, Inc.
 http://www.circle.net

   -Original Message-
   From: Brian Feldman [mailto:gr...@unixhelp.org]
   Sent: Tuesday, February 16, 1999 7:48 AM
   To: Matthew Dillon
   Cc: Khetan Gajjar; curr...@freebsd.org
   Subject: Re: Problems in VM structure ?
   
   
   On Tue, 16 Feb 1999, Matthew Dillon wrote:
   
:maxusers 256

Try reducing maxusers to 128.  Another person 
   reported similar behavior
to me and after a bunch of work he tried going back 
   to a basic 
distribution -- and everything started working again.

It turned out that a maxusers value of 256 and 512 
   were causing his machine
to go poof, but a maxusers value of 128 worked fine.

I haven't tracked the problem down yet.  Please try 
   reducing your maxusers
to 128 and email the results to current.
   
   For what it's worth, my maxusers is 250 and my system is 
   quite stable, even
   during a make -j25 buildworld.
   

  -Matt


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message

   
Brian Feldman_ __  
   ___ ___ ___  
gr...@unixhelp.org   _ __ ___ | _ ) __|   \ 
http://www.freebsd.org/ _ __ ___  | _ \__ \ |) |
FreeBSD: The Power to Serve!  _ __ ___  _ 
   |___/___/___/ 
   
   
   To Unsubscribe: send mail to majord...@freebsd.org
   with unsubscribe freebsd-current in the body of the message
   


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



SMP and SO5.0

1999-02-16 Thread Daniel O'Connor
Hi,
I downloaded Star Office 5 and only THEN realised that the code for doing linux 
thread
emulation is #ifndef SMP :) Still, after downloading 70 meg over a 56k modem 
and paying
19c/meg I was gonna try the sucker regardless.. And well, it works!

The install hung at the end, after its done everything, so I killed it, but 
after that I
can run it with (seemingly) no problems.. (Except for the 2000 odd 'shared 
address space
fork attempted' messages in my syslog)

I only had a quick fiddle, but it started up everything fine and ran quite 
well..

The install was a pain tho, as I had to unpack the setup program (its a self 
extracting
zip) and rename the libs in it to lower case and then add an LD_LIBRARY_PATH to 
point to
them, but apart from that it was OK.

Its worth noting though, that eMusic which uses Linux threads doesn't work under
emulation (it just hangs) I think I'll boot a non-SMP kernel and have a go 
('cause it
took me an hour to find all of the $...@$ dependancies it needs because Linux 
ldd doesn't
work anymore)

---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
The nice thing about standards is that there
are so many of them to choose from.
  -- Andrew Tanenbaum


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: inode / exec_map interlock ? (follow up)

1999-02-16 Thread Alan Cox
On Tue, 16 Feb 1999, John S. Dyson wrote:

 If we can get ALC to agree, I prefer him to be the first line (but I am
 willing to fill-in and support DG and ALC when needed.)  ...

I am willing.  In the meantime, let's try to cool things down a bit.

Alan


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: Buildworld fails on today 3.1-STABLE!

1999-02-16 Thread Mike Smith
  I usually keep -O to just '-O' - I had been upping it recently, but then it
  started breaking even some of my simple programs, so leasson learn't, it's
  staying at just '-O' from now on in... (safety first? :-)
 
 -O2 works fine too. -O3 does not. We'll probably see the newer version
 of compiler before this is fixed.

No, -O2 does not work fine; we've seen reports of it breaking things 
before.

-- 
\\  Sometimes you're ahead,   \\  Mike Smith
\\  sometimes you're behind.  \\  m...@smith.net.au
\\  The race is long, and in the  \\  msm...@freebsd.org
\\  end it's only with yourself.  \\  msm...@cdrom.com




To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: SMP and SO5.0

1999-02-16 Thread Luoqi Chen
 Hi,
 I downloaded Star Office 5 and only THEN realised that the code for doing 
 linux thread
 emulation is #ifndef SMP :) Still, after downloading 70 meg over a 56k modem 
 and paying
 19c/meg I was gonna try the sucker regardless.. And well, it works!
 
 The install hung at the end, after its done everything, so I killed it, but 
 after that I
 can run it with (seemingly) no problems.. (Except for the 2000 odd 'shared 
 address space
 fork attempted' messages in my syslog)
 
 I only had a quick fiddle, but it started up everything fine and ran quite 
 well..
 
 The install was a pain tho, as I had to unpack the setup program (its a self 
 extracting
 zip) and rename the libs in it to lower case and then add an LD_LIBRARY_PATH 
 to point to
 them, but apart from that it was OK.
 
 Its worth noting though, that eMusic which uses Linux threads doesn't work 
 under
 emulation (it just hangs) I think I'll boot a non-SMP kernel and have a go 
 ('cause it
 took me an hour to find all of the $...@$ dependancies it needs because Linux 
 ldd doesn't
 work anymore)
 
 ---
 Daniel O'Connor software and network engineer
 for Genesis Software - http://www.gsoft.com.au
 The nice thing about standards is that there
 are so many of them to choose from.
   -- Andrew Tanenbaum
 
You may try my patch at http://www.freebsd.org/~luoqi, which would allow
linux threads to run on SMP.

-lq


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: SMP and SO5.0

1999-02-16 Thread Brian Feldman
On Tue, 16 Feb 1999, Luoqi Chen wrote:

  Hi,
  I downloaded Star Office 5 and only THEN realised that the code for doing 
  linux thread
  emulation is #ifndef SMP :) Still, after downloading 70 meg over a 56k 
  modem and paying
  19c/meg I was gonna try the sucker regardless.. And well, it works!
  
  The install hung at the end, after its done everything, so I killed it, but 
  after that I
  can run it with (seemingly) no problems.. (Except for the 2000 odd 'shared 
  address space
  fork attempted' messages in my syslog)
  
  I only had a quick fiddle, but it started up everything fine and ran quite 
  well..
  
  The install was a pain tho, as I had to unpack the setup program (its a 
  self extracting
  zip) and rename the libs in it to lower case and then add an 
  LD_LIBRARY_PATH to point to
  them, but apart from that it was OK.
  
  Its worth noting though, that eMusic which uses Linux threads doesn't work 
  under
  emulation (it just hangs) I think I'll boot a non-SMP kernel and have a go 
  ('cause it
  took me an hour to find all of the $...@$ dependancies it needs because 
  Linux ldd doesn't
  work anymore)
  
  ---
  Daniel O'Connor software and network engineer
  for Genesis Software - http://www.gsoft.com.au
  The nice thing about standards is that there
  are so many of them to choose from.
-- Andrew Tanenbaum
  
 You may try my patch at http://www.freebsd.org/~luoqi, which would allow
 linux threads to run on SMP.
 
 -lq

With any form of kernel threads not working, and aio being highly unstable for
SMP because of the VM system, is it not worthwhile to actually implement or
merge the changes like this?

 
 
 To Unsubscribe: send mail to majord...@freebsd.org
 with unsubscribe freebsd-current in the body of the message
 

 Brian Feldman_ __  ___ ___ ___  
 gr...@unixhelp.org   _ __ ___ | _ ) __|   \ 
 http://www.freebsd.org/ _ __ ___  | _ \__ \ |) |
 FreeBSD: The Power to Serve!  _ __ ___  _ |___/___/___/ 



To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: runsocks (Was Re: gpib driver - does anybody use it?)

1999-02-16 Thread Warner Losh
In message 
pine.osf.4.05.9902101658550.21416-100...@mercury.physics.adelaide.edu.au Kris 
Kennaway writes:
: runsocks works fine for me in socksifying the stuff I use it for
: (FTP clients, simple TCP apps, etc). What are you having problems
: with?

I have verified that runsocks works with both a.out and elf binaries
(but not both at the same time) with the most current port.  It does
not work for statically linked binaries.  Anything outside of that are
that isn't pilot error is a bug that I'd be interested in...

Warner


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: runsocks (Was Re: gpib driver - does anybody use it?)

1999-02-16 Thread Warner Losh
In message 19990210135902.a7...@internal Andre Albsmeier writes:
: Hmm, just finished my 3.1 upgrade, compiled socks and runsocks seems
: to work now. The only thing that doesn't work is compiling the telnet
: included with socks5:
: 
: cc -I. -I../../include -I./../../include -O -pipe -DANDRE 
-D__USE_FIXED_PROTOTYPES__  -DHAVE_SETUPTERM  -DSOCKS -DINCLUDE_PROTOTYPES 
-DKLUDGELINEMODE  -DSOCKS -DINCLUDE_PROTOTYPES -o telnet authenc.o commands.o 
main.o network.o ring.o sys_bsd.o telnet.o terminal.o tn3270.o utilities.o 
-L../../lib -lsocks5   -lcrypt   -lncurses -Llibtelnet -ltelnet
: telnet.o: In function `gettermname':
: telnet.o(.text+0x9f2): undefined reference to `ttytype'
: *** Error code 1 (continuing)
: `all' not remade because of errors.
: 
: But this doesn't bother me because always I runsocks the FreeBSD telnet.
: 
: Anyway, I will keep on experimenting on my home machine (where it failed
: yesterday) and look what happened. Maybe it was just to late in the evening

Ah yes.  the telnet bug.  I had forgotten about that one.  I'll try to
fix it shortly.  In fact, most of the r utilities that socks creates
could likely be better integrated with FreeBSD's commands.  I'll look
into how hard that would be.

Warner


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: runsocks (Was Re: gpib driver - does anybody use it?)

1999-02-16 Thread Warner Losh
In message 
pine.osf.4.05.9902120002140.29581-100...@mercury.physics.adelaide.edu.au Kris 
Kennaway writes:
: Yeah, this doesn't comple for some reason as of about 1.0r4. The port just
: doesn't bother trying to install it - no-one's cared enough to look at why
: it's broken and how to fix it.

It is broken because it assume too many implementation details about
symbols being defined.  A more accurate description would be that no
one has cared enough to actually fix it. :-)

Warner


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: How to power off an ATX power supply machine on shutdown ?

1999-02-16 Thread Warner Losh
In message pine.bsf.4.05.9902120005080.38269-100...@localhost Matthew Thyer 
writes:
: I have apm in the kernel and it probes as apm v 1.2 but when
: the shutdown -p now command is run, the power is not turned
: off and I have to hold down the power button for 4 seconds to
: turn it off.
: 
: Hows it done ?

You need to set apm_enabled=YES in your rc.conf file.

Warner


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: lpt0

1999-02-16 Thread Warner Losh
In message 199902141331.faa27...@hub.freebsd.org Jonathan M. Bresler writes:
:   how much information about this should be included in
:   /usr/src/UPDATING?   the entry there talks about the change but does
:   not provide enough information to successfully upgrade (ppc0 is not
:   mentioned, nor does it provide a pointer to where to go for  more
:   information.)  ;(

I'm about to commit a change to UPDATING to point to this URL and man
page.  I'm just now catching up from being gone for a week.

Warner


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: Aladdin chipset SMBus support available!

1999-02-16 Thread Warner Losh
: Not to stop you in your tracks, but I would really love to see
: somebody (more capable than the PAO people) work out a power
: management architecture for us before we have too many more
: hacks in this area...

I'd have to agree that a unified power management architecture would
be a good thing.  There is also the new APCI to consider as well.

Warner


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



HEADS UP: Don't abuse heads up

1999-02-16 Thread Warner Losh

I have a request.  In order to make it easier for me to know what to
put into UPDATING in a timely manner, I do a scan +freebsd-current |
egrep -i 'heads* up'.  Please do not have long discussions with the
heads up phrase in the subject line, if you can avoid it.  That will
make my job easier.

Thanks.

Warner


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



You Got To Love the New Kind of Spam 8)

1999-02-16 Thread Amancio Hasty

SGI is releasing GLX 8) 

http://biz.yahoo.com/prnews/990216/ca_silicon_2.html

Have Fun,
Amancio

P.S.: If companies start dumping large packages is going to weight us down :(




To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: runsocks (Was Re: gpib driver - does anybody use it?)

1999-02-16 Thread Andre Albsmeier
On Tue, 16-Feb-1999 at 22:05:05 -0700, Warner Losh wrote:
 In message 
 pine.osf.4.05.9902101658550.21416-100...@mercury.physics.adelaide.edu.au 
 Kris Kennaway writes:
 : runsocks works fine for me in socksifying the stuff I use it for
 : (FTP clients, simple TCP apps, etc). What are you having problems
 : with?
 
 I have verified that runsocks works with both a.out and elf binaries
 (but not both at the same time) with the most current port.  It does
 not work for statically linked binaries.  Anything outside of that are
 that isn't pilot error is a bug that I'd be interested in...

Must have been a pilot error. Now it's working (The first time, I
did it very late at night :-)).

-Andre

 
 Warner


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: VM patch.. SMP and SO5.0

1999-02-16 Thread Julian Elischer
who's looked at this.
It looks to me that this is serious stuff
spliting the pmap out of the vmspace structure is a big change.
caertainly a logical move but requires checking..

I guess it should be refered to the VM cabal.

I presume that this is to be done in conjunction with the linuxthreads
(and native threads) code already committed... 

What exactly is the reason for separating them?

julian

On Tue, 16 Feb 1999, Luoqi Chen wrote:
 You may try my patch at http://www.freebsd.org/~luoqi, which would allow
 linux threads to run on SMP.



To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: SMP and SO5.0

1999-02-16 Thread Julian Elischer
I'm not sure why you need a different page directory for each processor.
what's your thinking on this?

You might add some comments in your patches  so that if becomes more
obvious what you are doing...




To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: You Got To Love the New Kind of Spam 8)

1999-02-16 Thread Kenneth D. Merry
Amancio Hasty wrote...
 
 SGI is releasing GLX 8) 
 
 http://biz.yahoo.com/prnews/990216/ca_silicon_2.html
 
   Have Fun,
   Amancio
 
 P.S.: If companies start dumping large packages is going to weight us down :(

Heh.  That's pretty cool.  Although I wouldn't say that GLX itself is
exactly huge.

What they've released is basically the X server side connecting glue that
allows connecting up OpenGL to an X server.  Here's a snippet from the
readme:

=
GLX is used to connect an X server and an OpenGL implementation. By
itself, the GLX distribution is incomplete. XFree86 (or other code based
on the X11R6 release) provides the X server.
=

They aren't releasing, however, their OpenGL implementation.  Here's what
they said about that:

=
Please do not deluge SGI with requests to make our SI available as open
source. We are fully aware of the issues involved.
=

Apparantly Red Hat and some other company (Precision Insight) are working
on getting Mesa to work with GLX.

Ken
-- 
Kenneth Merry
k...@plutotech.com


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: SMP and SO5.0

1999-02-16 Thread Julian Elischer


On Tue, 16 Feb 1999, Luoqi Chen wrote:
 You may try my patch at http://www.freebsd.org/~luoqi, which would allow
 linux threads to run on SMP.

I've gone through these patches and I can see that they are really needed
for SMP where address spaces are shared.

There are details I didn't get, such as where is the per-processor
pde pointed, (i.e. where is the per processor KVM range) and is there a
single page table for each processor that is
always mapped into the processor specific slot for that process.

another question that is raised I guess is how do we tell gdb to switch
between processors when reading core-dumps :-).





To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message



Re: /etc/defaults/rc.conf

1999-02-16 Thread Greg Lehey
On Tuesday, 16 February 1999 at  9:24:31 -0800, Jordan K. Hubbard wrote:
 If I have a /etc/defaults/rc.conf, then my /etc/rc.conf won't be consulted.

 Wrong.  You need to read just a bit FURTHER into that file before
 jumping to such conclusions. :-)

Been there, done that.  Next thing is to write a book about it.  Can I
hope that it won't change again this year?

Greg
--
See complete headers for address, home page and phone numbers
finger g...@lemis.com for PGP public key


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message