setting up file system

[Matt Graham]

On 2014-07-25 15:06, Michael Butash wrote:
> Don't make your bootable an extended (I don't think this will work if
> I remember right)

The "bootable" flag in the partition table is only checked and used by 
the DOS/Windows boot sectors.  GRUB, LILO, and GRUB2 ignore it, and IIRC 
only LILO needs to have the kernel/initrd within the BIOS-addressable 
area of the disk (used to be the first 8G or first 32G, is larger now.)

>  On 07/25/2014 02:59 PM, Michael Havens wrote:
>> it seems a more recent version of cfdisk will create filesystems

This seems like a horrible idea to me.

>> root at debian:~# mkfs -v -t ext4 /dev/sda6
>> Could not stat /dev/sda6 --- No such file or directory

>> root at debian:~# fdisk -l /dev/sda
>> /dev/sda1 2048 7813119 3905536 82 Linux swap / Solaris
>> /dev/sda2 7815166 488281249 240233042 5 Extended
>> /dev/sda5 * 7815168 105469951 48827392 83 Linux
>> /dev/sda6 437499848 476569864 19535008+ 83 Linux
>> /dev/sda7 476569928 488281249 5855661 82 Linux swap / Solaris

This seems odd--why is there a bunch of empty space between sda5 and 
sda6?  You don't need 2 swap partitions; distros can share swap 
partitions.

>> Please, what did I do wrong or else what is the problem?

Is udev running?  What does "ls -l /dev/sd*" tell you?  If udev or 
systemd isn't running, then the device node /dev/sda6 may not have been 
created.  "mknod /dev/sda6 b 8 6" will create it manually.  But if it's 
not showing up, then you should find out why udev or systemd isn't 
running.  Having device nodes automatically added when new devices are 
plugged in works and is useful.

-- 
Crow202 Blog: http://crow202.org/wordpress
There is no Darkness in Eternity
But only Light too dim for us to see.