Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Poole, Donald R. <drpoole@swri.org>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot RFS Login Question
Date: Thu, 9 Feb 2012 15:16:53 +0000	[thread overview]
Message-ID: <CB593EC4.2F2F%donald.poole@swri.org> (raw)
In-Reply-To: <8762fg4em2.fsf@macbook.be.48ers.dk>

On 2/9/12 2:04 AM, "Peter Korsgaard" <jacmet@uclibc.org> wrote:


>>>>>> "Donald" == Poole, Donald R <drpoole@swri.org> writes:
>
>Hi,
>
> >> If you extract the tarball to your nfsroot as root, yes (or use one of
> >> the other filesystem outputs). You are not trying to use output/target
> >> directly, are you?
>
> Donald> No, I am not. After I create an ext3 filesystem on my SD card
> Donald> (sudo mkfs.ext3 /dev/sdc1 in my case) and mount the newly
> Donald> create filesystem (sudo mount /dev/sdc1 /path/to/mount/point)
> Donald> is do a "sudo tar -xvf rootfs.tar -C /path/to/mount/point".
> Donald> So, when that is all said and done, my filesystem is indeed
> Donald> owned by root, but the setuid bit for /bin/busybox was not set.
>
>Setuid is handled by the device table. Do you have
>
>BR2_ROOTFS_DEVICE_TABLE="target/generic/device_table.txt"
>
>In your Buildroot .config?
>
>-- 
>Bye, Peter Korsgaard

Hmm, interestingly I do have that in my .config.  Why would it have failed
to execute the Setuid in this case?

Donald R. Poole, Jr.
Research Engineer
Voice: 210.522.3131 | Fax: 210.522.4931
Tactical Networks & Communications (tacticalnetworks.swri.org)
Southwest Research Institute (SwRI)

  reply	other threads:[~2012-02-09 15:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-25 15:16 [Buildroot] Buildroot RFS Login Question Poole, Donald R.
2012-01-25 20:34 ` Peter Korsgaard
2012-01-25 20:56   ` Poole, Donald R.
2012-01-25 22:19     ` Peter Korsgaard
2012-02-07  6:31       ` Poole, Donald R.
2012-02-07  9:01         ` Peter Korsgaard
2012-02-08 15:20           ` Poole, Donald R.
2012-02-08 16:18             ` Peter Korsgaard
2012-02-08 16:25               ` Poole, Donald R.
2012-02-08 16:34                 ` Peter Korsgaard
2012-02-08 23:17                   ` Poole, Donald R.
2012-02-09  6:29                     ` Peter Korsgaard
2012-02-09  6:49                       ` Poole, Donald R.
2012-02-09  8:04                         ` Peter Korsgaard
2012-02-09 15:16                           ` Poole, Donald R. [this message]
2012-02-09 15:36                             ` Peter Korsgaard
2012-02-09 19:56                               ` Poole, Donald R.
2012-02-09 21:22                                 ` Peter Korsgaard
2012-02-15 15:22                                   ` Poole, Donald R.
  -- strict thread matches above, loose matches on Subject: below --
2012-01-24 19:59 [Buildroot] FW: " Poole, Donald R.
2012-01-26  7:01 ` [Buildroot] " Sinan Akman
2012-01-26 14:59   ` Poole, Donald R.
     [not found] <CAMe6wuROmEc_vWn8AqYdiRa9bo0Yc2iA9WAFbiy+kWohq09=Ag@mail.gmail.com>
2012-01-22 21:43 ` Peter Korsgaard
     [not found]   ` <CAMe6wuTrAtUXsjByY6pBd9-wZKme0gyvSTzsPnEiFGK3X-n=3g@mail.gmail.com>
2012-01-24 20:29     ` Peter Korsgaard

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=CB593EC4.2F2F%donald.poole@swri.org \
    --to=drpoole@swri.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox