From: Jonathan Liu <net147@gmail.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] boot-directdisk: mount root by MBR disk signature for Linux 3.8+
Date: Tue, 09 Jul 2013 23:58:22 +1000 [thread overview]
Message-ID: <51DC16FE.9070103@gmail.com> (raw)
In-Reply-To: <51B5FE40.10107@linux.intel.com>
On 11/06/2013 2:26 AM, Darren Hart wrote:
>
> On 06/08/2013 06:03 AM, Jonathan Liu wrote:
>> Hi Darren,
>>
>>>> + sed -i "s|\broot=[^ ]*|root=PARTUUID=$DISK_SIGNATURE-02|" $HDDDIR/syslinux.cfg
>>> In bootimg.bbclass I have been abstracting out the boot loader so it is
>>> not explicitly referenced. Something like that is in order here. For
>>> example, an EFI boot-directdisk (which admittedly doesn't exist yet)
>>> would not have a syslinux.cfg but would still need the change. Consider
>>> using the syslinux class to abstract this necessary change. Then I can
>>> add the gummiboot change when EFI support is added.
>> Do you mean adding a function to the syslinux class which updates root=
>> in syslinux.cfg previously created by build_syslinux_cfg()?
> In the words of a wise director at a large technology company, "I meant
> whatever is the most intelligent." :-)
>
> This could be a new function in syslinux.bbclass. It could also be a
> parameter to build_syslinux_cfg which would allow it to be used from
> either bootimg.bbclass, boot-directdisk.bbclass, with or without EFI,
> with various kernel versions, etc. I suspect some parameterization will
> result in the cleanest, most maintainable approach, but investigation is
> required.
>
> Thanks!
>
> Darren
Submitted V3 patch which sets SYSLINUX_ROOT appropriately instead of
modifying syslinux.cfg directly.
Regards,
Jonathan
>
>>> --
>>> Darren
>>>
>>>> + fi
>>>> +
>>>> mkdosfs -n ${BOOTDD_VOLUME_ID} -S 512 -C $HDDIMG $BLOCKS
>>>> mcopy -i $HDDIMG -s $HDDDIR/* ::/
>>>>
>>>> @@ -71,10 +88,8 @@ build_boot_dd() {
>>>> END3=`expr \( $ROOTFSBLOCKS \* 1024 \) + $END1`
>>>>
>>>> echo $ROOTFSBLOCKS $TOTALSIZE $END1 $END2 $END3
>>>> - rm -rf $IMAGE
>>>> dd if=/dev/zero of=$IMAGE bs=1024 seek=$TOTALSIZE count=1
>>>>
>>>> - parted $IMAGE mklabel msdos
>>>> parted $IMAGE mkpart primary fat16 0 ${END1}B
>>>> parted $IMAGE unit B mkpart primary ext2 ${END2}B ${END3}B
>>>> parted $IMAGE set 1 boot on
>>>>
>> Regards,
>> Jonathan
>>
prev parent reply other threads:[~2013-07-09 14:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 4:31 [PATCH] boot-directdisk: mount root by MBR disk signature for Linux 3.8+ Jonathan Liu
2013-06-07 23:28 ` Darren Hart
2013-06-08 13:03 ` Jonathan Liu
2013-06-10 16:26 ` Darren Hart
2013-07-09 13:58 ` Jonathan Liu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51DC16FE.9070103@gmail.com \
--to=net147@gmail.com \
--cc=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.