inxi can't list remote partition name with space (\040) in fstab.

[GoogleCodeExporter]

What steps will reproduce the problem?

1. Mount a remote partition with space (\040) in its name
Ex in /etc/fstab:
//mafreebox.freebox.fr/Disque\040dur    /freebox/Disque\040dur  cifs    
_netdev,guest,cache=none,uid=1000,iocharset=utf8,file_mode=0666,dir_mode=0777   
0       0

2. Call 'inxi -p'

What is the expected output? What do you see instead?

I expected:

ID-11: /freebox/Disque dur size: 229G used: 195G (90%) fs: cifs remote: 
//mafreebox.freebox.fr/Disque Dur

I got:

ID-11: /freebox/Disque dur size: 229G used: 195G (90%) fs: N/A remote: 
//mafreebox.freebox.fr/Disque

What version of the product are you using? On what operating system?

inxi 2.1.28-00 (2014-05-05) on Xubuntu 14.10

Original issue reported on code.google.com by Paul.Gab...@gmail.com on 26 Oct 2014 at 7:08

[GoogleCodeExporter]

Please provide the debugger data set: inxi -xx@14

inxi does I believe handle a space in the mount point, but NOT in the remote 
file system.

It's quite unlikely that I can make inxi handle spaces in that part of the 
data, but it's possible, but only after I see your actual data.

inxi does not use fstab because fstab mount points have zero necessary 
connection to what partitions are actually mounted at the time you run inxi.

Once I see your real data, make sure the remote file sysatem is mounted when 
you run the above debugger command, I can see if there is a hack to support a 
space in the remote file system name, something I have to admit I have never 
seen so far.

Once I have the data, I'll see if anything can be done. No data means no fixes, 
of course.

Original comment by inxi-...@techpatterns.com on 27 Oct 2014 at 12:30

[GoogleCodeExporter]

By the way, in general it's good to update to current inxi (2.2.15 at this 
moment) before posting a bug report, your version is many months old.

Original comment by inxi-...@techpatterns.com on 27 Oct 2014 at 12:31

[GoogleCodeExporter]

The result of 'inxi -xx@14' is inxi-oburo-20141028-094837-all.tar.gz (on 
ftp.techpatterns.com/incoming).

The remote file system ('//mafreebox.freebox.fr/Disque\040dur') was mounted.

My version (inxi 2.1.28) is the latest version provided by Ubuntu.

Original comment by Paul.Gab...@gmail.com on 28 Oct 2014 at 8:55

[GoogleCodeExporter]

I tried with inxi 2.2.15: I got the same (bad) result... 

Original comment by Paul.Gab...@gmail.com on 28 Oct 2014 at 8:58

[GoogleCodeExporter]

Two entries in one row with spaces in the name will be tricky. It would 
probably require fully redoing that logic section because it would have to 
count out or in from known good columns to the ones that could have spaces. 
gawk in this case is using spaces as column identifiers, though it's possible I 
could do it differently, but I have to be very careful with changes there 
because that code is very tricky, and has to handle many different output 
formats. I doubt I can get to this any time soon but it will get done at some 
point in the future, so the issue is accepted. The solution ideally will handle 
any number of spaces, not the finite number that inxi now handles for mount 
points only.

Original comment by inxi-...@techpatterns.com on 28 Oct 2014 at 5:45

• Changed state: Accepted