Language Selection

English French German Italian Portuguese Spanish

Texstar's blog

PCLinuxOS Enlightenment (E-17) Desktop updated.

Filed under
Linux

We’re excited to announce the PCLinuxOS Enlightenment Desktop packages have been updated to the second beta release of the Enlightenment Foundation Libraries.

Maintenance Release - pclinuxos kde 2010.10

Release Date: 10-28-2010
Size: 698 MB
Md5Sum:43b81b9c2334acaa55959f89ec6a5d5d
Produced by: Texstar
User Level: Beginner, Intermediate, Advanced

Release Date: 10-28-2010
KDE-minime
Size: 436 MB
Md5Sum:bbff5cb76f5b7683e692c5f6e83abd70
User Level: Intermediate, Advanced

Maintenance Release - pclinuxos lxde 2010.10

Filed under
Linux

Release Date: 10-28-2010
Size: 587MB
Md5Sum: 8ed461087f8e360d0fc1268217f36bc1
Produced by: Neal Brooks
User Level: Intermediate, Advanced

Mini Version
Size: 494MB
Md5sum: 74953c3b58963ee31d3d194e87152a6f

Maintenance Release - pclinuxos phoenix xfce 2010.10

Filed under
Linux

Release Date: 10-28-2010
Size: 640 MB
MD5Sum: 50cf18f74a22ce491d65e92d13736665
Produced by: Joble
User Level: Intermediate, Advanced

PCLinuxOS Phoenix Xfce Edition features the lightweight but fully functional Xfce desktop environment. Is it designed for productivity. It load and executes applications fast while conserving system resources.

Features:

Maintenance Release - pclinuxos zen mini 2010.10

Filed under
Linux

Release Date: 10-28-2010
Size: 330 MB
Md5Sum: 1d53cf500db02eab4bbc1e0df79e3440
Produced by: Siamer
User Level: Intermediate, Advanced

Distribution Release - pclinuxos enlightenment 2010.11

Filed under
Linux

Release Date: 11-01-2010
Size: 700 MB
Md5Sum: fd5095e8490da12e09ee0b4afaaec336
Produced by: Texstar and Associates
Artwork Theme by: Agust
User Level: Intermediate, Advanced

Light/Mini Version
Size: 483MB
Md5Sum: b6647443b972d9c6d7ff6b5e56183bac
Produced by: smurflover

Here we go again with the XGL

First it was Novell announcing its contribution of the Xgl graphics subsystem and the 'Compiz ' compositing manager to the X.org project. These enhancements open up a whole world of hardware acceleration, fancy animation, separating hardware resolution from software resolution, and more. As a result, Linux desktops will become more usable, end-user productivity will increase, and Linux is firmly positioned at the forefront of client computing technology.

Now Fedora jumps in and is doing something totally different than Novell. AIGLX is a project that aims to enable GL-accelerated effects on a standard desktop. We have a lightly modified X server (that includes a couple of extensions), an updated Mesa package that adds some new protocol support and a version of metacity with a composite manager.

PCLinuxOS .92 Test 01 ISO Available

Houston, TX, October 27, 2005: PCLinuxOS .92 Test 01 is available at the following location:

http://distro.ibiblio.org/pub/linux/distributions/texstar/pclinuxos/live-cd/english/preview/

Please note this is not a final release iso. We will not answer support questions concerning this test release. Feedback however can be sent to pclinuxos-dev at sbcglobal.net.

PCLinuxOS .92 features an updated 2.6.12-oci5 kernel, hotplug has been moved to udev to provide faster boot times. The fabulous kde has been updated to verison 3.4.3. Koffice replaces Openoffice on the livecd. Openoffice 2.0 can be installed after a hard drive install. xorg has been updated to xorg.cvs. Approx 400 package update brings PCLinuxOS .92 up to date with the latest open source applications.

PCLinuxOS Preview 9.1 updated and released.

PCLinuxOS Preview 9.1 is now posted up on the bittorrent tracker located at http://www.pclinuxonline.com/tracker. This is an update for the livecd with fixes for various issues found after the release of preview 9.

Preview 9 Delayed

I have all the packages updated that I want to go into Preview 9 but the mklivecd scripts need a small update for the hardware detection for monitors and setting the screen resolution. Unfortunately no one is available from the mklivecd development team at this time to take a peek at the perl code which really puts a kink in getting Preview 9 out the door.

Almost time.

I've just about got everything ready to cut another iso. Ocilent is going to work up a new oci5 kernel using a different kernel scheduler so that usb hd drives can be booted. Ikrekes sent me a patch to the livecd-install to properly create the initrd for usb hd boot support. I plan on testing this today.


I ported drakxtools and a new drakconf from Mandriva and it seems to be working good. Scott Greeding will be back in 4-5 days and will help me get synaptic in, the menu structure better intergrated and a more sane layout.


Mozilla-Firefox was updated today to version 1.0.3. Im hoping it will fix dialup users problems with dns. I cant reproduce the problem so it is hard to fix something that isnt broken

Printer Updates

I updated some more of the printer rpms today. I found the gimp-print rpms have many of the missing printer drivers and also a minor bug fix to hplip rpms so hopefully these new printer rpms will finally fix everyones printer problems. I also updated kdelibs-3.4.0-7tex rpms to fix a security problem that was posted here on tuxmachines yesterday. Jrangles and Ocilent sent me some kdm login manager themes which I need to check into.

TheDarb got the premium server up and running and I just rsync'd everything up that was posted today. I will start emailing users who donated funds tomorrow after a few tests of the server.

Kernel updated 2.6.11-oci4

Yesterday I got to experience Ocilent's world. We had a problem with the oci3 kernel where if a user yanked out his usbkey without unmounting it the desktop would crash. I spent all of yesterday evening trying different config options and finally found a fix. I must have built 20 kernels until I hit the magic fix which turned out to be the preemption option that was affecting the usb port. Go figure. Anyway I have a new respect for kernel developers. I think I'm gonna stick with packaging from now on!

Re-install

Filed under
News

Well I messed around this afternoon and managed to totally break my menus so after messing around for a few hours, I backed everything up and did a new install of Preview 81a then updated everything including unstable. I total of 211 packages and Im back in business. I still need to copy my backup stuff back over but man everything is running so much better. I had been using this partition since I converted it from Mandrake 9.2 to PCLinuxOS preview 4 and been updating all this time. So all in all something good came out of something bad. Everything is snappy again. I'll probably be moving everything from unstable tomorrow into updates. I didnt run into any conflicts updating my p81a install from unstable so I'll get to rocking with new packages again.

Problems Problems Problems

Filed under
News

I'm not a big fan of Gnome but I decided to work up 2.10 as some of the pclinuxos users do use that desktop enviroment. Right off the bat I hit a snag. Seems the GTK2 linux-fb build has been broken since 2.50! I've been using 2.4.9 all this time as it works so well with ALL of my GTK2 applications including a bought and paid for FTP client (iglooftp pro). Needless to say without the linux-fb backend, Iglooftp is pretty useless and many GTK2 applications will have to be re-worked. The really bad part is not a single person is maintaining this code in the GTK2 tree. I tried my best to get it to build but it was just beyond my coding experience. I tried to work up gnome using GTK 2.4.9 but it is so old that gnome 2.10 wouldnt build against it. So for now I've put the new gnome build on the back burner until I can get kde 3.4 offical release out the door.

Big rpm update

Filed under
News

I've been a busy bee the past couple of days generating a big pack of rpm updates. udev is about fixed for the printers so I'm happy about that. There is a problem with cd symlinks especially for cdrw devices but the udev mailing list shows this is being addressed and a new version of udev will be out shortly.

Cybercfo is building an Amarok livecd based on a stripped down version of pclinuxos. I updated all the gstreamer rpms as well as amorak from their cvs build last night so he would have some new packages to work with for his project. You can find out more information about this exciting project at:

2-10-05

Filed under
News

Im still having some printer, network printer and usb issues with pclinuxos updates. I've been digging into hotplug and udev and have gotten a few more printers functional now. Usbkeys are still dead and I know it is related to udev and hotplug. Im hoping these issues will clear out in the next few days and I am able to cut an updated iso.

I also found xorg 6.8.2 released today so I built a set of binaries and uploaded them to the premuim server and ibiblio.org. Tonight I noticed in the forums a person who has the unichrome video card that will only go 800x600 so I downloaded the r30 unichrome driver release and added to my next build of xorg 6.8.2-2tex which I will post tomorrow. Hopefully his video will be able to go to a higher resolution.

Syndicate content

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