Mail Archives: cygwin/2009/10/28/11:49:31
On 10/28/2009 05:29 AM, Stern, Eli wrote:
> Hi,
>
> I am developing a diskless embedded system (aka the target) that uses Linux as its Operating system. The target connects directly to my PC (XP).
> I would like to boot the target to an NFS server, where is will get the file system.
> I would like to use the Cygwin NFS server in the following manner:
> - Create the target file system on the host (the build host is Linux)
> - Save it to the NFS server. This can be done as part of the build process (send the build results to the NFS server instead of storing locally).
> - Boot the target via NFS
>
> I am currently encountering the following problem:
> When the file system is created, some special files (actually devices), e.g. /dev/console and /dev/tts/0, are craeted using "sudo mknod". When this is done to a regular Linux directory, these devices are create with uid and gid as "root". But when created on the Cygwin NFS server, they are created with my uid and gid.
> Later when the target tries to boot from the NFS, it will not use these devices, since they are not owned by "root", and the boot fails.
>
> How can I get these devices to be owned by "root" (i.e. uid:gid == 0:0)?
Why doesn't the "no_root_squash" option work?
--
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
216 Dalton Rd. (508) 893-9889 - FAX
Holliston, MA 01746
_____________________________________________________________________
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
- Raw text -