Language Selection

English French German Italian Portuguese Spanish

Genesis of an Operating System

Filed under
PCLOS
Interviews
-s

Just say the name Texstar to anyone that runs Linux and see a smile with an expression of recognition and appreciation light their face. When Texstar first began using Linux eight years ago, he had no idea he would someday become an icon of creativity, ingenuity, and self-sacrifice. Eternally humble, he may not agree to this description, but these are just some of the superlatives used to describe him by users of his os, visitors to his site, and personal friends of the man.

Texstar began to gain recognition approximately five years ago when he began packaging and providing rpms and howtos for current MandrakeLinux releases. Later he began providing these rpms through his website. This website grew in popularity as all of Linuxdom began linking to it. From mailing lists to newsgroups, from discussion forums to websites, pclinuxonline and Texstar were on a roll. This snowball effect has lead him to provide one of the most beautiful, complete, and stable operating systems in existence.

It began with Redhat 5.2 for Texstar, having become disenchanted with Windows. He said, "I wanted to get away from Windows because it wouldn't let me have control over my computer. It was forcing me to install things I didn't want or need." He soon moved on to Mandrake because it was a revolutionary operating system for its time. With its roots in Redhat but featuring KDE instead of Gnome and the ambitious goal of including graphical configuration tools, Texstar and many others were hooked.

However, it wasn't long before stability issues, missing features, and undesired customizations inspired Texstar to begin patching Mandrake's rpms and KDE's sources then repackaging them for himself. When others posted on help forums about some of the same issues he had resolved, he stepped forward to offer advice and assistance. This lead to him offering users the opportunity to install his rpms to fix those pesky bugs and enjoy the extra features so hard for the newcomer or layperson to implement. He explained, "It was fun and challenging. It was like a puzzle, where all the pieces have to fit just right or the program won't work. Plus there is something satisfying to take raw source code and convert it into something a user can install and use." There were rarely any adverse issues and those rpms reaped more and more praise. Users wanted more. Requests for features and updates soon followed. Texstar and his site grew in popularity.

With management, developer, and philosophical changes afoot in Paris, Texstar felt the time was right to offer his finely tuned and beautifully customized system to others. "I wanted something that a person could boot and know right away if the OS would be compatible with their computer. With so many hardware configurations, it's nice to know right from the start if pclinuxos is right for your system. I saw Jaco was doing livecd scripts and I got involved in the project which gave me an outlet to produce a livecd with my rpm packages. I also enjoy playing with the livecd technology." Thus the PCLinuxOS livecd was born.

The road to producing this livecd hasn't been unencumbered. As with all software there are compatibility issues, bugs, and personnel problems. Previews 1 & 2 were private releases to test hardware detection. Preview 3 was a limited release to guage interest and Tex was not disappointed. People were very interested. Someone, not mentioning any names, posted a manual way of installing the livecd to a harddrive. It and the discussion that followed showed an indication of the interest in installing onto harddrives. This inspired Texstar to implement an easy harddrive installer. Preview 4 featured a harddrive installer but presented trouble for some setups. Texstar and mklivecd developer Jaco worked hard hammering out the kinks on the hardware detection, booting scripts, and harddrive installer until Jaco became too busy in his real life and passed the mantle to Tom.

Tom became interested in working on the PCLinuxOS livecd project because he was "very impressed with the quality of PCLinuxOS and was more comfortable with a Mandrake based livecd than with Knoppix. I also wanted to get a device working in Linux - a magneto optical drive." In February of last year "I asked Tex how I could help, and he told me 'Please help Jaco (with mklivecd).'"

The rest shall we say is history. There have been 4 new releases since featuring better hardware detection and support for more modern and exotic hardware. Newest versions of applications, the latest kernels and related technologies, more customizable features and all the eye candy for which one could hope are the things users get when they download PCLinuxOS. In the future Tom hopes "to see overall continued improvement across the board, more i18n, use of a copy-on-write filesystem such as unionfs. Longer term, possibly a reduction or complete replacement of the Mandrake hardware detection/configuration tools." Tex humbly states "We plan to continue to improve it and hopefully become a major player in the next few years."

PCLinuxOS Preview 8.1 is due out any day now and excitement is in the air. Some of the things that we can expect from it are listed in the comments of this article. As always the project is nothing without its users and their bug reports.

Superb!

Awesome job srlinuxx, thanks for the article. Sal

re: Superb

Thanks for saying Sal, and thanks for submitting it to pclo!

----
You talk the talk, but do you waddle the waddle?

Oh nooo...

He was assimilated! Sad

----
You talk the talk, but do you waddle the waddle?

Thanks!

Thanks for the compliment on the story. Yes, I agree Tex is awesome, but I'm a little prejudiced! Big Grin Actually Tex is a bit shy and shuns the spotlight. I think he's a little embarrassed by my article, as he'd never toot his own horn. He works so hard all the time to fix the littlest bug for anyone who reports such-and-such isn't working here. He tends to sweat the details. I just wanted folks to know how dedicated to them he really is. He's an awesome person working practically 24/7 and yet seems to find time for his family and friends when they need him. And he's darn cute too! Big Grin

----
You talk the talk, but do you waddle the waddle?

re: It's time for Texstar.

wow, wonderful of you to share those kind words. I agree completely... well, except for the gentoo part! Big Grin

----
You talk the talk, but do you waddle the waddle?

Just joking around

Oh, I was just joshin around with ya about Gentoo. I've always been one to say use whatever works best for you and your hardware. I love pclos as well. Funny, my two favorite distros couldn't be more different. Big Grin

----
You talk the talk, but do you waddle the waddle?

Thanks for the article!

srlinuxx superb article!
Thanks for it, and thank you for the picture.
Watch out Tex what some good friends of yours will do with it.
If I may add some personal experience with Texstar just to illustrate
the kind of the guy he is:

I been with PCLOS since pre3 but i wasn't very active neither on the forum, neither on the mailing list, mostly because some painfull experience on the Mandrake Club. But as time went on I become more and more impressed with pclos, and shortly after p5 it replaced my main (at the time) operating system (mandy with plf and spiced up with Texstar's rpm's). Found out about the irc channel, and although never used irc before, I was very soon "hooked" mostly because the wonderful guys i met (Tom, oilent1, etjr, Xterm, Talyn, CyberCFO, cybonix, el_cuco, neverstop, boford, mexashaggy, Darb, Sal_....Sould I continue?) in no time I learned more about linux than years and years before. I wanted to give back some in return, so started to answer questions I knew or thought i knew the answer for. Started to send my findings, little code contributions to Tom ( I was mostly active with the livecd) and it somehow got to Tex as well. I hardly even thought he knew who I am when on my birthday a few days ago i opened my e-mail
and I found the most touching birtday present i ever got in my life.
A few days before I was asking on the mailing list for a package which wasn't really that important (never made it to the repository), anyways the birtday present was a congratulation e-mail from Texstar with this little applet packaged and attached to it.

I don't know how you can be more human than that. Texstar, I never met you in person, but feel closer than a few "friend" who I might meet every day. I love you man for who you are, what you do, and for all the excitement you are bringing in quite a few of us life.

ikerekes

re: Thanks for the article!

Thank /you/ for the kind words about my story and even more for sharing your experiences with Texstar and pclos. There is definitely more to Texstar than meet the eye.

----
You talk the talk, but do you waddle the waddle?

re: another satisfied pclos user

very nicely put, couldn't agree more.

----
You talk the talk, but do you waddle the waddle?

Texstar is incredible

I have tried some 80 different distros, and I mean really installed them to hdd, and gave them some time. I don't know much about tweaking, so that has something to do with why I prefer PCLinuxOS, but with it I don't have to tweak. It really dose just work. I presently have it on 6 boxes, from a p11 300 to an athlon xp 2800, and everything works perfectly.

Tex certainly deserves every accolade he gets and more. I have nothing but respect and admiration for him. I was also glad to see the picture, and didn't expect him to be as young as he is.

srlinuxx, Thank you for the article, I very much enjoyed it.

re: Texstar is incredible

Yep, he is. Thanks for visiting and your comments.

Keep an eye open, .94 is due out in a month or so.

----
You talk the talk, but do you waddle the waddle?

re: Texstar is incredible

I just wanted to add my noobsense to this discussion. I found myself looking for a winxp replacement about 8 months ago following a system failure. When I contacted my manufacturer and was told that the only way to get windows to run on my rebuilt system was to buy a new copy, I told them to forget it.

I had heard about this linux thing and decided to search the net for some info. I was lucky, I stumbled on to PCLOS and began reading the forums and decided to try it. 20 mins after getting the livecd running, it was installed and purring like a kitten.

I've learned a lot over the past 8 months, and the most important thing I've learned is the love and respect that the entire PCLOS community has for Texstar, myself included.

Prior to PCLinuxOS I had no idea what IRC was, now I can't go a day without logging in to chat with real friends. More than once I've been on the channel when Tex logs in and he speaks to each of us as if we've known each other all our lives. He is truly a humble and wonderful human being.

Thanks for your article, he deserves to be acknowledged.

sd

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Security: OpenSSL, IoT, and LWN Coverage of 'Intelpocalypse'

  • Another Face to Face: Email Changes and Crypto Policy
    The OpenSSL OMC met last month for a two-day face-to-face meeting in London, and like previous F2F meetings, most of the team was present and we addressed a great many issues. This blog posts talks about some of them, and most of the others will get their own blog posts, or notices, later. Red Hat graciously hosted us for the two days, and both Red Hat and Cryptsoft covered the costs of their employees who attended. One of the overall threads of the meeting was about increasing the transparency of the project. By default, everything should be done in public. We decided to try some major changes to email and such.
  • Some Basic Rules for Securing Your IoT Stuff

    Throughout 2016 and 2017, attacks from massive botnets made up entirely of hacked [sic] IoT devices had many experts warning of a dire outlook for Internet security. But the future of IoT doesn’t have to be so bleak. Here’s a primer on minimizing the chances that your IoT things become a security liability for you or for the Internet at large.

  • A look at the handling of Meltdown and Spectre
    The Meltdown/Spectre debacle has, deservedly, reached the mainstream press and, likely, most of the public that has even a remote interest in computers and security. It only took a day or so from the accelerated disclosure date of January 3—it was originally scheduled for January 9—before the bugs were making big headlines. But Spectre has been known for at least six months and Meltdown for nearly as long—at least to some in the industry. Others that were affected were completely blindsided by the announcements and have joined the scramble to mitigate these hardware bugs before they bite users. Whatever else can be said about Meltdown and Spectre, the handling (or, in truth, mishandling) of this whole incident has been a horrific failure. For those just tuning in, Meltdown and Spectre are two types of hardware bugs that affect most modern CPUs. They allow attackers to cause the CPU to do speculative execution of code, while timing memory accesses to deduce what has or has not been cached, to disclose the contents of memory. These disclosures can span various security boundaries such as between user space and the kernel or between guest operating systems running in virtual machines. For more information, see the LWN article on the flaws and the blog post by Raspberry Pi founder Eben Upton that well describes modern CPU architectures and speculative execution to explain why the Raspberry Pi is not affected.
  • Addressing Meltdown and Spectre in the kernel
    When the Meltdown and Spectre vulnerabilities were disclosed on January 3, attention quickly turned to mitigations. There was already a clear defense against Meltdown in the form of kernel page-table isolation (KPTI), but the defenses against the two Spectre variants had not been developed in public and still do not exist in the mainline kernel. Initial versions of proposed defenses have now been disclosed. The resulting picture shows what has been done to fend off Spectre-based attacks in the near future, but the situation remains chaotic, to put it lightly. First, a couple of notes with regard to Meltdown. KPTI has been merged for the 4.15 release, followed by a steady trickle of fixes that is undoubtedly not yet finished. The X86_BUG_CPU_INSECURE processor bit is being renamed to X86_BUG_CPU_MELTDOWN now that the details are public; there will be bug flags for the other two variants added in the near future. 4.9.75 and 4.4.110 have been released with their own KPTI variants. The older kernels do not have mainline KPTI, though; instead, they have a backport of the older KAISER patches that more closely matches what distributors shipped. Those backports have not fully stabilized yet either. KPTI patches for ARM are circulating, but have not yet been merged.
  • Is it time for open processors?
    The disclosure of the Meltdown and Spectre vulnerabilities has brought a new level of attention to the security bugs that can lurk at the hardware level. Massive amounts of work have gone into improving the (still poor) security of our software, but all of that is in vain if the hardware gives away the game. The CPUs that we run in our systems are highly proprietary and have been shown to contain unpleasant surprises (the Intel management engine, for example). It is thus natural to wonder whether it is time to make a move to open-source hardware, much like we have done with our software. Such a move may well be possible, and it would certainly offer some benefits, but it would be no panacea. Given the complexity of modern CPUs and the fierceness of the market in which they are sold, it might be surprising to think that they could be developed in an open manner. But there are serious initiatives working in this area; the idea of an open CPU design is not pure fantasy. A quick look around turns up several efforts; the following list is necessarily incomplete.
  • Notes from the Intelpocalypse
    Rumors of an undisclosed CPU security issue have been circulating since before LWN first covered the kernel page-table isolation patch set in November 2017. Now, finally, the information is out — and the problem is even worse than had been expected. Read on for a summary of these issues and what has to be done to respond to them in the kernel. All three disclosed vulnerabilities take advantage of the CPU's speculative execution mechanism. In a simple view, a CPU is a deterministic machine executing a set of instructions in sequence in a predictable manner. Real-world CPUs are more complex, and that complexity has opened the door to some unpleasant attacks. A CPU is typically working on the execution of multiple instructions at once, for performance reasons. Executing instructions in parallel allows the processor to keep more of its subunits busy at once, which speeds things up. But parallel execution is also driven by the slowness of access to main memory. A cache miss requiring a fetch from RAM can stall the execution of an instruction for hundreds of processor cycles, with a clear impact on performance. To minimize the amount of time it spends waiting for data, the CPU will, to the extent it can, execute instructions after the stalled one, essentially reordering the code in the program. That reordering is often invisible, but it occasionally leads to the sort of fun that caused Documentation/memory-barriers.txt to be written.

US Sanctions Against Chinese Android Phones, LWN Report on Eelo

  • A new bill would ban the US government from using Huawei and ZTE phones
    US lawmakers have long worried about the security risks posed the alleged ties between Chinese companies Huawei and ZTE and the country’s government. To that end, Texas Representative Mike Conaway introduced a bill last week called Defending U.S. Government Communications Act, which aims to ban US government agencies from using phones and equipment from the companies. Conaway’s bill would prohibit the US government from purchasing and using “telecommunications equipment and/or services,” from Huawei and ZTE. In a statement on his site, he says that technology coming from the country poses a threat to national security, and that use of this equipment “would be inviting Chinese surveillance into all aspects of our lives,” and cites US Intelligence and counterintelligence officials who say that Huawei has shared information with state leaders, and that the its business in the US is growing, representing a further security risk.
  • U.S. lawmakers urge AT&T to cut commercial ties with Huawei - sources
    U.S. lawmakers are urging AT&T Inc, the No. 2 wireless carrier, to cut commercial ties to Chinese phone maker Huawei Technologies Co Ltd and oppose plans by telecom operator China Mobile Ltd to enter the U.S. market because of national security concerns, two congressional aides said. The warning comes after the administration of U.S. President Donald Trump took a harder line on policies initiated by his predecessor Barack Obama on issues ranging from Beijing’s role in restraining North Korea to Chinese efforts to acquire U.S. strategic industries. Earlier this month, AT&T was forced to scrap a plan to offer its customers Huawei [HWT.UL] handsets after some members of Congress lobbied against the idea with federal regulators, sources told Reuters.
  • Eelo seeks to make a privacy-focused phone
    A focus on privacy is a key feature being touted by a number of different projects these days—from KDE to Tails to Nextcloud. One of the biggest privacy leaks for most people is their phone, so it is no surprise that there are projects looking to address that as well. A new entrant in that category is eelo, which is a non-profit project aimed at producing not only a phone, but also a suite of web services. All of that could potentially replace the Google or Apple mothership, which tend to collect as much personal data as possible.

today's howtos

Mozilla: Resource Hogs, Privacy Month, Firefox Census, These Weeks in Firefox

  • Firefox Quantum Eats RAM Like Chrome
    For a long time, Mozilla’s Firefox has been my web browser of choice. I have always preferred it to using Google’s Chrome, because of its simplicity and reasonable system resource (especially RAM) usage. On many Linux distributions such as Ubuntu, Linux Mint and many others, Firefox even comes installed by default. Recently, Mozilla released a new, powerful and faster version of Firefox called Quantum. And according to the developers, it’s new with a “powerful engine that’s built for rapid-fire performance, better, faster page loading that uses less computer memory.”
  • Mozilla Communities Speaker Series #PrivacyMonth
    As a part of the Privacy Month initiative, Mozilla volunteers are hosting a couple of speaker series webinars on Privacy, Security and related topics. The webinars will see renowned speakers talking to us about their work around privacy, how to take control of your digital self, some privacy-security tips and much more.
  • “Ewoks or Porgs?” and Other Important Questions
    You ever go to a party where you decide to ask people REAL questions about themselves, rather than just boring chit chat? Us, too! That’s why we’ve included questions that really hone in on the important stuff in our 2nd Annual Firefox Census.
  • These Weeks in Firefox: Issue 30