i tried to compile the kernel in slackware 14.1
and reboot the machine, but there're some problems like these:
http://slackware.im/media/cache/page...56408749f.jpeg

http://slackware.im/media/cache/page...57c6dd554.jpeg

i tried :
cd /usr/src/linux
make
make modules_install
make installa

and thats my /etc/fstab:

/dev/sda3 swap swap defaults 0 0
/dev/sda2 / ext4 defaults 1 1
/dev/sda1 /boot ext4 defaults 1 2
/dev/sda4 /home jfs defaults 1 2
#/dev/cdrom /mnt/cdrom auto noauto,owner,ro,comment=x-gvfs-show 0 0
/dev/fd0 /mnt/floppy auto noauto,owner 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
proc /proc proc defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
debugfs /sys/kernel/debug debugfs defaults 0 0

how can i make it
thx...

Are you using initrd? Is the default kernel config for the huge kernel or generic? Why are you passing /dev/hda1 as the root device? What's in your lilo.conf file?

There is something missing in your build because root is mounting read-only.

The error message "Filesystem with huge files cannot be mounted RDWR without CONFIG_LBDAF" says it all. Just look at the help text of this option when you do menuconfig.
.

1 members found this post helpful.

thx
the problem has been solved.

please tell us how, as that could help others.

thx,
the problem has been solved.

The error message "Filesystem with huge files cannot be mounted RDWR without CONFIG_LBDAF" says it all.

i msut chose this "Support for large (2TB+) block devices and files" when i "make menuconfig" .
because:

This option is required to support the full capacity of large
(2TB+) block devices, including RAID, disk, Network Block
Device, Logical Volume Manager (LVM) and loopback.

This option also enables support for single files larger than
2TB.
The ext4 filesystem requires that this feature be enabled in
order to support filesystems that have the huge_file feature
enabled. Otherwise, it will refuse to mount in the read-write
mode any filesystems that use the huge_file feature, which is
enabled by default by mke2fs.ext4. The GFS2 filesystem also requires this feature....

yeah

watch #6

Thanks.