Search
288 results for “smxi”
-
Next #inxi is shaping up well, all running in #pinxi now. Came across an ancient distro I'd never heard of, #TDSDE, which apparently preceded Gentoo by a few months. Poor docs, unreliable source builds, but got everything inxi cares about working, and found some weak spots. These corner case distros often expose weak assumptions.
Also locked down #rpm packages, #urpm #eopkg #pisi repo reports, which were not great, or not working.
Took a while to get enough fixes to warrant a new release.
-
Next #inxi is shaping up well, all running in #pinxi now. Came across an ancient distro I'd never heard of, #TDSDE, which apparently preceded Gentoo by a few months. Poor docs, unreliable source builds, but got everything inxi cares about working, and found some weak spots. These corner case distros often expose weak assumptions.
Also locked down #rpm packages, #urpm #eopkg #pisi repo reports, which were not great, or not working.
Took a while to get enough fixes to warrant a new release.
-
Found issues in #inxi repo report for some software sorced repo lists.: #mageia's #urpmq, #pisi, #solus #eopkg. These all are roughly similar and all had same report glitch of showing one repo data source per output line instead of source then all repos. The output was also weird. Corrected in #pinxi. Thanks #mrmazda for noticing.
Then noticed the #rpm package count failed for mageia. Turns out they are using different version of rpm, missing some options so no results. Will add workaround.
-
Found issues in #inxi repo report for some software sorced repo lists.: #mageia's #urpmq, #pisi, #solus #eopkg. These all are roughly similar and all had same report glitch of showing one repo data source per output line instead of source then all repos. The output was also weird. Corrected in #pinxi. Thanks #mrmazda for noticing.
Then noticed the #rpm package count failed for mageia. Turns out they are using different version of rpm, missing some options so no results. Will add workaround.
-
Found issues in #inxi repo report for some software sorced repo lists.: #mageia's #urpmq, #pisi, #solus #eopkg. These all are roughly similar and all had same report glitch of showing one repo data source per output line instead of source then all repos. The output was also weird. Corrected in #pinxi. Thanks #mrmazda for noticing.
Then noticed the #rpm package count failed for mageia. Turns out they are using different version of rpm, missing some options so no results. Will add workaround.
-
@canleaf @[email protected] @LilahTovMoon webkit hasn't been the Chrome engine since who knows how long ago. Probably close to 20 years now'
Went like this: #KDE' #Konqueror web and file browser had a quite clean but basic HTML engine #KHTML. Apple wanted an engine for their new #Safari browser and picked KHTML. Mozilla's gecko (not positive was gecko then) was a mess so wasn't used. KHTML was #GPL hurray! Became AppleWebkit. Google picked it for new Chrome. Soon forked wk to #Blink. Power of GPL.
-
To release next #inxi now, or not to release and wait for more fixes/issues etc to show up? Always a tough call when there are not a huge amount of fixes, but there are real fixes that impact some people. Right now it's a little light for a new release for my taste, but it's been about 6 weeks, and the bugs/fixes I got were real issues, and should probably move from #pinxi to inxi.
This makes 3.3.35, like 3.3.34, mostly corner case fixes and updates. Which suggests... stability?!
-
@SpaceLifeForm Buried in that article is a link to this one: https://ipullrank.com/google-algo-leak which is an SEO guy the initial article author contacted who reviewed the leaked docs.
This stuff used to be interesting to me, #SERPs, #SEO, etc, but in the end, it's a horrible way to spend my time, so we just started focusing on content and quality and saved ourselves some headaches. That's a formula that has always worked, by the way.
-
Added initial support in #pinxi (next #inxi) for Loongson GPUs, but I have almost no data, so it won't be very meaningful. More important is to add in support on backend tools/gpu_raw.pl and gpu_ids.pl, which is where the GPU arch data for inxi gets generated.
Support for Loongson CPUs is totally lacking, I have no data, no cpuid data, nothing, though I found a good source for at least some of the features, process nodes, etc, but no way to match to actual CPUs.
And so it goes.
-
@[email protected] I was a member of a small team that managed to solve issues users hit but it took huge amount of work plus distro made some poor choices but was very popular while it lasted. #inxi is what remains active from that experience. Still same goals: trying to smooth bumps users of #FreeDesktops and #FreeServers might hit, help users, distro support people, sys admins.
People fail to grasp "Linux" is not a single OS/app vendor, keep looking for a "they" to fix things
2/ -
@erikcats @arstechnica I'm going to take a good look at #stract search stract.com, particularly its user settings.
Believe it or not Google used to have great search initially made by and for engineers. All kinds of search operators. You could interact with a google engineer (Matt Cutts) directly, and he was a real human.
This is why a lot of us in web dev community actively promoted Google.
Then they took down their lobby "Don't be Evil" sign. Which Strict alludes to in their about page.
-
Meanwhile, on the #inxi / #pinxi front, all remains peaceful. Issues reported are resolved.
It's lingering in that odd space where not quite enough updates to warrant a new release, so waiting for more to pop up.
I'm calling the long refactor roughly completed with 3.3.33 a win, I'm not hitting code in general that makes me wince, hides issues, or makes logic hard to understand. This was the goal, so looks like a win.
I get slightly nervous when nothing shows up, but that's old habits.
-
A another day in the life for #inxi: Issue 303 on @Codeberg noted #mesa version in #OpenGL was failing on one user's output.
With some good sleuthing (not by me, gfxstrand the OP figured it out), turns out that when mesa is built from git, it added an extra string to end of version number string, which then broke the regex.
While technically working now in #pinxi, I will probably make this pattern less picky in case other weird variants crop up.
Another good cb issue. Not missing #github.
-
@axelrafn @ThePlant the team that did Audacity were aging out and had noted in blog post how the stuff is so complex to do they had been trying to get younger devs involved but zero skilled ones appeared which is when they decided to sell it. There were core upgrades they wanted to do but couldn't get done and they did not want their creation to wither and fade.
These things resonate because I do a specialized audio processing tool #acxi which touches on core audio file processing issues.
2/ -
@axelrafn @ThePlant the team that did Audacity were aging out and had noted in blog post how the stuff is so complex to do they had been trying to get younger devs involved but zero skilled ones appeared which is when they decided to sell it. There were core upgrades they wanted to do but couldn't get done and they did not want their creation to wither and fade.
These things resonate because I do a specialized audio processing tool #acxi which touches on core audio file processing issues.
2/ -
@axelrafn @ThePlant the team that did Audacity were aging out and had noted in blog post how the stuff is so complex to do they had been trying to get younger devs involved but zero skilled ones appeared which is when they decided to sell it. There were core upgrades they wanted to do but couldn't get done and they did not want their creation to wither and fade.
These things resonate because I do a specialized audio processing tool #acxi which touches on core audio file processing issues.
2/ -
https://youtu.be/I4pDLPYvgdA?si=LqUFjIyOjmsXKnsS
Incredible. Worth more than a thought or two. "He just wants to be a cat"
-
@foxyoreos @soatok @gsuberland I've always been puzzled why anyone would volunteer their finite free time as a mod for a fully for profit corporate web corporation.
I've done modding but only for free and autonomous projects. It's a thankless task. I'd never do it again.
The really sad thing is the move from specialist run forums to single point of failure stack* type properties. #ExpertsExchange has been mentioned. #Github should be added to list of bad faith organizations.
-
@blaise #Slackware is alive and kicking. #PatrickVolkerding still #BDFL. Great community, one of my favorites. Have been super helpful in development of more hardware oriented features of #inxi in particular CPU and recent RAM upgrades. Very pleasant to deal with.
-
A day in the life of #inxi Got forum issue on #linuxquestions.org #slackware forums. inxi has special slackware package manager repo handling because unlike most distros its not built out of packages. So there's a variety of pms most of which inxi knows about. In this case repo file syntax has changed for #slpkg leading me to refactor that logic. Now handles original then modified original and now new syntax. So works with any era.
And that's why inxi is so big. Special cases the norm.
-
@carmenbianca @samueljohnson @egeexyz after being a team member of several such derived distros my conclusion was to use the base distro, like #Debian, #Arch, #Slackware.
However it's important to differentiate between distros that alter the base and distros that don't. Or do it minimally. Test is if you remove derived child distro sources you can return to base eg #Garuda #Endeavor > Arch, #MX #antiX #Sparky > Debian with minimal issues.
I learned this the hard way.
-
Due to an almost overwhelming popular demand (ok ok, a guy asked when I'd release), I grit my teeth, did the last horrifically tedious manual matching tables data updates last night in #pinxi (next #inxi), which always means release is going to be within a day or two.
So this nice collection of corner case fixes will probably go out the door today.
I'm calling it: @Codeberg is working _exactly_ the way I hoped it would. Signal to noise ratio in issues radically higher now than on github.
-
In terms of the #acxi code itself, because #inxi is far larger and more complex, and requires far more code discipline to maintain, and gets refactors all the time to achieve that goal, acxi tends to follow along like inxi's little brother, and benefits from all the improvements I introduce internally in inxi code. Particularly #Perl syntax and structures. In this sense, inxi really benefits acxi since acxi's code basically gets a 'free' upgrade using my latest stress tested inxi techniques
-
In terms of the #acxi code itself, because #inxi is far larger and more complex, and requires far more code discipline to maintain, and gets refactors all the time to achieve that goal, acxi tends to follow along like inxi's little brother, and benefits from all the improvements I introduce internally in inxi code. Particularly #Perl syntax and structures. In this sense, inxi really benefits acxi since acxi's code basically gets a 'free' upgrade using my latest stress tested inxi techniques
-
In terms of the #acxi code itself, because #inxi is far larger and more complex, and requires far more code discipline to maintain, and gets refactors all the time to achieve that goal, acxi tends to follow along like inxi's little brother, and benefits from all the improvements I introduce internally in inxi code. Particularly #Perl syntax and structures. In this sense, inxi really benefits acxi since acxi's code basically gets a 'free' upgrade using my latest stress tested inxi techniques
-
And that closes the very first @Codeberg #acxi issue. And creates the first proper #codeberg acxi release, 3.6.02.
acxi is designed to be very stable, unlike #inxi which evolves constantly, and only gets updates for fixes, like this one, or to introduce new features wanted by me or a small handful of acxi users I know. eg --tagllst, which the #slackware packager requested. A feature I now use all the time. This has happened with several powerful features. Benefit of a few good eyes.
-
And that closes the very first @Codeberg #acxi issue. And creates the first proper #codeberg acxi release, 3.6.02.
acxi is designed to be very stable, unlike #inxi which evolves constantly, and only gets updates for fixes, like this one, or to introduce new features wanted by me or a small handful of acxi users I know. eg --tagllst, which the #slackware packager requested. A feature I now use all the time. This has happened with several powerful features. Benefit of a few good eyes.
-
And that closes the very first @Codeberg #acxi issue. And creates the first proper #codeberg acxi release, 3.6.02.
acxi is designed to be very stable, unlike #inxi which evolves constantly, and only gets updates for fixes, like this one, or to introduce new features wanted by me or a small handful of acxi users I know. eg --tagllst, which the #slackware packager requested. A feature I now use all the time. This has happened with several powerful features. Benefit of a few good eyes.
-
First @Codeberg #acxi issue (silly mistake, and good issue). acxi is a specialized CLI audio processing tool that, unlike #inxi (which is made as general utility for the wider #FreeSoftware ecosystem), is intended to meet specific audio file processing needs. It makes no effort to be 'easy' or 'user friendly', although it is immensely powerful. But not for newbies. Unlike inxi, which is fully operational out of the box, acxi does nothing until configured or run with the right CLI switches.,
-
First @Codeberg #acxi issue (silly mistake, and good issue). acxi is a specialized CLI audio processing tool that, unlike #inxi (which is made as general utility for the wider #FreeSoftware ecosystem), is intended to meet specific audio file processing needs. It makes no effort to be 'easy' or 'user friendly', although it is immensely powerful. But not for newbies. Unlike inxi, which is fully operational out of the box, acxi does nothing until configured or run with the right CLI switches.,