Leslie P. Polzer wrote:
Should I format the image before using fdisk on?
It would be better to fix fdisk, something's not right.
GNU Parted does work in this case, and util-linux
fdisk probably, too...
PS: Excuse me for orrible errors in my previous message but I wrote it
after teen hour of work, with only one idea on my mind: go bed! :)
Oh, I didn't notice it at all. :)
Leslie
]> It would be better to fix fdisk, something's not right
Excuse me but I'm not expert and confused...
~/# mkfs.ext2 DISK
mke2fs 1.35 (28-Feb-2004)
DISK is not a block special device.
Proceed anyway? (y,n) y
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
16384 inodes, 65536 blocks
3276 blocks (5.00%) reserved for the super user
First data block=1
8 block groups
8192 blocks per group, 8192 fragments per group
2048 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 26 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to
override.
And after making a second extended file system on DISK file:
bash-3.00# ./fdisk -G DISK
GNU Fdisk 1.0
Copyright (C) 1998 - 2006 Free Software Foundation, Inc.
This program is free software, covered by the GNU General Public
License.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
Using /PATH/DISK
Command (m for help): p
Disk /PATH/DISK: 67 MB, 67108864 bytes
4 heads, 32 sectors/track, 1024 cylinders
Units = cylinders of 128 * 512 = 65536 bytes
Device Boot Start
End Blocks Id System
/PATH/DISK1 1 1024
65520 83 Linux
Command (m for help): n
Command (m for help): n
Command (m for help): m
Command action
a toggle bootable flag
b edit bsd disklabel
d delete a partition
l list known partition types
m print this menu
n add a new partition
o create a new empty DOS partition table
p print the partition table
q quit without saving changes
s create a new empty Sun disklabel
t change a partition's system id
u change display/entry units
w write table to disk and exit
x extra functionality (experts only)
Command (m for help): a
Partition number (1-1): 1
Error: The flag 'boot' is not available for loop disk labels.
Command (m for help):
First the `n' command don't work and don't print an error message...
but my question is?
Fdisk should work with a file without filesystem?
Thank's, Christian.
|