Invalid argument

Technical issues/questions of an intermediate or advanced nature.
donald
Full of knowledge
Full of knowledge
Posts: 1127
Joined: 17 Jun 2013, 13:17
Distribution: Porteus 3.2.2 XFCE 32bit
Location: Germany

Re: Invalid argument

Post#16 by donald » 10 Jan 2017, 01:25

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
Samurai
Samurai
Posts: 174
Joined: 09 Jul 2015, 14:17
Distribution: Porteus x86 arm
Location: Liechtenstein

Re: Invalid argument

Post#17 by jssouza » 10 Jan 2017, 05:27

We (I) need a plan B...
Did you try using the 4.8.11 kernel in Porteus 3.2.2? This worked.

donald
Full of knowledge
Full of knowledge
Posts: 1127
Joined: 17 Jun 2013, 13:17
Distribution: Porteus 3.2.2 XFCE 32bit
Location: Germany

Re: Invalid argument

Post#18 by donald » 10 Jan 2017, 06:28

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

User avatar
Ed_P
Contributor
Contributor
Posts: 3072
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Invalid argument

Post#19 by Ed_P » 10 Jan 2017, 06:43

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

User avatar
Ed_P
Contributor
Contributor
Posts: 3072
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Invalid argument

Post#20 by Ed_P » 10 Jan 2017, 16:40

Bogomips wrote: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"; ...
:lol:
Ed

Bogomips
Full of knowledge
Full of knowledge
Posts: 2522
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: Invalid argument

Post#21 by Bogomips » 10 Jan 2017, 20:43

^ Where there's a way, there's a will. Have to go to dentist tomorrow, so can't really concentrate on an alternative solution. :(
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

Bogomips
Full of knowledge
Full of knowledge
Posts: 2522
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: Invalid argument

Post#22 by Bogomips » 11 Jan 2017, 14:05

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//
  
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

User avatar
Ed_P
Contributor
Contributor
Posts: 3072
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Invalid argument

Post#23 by Ed_P » 11 Jan 2017, 20:02

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

Bogomips
Full of knowledge
Full of knowledge
Posts: 2522
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: Invalid argument

Post#24 by Bogomips » 11 Jan 2017, 20:30

  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. :twisted:
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

User avatar
Ed_P
Contributor
Contributor
Posts: 3072
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Invalid argument

Post#25 by Ed_P » 11 Jan 2017, 23:13

Bogomips wrote:
  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.
donald wrote: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...
Ed

Bogomips
Full of knowledge
Full of knowledge
Posts: 2522
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: Invalid argument

Post#26 by Bogomips » 11 Jan 2017, 23:20

Ed_P wrote:
donald wrote: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.
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

beny
Full of knowledge
Full of knowledge
Posts: 720
Joined: 02 Jan 2011, 11:33
Location: italy

Re: Invalid argument

Post#27 by beny » 15 Jan 2017, 17:37

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.

User avatar
ncmprhnsbl
Full of knowledge
Full of knowledge
Posts: 796
Joined: 20 Mar 2012, 03:42
Distribution: 3.2.2-64bit xfce/openbox
Location: australia
Contact:

Re: Invalid argument

Post#28 by ncmprhnsbl » 18 Jan 2017, 22:03

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...
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
Ed_P
Contributor
Contributor
Posts: 3072
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Invalid argument

Post#29 by Ed_P » 19 Jan 2017, 00:51

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

User avatar
ncmprhnsbl
Full of knowledge
Full of knowledge
Posts: 796
Joined: 20 Mar 2012, 03:42
Distribution: 3.2.2-64bit xfce/openbox
Location: australia
Contact:

Re: Invalid argument

Post#30 by ncmprhnsbl » 19 Jan 2017, 01:46

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...
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

Post Reply