| DistroWatch Weekly
If you've enjoyed this week's issue of DistroWatch Weekly, please consider sending us a tip.
(Tips this week: 0, value: US$0.00)
|Linux Foundation Training
|Reader Comments • Jump to last comment
1 • older machines (by sclebo05 on 2003-09-08 16:07:40 GMT) |
as the user of an older machine (pentium 200mhz) i would like to see some sort of comprehensive list of distros that would run on this kind of hardware. after lots of searches on a forums i chose slackware, but having this information on your site could save someone a lot of work.
2 • Reviews of Geek Distros (by madhunter at 2003-09-08 17:12:00 GMT)
Yeah, I know MadAdmin basically builds his own cross and hands the hammer and nails to the critically minded every time he write a review for anything- whether it's a distro, new software, etc. Opinions are like buttholes, and apparently everyone can have one EXCEPT for the guy writing the article!
3 • Re-thinking the "distribution" model (by bhhenry at 2003-09-08 18:26:35 GMT)
How about a "DistroWatch Magazine"? Included each month is a CD-ROM with a distro or two.
4 • Wi-Fi (by Gary Higgs at 2003-09-08 21:16:52 GMT)
Really like this web site for keeping up with Linux distros..is there a distro that I might expect to work with my Siemens SpeedStream WAP router?....would like to go back to Linux on at least one box here, but what to know if I can make it fly first.
5 • Page Hit rankings (by Andrew at 2003-09-08 21:30:23 GMT)
Congratulations on finding an excellent solution to the Great Ranking Dillema! Let's hope everyone will be satisfied with this system - I know I am.
6 • Re: Page Hit Rankings (by Amresh on 2003-09-08 22:09:32 GMT)
Personally I believe that Page Hit Rankings(PHR) should not be taken too seriously. By this I mean no disrespect to those who treat the PHR of a distribution as a measure of its popularity :)
If a distribution A, for example despite being one of those with a high PHR, cannot be suitable for my needs(for whatever reason), I will look for one that IS. The only role PHR will have to play in this process is that I would tend to look down the list till I find a 'suitable' distro. I dont think my choice of a distribution would be influenced by its PHR in any way.And I fail to see why its generating so much talk. Don't take it too seriously.
OTOH, I think its time someone came up with a 'scientifically correct' method of PHR. Something that will not be so controversial. It could also make an interesting research thesis. Any takers?
(Having worked in a related field - performance based ranking - I think I could :))
7 • Mephis Logo (by Anonymous on 2003-09-08 23:33:30 GMT)
I'm sorry, but to me the Mephis Logo looks like an ant with a giant hard-on.
8 • Old Hardware (by AlanS at 2003-09-09 01:38:55 GMT)
For the purposes of an old hardware page I'd draw the line at Pentium MMX/Pentium II. When they went from i586 to i686, just what makes sense to me.
9 • Old Hardware (by lucas at 2003-09-09 02:01:52 GMT)
i think the line problem can be solved just the way you have set the PHR, let us choose the line, if it won't be too troublefull.
10 • Old Hardware (by Julle on 2003-09-09 06:22:52 GMT)
I think that it is impossible to draw a line between old and new hardware. At least one that will satisfy all. :) Some kind of listing where distros would be ranked according to their harware requirements would be best solution.
This kind of lists advantage would also be that people could easily find the kind of distro they are looking for. If you are looking for distro that will run smoothly in your current hardware you would choose distro that is reported to work in "older" hardware then your curent one. If you don't mind little slow system but want more eye candy you could pick distro that just barely runs with your current hardware.
11 • on old hardware distros (by Peter Damoc at 2003-09-09 12:31:54 GMT)
IMHO what people need is a list with distros that could offer a desktop solution (think graphical browser) for computers with CPUs in the 586 class (or older) with 32 Mb of RAM (or less)!
An alternative to Win95 if you may. :D
12 • Old Hardware (by David Montminy at 2003-09-09 14:57:14 GMT)
You should consider a time frame, like 3,4 or 5 years ago , to seperate old from newer computers. 5 years ago, we saw the very first Pentium III. Anything pentium II and down is second grade and should be considered "Not that old, but not quite recent", Finaly, anything from 6-10 years ago is really old hardware. (Pentium 200mmx was THE top in 1996, if i remember correctly)
It would also be useful to know if there are "client distros" that could be run to make the very old ones graphical terminals.
13 • Re-thinking the 'distribution' model: about Suse (by L Gandolfo at 2003-09-10 00:58:03 GMT)
Indeed, Suse could show more flexibility.
Once a customer has bought a Professional edition with 900 pages of documentation, he/she doesn't have much interest in having those books again in the near future.
Therefore Suse could offer a wider choice, as Mandrake does.
What about a CDs or DVD only edition, maybe with a booklet updating only what is new.
I believe it would be in the best interest of both Suse and its customers.
14 • Old hardware (by Robbage at 2003-09-10 02:12:00 GMT)
I agree with David Montminy, although I'd set the timeframe to 3 months, since it seems no sooner have I upgraded to'the latest, coolest hardware' than it's already old hat :)
(But seriously.. 5 years seems like a good timeframe.. but this might need to be scaled as we approach the sentient computer age a la 'Terminator')
15 • old hardware (by warpengi at 2003-09-10 03:59:35 GMT)
I would like to see distros that use a GUI on older hardware. In that case there are plenty of distros that will run on PII's. Once you get to Pentium MMX and down to 486 fewer distros will run with acceptable speed. There are probably several classes; 386/486, 486/P1, P1/Pentium Pro/Pentium with MMX, PII.
There are plenty of P1's and PII's headed for the landfills these days. It would be great to get new computer users started on these older systems using a linux distro that allows them to surf the net and do word processing and e-mail.
16 • Old PCs ram and HD constraints (by monkymind on 2003-09-10 05:10:42 GMT)
Old hardware could be sorted by ram size/type and/or video card size. HD size is also another limiting factor for old PCs.
Old = EDO 72 pin (32meg +)
Really old = 30 pin simms (8-16 meg+)
Anything that has 168 pin sdram 64-128meg is modern enough to run most linux flavours.
Does anyone know if any of palmtop (qtopia) like environments and browsers can be used on old hardware??
17 • Linux for Old Hardware (by John Gabriel at 2003-09-10 15:16:05 GMT)
Rather than focus on the processor or other technologies, I think the most important factor for running Linux on older PC's is memory.
If you want to run a modern Linux with KDE or Gnome, 128 MB of RAM is about the minimum, with 256 MB or more recommended.
My recommendation would be to feature a list of Linuxes designed to run in less than 64 MB. You could make it 32 MB, if you really wanted to keep the list small, but having 64 MB of RAM on a Pentium I wasn't uncommon. From there, anyone perusing the list could check out memory and other requirements for distro's that would suit their needs.
18 • Magazine Distribution (by DaveW on 2003-09-10 16:25:00 GMT)
Your idea could turn out to be the next big thing, as Linux and the rest of the open source/free software community moves away from the older Microsoft generation's way of doing things.
Of course, Britain-based Linux Format magazine has been including distro disks for some time (It's where I got my first Mandrake.)
But a magazine dedicated to one distro would have a shot at really opening up a market for Linux. A live-style distro like Knoppix would seem like the likeliest candidate for such distribution, since the user-reader could simply pop the cd into the machine and get started, with guidance from the print magazine.
The biggest problem I see would be ongoing content: You have the first issue with the distro attached and probably most of the print content dedicated to how to install/use it. Then what? New readers would need the first issue to get the basic distro, but once they have it, they want the next issues to contain additional apps. Getting bookstores and the like to keep Issue One around for a long time would be difficult. Or, if the base distro is as small as Knoppix, I suppose the latest version could be in every issue, with apps on additional disks. But then you're back to the problem with the print content: nobody wants to see most of that taken up with intro/installation stuff every time.
So there are some concepts to work out, but I think this could be one of those simple ideas that turns out to be amazingly fertile.
19 • Knoppix's fate?! (by maurice on 2003-09-10 17:52:13 GMT)
That's not a good news:
Closed because of "Software-Patents"
In the next few days, the European Parliament will decide about the legalisation and adoption of so-called "software patents" in Europe, which are already used by large companies in other countries to put competitors out of business. This can lead to the termination of many software projects such as KNOPPIX, at least within Europe, because the holders of the over 30,000 already granted "software patents" (currently without a legal foundation) can claim exclusive rights and collect license fees for trivial things like "progress bars", "mouseclicks on online order forms", "scrolling within a window" and similar. That way, software developers will have to pay the "software-patentholders" for using these features, even in their own, completely self-developed applications, which can completely stall the development of innovative software for small and medium companies. Apart from this, the expense for patent inquiries and legal assistence is high, for even trying to find out if the self-developed software is possibly violating "software-patents", if you want to continue to market your software. Contrary to real patents, "software-patents" are, in the current draft, monopolization of business ideas and methods, even without any tangible technical implementation.
More about the current major problem at http://swpat.ffii.org/index.en.html
20 • Re-thinking the 'distribution' model: about Suse (by L Gandolfo at 2003-09-10 0 (by Daniel M. Stadnyckyj at 2003-09-12 02:13:42 GMT)
L. Gandolfo makes some valid points. SuSE and the other major distros might want to offer the documentation in a binder format. That way it can be updated with the newer information 'addendums" and also have the core material for newbies. The new documentation along with the discs can be offered in a packet that can just be added to the binder.Certain PC games were packaged in this format.
Just a thought.
21 • Page Hit rankings (by James on 2003-09-12 20:25:10 GMT)
Why not keep the default view the original 12 months like it used to be rather than the 3 months it is now.
I know it lets you store a cookie with your preference, but shouldn't those not changing the value see what it used to show?
22 • RE: Page Hit rankings (by ladislav at 2003-09-15 09:53:13 GMT)
Why not keep the default view the original 12 months like it used to be rather than the 3 months it is now.
That's what choice is about. If you don't like the default, by all means do exercise your right to choose a different default option.
23 • Well... (by Sam at 2004-07-20 23:45:29 GMT)
I would really like to have a linux capable of running a graphical interface on 32mb ram. It would make alot of useless computers useful...
Number of Comments: 23
Display mode: DWW Only • Comments Only • Both DWW and Comments
|• Issue 746 (2018-01-15): deepin 15.5, openSUSE's YaST improvements, new Ubuntu 17.10 media, details on Spectre and Meltdown bugs|
|• Issue 745 (2018-01-08): GhostBSD 11.1, Linspire and Freespire return, wide-spread CPU bugs patched, adding AppImage launchers to the application menu|
|• Issue 744 (2018-01-01): MX Linux 17, Ubuntu pulls media over BIOS bug, PureOS gets endorsed by the FSF, openSUSE plays with kernel boot splash screens|
|• Issue 743 (2017-12-18): Daphile 17.09, tools for rescuing files, Fedora Modular Server delayed, Sparky adds ARM support, Slax to better support wireless networking|
|• Issue 742 (2017-12-11): heads 0.3.1, improvements coming to Tails, Void tutorials, Ubuntu phasing out Python 2, manipulating images from the command line|
|• Issue 741 (2017-12-04): Pop!_OS 17.10, openSUSE Tumbleweed snapshots, installing Q4OS on a Windows partition, using the at command|
|• Issue 740 (2017-11-27): Artix Linux, Unity spin of Ubuntu, Nitrux swaps Snaps for AppImage, getting better battery life on Linux|
|• Issue 739 (2017-11-20): Fedora 27, cross-distro software ports, Ubuntu on Samsung phones, Red Hat supports ARM, Parabola continues 32-bit support|
|• Issue 738 (2017-11-13): SparkyLinux 5.1, rumours about spyware, Slax considers init software, Arch drops 32-bit packages, overview of LineageOS|
|• Issue 737 (2017-11-06): BeeFree OS 18.1.2, quick tips to fix common problems, Slax returning, Solus plans MATE and software management improvements|
|• Issue 736 (2017-10-30): Ubuntu 17.10, "what if" security questions, Linux Mint to support Flatpak, NetBSD kernel memory protection|
|• Issue 735 (2017-10-23): ArchLabs Minimo, building software with Ravenports, WPA security patch, Parabola creates OpenRC spin|
|• Issue 734 (2017-10-16): Star 1.0.1, running the Linux-libre kernel, Ubuntu MATE experiments with snaps, Debian releases new install media, Purism reaches funding goal|
|• Issue 733 (2017-10-09): KaOS 2017.09, 32-bit prematurely obsoleted, Qubes security features, IPFire updates Apache|
|• Issue 732 (2017-10-02): ClonOS, reducing Snap package size, Ubuntu dropping 32-bit Desktop, partitioning disks for ZFS|
|• Issue 731 (2017-09-25): BackSlash Linux Olaf, W3C adding DRM to web standards, Wayland support arrives in Mir, Debian experimenting with AppArmor|
|• Issue 730 (2017-09-18): Mageia 6, running a completely free OS, HAMMER2 file system in DragonFly BSD's installer, Manjaro to ship pre-installed on laptops|
|• Issue 729 (2017-09-11): Parabola GNU/Linux-libre, running Plex Media Server on a Raspberry Pi, Tails feature roadmap, a cross-platform ports build system|
|• Issue 728 (2017-09-04): Nitrux 1.0.2, SUSE creates new community repository, remote desktop tools for GNOME on Wayland, using Void source packages|
|• Issue 727 (2017-08-28): Cucumber Linux 1.0, using Flatpak vs Snap, GNOME previews Settings panel, SUSE reaffirms commitment to Btrfs|
|• Issue 726 (2017-08-21): Redcore Linux 1706, Solus adds Snap support, KaOS getting hardened kernel, rolling releases and BSD|
|• Issue 725 (2017-08-14): openSUSE 42.3, Debian considers Flatpak for backports, changes coming to Ubuntu 17.10, the state of gaming on Linux|
|• Issue 724 (2017-08-07): SwagArch 2017.06, Myths about Unity, Mir and Ubuntu Touch, Manjaro OpenRC becomes its own distro, Debian debates future of live ISOs|
|• Issue 723 (2017-07-31): UBOS 11, transferring packages between systems, Ubuntu MATE's HUD, GNUstep releases first update in seven years|
|• Issue 722 (2017-07-24): Calculate Linux 17.6, logging sudo usage, Remix OS discontinued, interview with Chris Lamb, Debian 9.1 released|
|• Issue 721 (2017-07-17): Fedora 26, finding source based distributions, installing DragonFly BSD using Orca, Yunit packages ported to Ubuntu 16.04|
|• Issue 720 (2017-07-10): Peppermint OS 8, gathering system information with osquery, new features coming to openSUSE, Tails fixes networking bug|
|• Issue 719 (2017-07-03): Manjaro 17.0.2, tracking ISO files, Ubuntu MATE unveils new features, Qubes tests Admin API, Fedora's Atomic Host gets new life cycle|
|• Issue 718 (2017-06-26): Debian 9, support for older hardware, Debian updates live media, Ubuntu's new networking tool, openSUSE gains MP3 support|
|• Issue 717 (2017-06-19): SharkLinux, combining commands in the shell, Debian 9 flavours released, OpenBSD improving kernel security, UBports releases first OTA update|
|• Issue 716 (2017-06-12): Slackel 7.0, Ubuntu working with GNOME on HiDPI, openSUSE 42.3 using rolling development model, exploring kernel blobs|
|• Issue 715 (2017-06-05): Devuan 1.0.0, answering questions on systemd, Linux Mint plans 18.2 beta, Yunit/Unity 8 ported to Debian|
|• Issue 714 (2017-05-29): Void, enabling Wake-on-LAN, Solus packages KDE, Debian 9 release date, Ubuntu automated bug reports|
|• Issue 713 (2017-05-22): ROSA Fresh R9, Fedora's new networking features, FreeBSD's Quarterly Report, UBports opens app store, Parsix to shut down, SELinux overview|
|• Issue 712 (2017-05-15): NixOS 17.03, Alpha Litebook running elementary OS, Canonical considers going public, Solus improves Bluetooth support|
|• Issue 711 (2017-05-08): 4MLinux 21.0, checking file system fragmentation, new Mint and Haiku features, pfSense roadmap, OpenBSD offers first syspatch updates|
|• Issue 710 (2017-05-01): TrueOS 2017-02-22, Debian ported to RISC-V, Halium to unify mobile GNU/Linux, Anbox runs Android apps on GNU/Linux, using ZFS on the root file system|
|• Issue 709 (2017-04-24): Ubuntu 17.04, Korora testing new software manager, Ubuntu migrates to Wayland, running Nix package manager on alternative distributions|
|• Issue 708 (2017-04-17): Maui Linux 17.03, Snaps run on Fedora, Void adopts Flatpak, running Android apps on GNU/Linux, Debian elects Project Leader|
|• Issue 707 (2017-04-10): PCLinuxOS 2017.03, Canonical stops Unity development, OpenBSD on a Raspberry Pi, setting up a VPN for privacy|
|• Issue 706 (2017-04-03): Super Grub2 Disk, Snap packages of deepin applications, Subgraph OS routes network traffic for one application, announcements from Linux Mint|
|• Issue 705 (2017-03-27): Minimal Linux Live, sharing control of the operating system, new KaOS features, Uplos32 provides 32-bit fork of PCLinuxOS|
|• Issue 704 (2017-03-20): ToarusOS 1.0.4, Linux Mint's security record, Debian starts Project Leader election, Ubuntu 12.04 reaches end-of-life|
|• Issue 703 (2017-03-13): SolydXK 201701, CloudReady, Solus announces new features, KDE Connect sends text messages from desktop, openSUSE's YaST module for Let's Encrypt|
|• Issue 702 (2017-03-06): Fatdog64 Linux, elementary OS bundled with new netbook, Haiku announces new features, security and the size of a distro's development team|
|• Issue 701 (2017-02-27): OBRevenge 2017.02, Mageia 6 delays, NetBSD reproducible builds, questions about swap space, trying to steam video on a Raspberry Pi|
|• Issue 700 (2017-02-20): RaspBSD, Debian replaces Icedove with Thunderbird, Fedora's licensing guidlines, tips for switching shells, finding battery charge, getting IP address and killing processes|
|• Issue 699 (2017-02-13): Clear Linux, GhostBSD network utility ported to FreeBSD, Ubuntu coming to Fairphone, elementary OS crowd funding an app store|
|• Issue 698 (2017-02-06): Solus 2017.01.01, comparing containers with portable applicatins, Tails dropping 32-bit support, Debian Stretch enters freeze|
|• Issue 697 (2017-01-30): Subgraph OS 2016.12.30, running Ubuntu on an Android phone, Arch Linux phasing out 32-bit support, Linux Mint testing updated LMDE media|
|• Issue 696 (2017-01-23): GoboLinux 016, remotely running desktop applications, Solus adopting Flatpak, KDE neon using Calamares, TrueOS tests OpenRC|
|• Issue 695 (2017-01-16): Zorin OS 12, Peppermint team fixes installer bug, Debian refreshes Jessie media, Ubuntu improves low graphics mode, Exciting things coming in 2017|
|• Full list of all issues|
|Random Distribution |
Momonga Linux is a Japanese Linux distribution developed in a bazaar-style model by its developer community. The distribution's main features include secure default settings, strong support and usage of Ruby, easy handling and processing of electronic documents, packages for scientific and technical computations, an easily configurable installer, support for a large number of file systems, and selection of newest packages at the time of installation.