I recompiled the kernel as you said, and noticed that it doesn't
complain about missing partfs during boot anymore; however there is no
additional sd*, still only sdM0 and sdU0.0, which still doesn't show me
any partitions.

Am 26.03.2013 14:07, schrieb erik quanstrom:
> On Tue Mar 26 08:52:50 EDT 2013, f.psi...@gmx.de wrote:
>> I'm currently trying to set up a usb-hdd as my root filesystem; I found
>> out, that I have to use partfs to actually see the partitions I create,
>> however they don't show up after the next reboot; i have to use fdisk's
>> and prep's w command (without actualy modifying the partition table), to
>> see the partitions I created in the file system. Is that normal?
> 
> that is normal.  but, there is no need to fdisk your disk unless you're
> booting from dos.  you can use prep directly.  for fdisk+prep the
> normal way to do this would be
>       disk/fdisk /dev/sdXX/data>/dev/sdXX/ctl
>       test -f /dev/sdXX/plan9 && disk/prep /dev/sdXX/plan9>/dev/sdXX/ctl
> if you have prep only, only this would be needed
>       disk/prep /dev/sdXX/plan9>/dev/sdXX/ctl
> this is prepackaged in /rc/bin/diskparts, and the kernel will do
> this for you on boot.
> 
>> Also, I don't yet quite understand how to boot from such a partition.
>> Somehow I need to get partfs into the kernel; but I don't know how, and
>> after that, how to use it for booting form the external hdd.
> 
> you need to build partfs into your kernel.  add
>       /arm/bin/disk/partfs
> to the bootdir section of your kernel configuration file and rebuild.
> in the rpi's case, i believe the kernel config is named /sys/src/9/bcm/pi
> or picpu.
> 
> - erik
> 


Reply via email to