Pete French petefre...@ticketswitch.com wrote:
Is there a way inside the install environment to see
what the kernel has detected and created in /dev ?
Go into Fixit# and examine /dev and/or the dmesg.
___
freebsd-stable@freebsd.org mailing list
On Wed, 08 Dec 2010 01:00:34 -0800
per...@pluto.rain.com wrote:
Go into Fixit# and examine /dev and/or the dmesg.
The problem is there's no ls in FixIt mode so you need to use
echo * to see what files are present.
--
Bruce Cran
___
On Wed, 8 Dec 2010 20:01:32 +1000
Andy Farkas chuzzwa...@gmail.com wrote:
Why is this so?
I think the Fixit environment only contains tools necessary for
installing the system and has traditionally needed to be small enough
to fit on a 1.44MB floppy disk. So since ls wasn't required it
wasn't
On Wed, Dec 8, 2010 at 7:17 PM, Bruce Cran br...@cran.org.uk wrote:
On Wed, 08 Dec 2010 01:00:34 -0800
per...@pluto.rain.com wrote:
Go into Fixit# and examine /dev and/or the dmesg.
The problem is there's no ls in FixIt mode so you need to use
echo * to see what files are present.
Why is
So since ls wasn't required it wasn't included.
I just booted an old 6.1-RELEASE CD and selected Fixit mode...
ls -lF works as expected!
-andyf
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To
On Wed, 8 Dec 2010 20:29:31 +1000
Andy Farkas chuzzwa...@gmail.com wrote:
So since ls wasn't required it wasn't included.
I just booted an old 6.1-RELEASE CD and selected Fixit mode...
ls -lF works as expected!
I should clarify that by saying that ls is included in the live
filesystem
On Wed, Dec 08, 2010 at 09:17:27AM +, Bruce Cran wrote:
On Wed, 08 Dec 2010 01:00:34 -0800
per...@pluto.rain.com wrote:
Go into Fixit# and examine /dev and/or the dmesg.
The problem is there's no ls in FixIt mode so you need to use
echo * to see what files are present.
Sort of.
On Mon, Dec 6, 2010 at 6:52 PM, Pete French petefre...@ticketswitch.com wrote:
I am not burning a CD or using any physical media. I am booting
directly off the image file using iLO. Hence the stuff in that thread
doesnt apply. It's defintely 8 specific - I can boot an mage
from 7 it works
On Mon, 6 Dec 2010 16:40:35 -0800
Jeremy Chadwick free...@jdc.parodius.com wrote:
If there is a physical CD-ROM drive which is upsetting sysinstall, I
wouldn't be surprised (sysinstall is depressing, please don't get me
started on it. :-) ). I'm willing to bet it makes the assumption
If there's more than one CD device you'll get a prompt asking which to
use.
...which is precisely what happens under 7.X
So, now that I have it installed, when I am logged into the machine
I have these devices in /dev:
crw-r- 1 root operator0, 89 7 Dec 02:39 /dev/acd0
crw-r-
My problem was that the ILO CDROM presented it's drive as starting
from block one (or somesuch nonsense). I ended up doing a netinstall
because the boot would work (BIOS understood what was going on) but
FreeBSD did not.
Interesting ... I've never seen that, but it's always good to know that
Trying to re-install a set of HP servers over the iLO, and every time
I tried to install the 8.1 CD I ended up with an error message
telling me that the CD looked more like an audio CD than a FreeBSD
distibution.
I ouzzled over it a bit, and then remembered that I originally installed
these
on 07/12/2010 00:51 Pete French said the following:
Trying to re-install a set of HP servers over the iLO, and every time
I tried to install the 8.1 CD I ended up with an error message
telling me that the CD looked more like an audio CD than a FreeBSD
distibution.
I ouzzled over it a bit,
On Mon, Dec 06, 2010 at 10:51:36PM +, Pete French wrote:
Trying to re-install a set of HP servers over the iLO, and every time
I tried to install the 8.1 CD I ended up with an error message
telling me that the CD looked more like an audio CD than a FreeBSD
distibution.
I ouzzled over it
Basically if it feels like you are the first one to report the problem, then,
unfortunately, the onus is on you...
Sure, I've been around here long enough to know this - was just trying to see
if anyone else knew about it, as it takes so long to boot over the network
that I really didn't want
on 07/12/2010 01:27 Pete French said the following:
Actually my expereice of filing PR's has been pretty positive over the
years. Am a bit surprised you feel this way. Investigating and posting
here also generates reseults, but I do like to tag them onto a PR in
the end, just so they dont get
Apparently you've been born with a silver spoon or something :-)
...more likely an ability to irritate people until it gets fixed ;-)
Because few thousand other people do not seem to be as lucky:
http://people.freebsd.org/~edwin/gnats/gnats-openpercategorycummulative.html
ah, not good graph
So, I just gave the 8.1 CD a try - which didnt take nearly as long as
anticipated. End result is that it also fails to insall. Pr
filed as http://www.freebsd.org/cgi/query-pr.cgi?pr=152874
Am wndering if this could be due to the change in the USB stack
somehow though - I have a feeling that iLO
This problem has been reported many times in the past and almost
certainly has nothing to do with 8.x. Here's a thread about the matter
where a user states the same as you but about 7.1:
http://unix.derkeiler.com/Mailing-Lists/FreeBSD/questions/2008-10/msg00307.html
I found that - it
on 07/12/2010 01:44 Pete French said the following:
Apparently you've been born with a silver spoon or something :-)
...more likely an ability to irritate people until it gets fixed ;-)
That's exactly the reason why I said unless the reporter also actively pursues
it :-)
Because as my
On Monday 06 December 2010 06:46 pm, Pete French wrote:
So, I just gave the 8.1 CD a try - which didnt take nearly as long
as anticipated. End result is that it also fails to insall. Pr
filed as http://www.freebsd.org/cgi/query-pr.cgi?pr=152874
Am wndering if this could be due to the change
on 07/12/2010 01:46 Pete French said the following:
So, I just gave the 8.1 CD a try - which didnt take nearly as long as
anticipated. End result is that it also fails to insall. Pr
filed as http://www.freebsd.org/cgi/query-pr.cgi?pr=152874
BTW, that error message is produced by sysinstall on
This problem may be a reverse problem of this PR:
http://www.freebsd.org/cgi/query-pr.cgi?pr=138789
In other words, your virtual CD-ROM reads correct TOC from mounted
image but block size is wrong? Maybe old umass(4) corrects this case
heuristicly but the new USB stack doesn't?
Might be
On Mon, Dec 06, 2010 at 11:52:25PM +, Pete French wrote:
This problem has been reported many times in the past and almost
certainly has nothing to do with 8.x. Here's a thread about the matter
where a user states the same as you but about 7.1:
Quoth Pete French on Monday, 06 December 2010:
Apparently you've been born with a silver spoon or something :-)
...more likely an ability to irritate people until it gets fixed ;-)
Because few thousand other people do not seem to be as lucky:
On Tue, 7 Dec 2010, Andriy Gapon wrote:
on 07/12/2010 01:44 Pete French said the following:
Apparently you've been born with a silver spoon or something :-)
...more likely an ability to irritate people until it gets fixed ;-)
That's exactly the reason why I said unless the
26 matches
Mail list logo
