Slashdot Mirror


Linux Fatware: Distros That Need To Slim Down

snydeq writes "We need bare-bones Linux distros tailored for virtual machines or at least the option for installs, writes Deep End's Paul Venezia. 'As I prepped a new virtual server template the other day, it occurred to me that we need more virtualization-specific Linux distributions or at least specific VM-only options when performing an install. A few distros take steps in this direction, such as Ubuntu and OEL jeOS (just enough OS), but they're not necessarily tuned for virtual servers. For large installations, the distributions in use are typically highly customized on one side or the other — either built as templates and deployed to VMs, or deployed through the use of silent installers or scripts that install only the bits and pieces required for the job. However, these are all handled as one-offs. They're generally not available or suitable for general use.'"

17 of 299 comments (clear)

  1. Really? by Anonymous Coward · · Score: 5, Informative

    Got that. It's called Debian Net Install.
    Done.

    1. Re:Really? by Freshly+Exhumed · · Score: 4, Informative

      TFA was a complete exercise in BS. Here's another example of how to do a slim Linux install: during a Mageia or Mandriva install, select the Custom option, deselect everything, click through to proceed but when it stops to check if you really, really want to have such a sparse choice select "truly-minimal-install" and you will get exactly what it says, without X or even man pages.

      --
      I deny that I have not avoided attaining the opposite of that which I do not want.
    2. Re:Really? by the_B0fh · · Score: 4, Informative

      Because some of us have used both, and know people who are the release managers for both, and know what kind of shortcuts Ubuntu takes (things that will screw you over).

      debian testing is far more stable than ubuntu stable.

    3. Re:Really? by RevSpaminator · · Score: 4, Informative

      Ubuntu didn't always suck. I've used it since the Flatulent Badger release and, for years, it was pretty standard Debian with a bunch of stuff preconfigured for new users. Over the last 3 or 4 years I've watched it become more and more "user friendly" and it seems like every release breaks a bunch of things I had manually installed/configured. Now when I go into familiar /etc files I see, more and more, "# Do not edit this file. Some new mysterious daemon will screw up all your hard work." Unity wasn't why I gave up on Ubuntu, but it certainly didn't help. I don't appreciate any GUI that presumes I want to do everything full screen mode. (I could save the cycles and not load any GUI for that.) I've now switched to Arch Linux. I'm learning a lot of things I never had to deal with before. I still don't have it the way I want it, but the rolling releases make it worth the effort. I particularly appreciate the fact that the Arch website regularly notifies users when an update needs special attention or of major architectural changes.

  2. Ubuntu Core by simonbp · · Score: 4, Informative

    Ubuntu core distribution is ~34 MB, and available for x86, amd64, and ARM. It's more than suffcient to bootstrap a lean OS.

    1. Re:Ubuntu Core by ilikenwf · · Score: 4, Informative

      It's also nonstandard in terms of all the stupid patches and daemons it comes with.

    2. Re:Ubuntu Core by higuita · · Score: 4, Informative

      No Linux distro on the planet uses the stock kernel.

      Slackware uses stock kernels

      All of them have different locations for many different files.

      Slackware puts the files where the app developers want to, they dont move files around, breaking stuff (are you listen redhat/fedora!)

      All of them have major patchs to all sorts of 'standard' apps.

      Slackware tried to used just the upstream code. Only when there are problem reported and there is a fix in the upstream cvs/svn/git, its is ported to the latest release (or the git version is used)

      So yes, there are standard, plain and simple distros... slackware is one of the most stable distros there is by not messing all over

      Linux's lack of standardization is repeatedly brought up as one of its largest problems in becoming a more common desktop since software vendors don't want to target a bunch of slightly different distro's to pick up a statistically insignificant portion of the population.

      Strange, there are things like static binaries, that work EVERYWHERE... you can also ship the libraries, for a pseudo static binary.
      But solving that isnt that hard, just have several VMs with the main distros and recompile... yes, its harder than having the source code open and let users/distros developers compile it for you, but that is the price for having closed source.

      --
      Higuita
  3. TurnKey Core by americamatrix · · Score: 4, Informative

    I always like to use TurnKey Core for such things http://www.turnkeylinux.org/core

    It's small, lightweight and runs very quickly even on older hardware. It does a great job.


    -americamatrix

  4. Archlinux, Slackware, Gentoo by ilikenwf · · Score: 5, Informative

    If you really want lightweight and have a specific purpose in mind, just use something that only gives you what you want/need based on what you install. Then, localepurge.

  5. #! Linux by Tyler+R. · · Score: 5, Informative

    I'm really liking Crunchbang lately! It's very fast, very stable, and it's based on Debian so it works pretty well with mainstream software. It also comes with non free repositories, and codecs.

  6. task-*.rpm by hduff · · Score: 4, Informative

    For RPM-based distros, it's easy enough to set up a task-*.rpm to install a minimal subset of the entire repository for a specific purpose, like a LAMP server. I'm sure .deb-based distros have something similar, so I'm really not seeing the problem here, just a lack of understanding the power of FOSS by the OP.

    --
    "I believe in Karma. That means I can do bad things to people all day long and I assume they deserve it." : Dogbert
  7. Re:Agree -- issues w/ VirtualBox... by Sparticus789 · · Score: 4, Informative

    PEBKAC

    I have Fedora 18 running in VBox with a Windows 7 host at this exact moment.

    --
    sudo make me a sandwich
  8. Re:RHEL/CENTOS minimal by gbjbaanb · · Score: 4, Informative

    CentOS minimal is 342Mb, which isn't as small as the Ubuntu, but I guess it comes with more "what you'd install anyway" packages.

    There's the netinstall too, which is 230Mb. Nowadays if it can fit on a CD, its considered insignificant in size.

  9. SUSE Studio is another option by houghi · · Score: 5, Informative

    http://susestudio.com/ and make your own. As light or as heavy as you desire.
    A starting point is JeOS. From the first page:
    You can export your custom operating system as a Virtual machine, Live USB Disk, CD/DVD-ROM, Hard Disk Image and so much more.

    As you want something very specific a great way would be SUSE Studio. Because I might want just a little bit different configuration then what you would want.

    --
    Don't fight for your country, if your country does not fight for you.
  10. Re:It's already there... by volkerdi · · Score: 4, Informative

    2GB for a full Slackware install? Try nearly 8.

    And yeah, I'd like to put it on a diet, but once something is already included it becomes quite entrenched. It's extremely difficult to remove anything large enough to make a difference without causing rioting in the streets with torches and pitchforks. I suspect it's the same for any Linux distribution.

  11. What about PuppyLinux or DamnSmallLinux? by hillbluffer · · Score: 4, Informative

    What about PuppyLinux or DamnSmallLinux?

    http://puppylinux.org/ http://www.damnsmalllinux.org/

    Both are tiny, and boot in less than a minute.

  12. Re:Your problem has already been solved. by zachary.grafton · · Score: 4, Informative

    I've been using it for almost 6 years as my primary desktop and laptop OS. Never had an issue like that, but then again, I take the time to search for critical bugs before I update, and considering this situation is supposed to be used for multiple VMs, it's not like rolling back to a previous snapshot is hard, minimal testing before deploying is assumed.