Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
and so on. Last bugs have been difficult to resolve, hoping today's is the final real one.
pinxi 3.3.09-32 - last bugs being fixed!
model: AMD Ryzen 5 2600
type: MT MCP
family: 17 (23)
L1: 576 KiB
desc: d-6x32 KiB; i-6x64 KiB
L2: 3 MiB
desc: 6x512 KiB
L3: 16 MiB
desc: 2x8 MiB
Re visibility, if anyone is bored, go to https://github.com/smxi/inxi and star the project if you haven't already done it. Going over 1000 would be funny. Otherwise I don't really care that much, more users is in a sense just more work for me, so it's not like I actually benefit in any real way.
And IRC, irc.oftc.net #smxi or irc.libera.chat #smxi - You can also find damentz of liquorix on the oftc smxi channel. Also some distro maintainers, some sys admin guys, elbrus cpu guys. A lot of the stuff to develop inxi never touches github, all the web docs are on smxi.org - see smxi.org/docs/inxi-about.htm No shortage of publicity on inxi, except lately youtube videos have slowed down. Also tried to get the explaining computers guy to help with arm soc stuff, but no go again.
inxi depends on user feedback, aka, issues, from forums I track and have working relationships with key people behind the scenes who are frequent behind the scenes contributors. techpatterns.com/forums also sometimes, github issues sometimes, email issues, forum pms sometimes. There's a lot more going on than github issues with inxi development. None of the recent BSD stuff was public, that was all email. pinxi -Cay1 vs inxi -Ca shows difference, 3.3.10 is almost ready with beta pinxi
Arch packages in AUR pinxi, which is sort of silly, but makes pacman users happy, all the AUR pinxi package does is get the latest inxi-perl/pinxi version, same as wget or curl would do, probably installs the man pages, but inxi -U or pinxi -U --man do that anyway.
Number 1 issue is legacy inxi stuck versions in frozen pool distros then users filing issue or bug reports against issues that were fixed years ago.
A while ago I tried to get @distrotube to test desktops but no luck.
I only use git pushes to commit changes to master and more often, inxi-perl branches. Zero reason to use git.
cd /usr/local/bin && wget -O inxi smxi.org/inxi && chmod +x inxi
cd /usr/local/bin && curl -o pinxi -L smxi.org/inxi
then to install man:
pinxi -U --man
I personally do not understand why people use git as a simple file downloading tool, but each to their own.
I know of at least 1 gaming company that uses it for debugging their Linux game issues. Main problem is that some distros lag so far behind in version that it's almost comical.
Don't hold your breath for contributors, lol, inxi is hard to work on, you have to be good at Perl (I've upped the internal level a lot to levarage the power of native Perl methods and data structures), good at regex, willing to real research, it's not easy stuff to do. i get occasional tiny patches.
If you want to use hte real current version, run pinxi (development version, different name so you can run them side by side, compared, test, etc), not inxi. Use -U flag to update. Big changes about to go into next inxi. I don't actually run inxi myself except now and then to test how output compares to pinxi.
cd /usr/local/bin && wget -O pinxi smxi.org/pinxi && chmod +x pinxii
I put it in /usr/local/bin so it's in PATH. First thing I install on any new system.
the 15 open issues are mostly ongoing updates, not necessarily issues in the normal sense, just things that will always need to be updated. I've had close to zero luck getting anyone to help or contribute to even collecting data on those, the age of the graybeards is fading, it's the time of script kiddies, lol... who expect 'someone else' to do the work.
Free software developer.
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!