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
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, suc
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
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
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 linuxthread
On Tue, 16-Feb-1999 at 22:05:05 -0700, Warner Losh wrote:
> In message
>
> 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
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
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.
Th
: 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
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,
In message 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" i
In message
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
symbol
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
-
In message
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 curr
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 we
> 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, afte
> > 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
>
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 maj
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 every
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 l
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 y
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
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,
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 -DDEB
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, ho
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
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 pi
> 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
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 m
>
> 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 West
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
>
> ===> 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
> 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 messa
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
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'
> > 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
> ca
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
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/def
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
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 misma
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.
> 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.con
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 w
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
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 tha
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 t
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|
\==
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 t
: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 mac
49 matches
Mail list logo
