inutoc on AIX 5.2 - doesn't work when in `pwd` is space

[Andy]

# pwd
/install/Netscape 7.1
# inutoc .
restore: 0511-126 Cannot open /install/Netscape: A file or directory
in the path name does not exist.
Mount volume 1 on /install/Netscape.
Press the Enter key to continue.
# cd ..
# mv Netscape* Netscape_7.1
# cd Netscape_7.1
# pwd
/install/Netscape_7.1
# inutoc .
#

Is it OK?

thx and regards,
A.,

[Kent Squires]

i opened up a PMR with IBM on this and reqeusted spaces be allowed.

Hopefully the developers will agree to the change, but right now it's
"working as designed".

On 11 Sep 2003 07:33:59 -0700, [email]gk15374@yahoo.com[/email] (Andy) wrote:

># pwd
>/install/Netscape 7.1
># inutoc .
>restore: 0511-126 Cannot open /install/Netscape: A file or directory
>in the path name does not exist.
>Mount volume 1 on /install/Netscape.
> Press the Enter key to continue.
># cd ..
># mv Netscape* Netscape_7.1
># cd Netscape_7.1
># pwd
>/install/Netscape_7.1
># inutoc .
>#
>
>Is it OK?
>
>thx and regards,
>A.,

[Todd H.]

Kent Squires <ksquires@geeks.org> writes:

> i opened up a PMR with IBM on this and reqeusted spaces be allowed.
>
> Hopefully the developers will agree to the change, but right now it's
> "working as designed".

Yikes. What respectable UNIX sysadmin would use spaces in a filename
much less a directory names in UNIX? Or did the Netscape installer
program do that?

The script should be able to handle it though if AIX allows the
creation of such a directory, I can agree. :-)

Best Regards,
--
Todd H.
[url]http://www.toddh.net/[/url]

[Steve Nottingham]

[email]comphelp@toddh.net[/email] (Todd H.) wrote in message news:<m07k4f9nuy.fsf@rcn.com>...

> Kent Squires <ksquires@geeks.org> writes:

> > i opened up a PMR with IBM on this and reqeusted spaces be allowed.
> >
> > Hopefully the developers will agree to the change, but right now it's
> > "working as designed".

>
> Yikes. What respectable UNIX sysadmin would use spaces in a filename
> much less a directory names in UNIX? Or did the Netscape installer
> program do that?
>
> The script should be able to handle it though if AIX allows the
> creation of such a directory, I can agree. :-)
>
> Best Regards,

Spaces can only be tolerated if you use backslashes before the space
or enclose the directory in double quotes ("). This isn't a comedy
operating system like that Windoze sh*te :-)

Steve

[Jurjen Oskam]

In article <o281mvsqh0hhhv93je79hbov86avkkiu7a@4ax.com>, Kent Squires wrote:

> i opened up a PMR with IBM on this and reqeusted spaces be allowed.
>
> Hopefully the developers will agree to the change, but right now it's
> "working as designed".

I've had to go through this "works as designed"-crap myself recently, with
a TSM problem. You should challenge the "works as designed" response, the
manual page of inutoc is entirely clear about this:

inutoc [ Directory ]

Combine this with the syntax of mkdir, rmdir, mount, etc :

mkdir [ -m Mode ] [ -p ] Directory ...
rmdir [ -p ] Directory ...
mount [ -f ] [ -n Node ] [ -o Options ] [ -p ] [ -r ] [ -v VfsName ] [ -t Type |
[ Device | Node:Directory ] Directory | all | -a ] [-V [generic_options]


They say that inutoc works as designed? Then ask for mkdir, rmdir, mount, etc.
to be fixed, since these are obviously broken since they *do* work with
directories with spaces in their names. This must, of course, be fixed.


Show them the absurdity of their "works as designed", and lead them to a
contradiction.

--
Jurjen Oskam

PGP Key available at [url]http://www.stupendous.org/[/url]

[Jurjen Oskam]

In article <m07k4f9nuy.fsf@rcn.com>, Todd H. wrote:

> Yikes. What respectable UNIX sysadmin would use spaces in a filename
> much less a directory names in UNIX? Or did the Netscape installer
> program do that?

A respectable UNIX sysadmin would take spaces in filenames into account,
since spaces are an allowed part of a filename (and *especially* so
with the new cifs filesystem; in the Windows world these names are quite
common).

There's a reason GNU find and GNU cpio have the -null option; they close
the hole that's created by having control characters in filenames.

--
Jurjen Oskam

PGP Key available at [url]http://www.stupendous.org/[/url]

[Steve Nottingham]

Jurjen Oskam <joskam@quadpro.stupendous.org> wrote in message news:<slrnbm2qnr.9nu.joskam@calvin.quadpro.stupend ous.org>...

> In article <o281mvsqh0hhhv93je79hbov86avkkiu7a@4ax.com>, Kent Squires wrote:
>

> > i opened up a PMR with IBM on this and reqeusted spaces be allowed.
> >
> > Hopefully the developers will agree to the change, but right now it's
> > "working as designed".

>
> I've had to go through this "works as designed"-crap myself recently, with
> a TSM problem. You should challenge the "works as designed" response, the
> manual page of inutoc is entirely clear about this:
>
> inutoc [ Directory ]

And intutoc netscape 7.1 is not the same as inutoc "netscape 7.1"

>
> Combine this with the syntax of mkdir, rmdir, mount, etc :
>
> mkdir [ -m Mode ] [ -p ] Directory ...
> rmdir [ -p ] Directory ...

If you do mkdir wibble blah, you will get two directories, if you do
mkdir "wibble blah" you will get one directory

> mount [ -f ] [ -n Node ] [ -o Options ] [ -p ] [ -r ] [ -v VfsName ] [ -t Type |
> [ Device | Node:Directory ] Directory | all | -a ] [-V [generic_options]
>
>
> They say that inutoc works as designed? Then ask for mkdir, rmdir, mount, etc.
> to be fixed, since these are obviously broken since they *do* work with
> directories with spaces in their names. This must, of course, be fixed.
>
>

They are not broken, they are working as designed, AIX uses spaces as
the delimiting character. Taking this one step further, how would it
interpret this command: cp wibble blah blah wibble ! Doing it the
correct way with quotes: cp "wibble blah" "blah wibble"

Windows does not allow filenames with spaces, what it does do is put
the file name in the comment field, so it is a hack as the filename is
still in 8.3 format e.g. Program Files actually is Program~1. AIX
allows spaces in the filename, but you HAVE to use quotes to get them
there.

Steve

[Jurjen Oskam]

In article <42862645.0309120158.7611a1dc@posting.google.com >, Steve Nottingham wrote:

>> inutoc [ Directory ]

>
> And intutoc netscape 7.1 is not the same as inutoc "netscape 7.1"

No. I didn't say it was. The point is that "inutoc ." fails if the
current directory has a space in the name. That is broken behaviour.
You *cannot* get inutoc to work on a directory that has a space in
the name, even if you *do* specify the full path, with quotes.

> Windows does not allow filenames with spaces, what it does do is put
> the file name in the comment field, so it is a hack as the filename is
> still in 8.3 format e.g. Program Files actually is Program~1.

Wrong. On NTFS, filenames are not restricted to 8.3. Those names are by
default still generated *for backwards compatibility*, but that is tunable.
You can turn off 8.3 names generation. Also, spaces *are* allowed in
filenames, and no hack is required.

--
Jurjen Oskam

PGP Key available at [url]http://www.stupendous.org/[/url]

[Todd H.]

[email]steve@wakefieldrfc.freeserve.co.uk[/email] (Steve Nottingham) writes:

> Jurjen Oskam <joskam@quadpro.stupendous.org> wrote in message news:<slrnbm2qnr.9nu.joskam@calvin.quadpro.stupend ous.org>...

> > They say that inutoc works as designed? Then ask for mkdir, rmdir,
> > mount, etc. to be fixed, since these are obviously broken since
> > they *do* work with directories with spaces in their names. This
> > must, of course, be fixed.

>
> They are not broken, they are working as designed, AIX uses spaces as
> the delimiting character.

Steve, you've missed the gist of what Jurjen was saying. He was
highlighting:

mkdir "blah foo" CORRECTLY creates a directory with a space.
rmdir "blah foo" will CORRECTLY remove that directly.
etc.

Which makes it clear that AIX does allow spaces in directory names.

But intuoc ./ or whatever started this thread happens to choke when it
encounters dirs with spaces in them. Which obviously is absurd and
broken because, obviously, AIX does permit spaces in directory names
if mkdir and rmdir allow them.

--
Todd H.
[url]http://www.toddh.net/[/url]

[Andy]

[email]steve@wakefieldrfc.freeserve.co.uk[/email] (Steve Nottingham) wrote in message news:<42862645.0309120158.7611a1dc@posting.google. com>...

> Jurjen Oskam <joskam@quadpro.stupendous.org> wrote in message news:<slrnbm2qnr.9nu.joskam@calvin.quadpro.stupend ous.org>...

> > In article <o281mvsqh0hhhv93je79hbov86avkkiu7a@4ax.com>, Kent Squires wrote:
> >

> > > i opened up a PMR with IBM on this and reqeusted spaces be allowed.
> > >
> > > Hopefully the developers will agree to the change, but right now it's
> > > "working as designed".

> >
> > I've had to go through this "works as designed"-crap myself recently, with
> > a TSM problem. You should challenge the "works as designed" response, the
> > manual page of inutoc is entirely clear about this:
> >
> > inutoc [ Directory ]

>
> And intutoc netscape 7.1 is not the same as inutoc "netscape 7.1"

Mr. Nottingham,
I had run "inutoc ." being in "/install/Netscape 7.1/"!!!! It had to
work if there would be no bug related to the command. Please don't
tell me that I should run inutoc "." - it is crazy!!!

>

> >
> > Combine this with the syntax of mkdir, rmdir, mount, etc :
> >
> > mkdir [ -m Mode ] [ -p ] Directory ...
> > rmdir [ -p ] Directory ...

>
> If you do mkdir wibble blah, you will get two directories, if you do
> mkdir "wibble blah" you will get one directory
>

> > mount [ -f ] [ -n Node ] [ -o Options ] [ -p ] [ -r ] [ -v VfsName ] [ -t Type |
> > [ Device | Node:Directory ] Directory | all | -a ] [-V [generic_options]
> >
> >
> > They say that inutoc works as designed? Then ask for mkdir, rmdir, mount, etc.
> > to be fixed, since these are obviously broken since they *do* work with
> > directories with spaces in their names. This must, of course, be fixed.
> >
> >

>
> They are not broken, they are working as designed, AIX uses spaces as
> the delimiting character. Taking this one step further, how would it
> interpret this command: cp wibble blah blah wibble ! Doing it the
> correct way with quotes: cp "wibble blah" "blah wibble"
>
> Windows does not allow filenames with spaces, what it does do is put
> the file name in the comment field, so it is a hack as the filename is
> still in 8.3 format e.g. Program Files actually is Program~1. AIX
> allows spaces in the filename, but you HAVE to use quotes to get them
> there.
>
> Steve