Perfect. Thanks trash80.
Back to top |
inixi in Pardus
Pardus got the same Issue like ArchLinux
/usr/local/bin is not a directory by default! inxi needs to be put to /usr/bin instead and the dircetory to do the symbolic-link for konversation is: cd /usr/bin && ln -s inxi /usr/kde3.5/apps/konversation/scripts <fixed link syntax> great work! Back to top |
inxi 0.9.4 is released.
This fixes issues where spaces are used in mounted drive's names. One user worked hard to figure out a way to put spaces in their mounted partitions, but they were no match for h2. Previously, these were read incorrectly by inxi, and ignored, which caused mathematical errors in reporting percent used. install or update, and enjoy. Back to top |
minor reporting of xorg settings
Hi TechAdmin
I am just building sidux pontos and before running smxi and nvidia stuff I grabbed inxi and here is my output Graphics: Card nVidia Device 0640 tty resolution ( 141x40 ) its supposed to read 1440 x 900 by 75 Hz No need to look at links unless it excites the curious....heh heh www.mediafire.com/?sharekey=eaf07483aaaea11091b20cc0d07ba4d251df390f17746027 www.mediafire.com/imageview.php?quickkey=mmgo2dtumty&thumb=4 Still having troubles with file sharing site so maybe you can only see the bottom link....if anyone cared to look cheerio Back to top |
don't worry about images, just copy in your inxi -G
output into [ code ]..... [ /code ] (get rid of spaces) and we'll check it out. also, visit irc.oftc.net channel #linux-smokers-club and see if you can give trash80 or me some feedback in real time. There aren't many things that can go wrong there, but maybe you found one of them, you never know. Back to top |
pardus-release in inxi
hi,
is it possible to add on line 231. to "DISTROS_PRIMARY" the "pardus-release" Like this: Code: 231: DISTROS_PRIMARY="gentoo-release mandrake-release redhat-release slackware-version SuSE-release pardus-release" Back to top |
Yes, update now to 0.9.5
Pardus however isn't a primary, it's a derived, but other than that, inxi is updated. Back to top |
minor issue line 231
techAdmin
on same theme as line 231...not that I use it anymore...but maybe when you get a chance to do other things...you could update mandrake to mandriva? 2) I had not realised it might work for Mdv so depending on your reply....in the fullness of time...I shall post in Mdv forum at linuxquestions if you like? cheerio Back to top |
trash80 already has the mandriva stuff set and working as far as I know.
That required a new method, as far as I know it works as expected now. The logic for mandrake / mandriva there is NOT random, and should be working, it is definitely working for trash80, who runs mandriva. Back to top |
Once upon a time, I got this output (snipped for the sake of brevity.
:: Code :: System: Host gx280-debian running Linux 2.6.27-8.slh.1-sidux-686 i686 Distro Debian GNU/Linux 5.0
CPU: Quad Core Intel Xeon cache 1024 KB flags (sse3 nx lm) bmips 28727.4 Clock Speeds: (1) 3590.929 MHz (2) 3590.929 MHz (3) 3590.929 MHz (4) 3590.929 MHz Client Shell inxi 0.8.5 Today, I get this... :: Code :: System: Host gx280-debian Kernel 2.6.28-1.slh.2-sidux-686 i686 (32 bit) Distro Debian GNU/Linux 5.0
CPU: Single Core HT Intel Xeon cache 1024 KB flags (sse3 nx lm) bmips 7181.88 Clock Speeds: (1) 3590.941 MHz (2) 3590.941 MHz (3) 3590.941 MHz (4) 3590.941 MHz Client Shell inxi 0.9.5 For what it's worth. Obviously nothing creates any hardship. The system has (2) 3.6 GHz dual core Xeons. Back to top |
All times are GMT - 8 Hours |