Language Selection

English French German Italian Portuguese Spanish

Introducing Mustang Linux & Screenshots

Filed under
Linux

Mustang Linux is a brand new entry in the small Linux distribution field. It aims to provide a simple (single mini) CD based Linux end-user client. The system boots from CD and loads the base operating system into a RAM image. No hard drive required. Uses 168MB of RAMDISK and needs a 586 system or higher with at least 256MB of RAM. Most base packages are from Slackware. The kernel is the latest 2.6.16.19 compiled with nearly all network cards and options.

Also supports read/write to NTFS (Windows 2000 and XP) hard drives. This allows the creation of a 'file-based' filesystem for customization and adding software packages. Provided on CD are extra packages such as Ted, Firefox-2.0, CUPS printing, etc. It is designed to fit on a mini-CD (<200MB) and to provide a basic Web services and email (sylpheed).

Mustang Linux is a concept test for a pocket-sized carry anywhere OS that is impervious to virus problems. Future concepts include providing broadband Internet services that will integrate additional software as requested by the user. Also customised versions to individual taste.

Information taken from the Mustang Linux Website.

Mustang is a lightweight compact fork or extension of Buffalo Linux.

interesting, yet somehow familiar

This sounds a bit like Puppy Linux. Can someone explain how it differs, if it differs?

re: Mustang Linux

Just what the world needs, another tiny Linux Distro. I'm sure the differences between it and the existing players (DSL, Puppy, Feather, etc) will be outstanding and practically overwhelming.

//golf clap//

Puppy is its own creation, actually

Puppy actually was never truly Slack or Vector-based. Applications were compiled in Vector (actually first in Mandrake, if I recall correctly) because there were no compilation tools available in Puppy itself. Now there are.

My question about the similarity had more to do with the inner workings than the applications that are included. Mustang sounds like it creates a file on an existing hard drive partition that houses your installed applications and other setting, much the same as Puppy (and DSL?) does.

Feather, as I recall, ran in RAM, but you could not install additional applications unless you installed the distro to the hard drive. Mustang sounds more like Puppy and DSL in this regard.

However, I guess my underlying question is how will/does Mustang distinguish itself from Puppy and DSL?

Comment viewing options

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

More in Tux Machines

Games: Ostriv, Back to Bed, EVERSPACE, Hiveswap: Act 1

Openwashing and Microsoft FUD

BlueBorne Vulnerability Is Patched in All Supported Ubuntu Releases, Update Now

Canonical released today new kernel updates for all of its supported Ubuntu Linux releases, patching recently discovered security vulnerabilities, including the infamous BlueBorne that exposes billions of Bluetooth devices. The BlueBorne vulnerability (CVE-2017-1000251) appears to affect all supported Ubuntu versions, including Ubuntu 17.04 (Zesty Zapus), Ubuntu 16.04 LTS (Xenial Xerus) up to 16.04.3, Ubuntu 14.04 LTS (Trusty Tahr) up to 14.04.5, and Ubuntu 12.04 LTS (Precise Pangolin) up to 12.04.5. Read more

Security: Updates, 2017 Linux Security Summit, Software Updates for Embedded Linux and More

  • Security updates for Tuesday
  • The 2017 Linux Security Summit
    The past Thursday and Friday was the 2017 Linux Security Summit, and once again I think it was a great success. A round of thanks to James Morris for leading the effort, the program committee for selecting a solid set of talks (we saw a big increase in submissions this year), the presenters, the attendees, the Linux Foundation, and our sponsor - thank you all! Unfortunately we don't have recordings of the talks, but I've included my notes on each of the presentations below. I've also included links to the slides, but not all of the slides were available at the time of writing; check the LSS 2017 slide archive for updates.
  • Key Considerations for Software Updates for Embedded Linux and IoT
    The Mirai botnet attack that enslaved poorly secured connected embedded devices is yet another tangible example of the importance of security before bringing your embedded devices online. A new strain of Mirai has caused network outages to about a million Deutsche Telekom customers due to poorly secured routers. Many of these embedded devices run a variant of embedded Linux; typically, the distribution size is around 16MB today. Unfortunately, the Linux kernel, although very widely used, is far from immune to critical security vulnerabilities as well. In fact, in a presentation at Linux Security Summit 2016, Kees Cook highlighted two examples of critical security vulnerabilities in the Linux kernel: one being present in kernel versions from 2.6.1 all the way to 3.15, the other from 3.4 to 3.14. He also showed that a myriad of high severity vulnerabilities are continuously being found and addressed—more than 30 in his data set.
  • APNIC-sponsored proposal could vastly improve DNS resilience against DDoS