Project Home
Project Home
Documents
Documents
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - Issue with USB stick under 6.6: (13 Items)
   
Issue with USB stick under 6.6  
In  what may turn out to be a never ending attempt to create a bootable QNX 6.6 system using only QNX 6.6 I ran into 
this roadblock.

From a QNX 6.5 VM I do the following:

# devb-umass cam pnp disk name=umass
# ls /dev/umass0
/dev/umass0  /dev/umass0t179
# mkqnx6fsys -q /dev/umass0179
# mount -tqnx6 /dev/umass0t179 /fs/usb0

When I do exactly the same thing from the QNX 6.6 VM I get the following:
#mount -tqnx6 /dev/umass0t179
mount: Can't mount /fs/usb0 (type qnx6)
mount: Possible reason: Read-only file system

Anyone run into this before?
RE: Issue with USB stick under 6.6  
You need mount -t qnx6 -o sync=optional /dev/umass0t179 /fs/usb0

The USB device is not reporting that it supports the hardware sync command.

-----Original Message-----
From: Mitchell Schoenbrun [mailto:community-noreply@qnx.com] 
Sent: March-27-14 10:33 AM
To: general-filesystems
Subject: Issue with USB stick under 6.6

In  what may turn out to be a never ending attempt to create a bootable QNX 6.6 system using only QNX 6.6 I ran into 
this roadblock.

From a QNX 6.5 VM I do the following:

# devb-umass cam pnp disk name=umass
# ls /dev/umass0
/dev/umass0  /dev/umass0t179
# mkqnx6fsys -q /dev/umass0179
# mount -tqnx6 /dev/umass0t179 /fs/usb0

When I do exactly the same thing from the QNX 6.6 VM I get the following:
#mount -tqnx6 /dev/umass0t179
mount: Can't mount /fs/usb0 (type qnx6)
mount: Possible reason: Read-only file system

Anyone run into this before?



_______________________________________________

General
http://community.qnx.com/sf/go/post109636
To cancel your subscription to this discussion, please e-mail general-filesystems-unsubscribe@community.qnx.com
Re: RE: Issue with USB stick under 6.6  
Thanks for getting back to me so fast on this.  I notice that unlike 6.5, mkqnx6fsys does not create the .boot directory
.   Will just doing a "mkdir .boot" solve that?   It seemed like there was something special about the .boot directory 
that used to be created.
RE: RE: Issue with USB stick under 6.6  
mkqnx6fs  should create the /.boot directory automatically.  Yes, the /.boot directory is special, and doing an "mkdir /
.boot" isn't going to work.  Do you still have the 6.5.0 version of mkqnx6fs to try, and compare (use the same OS, just 
run the older binary).

-----Original Message-----
From: Mitchell Schoenbrun [mailto:community-noreply@qnx.com] 
Sent: March-27-14 10:41 AM
To: general-filesystems
Subject: Re: RE: Issue with USB stick under 6.6

Thanks for getting back to me so fast on this.  I notice that unlike 6.5, mkqnx6fsys does not create the .boot directory
.   Will just doing a "mkdir .boot" solve that?   It seemed like there was something special about the .boot directory 
that used to be created.



_______________________________________________

General
http://community.qnx.com/sf/go/post109638
To cancel your subscription to this discussion, please e-mail general-filesystems-unsubscribe@community.qnx.com
Re: RE: RE: Issue with USB stick under 6.6  
The difference appears to be "ls".
Under QNX 6.5 (and every QNX back to 4) when run as root, ls shows the DOT files.   Under 6.6 it does not.  Maybe this 
is how it is supposed to work?
Re: RE: RE: Issue with USB stick under 6.6  
Yes.  ls -a will show the '.' and '..' .

On Thu, Mar 27, 2014 at 11:05:30AM -0400, Mitchell Schoenbrun wrote:
> The difference appears to be "ls".
> Under QNX 6.5 (and every QNX back to 4) when run as root, ls shows the DOT files.   Under 6.6 it does not.  Maybe this
 is how it is supposed to work?
> 
> 
> 
> _______________________________________________
> 
> General
> http://community.qnx.com/sf/go/post109640
> To cancel your subscription to this discussion, please e-mail general-filesystems-unsubscribe@community.qnx.com
Re: Issue with USB stick under 6.6  
It's likely that you had an alias in your 6.5 system to add the -a to ls

On 2014-03-27 11:05 AM, Mitchell Schoenbrun wrote:
> The difference appears to be "ls".
> Under QNX 6.5 (and every QNX back to 4) when run as root, ls shows the DOT files.   Under 6.6 it does not.  Maybe this
 is how it is supposed to work?
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post109640
> To cancel your subscription to this discussion, please e-mail general-filesystems-unsubscribe@community.qnx.com

Re: Issue with USB stick under 6.6  
No it was changed.  We were the only system that did
the dots for root and it broke stuff.

On Thu, Mar 27, 2014 at 01:04:03PM -0400, Colin Burgess wrote:
> It's likely that you had an alias in your 6.5 system to add the -a to ls
> 
> On 2014-03-27 11:05 AM, Mitchell Schoenbrun wrote:
> > The difference appears to be "ls".
> > Under QNX 6.5 (and every QNX back to 4) when run as root, ls shows the DOT files.   Under 6.6 it does not.  Maybe 
this is how it is supposed to work?
> >
> >
> >
> > _______________________________________________
> >
> > General
> > http://community.qnx.com/sf/go/post109640
> > To cancel your subscription to this discussion, please e-mail general-filesystems-unsubscribe@community.qnx.com
> 
> 
> 
> 
> 
> _______________________________________________
> 
> General
> http://community.qnx.com/sf/go/post109647
> To cancel your subscription to this discussion, please e-mail general-filesystems-unsubscribe@community.qnx.com
Re: Issue with USB stick under 6.6  
> 
> No it was changed.  We were the only system that did
> the dots for root and it broke stuff.
> 
Sean,

    Now that I understand the change, it's not a problem.   But I'm very curious as what might have broke.   Anything 
obvious, or all subtle stuff?

Mitchell
Re: Issue with USB stick under 6.6  
On Thu, Mar 27, 2014 at 02:57:39PM -0400, Mitchell Schoenbrun wrote:
> > 
> > No it was changed.  We were the only system that did
> > the dots for root and it broke stuff.
> > 
> Sean,
> 
>     Now that I understand the change, it's not a problem.   But I'm very curious as what might have broke.   Anything 
obvious, or all subtle stuff?

There were a couple of packages that parsed the ls output on install
and got confused.  I don't remember which ones ATM.
Re: Issue with USB stick under 6.6  
And yes, I'll mention this change in the release notes.

> On Thu, Mar 27, 2014 at 02:57:39PM -0400, Mitchell Schoenbrun wrote:
> > > 
> > > No it was changed.  We were the only system that did
> > > the dots for root and it broke stuff.
> > > 
> > Sean,
> > 
> >     Now that I understand the change, it's not a problem.   But I'm very 
> curious as what might have broke.   Anything obvious, or all subtle stuff?
> 
> There were a couple of packages that parsed the ls output on install
> and got confused.  I don't remember which ones ATM.


Re: Issue with USB stick under 6.6  
> On Thu, Mar 27, 2014 at 02:57:39PM -0400, Mitchell Schoenbrun wrote:

> There were a couple of packages that parsed the ls output on install
> and got confused.  I don't remember which ones ATM.

At the risk of sounding Igorish, so at the risk for breaking existing customer script in favor of compatibility with 
packages most of us are not able to build anymore, the behavior was changed ?  

The change in behavior is not document in ls and I don`t recall reading about it anywhere.

Re: Issue with USB stick under 6.6  
On Mon, Mar 31, 2014 at 06:04:36AM -0400, Mario Charest wrote:
> > On Thu, Mar 27, 2014 at 02:57:39PM -0400, Mitchell Schoenbrun wrote:
> 
> > There were a couple of packages that parsed the ls output on install
> > and got confused.  I don't remember which ones ATM.
> 
> At the risk of sounding Igorish, so at the risk for breaking existing customer script in favor of compatibility with 
packages most of us are not able to build anymore, the behavior was changed ?  

I'm trying to hack up a way to build most things with what's
released in 6.6.

> 
> The change in behavior is not document in ls and I don`t recall reading about it anywhere.

This is being addressed in a release note.  On the other hand, the
root exception was never doc'd AFAICT so it now matches its previously
doc'd behaviour.