Difference Between Puppy & Ubuntu

For talk and support relating specifically to Puppy derivatives
Message
Author
User avatar
l2ulinux
Posts: 140
Joined: Tue 25 Jan 2011, 13:40
Location: Blountstown, Fl.

Difference Between Puppy & Ubuntu

#1 Post by l2ulinux »

Difference Between Puppy & Ubuntu

Puppy Linux and Ubuntu Linux are two of the more commonly used Linux distributions, or "distros, in existence in 2011. Even though they're both Linux, they're about as different as two Linux operating systems can be.

Puppy Disctinctives

Puppy Linux is a distribution to use on older computers, or to run from a CD or USB. The whole system is usually about 85MB, which is small for an operating system. As a result, Puppy Linux usually boots quickly. Many users choose Puppy Linux for this speed and for the tools that come standard on a Puppy system image that can be burned and booted from CD. Puppy is a good choice for older hardware, too. Because it's so small, you can easily install it onto an older hard drive. It takes up less space and operates smoothly.

Ubuntu Linux

Ubuntu Linux is a more full-fledged operating system. A typical Ubuntu download is 685 MB and fills a blank CD to the brim. After the installation to the hard drive it takes up significantly more than that. Ubuntu recommends 5GB for the system. Ubuntu is an operating system that is intended to compete on a level playing field with the Windows operating system, offering software alternatives in every arena of normal computer use: OpenOffice for office applications, Firefox for Internet browsing, Rhythmbox for music, and Totem Movie Player for video. When users need new software, Ubuntu provides Synaptic Package Manager to easily install new software, and Ubuntu takes care of automatic updates to your system, just like Windows.

Pros and Cons

Puppy and Ubuntu Linux are completely different operating systems based on the same linux kernel. After the kernel, their similarity ends. Puppy is much more bare-bones, intended for a different audience than Ubuntu. Puppy was made for slimmer, older hardware, while Ubuntu is made for the newest hardware on the market. That's not to say Ubuntu won't work well on a 3-year-old computer. It will, but it's made for direct competition with the newest operating systems, while Puppy is really not

Choosing Between Puppy and Ubuntu

Both Puppy and Ubuntu have a following, as evidenced by the many derivative distros that have arisen from both, such as MacPup, Muppy and Minipup ("puplets") for Puppy, and Xubuntu, Lubuntu, Kubuntu, and Masonux for Ubuntu Linux. However, Ubuntu, the most commonly used Linux distro, according to Distrowatch.com, will seem easier to use for most new users. Its appearance and graphical interface is more similar in function and style to a Windows operating system than Puppy's. Most new users will gravitate to Ubuntu, given this choice, unless older hardware dictates a slimmer operating system, in which case Puppy Linux would be a great choice

User avatar
mickee
Posts: 207
Joined: Tue 08 Feb 2011, 14:59
Location: Saskatoon SK Canada, Gateway 5300 Laptop, 600MHz Celeron, 384MB RAM, lucid puppy 5.2 (Full Install)
Contact:

#2 Post by mickee »

Strange this topic came up. I have a PC which I dual boot Win7 and ubuntu, (still jaunty). I use ubuntu when I can, Win7 if I must. I have puppy 5.2 on my laptop, an archaic piece of hardware from 1999. Works well there, in fact, the laptop was going to be trashed, and puppy linux saved it. I now use my puppy laptop most of the time, and ubuntu and Win7 only sporadically. Something to be said of using a computer in the livingroom, rather than at a desk. Plus ubuntu can be used by most Windows users, Puppy not so much. With 'root' comes great responsibility. A Windows only user I would never let them take my puppy for a walk unattended!

Love puppy. I have learned more about Linux since Feb this year than all my experience with ubuntu.. I can "use" ubuntu. Puppy is so much more involved than just "using". Puppy is about LIVING with Linux -- and that is a great place to live.

make sense?

Good Puppy! Sit! Good boy!
[img]http://i17.photobucket.com/albums/b68/The_Wizard_of_OZ/Lindows-NOT-1.jpg[/img]
Linux is [i][b]NOT[/b][/i] Windows. Doesn't [i][b]PRETEND[/b][/i] to be, Doesn't [i][b]WANT [/b][/i]to be; Don't try to [i][b]MAKE[/b][/i] it be.

User avatar
l2ulinux
Posts: 140
Joined: Tue 25 Jan 2011, 13:40
Location: Blountstown, Fl.

The Truth

#3 Post by l2ulinux »

I have been looking thru the forum and kept running across the web site listed. So I put what was there here were everyone could read and not have to go to another web page.
I love using Puppy and it is used on the same system with Win7. I use Puppy and sometimes other Linux releases myself. My grandkids I let use BrowserLinux.

I give THANKS to all who help bring THE PUPPY linux to us.

User avatar
Bernie_by_the_Sea
Posts: 328
Joined: Wed 09 Feb 2011, 18:14

Re: Difference Between Puppy & Ubuntu

#4 Post by Bernie_by_the_Sea »

l2ulinux wrote:Puppy Linux is a distribution to use on older computers, or to run from a CD or USB.
Puppy works fine on a brand new top-of-the-line computer. Ubuntu can be run from a CD or USB. A live CD is the only way I've ever looked at Ubuntu. I looked at it about three hours total in six years starting with 5.10. It's remained consistently crap over the years.
l2ulinux wrote:The whole system is usually about 85MB, which is small for an operating system. As a result, Puppy Linux usually boots quickly..
Puppy is usually about 120MB which is still small. Traditionally in Linux boot time is totally unimportant. Linux is known for running for years without a reboot. The command uptime is built into the Linux kernel to allow bragging about how long Linux has gone without a reboot. Today a friend of mine told me his Red Hat system has now been up 750 days. Linux is all about stability, not boot up speed.
l2ulinux wrote:Ubuntu is an operating system that is intended to compete on a level playing field with the Windows operating system, offering software alternatives in every arena of normal computer use: OpenOffice for office applications, Firefox for Internet browsing, Rhythmbox for music, and Totem Movie Player for video. When users need new software, Ubuntu provides Synaptic Package Manager to easily install new software, and Ubuntu takes care of automatic updates to your system, just like Windows. .
Ubuntu is far inferior to Windows and it’s an inferior distro in Linux. It’s designed for newbies and generally avoided by Linux old timers. Automatic updates? I've used the same version of XP for eight years without a single "update" automatic or otherwise.
l2ulinux wrote:After the kernel, their similarity ends. Puppy is much more bare-bones, intended for a different audience than Ubuntu. Puppy was made for slimmer, older hardware, while Ubuntu is made for the newest hardware on the market. That's not to say Ubuntu won't work well on a 3-year-old computer. It will, but it's made for direct competition with the newest operating systems, while Puppy is really not .
Actually Puppy compares well with any operating system and it’s certainly far superior to Ubuntu. Puppy was never intended to be used only on old hardware.
l2ulinux wrote:However, Ubuntu, the most commonly used Linux distro, according to Distrowatch.com, will seem easier to use for most new users. Its appearance and graphical interface is more similar in function and style to a Windows operating system than Puppy's. Most new users will gravitate to Ubuntu, given this choice, unless older hardware dictates a slimmer operating system, in which case Puppy Linux would be a great choice.
Ubuntu is certainly not the most commonly used Linux distro. Distrowatch ranks by measuring one and only one thing-- the number of hits on its own web pages. It's totally meaningless as far as determining the number of users. A person might check out a half dozen small systems on Distrowatch but that doesn’t mean he chose Puppy or anything else just because he looked at its page. Most Linux users never look at or have never heard of Distrowatch.

Newbies interested in a Windows lookalike are attracted to Ubuntu. Those with more sense are attracted to more traditional Linux distros... or to nontraditional Puppy. :)
[color=green]Frugal[/color]: Knoppix 6.4.4 DVD
[color=blue]USB[/color]: DSL 4.4.10
[color=red]Full[/color]: WinXP Pro
Puppy (Feb. 4 - May 12, 2011) led me back to Linux.

User avatar
mickee
Posts: 207
Joined: Tue 08 Feb 2011, 14:59
Location: Saskatoon SK Canada, Gateway 5300 Laptop, 600MHz Celeron, 384MB RAM, lucid puppy 5.2 (Full Install)
Contact:

Re: Difference Between Puppy & Ubuntu

#5 Post by mickee »

Bernie_by_the_Sea wrote:Newbies interested in a Windows lookalike are attracted to Ubuntu. Those with more sense are attracted to more traditional Linux distros... or to nontraditional Puppy. :)
What if they are attracted to both ubuntu and Puppy?
[img]http://i17.photobucket.com/albums/b68/The_Wizard_of_OZ/Lindows-NOT-1.jpg[/img]
Linux is [i][b]NOT[/b][/i] Windows. Doesn't [i][b]PRETEND[/b][/i] to be, Doesn't [i][b]WANT [/b][/i]to be; Don't try to [i][b]MAKE[/b][/i] it be.

nooby
Posts: 10369
Joined: Sun 29 Jun 2008, 19:05
Location: SwedenEurope

#6 Post by nooby »

I think that mickee point out the absolute biggest difference.

Ubuntu are so set on to discourage usage of root that you have a hard time getting if they have root or not. I am not that intelligent to find out.

Sure they have sudo and su? but do they really have root the way Puppy have?
And compare Puppy with other distros. How many of them do frugal install on NTFS and allow one to edit the menu.lst? I spent hours yesterday on getting sombody to tell me how I could edit the menu.lst on the NTFS HDD and then save it. Tested on four different Linux OS and none of them did allow me. TinyCore don't even encourage one to install the ntfs-3g tcz to be able to install on the _NTFS and to use it even.

Puppy are unique in how it allow root access to files that the others set as read only due to one boot on the same partition as the menu.lst is on so they don't allow one can change it from within AFAIK

Which other small Linux distro allow that?
I use Google Search on Puppy Forum
not an ideal solution though

User avatar
Bernie_by_the_Sea
Posts: 328
Joined: Wed 09 Feb 2011, 18:14

#7 Post by Bernie_by_the_Sea »

nooby wrote:Sure they have sudo and su? but do they really have root the way Puppy have?
And compare Puppy with other distros. How many of them do frugal install on NTFS and allow one to edit the menu.lst? I spent hours yesterday on getting sombody to tell me how I could edit the menu.lst on the NTFS HDD and then save it. Tested on four different Linux OS and none of them did allow me. TinyCore don't even encourage one to install the ntfs-3g tcz to be able to install on the _NTFS and to use it even.

Puppy are unique in how it allow root access to files that the others set as read only due to one boot on the same partition as the menu.lst is on so they don't allow one can change it from within AFAIK

Which other small Linux distro allow that?
Almost every version of Linux is set up with an option to run as root or as a user. Every time I boot up Mepis or PCLOS I am asked to choose to run as root or as a specific user before I can even get to a desktop. This root is the same as Puppy's root.

Frugal install is a very bad idea for almost every Linux distro. It is rightfully discouraged. A frugal makes some sense only in the case of (1) a relatively small OS that can fit in RAM and most importantly (2) enough RAM in the machine so that the distro isn’t forced to use swap space. Even then there may be problems with persistence. I would estimate that Ubuntu would need at least 10GB and possibly as much as 40GB RAM to work best as a frugal install. A frugal install originally called a “poor man’s install

nooby
Posts: 10369
Joined: Sun 29 Jun 2008, 19:05
Location: SwedenEurope

#8 Post by nooby »

Bernie I have either failed to express myself logically correct or the Developer of AntiX and Archiso and other linux distros know less than you do.

Even of one are root it is by design not possible to edit the menu.lst if it reside on the same partition as the subdirectory as one boot up in frugal install using a live CD iso.

If you can do it then please teach it to us that fail doing it. That would be of much help really. I go to bed now very late here. soon past midnight. 11.50 PM
I use Google Search on Puppy Forum
not an ideal solution though

User avatar
Bernie_by_the_Sea
Posts: 328
Joined: Wed 09 Feb 2011, 18:14

#9 Post by Bernie_by_the_Sea »

nooby wrote:Bernie I have either failed to express myself logically correct or the Developer of AntiX and Archiso and other linux distros know less than you do.
These are not the only possibilities. :)
nooby wrote:Even of one are root it is by design not possible to edit the menu.lst if it reside on the same partition as the subdirectory as one boot up in frugal install using a live CD iso.
This is not logically possible.

If it is not possible to edit the menu.lst or any other file then one is not running as root.

User avatar
8-bit
Posts: 3406
Joined: Wed 04 Apr 2007, 03:37
Location: Oregon

#10 Post by 8-bit »

I installed an early release of ubuntu that came in a Linux-Pro magazine.
When I did, I always logged on as root, basically defeating the so called protection one would get by NOT running as root.
And I still did not have control as some apps I would try to run would ask for root's password as a condition of running.
Needless to say, I trashed that installation and installed Puppy.
And by the way, Linux-Pro magazine was my first knowledge that Puppy Linux even existed!

nooby
Posts: 10369
Joined: Sun 29 Jun 2008, 19:05
Location: SwedenEurope

#11 Post by nooby »

Edit. I have found the post where Rcrsn51 explain how it fail to use root to edit the write protected menu.lst due to the whole partition or even the whole HDD is set to Read only regardless if one are root or not. Such setting at boot has higher authority for the OS then root has.

read here

http://www.murga-linux.com/puppy/viewto ... 802#518802
Is this the menu.lst file in your NTFS Windows partition that is run by grldr? It may be that Archiso is automatically mounting that partition as read-only.

If that's the case, you will have to go back to Puppy to edit the file.
Rcrsn51 would not write this way to me if that is not how Linux and any kind of OS works unless one have done like Barry has on Puppy. Barry has changed how it works so Puppy is an exception to the norm on any Unix OS.

And read here
http://antix.freeforums.org/solved-almo ... 08-15.html

Three guys knowing more about permissions and root and su and such spent hours on trying to help me and if it had been as easy as you say that would have been solved within 10 minutes or so.

I rather trust Rcrsn51 that he knows what he says.

This is the catch facts as I get it

If one boot the os the way I do and the os is a live distro that treat the HDD as if it is a CDROM then by design it is impossible to use root to change the menu.lst because the whole HDD is set up as read only.
Such boot up has a higher priority than being root. It will ignore that we are root and protect the hdd regardless of what we try to do. They built it that way.

So if you can trick it to do what you say in this thread that is great news and I would love that you share how you do it.


AFAIK that is how Unix and all their deriv... works apart from Puppy that can use another pupmode that do allow that one change things as root.

back to my older text

Bernie, it would be wonderful if you get it right.

but there are two "heavy" reasons that makes me think you read into my language something I have not said.

1. AntiCapitalistic who is the Developer of AntiX which is a kind of Simply Mepis but with a few changes and leaner he could not instruct me how to do it.

2. rcrsn51 here in puppy forum wrote in a way that I trust him on that if the script at boot set the partition that the menu.lst is on as read only then it does not help that one are root. Then that is too late.

My interpretation of his short text is that it is an hierarchical structural way programs work. What the script assign to that partition and all the files that is on it can not be altered by root ever.

so I trust that your set up is different from my set up.

The only way to be able to edit that menu.lst is to reboot and stop the boot process before the built in script assign the partition as read only and then bypass the script by jumping ahead of it's assigning and never let it set the partition as read only. Some script fail to boot up if one to this.

You being this sure of you being right can you not share exact how you set it up to work from before boot up.

1. I have an Acer D250 and the menu.lst is on sda3 which is a NTFS formatted internal HDD the primary drive.

2. My boot code is this.


title SwiftOS fail to do sda3 write but read okay
root (hd0,2)
kernel /swift/vmlinuz vga=791 fromhd=/dev/sda3 fromiso=/swift/swiftlinux-0_0_3.iso drvr=intel xres=1024x768
initrd /swift/initrd.gz


title Archiso-live
root (hd0,2)
kernel /archiso/boot/vmlinuz from=/dev/sda3/archiso rw elevator=deadline load=overlay session=xfce
initrd /archiso/boot/initrd.img


title antiX-11 frugal using iso use blkid
root (hd0,2)
kernel /antiXboot-M11/vmlinuz fromhd=UUID=C030C5AD30C5AAAC fromiso=antiX-M11.iso vga=791
initrd /antiXboot-M11/initrd.gz


title Porteus OS
rootnoverify (hd0,2)
kernel /porteusboot/vmlinuz rw
initrd /porteusboot/initrd.lz
boot

3. I have asked in Antix forum and I have asked another forum not sure where and I have asked in Puppy forum and in all three none of their equally sure answers as you being sure none of their suggestions did work. Until rcrsn51 answered me that it can not work due to the way an OS is set up at boot. it is not logically possible to get it to work unless you do as Barry Kauler did. Rewrote the whole thing to allow it.

Now your turn to do the impossible or at least to describe what it is you actually have done from set up to where things are when you do it.
I use Google Search on Puppy Forum
not an ideal solution though

User avatar
L18L
Posts: 3479
Joined: Sat 19 Jun 2010, 18:56
Location: www.eussenheim.de/

Difference Between Puppy & Ubuntu

#12 Post by L18L »

Big differences on
newest hardware :lol:

http://www.murga-linux.com/puppy/viewto ... 409#520409

Why is this in Forum index » Advanced Topics » Puppy Derivatives :?: :roll:

nooby
Posts: 10369
Joined: Sun 29 Jun 2008, 19:05
Location: SwedenEurope

Re: Difference Between Puppy & Ubuntu

#13 Post by nooby »

L18L wrote:Big differences on
newest hardware :lol:

http://www.murga-linux.com/puppy/viewto ... 409#520409

Why is this in Forum index » Advanced Topics » Puppy Derivatives :?: :roll:
I guess that mechmike tried to find a proper place and thought Hardware was the best choice. I would have placed it on Totally Off Topic instead :)
I use Google Search on Puppy Forum
not an ideal solution though

nooby
Posts: 10369
Joined: Sun 29 Jun 2008, 19:05
Location: SwedenEurope

#14 Post by nooby »

Bernie sorry I wrote such a long response above. What about this short version?

If one boot the os the way I do and the os is a live distro that treat the HDD as if it is a CDROM then by design it is impossible to use root to change the menu.lst because the whole HDD is set up as read only.
Such boot up has a higher priority than being root. It will ignore that we are root and protect the hdd regardless of what we try to do. They built it that way.

So if you can trick it to do what you say in this thread that is great news and I would love that you share how you do it.
I use Google Search on Puppy Forum
not an ideal solution though

User avatar
Bernie_by_the_Sea
Posts: 328
Joined: Wed 09 Feb 2011, 18:14

#15 Post by Bernie_by_the_Sea »

nooby wrote: If one boot the os the way I do and the os is a live distro that treat the HDD as if it is a CDROM then by design it is impossible to use root to change the menu.lst because the whole HDD is set up as read only.
This is impossible.
nooby wrote: Such boot up has a higher priority than being root. It will ignore that we are root and protect the hdd regardless of what we try to do. They built it that way.
They, and you, may think they built it that way but in fact it is impossible to build a Linux system that way.
nooby wrote: So if you can trick it to do what you say in this thread that is great news and I would love that you share how you do it.
Since root can do anything possible in Linux if it can't be done then root is not running -- a limited user called root is running. The "trick" is to become root. With root any drive/partition set up as read only at bootup can be changed to read and write at any time. A system booted with a read-only HD cannot prevent root from writing to that drive if it's physically possible.

nooby
Posts: 10369
Joined: Sun 29 Jun 2008, 19:05
Location: SwedenEurope

#16 Post by nooby »

Did I not made a copy that I actually was in root and it still told me that that partition or whole HDD was set as read only.

Still can you not describe what you actually do so one can learn to do the same.

And remember three Linux users that know how to use linux was as sure as you are now and them totally failed too to get the menu.lst getting accessable for saving and last but not least. Why would Rcrsn51 say that this is how it works if he doesn't know that from deep insight in linux.

I trust that what you refer to is something else. Maybe full install or you have frugal install on one partition and the menu.lst on another partition?

Something has to be different between the way it is set up at my place and how it is set up at your place or the structure or sequence we do the thing. So why not describe it.

The evidence or proof is in the taste of the pie. Referring to a recipe and not actually describing how you apply it don't make me trust we have the same thing set up.

I've done my best to describe my set up. What you have accomplished is a kind of miracle or astonishing achievement that can help many people so I would love that you share your knowledge and not keep it hidden.
I use Google Search on Puppy Forum
not an ideal solution though

User avatar
Bernie_by_the_Sea
Posts: 328
Joined: Wed 09 Feb 2011, 18:14

#17 Post by Bernie_by_the_Sea »

nooby wrote:Did I not made a copy that I actually was in root and it still told me that that partition or whole HDD was set as read only.

Still can you not describe what you actually do so one can learn to do the same.
I "described" what I would actually do -- "would" since I've never found myself in that odd situation -- I would switch to running as root.
nooby wrote:And remember three Linux users that know how to use linux was as sure as you are now and them totally failed too to get the menu.lst getting accessable for saving and last but not least. Why would Rcrsn51 say that this is how it works if he doesn't know that from deep insight in linux.
I didn't look at what Rcrsn51 wrote until now:
Rcrsn51 wrote:Is this the menu.lst file in your NTFS Windows partition that is run by grldr? It may be that Archiso is automatically mounting that partition as read-only.

If that's the case, you will have to go back to Puppy to edit the file.
Automatically mounting a partition as read-only does not mean that it cannot be unmounted, mounted as read/write or deleted by root. Going back to Puppy is a workaround and does not correct the read-only mounting.
nooby wrote: I trust that what you refer to is something else. Maybe full install or you have frugal install on one partition and the menu.lst on another partition?

Something has to be different between the way it is set up at my place and how it is set up at your place or the structure or sequence we do the thing. So why not describe it.
THERE IS NOTHING TO DESCRIBE. NOTHING. The type of install doesn't matter. The partition doesn't matter. Where files are doesn't matter. The sequence doesn't matter. The structure doesn't matter.
nooby wrote: The evidence or proof is in the taste of the pie. Referring to a recipe and not actually describing how you apply it don't make me trust we have the same thing set up.
This has NOTHING to do with any setup. It has nothing to do with "applying" anything. It has to do with one and only one thing, running as root.
nooby wrote: I've done my best to describe my set up. What you have accomplished is a kind of miracle or astonishing achievement that can help many people so I would love that you share your knowledge and not keep it hidden.

The evidence or proof is in the taste of the pie. Referring to a recipe and not actually describing how you apply it don't make me trust we have the same thing set up.
This has NOTHING to do with any setup. This has NOTHING to do with any "accomplishment" of mine. This has to do with the nature of Linux, what Linux is and what root is.

FYI, I am a capitalist, not a socialist. I have no interest in helping others outside of my own personal whim. I have no desire to "share" my knowledge. My knowledge is FOR SALE, not to give away. It is exactly this attitude and this sort of talk that bothers me on open source forums. It's one thing for a tinkerer to trade ideas or methods but it's another with constant demands for welfare handouts. Do you know why Microsoft has 85% of the OS market and why Linux has less than 2%? Do you know that one costs money while the other is free? The iPhone OS is already beating all versions of Linux combined... but then it's commercial, not amateur.
Attachments
Usage share of operating systems.jpeg
(15.42 KiB) Downloaded 1004 times

nooby
Posts: 10369
Joined: Sun 29 Jun 2008, 19:05
Location: SwedenEurope

#18 Post by nooby »

So you would do it but have never done it? No wonder that you are so sure it works then.

I was root at that moment. The Terminal confirmed me was root. Still I was not allowed to change that permission to change menu.lst to read and write.

Talk is easy. Show me that you can do it with the same set up I have that is what counts!
I use Google Search on Puppy Forum
not an ideal solution though

puppyite

#19 Post by puppyite »

nooby
Looks like you cause problems in every thread you post in.

User avatar
Bernie_by_the_Sea
Posts: 328
Joined: Wed 09 Feb 2011, 18:14

#20 Post by Bernie_by_the_Sea »

nooby wrote: I was root at that moment. The Terminal confirmed me was root. Still I was not allowed to change that permission to change menu.lst to read and write.

Talk is easy. Show me that you can do it with the same set up I have that is what counts!
You were NOT root. What the terminal confirmed is that you were running as someone named root but you were actually running as a limited user. How can you confirm that you are root? Simple. Just change the menu.lst permission to read and write. Can't do it? Then you have confirmed that you are not root. What counts is that if a person wants root privileges he must actually run as root and not as a limited user called root. What you have to do in your setup is figure out how to run as root and then you can change file permissions.

Post Reply