Language Selection

English French German Italian Portuguese Spanish

Is PCLINUXOS a debian distro or another type?

Filed under
PCLinuxOS

Is Codeweavers Cross Office program compatible with PCLINUXOS? I tried to install the beta version earlier today and it would not install. It uses a .sh extension. When I double clicked on the direct download from Codeweavers and I tried to install it, it said it was corrupt. And each subsequent download has said the same. Is it that it is not compatible with PCLINUXOS or is something else the issue.

Also, out of curiousity, are there big differences between PCLINUXOS, Dream Linux and MEPIS?
I have downloaded and used all three, and since they PCLINUX and MEPIS are both KDE based and Dream Linux is XOFC based, aside from the desktop interfaces, I did not see a big difference between them. They are all very stable, and very fast once downloaded and installed on to my local computer. By the Way, Codeweaver installed without a hitch into DreamLinux.

Thanks and regards.

Installing outside repos

Just another point of view, having used PCLinuxOS for over two years and one that likes to do what I want with my own computer, I tend to install software from across the net if I cannot find it in the repositories on PCLinuxOS.

In saying that, I believe most distro's tell you not to do that because if you get into borking the system they cannot help you because you may have changed something in the OS that they may not be aware of when you download out side of the repositories.

PCLinuxOS is a great Distro, and I have never had a problem by doing what I do, but if you do as I have your own data backed up and prepared to do a re-install of your system, as it is would not by fair to the support forums to ask how to fix something, if you are outside of the main repos.

Rodney

Member of Linux Geeks United
Linux Reg. #403050

crashes on K3b - to Walter

As I have also tried the K3b (however on Mandriva) I just assume that your problem is that you tried to burn
a disk with more than 80 min. of sound.

NOTE : If this is a music CD it must be under 80 min. otherwise the program will not
handle it.
For over 80 min. use Nautilus - it works perfect , if you have it.

Success!

Yes you can, but not many

Livecd needs 512 mb of drams and can not add programs.

Yes, you can install programs; not many, though. It uses a ramdisk that overlays the CD's read-only filesystem, but it's pretty small (depending on the amount of memory you have, of course). For example, I had just enough room to install the nvidia kernel modules to get Beryl working from the live CD. (This is why having a "persistent disk image" option would be nice.)

The live CD also ran adequately on a laptop with only 256MB of RAM (it did find and use the pre-existing swap partition, though).

The magic is fading

It had to happen, I suppose, especially when all efforts are going in to the new version. I'm having problems I can't fix and am going to develop an alternative.

~

You'll be back as soon as the stable version is released. It is simply the the best distro. I don't stop looking around either but I know it's PCLinuxOS for me - because it works ... and the community is A!

Registered Linux User No. 401868

~

archie wrote:
it's PCLinuxOS for me - because it works

Hi, archie. The trouble is it isn't working. I'll still try the new version, though.

K3b cd burner / PClinuxOS

I am new to linux and had a dual boot w/winXP Home & PClinuxOS.94 and very much enjoyed this linux OS.

Just a few days ago I upgraded to the PCLOS-2007 test release (which i think is the most beautiful and best linux distro i have seen so far)and everything worked wonderful except when I tried (K3b) to burn a CD ....it crashes.

I tried removing the program then re-installing it ....it helped a little, but again crashed just before i started the burn.

I'm wondering if anyone else is experiencing this problem or maybe i'm doing something wrong???

walter l jones

re: K3b cd burner / PClinuxOS

There were a few reports on the test 1 forum discussion and a coupla suggestions.

Crashes on PCLOS

I've been able to use K3b without any crashing but I've had other applications crashing.

Try posting on the forum and give details of exactly what you did. It may help to remove the k3b files and folders in .kde/share/config | apps

As for me, I'm going to develop my Vector installation further.

PCLOS is a MDK distribution

PCLOS is a MDK distribution there is a big difference in rpm packages and debian is a RPM based distro as far as that codeweavers i know that there is a mdk rpm and you will need kpackage to install it as far as PCLOS it is far more superior than any other distro out there i have used every single distro out there and when i came to PCLOS i stopped i have an older customer base and pclos keeps it simple so everyone can use it.

Mandriva & "package manager" - does not compute

malai5 wrote:
Mandriva ... does have one feature that PC Linux and most other Linux do not have and that is Automated RPM package download and install

There was I thinking I must have been the last person to discover that so many other distros have what Mandriva lacks, i.e. a decent package manager. But no, there is at least one yet to make the discovery.

I wonder whether there is anyone in the universe who thinks Mandriva has an intelligent marketing strategy or, indeed, any strategy? Anyone who thinks its numerous websites are informative and simple to navigate? Anyone who thinks it's set up to compete and prosper?

PC Linux

Hi All

Having tried many Linux distributions, the ones that are most user friendly are PC Linux and Mandriva "One" 2007.
However, Mandriva is only a small distribution compared to PC Linux, in that it has limited in house upgrades. BUT, it does have one feature that PC Linux and most other Linux do not have and that is Automated RPM package download and install. without reverting to the command line. That feature alone makes Mandriva "One" 2007, a shoo in for those crossing over from Windoze.

Apart from that, PC Linux is a very stable, feature packed and beautiful to look at, Linux OS, that I personally use. It just needs the RPM auto install and it would be as close to perfect an OS can be.

Cheers

Malai5

The Further You Go, The Less You Know.
www.mam3.com.au

CLI package install?

malai5 wrote:
Hi All
However, Mandriva is only a small distribution compared to PC Linux, in that it has limited in house upgrades. BUT, it does have one feature that PC Linux and most other Linux do not have and that is Automated RPM package download and install. without reverting to the command line. That feature alone makes Mandriva "One" 2007, a shoo in for those crossing over from Windoze.

Apart from that, PC Linux is a very stable, feature packed and beautiful to look at, Linux OS, that I personally use. It just needs the RPM auto install and it would be as close to perfect an OS can be.

Humm, better look again. PCLinuxOS comes with Synaptic already configured with our repositories. All you have to do is start Synaptic from the menu, click on the package you want to install, and click Apply. You never had to open a terminal to install an rpm from our repos.
Sal

Hi Sal That is correct, if

Hi Sal

That is correct, if the RPM package is in the repository, BUT, if it isn't then it's back to the command line.
As you know, RPM and TAR files are offered by NON "Free" source distributors to update their products that are in some linux distributions, Flash is one that springs to mind and was updated in Mandriva for Firefox. Another one was the VMware Beta 6.0 tools package that I needed.In Mandriva "One" 20et the07, it was automatic, in PClinux it was done through a terminal as root. No, not hard, once you get the hang of it, but a definate put off for the new emigrants from Windoze.

Think about it Sal, it would make PClinux just perfect.

Cheers

Malai5

The Further You Go, The Less You Know.
www.mam3.com.au

Broken packages and dependencies

We at the PCLinuxOS community have this much said warning to users wishing to install "outside" packages. Do it at your own risk. And in doing so there won't be support offered. The best deal is to make a software request in the forum, complete with links and what it's for, and if you get lucky, the devs would be quick on it.

There are literally a load of apps one can install from the PCLinuxOS repository.

Best regards

Registered Linux User No. 401868

It is no problem

to install Crossover Office on PCLinuxOS. You just have to follow the instructions on Codeweaver's website.

Did you install PCLinuxOS to your hard drive? If so, you should have seen the New User Guide icon on your desktop. Have you clicked that icon? It will take you to the new user's wiki site. The wiki site won't answer this specific question, but it will lead you to the PCLinuxOS support site, http://www.pclinuxos.com/forum/index.php .
Posting your question there will result in numerous replies to your question.

To specifically answer your question, a .sh file is used so that you can install the program on Linux, no matter what package manager it uses. It won't matter if it's Debian, RedHat, or Slackware, .deb-based, .rpm-based, or .tgz-based.

To install the software package you downloaded, open a terminal window. Change to the directory (cd) the downloaded file is in. Type chmod+x install-crossover-standard-prerelease-6.0.0beta3.sh. (I am assuming that is the name of the file you downloaded.) Then type sh install-crossover-standard-prerelease-6.0.0beta3.sh. The installation will begin.

You can't just double-click the file to install it. If you still don't understand, post your question on the forum @ http://www.pclinuxos.com/forum/index.php .

The following is an example of what you would type in the terminal window:

cd Downloads
chmod +x install-crossover-standard-prerelease-6.0.0beta3.sh
sh install-crossover-standard-prerelease-6.0.0beta3.sh

It's RPM based...

PCLinuxOS is an rpm-based distro unlike Debian or other Debian-based stuff. Maybe that's why CrossOffice has issues with it? I'm sorry, I've never used CrossOffice.

More in Tux Machines

Linux 5.3

  • Linux 5.3
    So we've had a fairly quiet last week, but I think it was good that we
    ended up having that extra week and the final rc8.
    
    Even if the reason for that extra week was my travel schedule rather
    than any pending issues, we ended up having a few good fixes come in,
    including some for some bad btrfs behavior. Yeah, there's some
    unnecessary noise in there too (like the speling fixes), but we also
    had several last-minute reverts for things that caused issues.
    
    One _particularly_ last-minute revert is the top-most commit (ignoring
    the version change itself) done just before the release, and while
    it's very annoying, it's perhaps also instructive.
    
    What's instructive about it is that I reverted a commit that wasn't
    actually buggy. In fact, it was doing exactly what it set out to do,
    and did it very well. In fact it did it _so_ well that the much
    improved IO patterns it caused then ended up revealing a user-visible
    regression due to a real bug in a completely unrelated area.
    
    The actual details of that regression are not the reason I point that
    revert out as instructive, though. It's more that it's an instructive
    example of what counts as a regression, and what the whole "no
    regressions" kernel rule means. The reverted commit didn't change any
    API's, and it didn't introduce any new bugs. But it ended up exposing
    another problem, and as such caused a kernel upgrade to fail for a
    user. So it got reverted.
    
    The point here being that we revert based on user-reported _behavior_,
    not based on some "it changes the ABI" or "it caused a bug" concept.
    The problem was really pre-existing, and it just didn't happen to
    trigger before. The better IO patterns introduced by the change just
    happened to expose an old bug, and people had grown to depend on the
    previously benign behavior of that old issue.
    
    And never fear, we'll re-introduce the fix that improved on the IO
    patterns once we've decided just how to handle the fact that we had a
    bad interaction with an interface that people had then just happened
    to rely on incidental behavior for before. It's just that we'll have
    to hash through how to do that (there are no less than three different
    patches by three different developers being discussed, and there might
    be more coming...). In the meantime, I reverted the thing that exposed
    the problem to users for this release, even if I hope it will be
    re-introduced (perhaps even backported as a stable patch) once we have
    consensus about the issue it exposed.
    
    Take-away from the whole thing: it's not about whether you change the
    kernel-userspace ABI, or fix a bug, or about whether the old code
    "should never have worked in the first place". It's about whether
    something breaks existing users' workflow.
    
    Anyway, that was my little aside on the whole regression thing.  Since
    it's that "first rule of kernel programming", I felt it is perhaps
    worth just bringing it up every once in a while.
    
    Other than that aside, I don't find a lot to really talk about last
    week. Drivers, networking (and network drivers), arch updates,
    selftests. And a few random fixes in various other corners. The
    appended shortlog is not overly long, and gives a flavor for the
    changes.
    
    And this obviously means that the merge window for 5.4 is open, and
    I'll start doing pull requests for that tomorrow. I already have a
    number of them in my inbox, and I appreciate all the people who got
    that over and done with early,
    
                    Linus
    
  • Linux Kernel 5.3 Officially Released, Here's What's New

    Linus Torvalds announced today the release of the Linux 5.3 kernel series, a major that brings several new features, dozens of improvements, and updated drivers. Two months in the works and eight RC (Release Candidate) builds later, the final Linux 5.3 kernel is now available, bringing quite some interesting additions to improve hardware support, but also the overall performance. Linux kernel 5.3 had an extra Release Candidate because of Linus Torvalds' travel schedule, but it also brought in a few needed fixes. "Even if the reason for that extra week was my travel schedule rather than any pending issues, we ended up having a few good fixes come in, including some for some bad Btrfs behavior. Yeah, there's some unnecessary noise in there too (like the speling fixes), but we also had several last-minute reverts for things that caused issues," said Linus Torvalds.

  • Linux 5.3 Kernel Released With AMD Navi Support, Intel Speed Select & More

    Linus Torvalds just went ahead and released the Linux 5.3 kernel as stable while now opening the Linux 5.4 merge window. There was some uncertainty whether Linux 5.3 would have to go into extra overtime due to a getrandom() system call issue uncovered by an unrelated EXT4 commit. Linus ended up reverting the EXT4 commit for the time being.

Kubernetes Leftovers

  • With its Kubernetes bet paying off, Cloud Foundry doubles down on developer experience

    More than 50% of the Fortune 500 companies are now using the open-source Cloud Foundry Platform-as-a-Service project — either directly or through vendors like Pivotal — to build, test and deploy their applications. Like so many other projects, including the likes of OpenStack, Cloud Foundry went through a bit of a transition in recent years as more and more developers started looking to containers — and especially the Kubernetes project — as a platform on which to develop. Now, however, the project is ready to focus on what always differentiated it from its closed- and open-source competitors: the developer experience.

  • Kubernetes in the Enterprise: A Primer

    As Kubernetes moves deeper into the enterprise, its growth is having an impact on the ecosystem at large. When Kubernetes came on the scene in 2014, it made an impact and continues to impact the way companies build software. Large companies have backed it, causing a ripple effect in the industry and impacting open source and commercial systems. To understand how K8S will continue to affect the industry and change the traditional enterprise data center, we must first understand the basics of Kubernetes.

  • Google Cloud rolls out Cloud Dataproc on Kubernetes

    Google Cloud is trialling alpha availability of a new platform for data scientists and engineers through Kubernetes. Cloud Dataproc on Kubernetes combines open source, machine learning and cloud to help modernise big data resource management. The alpha availability will first start with workloads on Apache Spark, with more environments to come.

  • Google announces alpha of Cloud Dataproc for Kubernetes

    Not surprisingly, Google, the company that created K8s, thinks the answer to that question is yes. And so, today, the company is announcing the Alpha release of Cloud Dataproc for Kubernetes (K8s Dataproc), allowing Spark to run directly on Google Kubernetes Engine (GKE)-based K8s clusters. The service promises to reduce complexity, in terms of open source data components' inter-dependencies, and portability of Spark applications. That should allow data engineers, analytics experts and data scientists to run their Spark workloads in a streamlined way, with less integration and versioning hassles.

IBM/Red Hat: Fedora's Power Architecture Builds, WebSphere/WebLogic's Demise, Red Hat’s David Egts

  • Fedora Is Beginning To Spin Workstation & Live Images For POWER

    If you are running the likes of the Raptor Blackbird for a POWER open-source desktop and wanting to run Fedora on it, currently you need to use the Fedora "server" CLI installer and from there install the desired packages for a desktop. But moving forward, Fedora is beginning to spin Workstation and Live images for PPC64LE. Complementing Fedora's Power Architecture images of Fedora Everything and Fedora Server, Workstation and Live images are being assembled. This is much more convenient for those wanting an IBM POWER Linux desktop thanks to the success of the Raptor Blackbird with most Linux distributions just offering the server/CLI (non-desktop) images by default for PPC64LE.

  • Are Application Servers Dying a Slow Death?

    There has been concern for nearly five years application servers are dead. Truth be told, they are not dead, but is their usage in decline? The simple answer is yes. Over the years, it appears corporate environments have decided the "return on investment" is not there when looking at Java application servers. On the surface, one might assume that the likes of WebSphere or WebLogic might be the ones in decline due to cost. Perhaps it is just affecting the proprietary choices, while their open source based derivatives are growing or remaining steady? Appears not. Whichever Java application server you choose, all of them are in a state of decline. Whether it be proprietary options such as WebSphere or WebLogic, or open source alternatives JBoss or Tomcat, all are in decline based on employment listings we review. However, they are not declining at the same pace. From our collection of data, WebSphere and WebLogic's decline has been more muted. The rate of reduction for each of these application servers is in the neighborhood of 25-35% over the last couple years. At the same time, the likes of JBoss and Tomcat have declined around 40-45%. Not a drastic difference, but one that still is notable.

  • Red Hat’s David Egts: Commercial Open Source Software to Drive Federal IT Modernization

    David Egts, chief technologist for Red Hat’s (NYSE: RHT) North American public sector division, advises federal agencies to adopt commercial open source software to help advance their information technology modernization efforts, GovCon Wire reported Aug. 23. He said Aug. 22 in an FCW thought piece that agencies should seek software vendors that are well-versed in open source technology as well as government security certifications in order to successfully modernize federal IT processes.

GNOME and gestures, Part 2: HdyLeaflet

A folded HdyLeaflet, just like GtkStack, shows one of its children at any given moment, even during child transitions. The second visible child during transitions is just a screenshot. But which child is “real” and which is a screenshot? Turns out the real child is the destination one, meaning the widget switches its visible child when the animation starts. It isn’t a problem if the animation is quick and time-based, but becomes very noticeable with a gesture. Additionally, it means that starting and cancelling a gesture switches the visible child two time. One solution would be only switching the visible child at the end of the animation (or not at all if it was canceled). The problem is that it’s a major behavior change: applications that listen to visible-child to know when to update the widgets, or sync the property between two leaflets will break. Another solution would be to draw both children during transitions, but it still means that visible-child changes two times if the gesture was canceled. The problem here is similar: applications wouldn’t expect the other child to still be drawn, but at least it’s just a visual breakage. And it still means that starting and canceling the gesture would mean two visible-child changes. The second solution may sound better, and yet the current WIP code uses the first one. Read more