Re: maxphys = 0??

[Poul-Henning Kamp]

In message <[EMAIL PROTECTED]>, "Daniel C. Sobral" writes:
>Poul-Henning Kamp wrote:
>> 
>> In message <[EMAIL PROTECTED]>, "Bria
>> n F. Feldman" writes:
>> >On Tue, 5 Oct 1999, Daniel C. Sobral wrote:
>> >
>> >> Poul-Henning Kamp wrote:
>> >> >
>> >> > You need to move your sources further forward.
>> >>
>> >> Alas, it didn't help. What versions of what files I should have? The
>> >> warnings are still appearing, at fsck time.
>> 
>> The lastest.
>
>Well, I tried with the latest after you said the above. I'll try
>with a later latest again. But, really...

Well, there are two options, either your sources are not up to date,
or your config is very special in some way...

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


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

Re: maxphys = 0??

[Daniel C. Sobral]

Poul-Henning Kamp wrote:
> 
> In message <[EMAIL PROTECTED]>, "Bria
> n F. Feldman" writes:
> >On Tue, 5 Oct 1999, Daniel C. Sobral wrote:
> >
> >> Poul-Henning Kamp wrote:
> >> >
> >> > You need to move your sources further forward.
> >>
> >> Alas, it didn't help. What versions of what files I should have? The
> >> warnings are still appearing, at fsck time.
> 
> The lastest.

Well, I tried with the latest after you said the above. I'll try
with a later latest again. But, really...

--
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]

"I always feel generous when I'm in the inner circle of a
conspiracy to subvert the world order and, with a small group of
allies, just defeated an alien invasion. Maybe I should value myself
a little more?"


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

PnP problems on install floppy in 4.0-SNAPS from current.freebsd.org

[Jason DiCioccio]

Yes yes.. Long subject, but anyhow.. The problem I am having is that 4.0
insists on detecting my ethernet card PnP at installation even though Id
ont want it to.. When it does, it freezes up, and its much easier for me
just to input the settings manually info the visual config.. I need to
disable on install disk, or get a 4.0 floppy that doesn't freeze on
'unknown0', of course, not having it detected at all would be preferable
:)..

Thanks in advance,
Jason DiCioccio




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

Re: maxphys = 0??

[Poul-Henning Kamp]

In message <[EMAIL PROTECTED]>, "Bria
n F. Feldman" writes:
>On Tue, 5 Oct 1999, Daniel C. Sobral wrote:
>
>> Poul-Henning Kamp wrote:
>> > 
>> > You need to move your sources further forward.
>> 
>> Alas, it didn't help. What versions of what files I should have? The
>> warnings are still appearing, at fsck time.

The lastest.

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


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

Re: maxphys = 0??

[Brian F. Feldman]

On Tue, 5 Oct 1999, Daniel C. Sobral wrote:

> Poul-Henning Kamp wrote:
> > 
> > You need to move your sources further forward.
> 
> Alas, it didn't help. What versions of what files I should have? The
> warnings are still appearing, at fsck time.
> 

Alas, similarly I get:
changing root device to wd0s1a
WARNING: #ad/0x20007 maxphys = 0 ??WARNING: #ad/0x20006 maxphys = 0 ??WARNING: 
#ad/0x20004 maxphys = 0 ??WARNING: #ad/0x20005 maxphys = 0 ??WARNING: #ad/2 maxphys = 
0 ??

-- 
 Brian Fundakowski Feldman   \  FreeBSD: The Power to Serve!  /
 [EMAIL PROTECTED]`--'



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

staroffice

[Randy Bush]

anyone successful installing staroffice 5.1?

is  still the best hint?

randy


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

linux emu and quake3test

[Kenneth Wayne Culver]

IT seems that a recent change to the linux emulation code has caused q3 to
have problems, whenever I try to go to an internet game, I get a message
on the console:

usage: ping [server]

doing this operation worked fine yesterday.

Kenneth Culver


=
| Kenneth Culver  | FreeBSD: The best OS around.|
| Unix Systems Administrator  | ICQ #: 24767726 |
| and student at The  | AIM: AgRSkaterq |
| The University of Maryland, | Website: (Under Construction)   |
| College Park.   | http://www.wam.umd.edu/~culverk/|
=



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

Re: [Patches avail?] Re: MMAP() in STABLE/CURRENT ...

[Matthew Dillon]

:>ECC doesn't protect against certain types of motherboard address line
:> errors (since although the ECC is correct, the selected address is wrong, so
:> thus the data is wrong). There's parity protection on parts of the CPU
:> address bus, but I don't believe there is any protection between the memory
:> controller and the DIMMs for this type of problem. A handful of metal
:> filings is also known to cause problems when it is dispersed properly. :-)
:
:Your suppose to remove the motherboard before drilling holes in your
:chassis!!!  :-).  And be careful when you strip them there screws out,
:that little bit of metal filings is enough to through one for some
:
:Rod Grimes - KD7CAX - (RWG25)[EMAIL PROTECTED]

Forget the drilling!  Blood conducts electricity... simply *installing*
a motherboard in those fraggin sharp-edged sheet metal chassis is enough!

-Matt
Matthew Dillon 
<[EMAIL PROTECTED]>


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

Re: {a}sync updates (was Re: make install trick)

[Matthew Dillon]

:>  We're talking about the special case of small root partitions, such that
:> softupdates inability to make empty space available quickly can make the
:> difference between a major operation's success or failure.
:> 
:>  This is almost impossible on a 1.8Gb root partition. 
:
:Again why?  What's the difference between a small / and a 1.8GB (byte not
:...
:Why would I be so concerned?  If I don't expect to need that 15M then,
:I've sized my partition just right.  Don't put cares in my basket that 
:...
:-- 
:-- David([EMAIL PROTECTED])

I think the argument has become somewhat skewed.  The softupdates bug
occurs when a filesystem fills up, it doesn't really matter how small or
large the filesystem is.

What matters more is how often a partition is actually written to and
how likely the chance of the partition filling up.

Personally speaking, I tend to use small (64-128MB) root partitions
with a separately mounted /usr and /var (and /tmp a softlink to /var/tmp).
In fact, I usually separate out /var/tmp as well.  I do this simply to
reduce the amount of writing that occurs on the root partition in order
to ensure that I don't lose it accidently.

This has saved my butt on innumerable occassions... there is something
to be said for being able to boot into a workable shell when you've
blown up the rest of the system!  With my configuration I feel perfectly
safe enabling softupdates on root.  In other configurations, such as 
having /usr and /var on the same partition as root, I might not
feel as safe.

-Matt
Matthew Dillon 
<[EMAIL PROTECTED]>


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

Re: {a}sync updates (was Re: make install trick)

[David O'Brien]

>   We're talking about the special case of small root partitions, such that
> softupdates inability to make empty space available quickly can make the
> difference between a major operation's success or failure.
> 
>   This is almost impossible on a 1.8Gb root partition. 

Again why?  What's the difference between a small / and a 1.8GB (byte not
bit) one?  There is nothing here to back this up.  Not enough space is
not enough space reguardless how much you started out with.


> And if you had a 1.8Gb partition with only 15Mb free, the last thing
> you'd care about is how softupdates will handle the situation.

Why would I be so concerned?  If I don't expect to need that 15M then,
I've sized my partition just right.  Don't put cares in my basket that 
don't need to be there.  More uninstatiated opions.
 
-- 
-- David([EMAIL PROTECTED])


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

Re: identd

[Ben Smithurst]

Phil 0. Nature wrote:

> Has anyone else experienced problems with identd not working?

Uh, you'd probably have to be more specific. What identd (pidentd
from ports, or something else). What version. In what way doesn't it
work. What error messages are being logged. What version of FreeBSD.
-current, presumably, but how recent.

The only small problem I've seen is this, with pidentd-2.8.5 from ports
on a 3.2-stable system:

Sep 30 21:54:20 scientia identd[75098]: getbuf: bad address (0f80 not in 
c0116360-0xFFC0) - ofile
Sep 30 21:54:20 scientia identd[75098]: k_getuid retries: 1
Oct  3 12:48:00 scientia identd[93188]: getbuf: bad address (137b not in 
c0116360-0xFFC0) - ofile
Oct  3 12:48:00 scientia identd[93188]: k_getuid retries: 1

but I haven't got round to looking into it much. Other than those two
errors, it works fine.

-- 
Ben Smithurst| PGP: 0x99392F7D
[EMAIL PROTECTED] |   key available from keyservers and
 |   [EMAIL PROTECTED]


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

RE: {a}sync updates (was Re: make install trick)

[David Schwartz]

> On Thu, Oct 07, 1999 at 03:15:03PM -0700, David Schwartz wrote:
> > > > There should be fairly few writes to the root partition, so having
> > > An opionion.  I use the HP workstation model where my / is
> 1800M.  I have
>
> > You are not disagreeing with him, David. You are just talking about
> > another scenario other than the one under discussion.
> > He was talking about the case where root is small. This
> whole discussion
> >   was about how softupdates behaves in the subcase of small
> root partitions.
>
> This discussion was NOT about "how softupdates behaves in the subcase of
> small root partitions"  Imp was having problems in the face of
> softupdates on a full /.  The problem exists *reguardless* of how big /
> is, the issues is % free.

No, this is a different issue. The problem was not that the filesystem was
full, but that the fill rate was comparable to the amount of 'empty' space.

> > If you have a 1.8Gb root partition that also includes /var
> and /usr, this
> > whole discussion is irrelevant.
>
> Why??  Because / can now not fill up?  I've installed enough
> KDE/GNOME/teTeX/etc... ports (plus /usr/{ports,src}) that I have acutally
> filled it up before.

Yes, but if you fill up your root partition, there's nothing that can be
done. Full is full.

We're talking about the special case of small root partitions, such that
softupdates inability to make empty space available quickly can make the
difference between a major operation's success or failure.

This is almost impossible on a 1.8Gb root partition. And if you had a 1.8Gb
partition with only 15Mb free, the last thing you'd care about is how
softupdates will handle the situation.

DS



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

Re: [Patches avail?] Re: MMAP() in STABLE/CURRENT ...

[Rodney W. Grimes]

> >On Thu, Oct 07, 1999 at 10:09:23AM -0700, Matthew Dillon wrote:
> >
> >> Intel's ECC implementation is not perfect (1), but it's good enough to 
> >> catch these sorts of problems.
> >
> >Just as an interesting side note, we had a motherboard which
> >supported ECC ram and had ECC ram in it and which was crashing.
> >Eventually we discovered that every 8th byte in page aligned 4KB
> >chunks was becomming corrupted.
> >
> >We replaced the ram and saw no improvement, and then got a replacement
> >motherboard. As far as I could see the only significant difference
> >between the new and old motherboard was the addition of a heat sink
> >to the memory controler chip. The machine is now perfectly happy.
> >
> >So it seems that ECC isn't enough if your memory controler is too
> >hot!
> 
>ECC doesn't protect against certain types of motherboard address line
> errors (since although the ECC is correct, the selected address is wrong, so
> thus the data is wrong). There's parity protection on parts of the CPU
> address bus, but I don't believe there is any protection between the memory
> controller and the DIMMs for this type of problem. A handful of metal
> filings is also known to cause problems when it is dispersed properly. :-)

Your suppose to remove the motherboard before drilling holes in your
chassis!!!  :-).  And be careful when you strip them there screws out,
that little bit of metal filings is enough to through one for some
real loops.  A good blast of 60psi dry air does wonders for ``fixing''
some of these really strange problems :-)

Now if I could just find something that would get sheet rock sanding
dust out of tape drive mechanisms, a dunk in the freon tank often
works, but that also cleans out all the lubrication :-).

-- 
Rod Grimes - KD7CAX - (RWG25)[EMAIL PROTECTED]


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

Re: {a}sync updates (was Re: make install trick)

[David O'Brien]

On Thu, Oct 07, 1999 at 03:15:03PM -0700, David Schwartz wrote:
> > > There should be fairly few writes to the root partition, so having
> > An opionion.  I use the HP workstation model where my / is 1800M.  I have

>   You are not disagreeing with him, David. You are just talking about
>   another scenario other than the one under discussion.
>   He was talking about the case where root is small. This whole discussion
>   was about how softupdates behaves in the subcase of small root partitions.

This discussion was NOT about "how softupdates behaves in the subcase of
small root partitions"  Imp was having problems in the face of
softupdates on a full /.  The problem exists *reguardless* of how big /
is, the issues is % free.

>   If you have a 1.8Gb root partition that also includes /var and /usr, this
> whole discussion is irrelevant.

Why??  Because / can now not fill up?  I've installed enough
KDE/GNOME/teTeX/etc... ports (plus /usr/{ports,src}) that I have acutally
filled it up before.  

(And before I'm attacked for my organization -- if I can get it back from
the CDROM and it lives in /usr, it is on the / file systems which I don't
back up, as there is no use to.)

-- 
-- David([EMAIL PROTECTED])


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

Re: make install trick

[David O'Brien]

>If you've done your job right, it can be mounted read-only.  This
> makes it harder for someone to break into the machine and obtain root
> access, because now they have to be root to unmount /usr and remount
> it read-write, so that they can put their trojan script on there that
> they're hoping you'll execute.

AND just how are crackers going to write their trojan's in my root owned
/usr (and remember root now owns the binaries in /usr) w/o *already*
being root.  This is just as weak as the argument that BPF makes a box
more vulnerable to having a rouge sniffer running on it.


>   You're right that this is a somewhat religious issue, however, if 
> you're going to run a huge root filesystem, then you are more likely 
> to get what you deserve if /usr or one of the other directories on 
> the root filesystem get trashed or fill up.

And just what do I "deserve"?  Fuh!  Yea, as some said, lets go with a
30MB / so you can't even have room for a second kernel.  You should see
how fscked up Beast.freebsd.org is because of all the /, /usr, /var,
/tmp, etc, were mis-sized.  If I "deserve" something, then what's the
proper sizes for these?  I can tell you I run out of space on / a lot
less my way and have space where I need it, than I do on machines with
the millions of partitions.

Fuh!

-- 
-- David([EMAIL PROTECTED])


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

Sv: My status with upgrade from 3.2 to 4.0

[Leif Neland]

> Another thing was
> syslogd was looking for /var/log/security and can't find it, how can i fix
> this?

Just touch /var/log/security

syslogd can't/doesn't _create_ files, just _append_ to existing ones.

Leif




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

Re: make install trick

[Brad Knowles]

At 3:21 PM -0700 1999/10/7, David O'Brien wrote:

>   HP and SGI workstations have a single huge /.  Why do you
> need /usr seperate from / when you aren't diskless (or /usr'less)?

If you've done your job right, it can be mounted read-only.  This 
makes it harder for someone to break into the machine and obtain root 
access, because now they have to be root to unmount /usr and remount 
it read-write, so that they can put their trojan script on there that 
they're hoping you'll execute.

I've admin'ed my share of HP and SGI machines in the past, and 
I've never used the standard partition configuration, just like I 
don't use the standard partition configuration for Solaris.  IMO, 
none of them are right, and they're wrong for the wrong reasons.


You're right that this is a somewhat religious issue, however, if 
you're going to run a huge root filesystem, then you are more likely 
to get what you deserve if /usr or one of the other directories on 
the root filesystem get trashed or fill up.

-- 
   These are my opinions -- not to be taken as official Skynet policy
  
|o| Brad Knowles, <[EMAIL PROTECTED]>Belgacom Skynet NV/SA |o|
|o| Systems Architect, News & FTP Admin  Rue Col. Bourg, 124   |o|
|o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels   |o|
|o| http://www.skynet.be Belgium   |o|
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
  Unix is like a wigwam -- no Gates, no Windows, and an Apache inside.
   Unix is very user-friendly.  It's just picky who its friends are.


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

Re: modules: how to use?

[The Hermit Hacker]

Worked like a charm, thanks...have fxp0 and procfs removed from my kernel
config and using modules...

On Fri, 8 Oct 1999, Daniel C. Sobral wrote:

> The Hermit Hacker wrote:
> > 
> > Just to confirm, *technically*, I should just have to comment out the
> > options PROCFS in my kernel config, rebuild and reboot and since procfs
> > isn't in the kernel, it will look for it as a module?
> 
> As long as the module is up to date.
> 
> --
> Daniel C. Sobral  (8-DCS)
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> 
>   "I always feel generous when I'm in the inner circle of a
> conspiracy to subvert the world order and, with a small group of
> allies, just defeated an alien invasion. Maybe I should value myself
> a little more?"
> 
> 

Marc G. Fournier   ICQ#7615664   IRC Nick: Scrappy
Systems Administrator @ hub.org 
primary: [EMAIL PROTECTED]   secondary: scrappy@{freebsd|postgresql}.org 



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

Re: Make world broken in doscmd; patch

[Marcel Moolenaar]

Philipp Mergenthaler wrote:

> the change in src/sys/i386/include/ucontext.h  (in struct __mcontext),
> where "struct  trapframe mc_tf;" was replaced by it's members
> broke doscmd.

Fixed. Thanks,

-- 
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases   http://www.scc.nl/
The FreeBSD projectmailto:[EMAIL PROTECTED]


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

Re: modules: how to use?

[Daniel C. Sobral]

The Hermit Hacker wrote:
> 
> Just to confirm, *technically*, I should just have to comment out the
> options PROCFS in my kernel config, rebuild and reboot and since procfs
> isn't in the kernel, it will look for it as a module?

As long as the module is up to date.

--
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]

"I always feel generous when I'm in the inner circle of a
conspiracy to subvert the world order and, with a small group of
allies, just defeated an alien invasion. Maybe I should value myself
a little more?"




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

Re: [Patches avail?] Re: MMAP() in STABLE/CURRENT ...

[David Greenman]

>On Thu, Oct 07, 1999 at 10:09:23AM -0700, Matthew Dillon wrote:
>
>> Intel's ECC implementation is not perfect (1), but it's good enough to 
>> catch these sorts of problems.
>
>Just as an interesting side note, we had a motherboard which
>supported ECC ram and had ECC ram in it and which was crashing.
>Eventually we discovered that every 8th byte in page aligned 4KB
>chunks was becomming corrupted.
>
>We replaced the ram and saw no improvement, and then got a replacement
>motherboard. As far as I could see the only significant difference
>between the new and old motherboard was the addition of a heat sink
>to the memory controler chip. The machine is now perfectly happy.
>
>So it seems that ECC isn't enough if your memory controler is too
>hot!

   ECC doesn't protect against certain types of motherboard address line
errors (since although the ECC is correct, the selected address is wrong, so
thus the data is wrong). There's parity protection on parts of the CPU
address bus, but I don't believe there is any protection between the memory
controller and the DIMMs for this type of problem. A handful of metal
filings is also known to cause problems when it is dispersed properly. :-)

-DG

David Greenman
Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org
Creator of high-performance Internet servers - http://www.terasolutions.com
Pave the road of life with opportunities.


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

Re: [Patches avail?] Re: MMAP() in STABLE/CURRENT ...

[David Malone]

On Thu, Oct 07, 1999 at 10:09:23AM -0700, Matthew Dillon wrote:

> Intel's ECC implementation is not perfect (1), but it's good enough to 
> catch these sorts of problems.

Just as an interesting side note, we had a motherboard which
supported ECC ram and had ECC ram in it and which was crashing.
Eventually we discovered that every 8th byte in page aligned 4KB
chunks was becomming corrupted.

We replaced the ram and saw no improvement, and then got a replacement
motherboard. As far as I could see the only significant difference
between the new and old motherboard was the addition of a heat sink
to the memory controler chip. The machine is now perfectly happy.

So it seems that ECC isn't enough if your memory controler is too
hot!

David.


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

Re: shell script trouble

[Pascal Hofstee]

On Thu, 7 Oct 1999, Chris D. Faulhaber wrote:

> There are some of Postfix's daemons running above, but you seem to be
> missing:
> 
> root  286  0.0  0.8   872  220  ??  Is   29Sep99   0:10.23
> /usr/local/libexec/postfix/master
> 
> Which is the actual process that listens on port 25.  Since 'postfix
> reload' cannot communicate with master, it says that postfix is not
> running.  Next step, find out where your master is?

master is located at:
/usr/local/libexec/postfix/master



  Pascal Hofstee - [EMAIL PROTECTED]

-BEGIN GEEK CODE BLOCK-
Version: 3.1
GCS d- s+: a-- C++ UB P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP--
t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+
--END GEEK CODE BLOCK--



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