All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9366] New: no link rootfs.ext4 -> rootfs.ext2
Date: Mon, 17 Oct 2016 21:40:55 +0000	[thread overview]
Message-ID: <bug-9366-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=9366

            Bug ID: 9366
           Summary: no link rootfs.ext4 -> rootfs.ext2
           Product: buildroot
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: mikhail_tchernychev at yahoo.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

Created attachment 6766
  --> https://bugs.busybox.net/attachment.cgi?id=6766&action=edit
this is .config file which make this problem.

Hi, I have compiled raspberry pi 3 image with config file attached here. 
Unfortunately at the very last stage I had manually link 

ln -s rootfs.ext2 rootfs.ext4

in the images/ directory, then run make again and it assembled sdcard.img

When I used default rpi3 config it was not the case, so it is something in my 
custom config, which is default based.

It seems it is something minor.

Thank you
Mikhail

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2016-10-17 21:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-17 21:40 bugzilla at busybox.net [this message]
2016-10-18 13:51 ` [Buildroot] [Bug 9366] no link rootfs.ext4 -> rootfs.ext2 bugzilla at busybox.net
2016-10-18 14:13 ` bugzilla at busybox.net

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=bug-9366-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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.