inxi root requirement

[VastOne]

It has nothing to do with the kernel

run this

Code Select Expand

whereis inxi

[Sector11]

It has nothing to do with the kernel

run this

Code Select Expand

whereis inxi

I am now on:
    VSIDO Liquorix Kernel 3.7.0-6
    VSIDO Liquorix Kernel 3.7.0-6 - Latest Upload 06JAN2013 20:58 CST

Ran smxi twice to get rid of "nouveau" liquorix updated and nvidia added.

Code Select Expand

sector11@sda10-11:~$ whereis inxi
inxi: /usr/sbin/inxi /usr/share/man/man1/inxi.1.gz
sector11@sda10-11:~$

That looks promising ... I am in OB:

Code Select Expand

sector11@sda10-11:~$ inxi
Error No: 1 - You must be root to run this script!
sector11@sda10-11:~$

OK, next:

Code Select Expand

sector11@sda10-11:~$ $PATH
bash: /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/sbin:/usr/sbin:/home/sector11/bin: No such file or directory
sector11@sda10-11:~$ export PATH="$PATH:/sbin:/bin"
sector11@sda10-11:~$ re
sector11@sda10-11:~$ $PATH
bash: /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/sbin:/usr/sbin:/home/sector11/bin:/sbin:/bin:/sbin:/usr/sbin:/home/sector11/bin: No such file or directory
sector11@sda10-11:~$ inxi
Error No: 1 - You must be root to run this script!
sector11@sda10-11:~$

Hmmmm reboot I believe I read.
BRB

[Sector11]

No go:

Code Select Expand

sector11@sda10-11:~$ inxi
Error No: 1 - You must be root to run this script!
sector11@sda10-11:~$

but it is here:

Code Select Expand

sector11@sda10-11:~$ sudo inxi
[sudo] password for sector11:
Resuming in non X mode: glxinfo not found. For package install advice run: inxi --recommends
CPU~Triple core AMD Athlon II X3 450 (-MCP-) clocked at 3214.616 Mhz Kernel~3.7.0-2.dmz.1-liquorix-amd64 x86_64 Up~2 min Mem~333.9/5962.4MB HDD~250.1GB(3.1% used) Procs~121 Client~Shell inxi~1.8.28 
sector11@sda10-11:~$

I must be junxed.

[Sector11]

No - not me, OpenBox ... I changed sessions:
Now in XFCE4

Code Select Expand

sector11@sda10-11:~$ $PATH
bash: /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/sbin:/usr/sbin:/home/sector11/bin: No such file or directory
sector11@sda10-11:~$ export PATH="$PATH:/sbin:/bin"
sector11@sda10-11:~$ re
sector11@sda10-11:~$ $PATH
bash: /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/sbin:/usr/sbin:/home/sector11/bin:/sbin:/bin:/sbin:/usr/sbin:/home/sector11/bin: No such file or directory
sector11@sda10-11:~$ inxi
Resuming in non X mode: glxinfo not found. For package install advice run: inxi --recommends
CPU~Triple core AMD Athlon II X3 450 (-MCP-) clocked at 3214.616 Mhz Kernel~3.7.0-2.dmz.1-liquorix-amd64 x86_64 Up~6 min Mem~167.4/5962.4MB HDD~250.1GB(3.1% used) Procs~118 Client~Shell inxi~1.8.28 
sector11@sda10-11:~$

Now I go back to OB and it works just fine.

So the problem is OB playing nice.

I'm going back to SDA1-2  for a bit...

[Sector11]

Back on SDA1-2
Does not work at all.
I am in XFCE4:

Code Select Expand

sector11@sda1-2:~$ whereis inxi
inxi: /usr/sbin/inxi /usr/share/man/man1/inxi.1.gz
sector11@sda1-2:~$ inxi
Error No: 1 - You must be root to run this script!
sector11@sda1-2:~$ $PATH
bash: /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/sbin:/usr/sbin:/home/sector11/bin: No such file or directory
sector11@sda1-2:~$ export PATH="$PATH:/sbin:/bin"
sector11@sda1-2:~$ re
sector11@sda1-2:~$ $PATH
bash: /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/sbin:/usr/sbin:/home/sector11/bin:/sbin:/bin:/sbin:/usr/sbin:/home/sector11/bin: No such file or directory
sector11@sda1-2:~$ inxi
Error No: 1 - You must be root to run this script!
sector11@sda1-2:~$


OK, end it for tonight....

[VastOne]

I finally found time to install a new VSIDO setup and have found the issue and now know what has been causing inxi to need sudo to run

inxi is part of smxi script package and now is a symlink to smxi instead of being it's own file, which is why Sector11 kept seeing it as a 14k file.. that is the size of the symlink

This requires running inxi as sudo because that is a smxi requirement. 

Solution - You can get the independent version of inxi and place it in your path and never have to use sudo again. The issue with this is it will never be updated, unless you go out and update it manually. This is an issue because it was updated just today within smxi

The VSIDO solution is to keep it just as it is, within the smxi scripts as a symlink and will require sudo to run it.  This will guarantee that inxi will stay updated.  I would recommend an alias of sudo inxi so that you only have to enter your password when you run it.

I think what has changed just recently is that smxi changed it from a full install of inxi to the symlink model.

At least I now know what is going on...

@Sector11 - Thanks for all your help on this!