I think the problem is with the system. If you cannot boot from the CD
Rom then I think you may have a more serious problem. I am somewhat
anti-Dell because of the 2 pieces of crap servers Boston User Groups
bought a few years ago (1 for BLU). Both systems failed after time.
On 01/26/2012 12:47
On Thu, Jan 26, 2012 at 2:35 AM, Mike Bilow mik...@colossus.bilow.comwrote:
Filesystems (and therefore fsck targets) reside on partitions of the
disk, something like /dev/sdc3, rather than the entire device (or an
image of it). This is inherent in the design of the system and is
independent
Not only Dell desktops, but I just ran into the same issue of not being
able to boot from a CD on an HP machine, which boots fine from a USB stick.
Also had problems bringing up the BIOS with the keyboard plugged into a
USB hub but it worked fine when connected directly to the box for some
As long as we're picking nits...
On Thu, Jan 26, 2012 at 10:08 AM, Michael ODonnell
michael.odonn...@comcast.net wrote:
most filesystems do normally reside on partitions
but that's not actually inherent in the design of the system ...
Not inherent in the design of *nix systems, certainly.
I have an internal hard drive that won't boot.
The system (Dell Studio Hybrid) also will not boot from CD-ROM (regardless
of what I do with the boot sequence, F2, BIOS settings etc.) In fact it
doesn't seem that BIOS settings actually get saved. But that's another
matter. I'm concerned with
Filesystems (and therefore fsck targets) reside on partitions of the
disk, something like /dev/sdc3, rather than the entire device (or an
image of it). This is inherent in the design of the system and is
independent of the types of filesystems or how they are mixed.
In order to access
