X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org From: "Stern, Eli" To: "cygwin AT cygwin DOT com" Date: Wed, 28 Oct 2009 10:29:32 +0100 Subject: Set uid and gid of a file to "root" Message-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 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).=20 I would like to boot the target to an NFS server, where is will get the fil= e 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 g= id as "root". But when created on the Cygwin NFS server, they are created w= ith my uid and gid. Later when the target tries to boot from the NFS, it will not use these dev= ices, 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 =3D=3D 0:0)= ?=20 Thanks Eli Stern -- 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