* problem with root filesystem
@ 2006-03-15 14:17 prafulla chandra vejendla
2006-03-15 22:13 ` Matthew Percival
0 siblings, 1 reply; 5+ messages in thread
From: prafulla chandra vejendla @ 2006-03-15 14:17 UTC (permalink / raw)
To: linux-omap-open-source
Hi all ,
i followed newbie guide and i mounted the root filesystem using the NFS. i
have given read/write access to that folder to all in the exports file .but
i am unable to create single directory in the target .why is it so ?? how to
overcome this problem . i have down loaded the root filesystem from the
following website http://linux.omap.com/pub/filesystem/rootfsosk.tar.bz2
--prafulla chandra
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: problem with root filesystem
2006-03-15 14:17 problem with root filesystem prafulla chandra vejendla
@ 2006-03-15 22:13 ` Matthew Percival
0 siblings, 0 replies; 5+ messages in thread
From: Matthew Percival @ 2006-03-15 22:13 UTC (permalink / raw)
To: Linux OMAP Open Source
G'Day,
> i followed newbie guide and i mounted the root filesystem using the NFS. i
> have given read/write access to that folder to all in the exports file .but
> i am unable to create single directory in the target .why is it so ?? how to
> overcome this problem . i have down loaded the root filesystem from the
> following website http://linux.omap.com/pub/filesystem/rootfsosk.tar.bz2
There are a few possible causes of this, but the most likely is that
you are mounting the filesystem as read-only; make sure you have `rw' in
the `bootargs' environmental variable in u-boot. Here is what I set
them to when using NFS:
setenv bootargs console=ttyS0,115200n8 noinitrd ip=on root=/dev/nfs rw
nfsroot=${MY_IP}:${PATH_TO_ROOTFS},nolock
saveenv
If that is not the problem, check the permissions as they are set on
the host system: it is possible, however unlikely, that you have them
set up in some strange way (eg -r-xr-xr-x).
-- Matthew
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: problem with root filesystem
@ 2006-03-16 14:56 prafulla chandra vejendla
2006-03-17 9:21 ` Ola Helm
0 siblings, 1 reply; 5+ messages in thread
From: prafulla chandra vejendla @ 2006-03-16 14:56 UTC (permalink / raw)
To: Linux-omap-open-source
Matthew,
I have the your steps. I have set rw in boot args and my bootargs also looks
like yours. And I have checked the access rights in the HOST and it has
fulll access. But still the problem prevails. What could be the reason.
G'Day,
> i followed newbie guide and i mounted the root filesystem using the NFS. i
> have given read/write access to that folder to all in the exports file
.but
> i am unable to create single directory in the target .why is it so ?? how
to
> overcome this problem . i have down loaded the root filesystem from the
> following website http://linux.omap.com/pub/filesystem/rootfsosk.tar.bz2
There are a few possible causes of this, but the most likely is that
you are mounting the filesystem as read-only; make sure you have `rw' in
the `bootargs' environmental variable in u-boot. Here is what I set
them to when using NFS:
setenv bootargs console=ttyS0,115200n8 noinitrd ip=on root=/dev/nfs rw
nfsroot=${MY_IP}:${PATH_TO_ROOTFS},nolock
saveenv
If that is not the problem, check the permissions as they are set on
the host system: it is possible, however unlikely, that you have them
set up in some strange way (eg -r-xr-xr-x).
-- Matthew
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: problem with root filesystem
2006-03-16 14:56 prafulla chandra vejendla
@ 2006-03-17 9:21 ` Ola Helm
2006-03-17 10:02 ` prafulla chandra vejendla
0 siblings, 1 reply; 5+ messages in thread
From: Ola Helm @ 2006-03-17 9:21 UTC (permalink / raw)
To: prafulla chandra vejendla; +Cc: Linux-omap-open-source
Hi,
What's the exact error code your system gives when you're trying to create
the folder?
Cheers,
/O
On 3/16/06, prafulla chandra vejendla <v.prafulla@gmail.com> wrote:
>
> Matthew,
>
> I have the your steps. I have set rw in boot args and my bootargs also
> looks
> like yours. And I have checked the access rights in the HOST and it has
> fulll access. But still the problem prevails. What could be the reason.
>
>
> G'Day,
>
> > i followed newbie guide and i mounted the root filesystem using the NFS.
> i
>
> > have given read/write access to that folder to all in the exports file
> .but
>
> > i am unable to create single directory in the target .why is it so ??
> how
> to
>
> > overcome this problem . i have down loaded the root filesystem from the
>
> > following website http://linux.omap.com/pub/filesystem/rootfsosk.tar.bz2
>
> There are a few possible causes of this, but the most likely is that
>
> you are mounting the filesystem as read-only; make sure you have `rw' in
>
> the `bootargs' environmental variable in u-boot. Here is what I set
>
> them to when using NFS:
>
> setenv bootargs console=ttyS0,115200n8 noinitrd ip=on root=/dev/nfs rw
>
> nfsroot=${MY_IP}:${PATH_TO_ROOTFS},nolock
>
> saveenv
>
> If that is not the problem, check the permissions as they are set on
>
> the host system: it is possible, however unlikely, that you have them
>
> set up in some strange way (eg -r-xr-xr-x).
>
> -- Matthew
> _______________________________________________
> Linux-omap-open-source mailing list
> Linux-omap-open-source@linux.omap.com
> http://linux.omap.com/mailman/listinfo/linux-omap-open-source
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: problem with root filesystem
2006-03-17 9:21 ` Ola Helm
@ 2006-03-17 10:02 ` prafulla chandra vejendla
0 siblings, 0 replies; 5+ messages in thread
From: prafulla chandra vejendla @ 2006-03-17 10:02 UTC (permalink / raw)
To: Ola Helm; +Cc: Linux-omap-open-source
Hi Helm,
i am getting this error
# mkdir adfadf
mkdir : Cannot Create Directory 'adfadf' : Read-only file system
--prafulla chandra
On 3/17/06, Ola Helm <ola.hel@gmail.com> wrote:
>
> Hi,
>
> What's the exact error code your system gives when you're trying to create
> the folder?
>
> Cheers,
>
> /O
>
> On 3/16/06, prafulla chandra vejendla < v.prafulla@gmail.com> wrote:
>
> > Matthew,
>
> I have the your steps. I have set rw in boot args and my bootargs also
> looks
> like yours. And I have checked the access rights in the HOST and it has
> fulll access. But still the problem prevails. What could be the reason.
>
>
> G'Day,
>
> > i followed newbie guide and i mounted the root filesystem using the NFS.
> i
>
> > have given read/write access to that folder to all in the exports file
> .but
>
> > i am unable to create single directory in the target .why is it so ??
> how
> to
>
> > overcome this problem . i have down loaded the root filesystem from the
>
> > following website http://linux.omap.com/pub/filesystem/rootfsosk.tar.bz2
>
>
> There are a few possible causes of this, but the most likely is that
>
> you are mounting the filesystem as read-only; make sure you have `rw' in
>
> the `bootargs' environmental variable in u-boot. Here is what I set
>
> them to when using NFS:
>
> setenv bootargs console=ttyS0,115200n8 noinitrd ip=on root=/dev/nfs rw
>
> nfsroot=${MY_IP}:${PATH_TO_ROOTFS},nolock
>
> saveenv
>
> If that is not the problem, check the permissions as they are set on
>
> the host system: it is possible, however unlikely, that you have them
>
> set up in some strange way (eg -r-xr-xr-x).
>
> -- Matthew
> _______________________________________________
> Linux-omap-open-source mailing list
> Linux-omap-open-source@linux.omap.com
> http://linux.omap.com/mailman/listinfo/linux-omap-open-source
>
>
>
>
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2006-03-17 10:02 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-03-15 14:17 problem with root filesystem prafulla chandra vejendla
2006-03-15 22:13 ` Matthew Percival
-- strict thread matches above, loose matches on Subject: below --
2006-03-16 14:56 prafulla chandra vejendla
2006-03-17 9:21 ` Ola Helm
2006-03-17 10:02 ` prafulla chandra vejendla
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox