On Thu, Dec 9, 2010 at 7:41 PM, Mulyadi Santosa
<mulyadi.sant...@gmail.com> wrote:
> On Fri, Dec 10, 2010 at 02:06, Prasad Joshi <prasadjoshi...@gmail.com> wrote:
>> After trying most of the block devices to boot the kernel under QEMU,
>> I added few printks around the code that does the mounting.
>>
>> The function mount_root() in file init/do_mounts.c, mounts the root
>> file system. Using following code
>>
>> printk("\n\nmajor=%d minor=%d\n\n", MAJOR(ROOT_DEV), MINOR(ROOT_DEV));
>> create_dev("/dev/root", ROOT_DEV);
>> mount_block_root("/dev/root", root_mountflags);
>>
>> Question 1: Why is it creating a new device file with name /dev/root
>> and mounting the /dev/root? I am specifying my root device to be
>> /dev/hda1 as a boot parameter.
>
> I think it's like unwritten rule...however, if you check /proc/mounts
> in working Linux boxes, it will surely shows /dev/root.
>
> OK, about the problem? Let's see....have you check your kernel config
> and confirm that these two options are enabled?
> CONFIG_SYSFS_DEPRECATED=y
> CONFIG_SYSFS_DEPRECATED_V2=y
>
Thanks a lot Mulyadi for your reply.
c...@prasad-desktop:/mnt/clfs/sources/linux-2.6.36$ grep
CONFIG_SYSFS_DEPRECATED .config
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y
> In short, it's a way to make "old" userspace tools understand the new
> way of Linux kernel represents device structures....Kindly try it and
> tell us if it does fix the problem..
>
I had these flags enabled from the start, but I never new why I
enabled them. Atleast now I know the reason.
Thanks a lot.
>
> --
> regards,
>
> Mulyadi Santosa
> Freelance Linux trainer and consultant
>
> blog: the-hydra.blogspot.com
> training: mulyaditraining.blogspot.com
>
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecar...@nl.linux.org
Please read the FAQ at http://kernelnewbies.org/FAQ
