netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bob Wirka <bobwirka@rtcworks.com>
To: Michael Richardson <mcr@sandelman.ottawa.on.ca>
Cc: netdev@oss.sgi.com, linux-net@vger.kernel.org
Subject: Re: NFS and Network Driver Question
Date: Wed, 20 Oct 2004 10:47:11 -0500	[thread overview]
Message-ID: <4176887F.3030406@rtcworks.com> (raw)
In-Reply-To: <7126.1098233641@marajade.sandelman.ottawa.on.ca>

[-- Attachment #1: Type: text/plain, Size: 2200 bytes --]

Yes, you are correct; thank you.

So now I've got an embedded x86 system that boots from a (detachable) 
floppy drive to the root file system on my laptop host. Syslinux works 
very well for the boot disk function.

This system is very cool; it will be used to initialize new units in 
production, and for providing a platform for easy debugging of applications.

The lessons learned here will also be used on the embedded ARM projects.

Thanks again to all who have helped.

Best regards,

Bob Wirka
Realtime Control Works

Michael Richardson wrote:

>-----BEGIN PGP SIGNED MESSAGE-----
>
>
>  
>
>>>>>>"Bob" == Bob Wirka <bobwirka@rtcworks.com> writes:
>>>>>>            
>>>>>>
>    Bob> Ok, now I feel like I'm taking crazy pills...
>
>    Bob> The embedded system boots up and mounts the root file system on
>    Bob> my host laptop. The 'rc.sysinit' startup script executes the
>    Bob> command 'mount -a' which should mount /proc, /dev/pts, and
>    Bob> /dev/shm, as listed in /etc/fstab. When executed, that command
>    Bob> returns "mount: only root can do that".
>
>    Bob> When I get to the bash prompt, 'whoami' reports that I am,
>    Bob> indeed, root. A 'mount -a' from the command prompt gives the
>    Bob> same result; it doesn't think I'm root for the mount command.
>
>  The mount command is perhaps setuid root, but you aren't mounting the
>root file system in a way that permits it to be identified as such.
>  Or, the file is in fact not owned by root, and is in fact setuid not-root.
>
>- --
>]     "Elmo went to the wrong fundraiser" - The Simpson         |  firewalls  [
>]   Michael Richardson,    Xelerance Corporation, Ottawa, ON    |net architect[
>] mcr@xelerance.com      http://www.sandelman.ottawa.on.ca/mcr/ |device driver[
>] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.2.2 (GNU/Linux)
>Comment: Finger me for keys
>
>iQCVAwUBQXW3KIqHRg3pndX9AQFERwQAhUpzaFDzVch+W2TEU2SFDtSJZObQ5yZ3
>7hhVtiDI5igzO/MHkipXm89LrNnfwSg+6jfMIo8MlWU+nuqHFWiHkrPeWj8jaFmd
>QQ+aHhryTn06fyU4UQg1OjEpcHHvo4pLr8lqPwebMjL2JKgk8CM/X2d1N6m9xT+2
>Nx8H0Rq84sM=
>=Dso2
>-----END PGP SIGNATURE-----
>
>
>  
>


[-- Attachment #2: Type: text/html, Size: 3131 bytes --]

  reply	other threads:[~2004-10-20 15:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-15 21:31 NFS and Network Driver Question Bob Wirka
2004-10-19 18:03 ` Bob Wirka
2004-10-20  0:19 ` Bob Wirka
2004-10-20  0:54   ` Michael Richardson
2004-10-20 15:47     ` Bob Wirka [this message]
2004-10-20 15:58   ` Stephen Hemminger
2004-10-20 16:03     ` Bob Wirka
2004-10-21 15:09     ` Bob Wirka
2004-10-21 15:50       ` Bob Wirka
2004-10-21 16:17       ` Henrik Nordstrom

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=4176887F.3030406@rtcworks.com \
    --to=bobwirka@rtcworks.com \
    --cc=linux-net@vger.kernel.org \
    --cc=mcr@sandelman.ottawa.on.ca \
    --cc=netdev@oss.sgi.com \
    /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;
as well as URLs for NNTP newsgroup(s).