Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

kernel message

0 views
Skip to first unread message

mel kravitz

unread,
Jan 27, 2000, 3:00:00 AM1/27/00
to
Hi,
Anyone know what this kernel message means:
' r devices on PCI bus 0: '

Something to worry about?
mel

To Unsubscribe: send mail to majo...@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message

Ben Smithurst

unread,
Jan 27, 2000, 3:00:00 AM1/27/00
to
mel kravitz wrote:

> Hi,
> Anyone know what this kernel message means:
> ' r devices on PCI bus 0: '

looks like the tail end of "probing for devices on PCI bus 0: ", displayed
when you boot.

> Something to worry about?

I don't think so, but what does a full "dmesg" show? It seems strange that
the message is being broken.

Ah... I see, is this from the security mail? You saw a line like:

foo kernel messages:


> r devices on PCI bus 0:

If so, that's just because the first part of the message has scrolled
out of the buffer, leaving just that, which the security script picks up
as being a new line. If that's the case, it's nothing to worry about,
concentrate on the kernel messages which really are new. :-)

--
Ben Smithurst / b...@scientia.demon.co.uk / PGP: 0x99392F7D

Matthew Joseff

unread,
Jan 28, 2000, 3:00:00 AM1/28/00
to

The hard drive in my server is starting to go buh bye (read: making bad
noises). Any suggestions on how to switch it out? I'm thinking
format & install FreeBSD on the new one then copy over neccessary files?
Or, mount the new drive and just cp -R everything. *shrug*

--
Matthew Joseff
System Administrator
Retribution.net

Ryan Thompson

unread,
Jan 28, 2000, 3:00:00 AM1/28/00
to
On Fri, 28 Jan 2000, Matthew Joseff wrote:
>
> The hard drive in my server is starting to go buh bye (read: making bad

"The" hard drive, huh... I always try to keep a small spare with a
defaulted FreeBSD install for emergencies. And, of course, I do regular
backups :-)

> noises). Any suggestions on how to switch it out? I'm thinking
> format & install FreeBSD on the new one then copy over neccessary files?
> Or, mount the new drive and just cp -R everything. *shrug*
>

I would just format & install FreeBSD on the new drive... Install the
latest -STABLE snapshot from releng3, install all your packages (i.e., run
pkg_info on the old system to see what you have :-) and copy over relevant
config files. Then you can start moving you other filesystems over
without much of a hassle.

I just spent a week or two going through a new install for our biggest
server, doing just that (i.e., installing on a new drive and moving over).
I ALSO took the time (because I had it) to carefully document any
deviations I made from a stock FreeBSD install... So, if, for some reason,
I was stuck without backups, or a similar alternative like a new drive, I
could be up and running in a few hours as opposed to a few days ;-)

--
Ryan Thompson <ry...@sasknow.com> 50% Owner, Sysadmin
SaskNow Technologies http://www.sasknow.com
#106-380 3120 8th St E Saskatoon, SK S7H 0W2

Matthew Joseff

unread,
Jan 28, 2000, 3:00:00 AM1/28/00
to
On Fri, 28 Jan 2000, Ryan Thompson wrote:
}On Fri, 28 Jan 2000, Matthew Joseff wrote:
}> The hard drive in my server is starting to go buh bye (read: making bad
}"The" hard drive, huh... I always try to keep a small spare with a
}defaulted FreeBSD install for emergencies. And, of course, I do regular
}backups :-)

That's phase II: Now I have some extra cash. :)

}I just spent a week or two going through a new install for our biggest
}server, doing just that (i.e., installing on a new drive and moving over).
}I ALSO took the time (because I had it) to carefully document any
}deviations I made from a stock FreeBSD install... So, if, for some reason,
}I was stuck without backups, or a similar alternative like a new drive, I
}could be up and running in a few hours as opposed to a few days ;-)

Good idea.

--
Matthew Joseff
System Administrator

NewsReal, Inc. www.newsreal.com

0 new messages