mount device problem

QNX Newsgroups (Archives) qdn.public.qnxrtp.os
1

Hi,

With RTP 6.1

I try to mount 2 device on the same partition, it’s not working, I got an
error like Resource busy

I understand what is that means but in a previous version like 6.0 patch C
it was working.

Is it supposed to be like it.

Here the command:
mount /dev/hd0t80 /dump
mount /dev/hd0t80 /help → Resource busy

Thanks

Rick

2

Rick <eric.dionne@eti-gaming.com> wrote:
: With RTP 6.1
: I try to mount 2 device on the same partition, it’s not working, I got an
: error like Resource busy

This is correct/expected/deliberate. It doesn’t make sense to mount
the same thing twice, and you get some weird aliasing/caching/coherence
issues.

: I understand what is that means but in a previous version like 6.0 patch C
: it was working.

That was a bug (well, more of an oversight :slight_smile:.

: Here the command:
: mount /dev/hd0t80 /dump
: mount /dev/hd0t80 /help → Resource busy

You could use proc symlinks to do this: “ln -sP /dump /help”.

3

Hi Rick,

You can only mount a device only once. If you would like to have /help
as well you can do a symbolic link to /dump

e.g. ln -s /dump /help

If this was working under 6.0 then it was a bug that was fixed in 6.1

Thanks

E.


Rick <eric.dionne@eti-gaming.com> wrote:

Hi,

With RTP 6.1

I try to mount 2 device on the same partition, it’s not working, I got an
error like Resource busy

I understand what is that means but in a previous version like 6.0 patch C
it was working.

Is it supposed to be like it.

Here the command:
mount /dev/hd0t80 /dump
mount /dev/hd0t80 /help → Resource busy

Thanks

Rick

4

Thaks guys, it makes sense

“Hardware Support Account” <hw@qnx.com> wrote in message
news:9m0i6n$r5$2@nntp.qnx.com…

Hi Rick,

You can only mount a device only once. If you would like to have /help
as well you can do a symbolic link to /dump

e.g. ln -s /dump /help

If this was working under 6.0 then it was a bug that was fixed in 6.1

Thanks

E.


Rick <> eric.dionne@eti-gaming.com> > wrote:
Hi,

With RTP 6.1

I try to mount 2 device on the same partition, it’s not working, I got
an
error like Resource busy

I understand what is that means but in a previous version like 6.0 patch
C
it was working.

Is it supposed to be like it.

Here the command:
mount /dev/hd0t80 /dump
mount /dev/hd0t80 /help → Resource busy

Thanks

Rick

5

Rick <> eric.dionne@eti-gaming.com> > wrote:
: With RTP 6.1
: I try to mount 2 device on the same partition, it’s not working, I got an
: error like Resource busy

John Garvey:

This is correct/expected/deliberate. It doesn’t make sense to mount
the same thing twice,

paul may:
i have to disagree on that one at least in certain situations,
for instance several qnx personel already know about the classic
amiga OS and the way it operates as they have/had these machines.

to give one example of why mounting one device several times
could be a good thing for RTP would be in any removable device,
weather it be a floppy, CDr, caddyed Hds ect.

in the amiga you can have say (floppy0) df0: mounted as a native
amiga FFS (FastFile System) and the same floppy drive mounted
as say a:

what does that get you you might ask ?, well you can insert a FFS floppy
in that same drive and access that disk by simply referencing fd0:
and you can pop that out and replace it with say a dos formated floppy
and access that disk as a standard dos floppy by referencing a: .

the cool part is that any mounted device such as the floppy
device would poll at access time and it would automaticly realise
that the current disk is eather a FFS or Dos formated disk and
show on the workbench (photon) a user configured .icon for the current
status of that real floppy drive.

its all the same to amigaOS, any device can be used in this way
if you have a reason to set it up to your prefered situation.

RTP should NOT be about restricting the options, it should be able
to adapt with great ease with nothing more than a few shell commands,
device drivers and intigrated UI.

YES i know it can well do this today, BUT the power is in the hardcore
programmers hands (no disrespect to those) and so far people seem content
on porting X apps and turning RTP towards a more hardcore linux style
operation rather than inovating on a 3rd party basis to extend
the raw RTP/Native Photon with the best thans been before it and new
ways to intigrate better idea`s.

if people can find a good reason to multi mount a real (or fake if
thats wanted)device then why remove that option if its useful to them ?,
if theres aliasing/caching/coherence problems perhaps better ways
to counter these problems should be initiated rather than restrict
the option and in doing so restrict the users/3rd party devs options
and how they might prefer to work/inovate ?.

another option id like to see perhaps one day in the near future for RTP would be the FAR more powerful amiga style mount and *assign* commands to replace these linux style symlinks, while there might be a case of legacy compatability to *Nix id submit that RTP should
primarily be considered the new OS that it is and everyone should
TRY and keep any legacy issues weather *nix, Dos, Mac, amiga or
whatever rocks ya boat as secondary issues and primarily everyone
should be working to make RTP/Native Photon the best/most versitile/
expandable and powerful user experience to date.

all the classic OS`s have their strong and weak points, but please
try and make this new RTP as expandable as possible not restrictive
to the end user or as seems the current case, turn it into another Linux.

its early days yet for RTP but it takes YOU* to help create the OS
Platform YOU want, do YOU want just another Linux to port those X apps
too or do you want a NEW Inovative RTP/Native Photon OS ?..

just MPOYU.

*everyone (not just John) reading and useing/trying out RTP.

heres the amigas assign syntax and output on my WinUAE as a reference and give some insight as to its power, id love an RTP enhanced assign 1 day.

(assign ? is the same as RTPs use assign` help syntax)
New Shell process 8
8.Memory:> assign ?
NAME,TARGET/M,LIST/S,EXISTS/S,DISMOUNT/S,DEFER/S,PATH/S,ADD/S,REMOVE/S,VOLS/S,DIRS/S,DEVICES/S:

Volumes:
Memory [Mounted]
32 [Mounted]
SECOND2GIG [Mounted]
NEW32 [Mounted]
work [Mounted]
CDC0 [Mounted]

Directories:
thor CDC0:CDC2/Thor
cdc2 CDC0:CDC2
cache work:CACHE
VMEM CDC0:
MUI CDC0:MUI
Picasso96 CDC0:picasso96/Picasso96
HELP CDC0:Locale/Help

  • CDC0:MUI/Docs
    LOCALE CDC0:Locale
  • CDC0:MUI/Locale
    KEYMAPS CDC0:Devs/Keymaps
    PRINTERS CDC0:Devs/Printers
    REXX CDC0:S
    CLIPS Memory:Clipboards
    T Memory:T
    ENV Memory:ENV
    ENVARC CDC0:Prefs/Env-Archive
    SYS CDC0:
    C CDC0:C
    S CDC0:S
    LIBS CDC0:Libs
  • CDC0:Classes
  • CDC0:MUI/Libs
    DEVS CDC0:Devs
    FONTS CDC0:Fonts
    L CDC0:L

Devices:
KRAW KCON PIPE AUDIO RAM
CON RAW SER PAR PRT
DH0 DF0 DH1 DH2 DH3
DH4 DF1 DF2 DF3
8.Memory:>

and you get some weird aliasing/caching/coherence
issues.

: I understand what is that means but in a previous version like 6.0 patch C
: it was working.

That was a bug (well, more of an oversight > :slight_smile:> .

: Here the command:
: mount /dev/hd0t80 /dump
: mount /dev/hd0t80 /help → Resource busy

You could use proc symlinks to do this: “ln -sP /dump /help”.

Paul May, Manchester, UK,
Phoenix Core © 1999, Phoenix Developer Consortium © 2000, Team Phx © 1999
Phinixi Technologies International LTD © 2000, Phinixi © 2000

6

Previously, Paul May wrote in qdn.public.qnxrtp.os:

Rick <> eric.dionne@eti-gaming.com> > wrote:
: With RTP 6.1
: I try to mount 2 device on the same partition, it’s not working, I got an
: error like Resource busy

John Garvey:
This is correct/expected/deliberate. It doesn’t make sense to mount
the same thing twice,


paul may:
i have to disagree on that one at least in certain situations,
for instance several qnx personel already know about the classic
amiga OS and the way it operates as they have/had these machines.

to give one example of why mounting one device several times
could be a good thing for RTP would be in any removable device,
weather it be a floppy, CDr, caddyed Hds ect.

in the amiga you can have say (floppy0) df0: mounted as a native
amiga FFS (FastFile System) and the same floppy drive mounted
as say a:

what does that get you you might ask ?, well you can insert a FFS floppy
in that same drive and access that disk by simply referencing fd0:
and you can pop that out and replace it with say a dos formated floppy
and access that disk as a standard dos floppy by referencing a: .

the cool part is that any mounted device such as the floppy
device would poll at access time and it would automaticly realise
that the current disk is eather a FFS or Dos formated disk and
show on the workbench (photon) a user configured .icon for the current
status of that real floppy drive.

its all the same to amigaOS, any device can be used in this way
if you have a reason to set it up to your prefered situation.

RTP should NOT be about restricting the options, it should be able
to adapt with great ease with nothing more than a few shell commands,
device drivers and intigrated UI.

YES i know it can well do this today, BUT the power is in the hardcore
programmers hands (no disrespect to those) and so far people seem content
on porting X apps and turning RTP towards a more hardcore linux style
operation rather than inovating on a 3rd party basis to extend
the raw RTP/Native Photon with the best thans been before it and new
ways to intigrate better idea`s.

if people can find a good reason to multi mount a real (or fake if
thats wanted)device then why remove that option if its useful to them ?,
if theres aliasing/caching/coherence problems perhaps better ways
to counter these problems should be initiated rather than restrict
the option and in doing so restrict the users/3rd party devs options
and how they might prefer to work/inovate ?.

another option id like to see perhaps one day in the near future for RTP would be the FAR more powerful amiga style mount and *assign* commands to replace these linux style symlinks, while there might be a case of legacy compatability to *Nix id submit that RTP should
primarily be considered the new OS that it is and everyone should
TRY and keep any legacy issues weather *nix, Dos, Mac, amiga or
whatever rocks ya boat as secondary issues and primarily everyone
should be working to make RTP/Native Photon the best/most versitile/
expandable and powerful user experience to date.

all the classic OS`s have their strong and weak points, but please
try and make this new RTP as expandable as possible not restrictive
to the end user or as seems the current case, turn it into another Linux.

its early days yet for RTP but it takes YOU* to help create the OS
Platform YOU want, do YOU want just another Linux to port those X apps

No !!!


too or do you want a NEW Inovative RTP/Native Photon OS ?..

Yes !!!


just MPOYU.

*everyone (not just John) reading and useing/trying out RTP.

heres the amigas assign syntax and output on my WinUAE as a reference and give some insight as to its power, id love an RTP enhanced assign 1 day.

(assign ? is the same as RTPs use assign` help syntax)
New Shell process 8
8.Memory:> assign ?
NAME,TARGET/M,LIST/S,EXISTS/S,DISMOUNT/S,DEFER/S,PATH/S,ADD/S,REMOVE/S,VOLS/S,DIRS/S,DEVICES/S:

Volumes:
Memory [Mounted]
32 [Mounted]
SECOND2GIG [Mounted]
NEW32 [Mounted]
work [Mounted]
CDC0 [Mounted]

Directories:
thor CDC0:CDC2/Thor
cdc2 CDC0:CDC2
cache work:CACHE
VMEM CDC0:
MUI CDC0:MUI
Picasso96 CDC0:picasso96/Picasso96
HELP CDC0:Locale/Help

  • CDC0:MUI/Docs
    LOCALE CDC0:Locale
  • CDC0:MUI/Locale
    KEYMAPS CDC0:Devs/Keymaps
    PRINTERS CDC0:Devs/Printers
    REXX CDC0:S
    CLIPS Memory:Clipboards
    T Memory:T
    ENV Memory:ENV
    ENVARC CDC0:Prefs/Env-Archive
    SYS CDC0:
    C CDC0:C
    S CDC0:S
    LIBS CDC0:Libs
  • CDC0:Classes
  • CDC0:MUI/Libs
    DEVS CDC0:Devs
    FONTS CDC0:Fonts
    L CDC0:L

Devices:
KRAW KCON PIPE AUDIO RAM
CON RAW SER PAR PRT
DH0 DF0 DH1 DH2 DH3
DH4 DF1 DF2 DF3
8.Memory:

and you get some weird aliasing/caching/coherence
issues.

: I understand what is that means but in a previous version like 6.0 patch C
: it was working.

That was a bug (well, more of an oversight > :slight_smile:> .

: Here the command:
: mount /dev/hd0t80 /dump
: mount /dev/hd0t80 /help → Resource busy

You could use proc symlinks to do this: “ln -sP /dump /help”.


Paul May, Manchester, UK,
Phoenix Core © 1999, Phoenix Developer Consortium © 2000, Team Phx © 1999
Phinixi Technologies International LTD © 2000, Phinixi © 2000