Why can i only copy 100 files with tar /cv6 /.???

the disk is a 1,4 mb floppy but the problem is arg list to
long i can not save on the Harddisc
"Jean-Pierre Radley" <jpr@jpr.com> schrieb im Newsbeitrag
news:20040413200635.GP21316@jpradley.jpr.com...

Waimer Jürgen typed (on Tue, Apr 13, 2004 at 12:34:17AM +0200):
| Why can i only copy 100 files with tar /cv6 /.???

You are not telling us how big they are. Maybe you have filled up the
floppy disk.

What errors do you get?


--
JP

thank you but the problem i the same
it runs Xenix ver 2.3.4 an it runs 16 years whitout problems.
when i make tar cv6F the Names are listet but Xenix say cannot acess
"Waimer Jürgen" <waimer@t-online.de> schrieb im Newsbeitrag
news:c5hfab$sbe$03$1@news.t-online.com...

sorry i start the System the correct Message is could not stat but its ok
and not a important Problem i save the Complette dir and have three Floppies
its not fine but ok

the ls Command with > give the same return arg list to long the shell is sh
as root

"James J" <SPAMMYjajii1@netscape.net> schrieb im Newsbeitrag
news:Xns94CBA162E17B1jajii1netscape@205.188.138.16 1...

"Waimer Jürgen" <waimer@t-online.de> expounded in
news:c5iifi$b7v$06$1@news.t-online.com:

Ah, "arg list too long" has nothing to do with tar. That's a limitation
of the shell. You didn't say which OS you're using, but I assume it's pre-
OSR 5. In OSR 5 they expanded the argument list limit (I forget if it's a
higher limit or no limit).

Anyway, there are various ways you could handle that. One way is to use
tar's F option to tell it to read the list of files to include from a file.
For example, if you wanted to include a* and b*, you could use something
like:

ls a* b* > /tmp/tarlist
tar cv6F /tmp/tarlist


And if that's not the problem, perhaps you could give a clearer example.
The command in your first post didn't really make sense.

James

"Waimer Jürgen" <Waimer@t-online.de> expounded in
news:c5jvcb$uhj$00$1@news.t-online.com:

"Cannot access"? Before you said "arg list too long". I don't know what
"cannot access" means. It's an incomplete message. But it's not the same
thing as "arg list too long".

Let's start over.

What is the exact command that you're entering?

If you are using one of the entries in /etc/default/tar, what does it look
like? For example, if you're using cv6, what does the line that starts
with "archive6=" look like.

What is the exact error message you're getting?

James

i use the command tar cv6 /usr/data/.* and tar splitt the volume but i
save all Data in the directory.

another Question what is with the Y 2000
the Fix 2000 runs but Xenix make after the Februar 29 problems You can test
it in the Sysadmsh the Date is not correct is 1 Day back
"James J" <SPAMMYjajii1@netscape.net> schrieb im Newsbeitrag
news:Xns94CD458732863jajii1netscape@205.188.138.16 1...

"Waimer Jürgen" <Waimer@t-online.de> expounded in
news:c5ka2g$dke$01$1@news.t-online.com:


Trying to enter the same arguments to the ls command probably would give
the "arg list too long" error. The error is coming from the shell, not the
ls or tar command. You need to build your list of files in a different
way. If I knew the specific commands you're using, I could suggest some
specific alternatives. But I'll make a guess.

You say that you're trying to save the complete directory. Does that mean
that you're using "*" (eg. "tar cv6 *")? If so, try using a "." (meaning
the current directory) instead (eg. "tar cv6 ."). Or if you're using a
path and "*" (eg. "tar cv6 /usr/data/*"), try just the directory name (eg.
"tar cv6 /usr/data").
If you give tar a directory name, it will include everything in that
directory, and every directory under it, so you don't have to use "*" and,
in fact, it's more efficient if you don't.

James

"Waimer Jürgen" <Waimer@t-online.de> expounded in
news:c5p4b0$qn4$01$1@news.t-online.com:

So it's working now? Good.

But if you're typing "tar cv6 /usr/data/.*" to save everything in
/usr/data, I'd suggest you at least leave off the "*", and all you really
need is "tar cv6 /usr/data".


I don't think I can help you with that one. I haven't used Xenix in
probably 2 or 3 years, maybe more, and I can't remember if I had problems
with the date after the Y2K patch.
Post a new message with "Xenix Y2K problem" or something like that as the
subject. Then maybe someone who knows something about it will see your
question.

James