Invalid argument

[donald]

So the sticky-bit is also set in 3.2.1
3.2.1 work..3.2.2 don't
We (I) need a plan B...

regarding the patterns
http://www.codecoffee.com/tipsforlinux/ ... 032-1.html

[jssouza]

We (I) need a plan B...

Did you try using the 4.8.11 kernel in Porteus 3.2.2? This worked.

[donald]

I'm sure it does.
But the more important question is why?

[Ed_P]

The plan B solution is simple, stay with 3.2.1 and wait for 3.2.3.

[Ed_P]

then just work around

Not much help

Code: Select all

k=$(uname -r)
if [[ ${k%-porteus} == 4.9.0 ]]; then echo "This doesn't work with this release"; ...

[Bogomips]

^ Where there's a way, there's a will. Have to go to dentist tomorrow, so can't really concentrate on an alternative solution.

[Bogomips]

Mebbe give this a whirl?

Code: Select all

k=$(uname -r)
if [[ ${k%-porteus} == 4.9.0 ]]; then  tar c  /home/guest/.config/nemo | tar  x  -C  /tmp/mod
else ...

Testing with sticky bit:

Code: Select all

guest@porteus:~$ mkdir tst
guest@porteus:~$ chmod 1777 tst
guest@porteus:~$ ls -ld tst
drwxrwxrwt 2 guest users 40 Jan 11 13:49 tst/

guest@porteus:~$ tar c /home/guest/.config | tar x -C tst
tar: Removing leading `/' from member names
guest@porteus:~$ du -sh tst
296K    tst

guest@porteus:~$ tree -ad tst
tst
└── home
    └── guest
        └── .config
            ├── autostart-scripts
            ├── gconf
            ├── gnome-mplayer
            ├── kdeconnect
            ├── mc
            ├── pulse
            └── session
10 directories

guest@porteus:~$ ls -ld tst/home/
drwxr-xr-x 3 guest users 60 Jan 11 13:53 tst/home//

No sticky in /tmp:

Code: Select all

guest@porteus:~$ ls -ld /tmp/
drwxrwxrwx 7 root root 36864 Jan 11 13:54 /tmp//
guest@porteus:~$ mkdir /tmp/mod
guest@porteus:~$ tar c /home/guest/.config | tar x -C /tmp/mod
tar: Removing leading `/' from member names
guest@porteus:~$ tree -ad /tmp/mod
/tmp/mod
└── home
    └── guest
        └── .config
            ├── autostart-scripts
            ├── gconf
            ├── gnome-mplayer
            ├── kdeconnect
            ├── mc
            ├── pulse
            └── session
10 directories

guest@porteus:~$ du -sh /tmp/mod/
340K    /tmp/mod/

guest@porteus:~$ ls -ld /tmp/mod/home/
drwxr-xr-x 3 guest users 4096 Jan 11 13:57 /tmp/mod/home//

Code: Select all

guest@porteus:~$ ls -ld /home/
drwxr-xr-x 6 guest users 60 Feb 18  2016 /home//
  

[Ed_P]

OMG!! Wouldn't it be easier to just change the script's mkdir /tmp/mod command to be just mkdir /mod?

[Bogomips]

1. Thought it needed to be in /tmp
2. Using the same cp -a --parents on an ordinary directory, got same error messages:

   Code: Select all

   guest@porteus:~$ mkdir ord
   guest@porteus:~$ cp -a --parents /home/guest/.config/ ord
   cp: preserving permissions for ‘ord/home/guest/.config/autostart-scripts’: Invalid argument
   cp: preserving permissions for ‘ord/home/guest/.config/gnome-mplayer’: Invalid argument
   cp: preserving permissions for ‘ord/home/guest/.config/mc’: Invalid argument
   cp: preserving permissions for ‘ord/home/guest/.config/pulse’: Invalid argument
   cp: preserving permissions for ‘ord/home/guest/.config/gconf’: Invalid argument
   cp: preserving permissions for ‘ord/home/guest/.config/kdeconnect’: Invalid argument
   cp: preserving permissions for ‘ord/home/guest/.config/session’: Invalid argument
   cp: preserving permissions for ‘ord/home/guest/.config’: Invalid argument
   cp: preserving permissions for ‘ord/home/guest’: Invalid argument

Been there, done that.

[Ed_P]

1. Thought it needed to be in /tmp
2. Using the same cp -a --parents on an ordinary directory, got same error messages

Ohh... so it's a whole release problem not just a 3.2.2 /tmp problem. I thought based on donald's post it was only a /tmp problem.

Now I copied to a different location
( cp -a -p /home/guest/.config/* /mnt/sda3/test ) -- (ext2 filesystem)
and got no error at all.

But I see now his destination is outside of the Porteus system. hmmmm...

[Bogomips]

Now I copied to a different location
( cp -a -p /home/guest/.config/* /mnt/sda3/test ) -- (ext2 filesystem)
and got no error at all.

But I see now his destination is outside of the Porteus system. hmmmm...

As pointed out before, -p != --parents.

[beny]

hi bogomips also in virtualbox build log i have the warning,sorry for the italian language but mean the same as you in cp option:

ld -r -m elf_x86_64 -T ./scripts/module-common.lds --build-id -o /tmp/vbox.0/vboxdrv.ko /tmp/vbox.0/vboxdrv.o /tmp/vbox.0/vboxdrv.mod.o ; true
cp: preservazione dei permessi per "/tmp/vbox.0/include/iprt/nocrt": Argomento non valido
cp: preservazione dei permessi per "/tmp/vbox.0/include/iprt": Argomento non valido
cp: preservazione dei permessi per "/tmp/vbox.0/include/VBox/vmm": Argomento non valido
cp: preservazione dei permessi per "/tmp/vbox.0/include/VBox": Argomento non valido
cp: preservazione dei permessi per "/tmp/vbox.0/include": Argomento non valido
cp: preservazione dei permessi per "/tmp/vbox.0/linux": Argomento non valido
cp: preservazione dei permessi per "/tmp/vbox.0/math/gcc": Argomento non valido
cp: preservazione dei permessi per "/tmp/vbox.0/math": Argomento non valido
cp: preservazione dei permessi per "/tmp/vbox.0/r0drv/linux": Argomento non valido
cp: preservazione dei permessi per "/tmp/vbox.0/r0drv": Argomento non valido
make KBUILD_VERBOSE=1 SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 CONFIG_MODULE_SIG= -C /lib/modules/4.9.0-porteus/build -j6 modules
make[1]: warning: -jN forced in submake: disabling jobserver mode.

[ncmprhnsbl]

i get the same 'invalid argument' with 4.9 kernel in Nemesis, and also with 4.9.4 kernel from neko..
so seems to confirm kernel related..
the copying seems to work as expected, though...

[Ed_P]

I've reverted back to 3.2.1. Less of a concern at this point.

[ncmprhnsbl]

still, it may be of value to probe this further...
a little search found this: http://lists.gnu.org/archive/html/bug-c ... 00013.html
which sounds not entirely unrelated..
although, on my void install(kernel 4.9.4, coreutils-8.26) cp -a --parents works without complaint and permissions seem correct...