The DistRogue

Saturday, January 26, 2008

Updates about SYS-Linux

I've learned a little more about SYS-Linux through the forums. Apparently, while it's still harder to upgrade than Windows, it *does* have a package-management system. And it uses the worst kind possible (at least IMO): Slackware's .TGZ packaging system. In a post, the lead developer says to download the packages yourself (as far as I can tell- I'm not a native Portugese speaker) and doesn't even provide a working link. I'm sorry, but I don't think "http:///" has any .TGZ packages. Anyways, downloading packages yourself, installing them via command line, and not even using dependency tracking? And this guy says his distro is for newbies? If you really like Slackware's packaging system, get Wolvix or Zenwalk, both of which have GUIs that download and install packages automatically, and have dependency tracking.
Then there's the package list. Bleeding-edge, fortunately enough, since you'll probably have to go for a while without upgrading it. In fact, it uses kernel 2.6.24-rc6-git2 (yes, a nightly build, which is probably as unstable and buggy as you can get- and this is the KERNEL!), Firefox 3.0-b2, Opera 3.25 (an ancient version released in 1998- cutting-edge indeed!), and db "1.85,2.4,3.3,4.2,4.4". Whatever than means. :S I honestly don't think a newbie likes it if their kernel crashes every 5 minutes, so they might want to pick a more stable version. Good news, though: kernel 2.6.24 just went stable!
And check it out: This distro satisfies everyone with its enormous package selection! Take a look at AV production, for instance:
* Audio-/Video-Studio/Produção: audacity 1.3.4 ; avidemux 2.4 , cinelerra 20071124 , dvdrip 0.98.8 , ffmpeg 20071102 , dvdshrink 2.6.1.10 , dvd+rw+tools 7.0 , k3b 1.0.4 , freevo 1.7.5 , acidrip 0.14, gstreamer 0.10.14 , kino 1.1.1 , kvideoencoder 0.0.8 , kstreamripper 0.3.4 , lxdvdrip 1.7 , mplayer 20071021 , muse 0.9.2 , rosegarden 1.6.1 , soundkonverter 0.3.6 , transcode 20071004 , sox 14.0 , streamripper 1.62.3 , winki 0.4.5

Errrm... Cool, but... I see 5 video editors (counting FFMpeg), 3 DVD rippers, 4 audio editors (counting Rosegarden), and a bunch of other redundant programs, but not much else. And under multimedia? There are 10 different media players. Looks like someone forgot didn't have time to fine-tune his app selection, did he?
And, of course, the all-emulating Wine.
* Emulador, p/usar programas de outros sistemas (McIntosh, Unix, Atari, Commodore, Windows): wine 0.9.51
Wait, Wine can emulate Mac/Atari/COMMODORE systems TOO? Wow, I never knew that! I always thought that "Wine is an Open Source implementation of the Windows API on top of X, OpenGL, and Unix," like the site says. Really, if you don't know what something does, don't put it in there.
Now for the challenge: I will make a CD image based on Xubuntu that is marginally complete (and it's not complete unless it has Compiz, we all know that much) and can still fit on a CD. It's not only possible, but easy thanks to Reconstructor, a tool for remastering Ubuntu images. It will have improved artwork, a more complete app selection, and Compiz, but most importantly, it will fit onto a CD roughly a quarter as large as the SYS-Linux image. I'm doing this just to show that it's possible to have a complete system that doesn't take up /!\ 11GB /!\ when installed. SYS-Linux is based on Slackware, but a key tenant of Slackware got lost somewhere in the remastering: "Keep It Simple, Stupid!"
From Arch (versionless),
The Distrogue.

Labels: , , , , ,

Monday, May 07, 2007

How to make a Live CD

Linux is a completely open-source family of operating systems (Linux itself isn't really an OS, but rather, a kernel), and so anyone can make their own distribution (in theory) and join in the action. But why do that? There are already hundreds of existing distributions, and odds are, one of them is right for whatever niche you have. This isn't a tutorial for making your own distro- that requires time, money, and m4d-1337 technical 5k!11z. This is how to make a Live CD for an application of your choice.

==Why have a Live CD?==

  • Portability. A program would normally have to be installed several times in order for it to be able to be used wherever you go, so why not put it on a CD?
  • Speed. Newsflash: If you dedicate an entire OS to just running one program, it'll run faster, and be more reliable.
  • It looks cool on a resumé. Wouldn't you like to say to a would-be employer, "I made my own Linux CD"?
Take a pick. The last one's especially important. It will get you unquestioned authority in computing.

==Choosing a base system==

There are a few options for a base system. Here are the best choices:
  • SLAX: The original remasterable Live CD. It runs a Slackware-based operating system with KDE. Only 200MB to start out.
  • Wolvix: An extremely feature-rich OS that uses XFCE and a ton of programs. I recommend the 1.1.0-beta series. The "Cub" edition is about 240MB, yet is a complete OS.
  • Myah: The version 2.0 series is pretty much the same as SLAX; however, the tech demos of the yet-unreleased Version 3 are i686-optimized (they run faster) and use XFCE. About 500MB.
Download the CD image (a .iso file) and extract it to a temporary folder in your home directory called "image".

==Adding the program==

SLAX 6-RC, Myah 3-TD1, and Wolvix 1.1.0 beta all use version 6 of the Linux-Live scripts. SLAX 5.1, Myah 2.2, and Wolvix 1.0.5, the stable versions, use version 5. This wouldn't be a big issue, except that the module format changed between those versions. It's probably a better idea to choose the newer versions of these distributions, because the new format makes smaller modules.
Make another folder called "program". Extract the file tree of the program to the folder. Inside, it should resemble a traditional Linux file system, with bin, etc, usr, or other folders (most of the time, it's just usr) in it.
Open up a terminal and type this:

cd image/name/tools

where name is either slax (for SLAX), wolvix (for Wolvix), or linuxcd (for Myah). Type the following commands:

chmod 755 *
mkdir ../modules
./dir2lzm ~/program ../modules/program.lzm

The first command makes all the tools for building LZM images (linux-live 6 modules) executable, so you can use them. The second makes a modules folder- this stores modules that are used at boot time. The third takes the program you made and turns it into an LZM file.

==Rebuild and burn==

You now have a file structure that you need to burn onto a CD. To do this, you need to make an ISO file.

cd ..
chmod 755 *.sh
./make_iso.sh

It will then prompt you for a name for the image. Hitting ENTER is usually fine.
In your home directory, there will be a CD image, ready to burn. Do so, but don't waste a CD-R on it, just use a CD-RW. It should fit, easily.

==Cut and try==

A Live CD usually doesn't come out right on the first try. Experiment with the image a bit. Here are some useful commands:

-lzm2dir: extracts an lzm file to a directory.
-chroot: allows you to run commands from inside another system. You can chroot to an extracted LZM file, for instance, and add or remove programs within the module itself.
-removepkg: This program comes with Myah OS, and allows you to cut down on the bloat that comes with it. ;)
-mo2dir: If you happen to have some old modules lying around, this convert them to LZM format.

==Examples==

The SuperTux Live CD is based on SLAX. The ThinkTanks Server Disk is based on Wolvix.

From Xubuntu 7.04,
The DistRogue.

Labels: , , , ,

Friday, March 23, 2007

Meet the pack...

Today, I was introduced to Wolvix, a SLAX-based live CD that uses XFCE instead of KDE. I've already downloaded the CD, added some custom SLAX modules (gotta have SuperTux and SuperTuxKart on there...), remastered the .ISO file, burned a CD, and made an untested QEMU image, so I can run it in Windows. Yes, in Windows. Now, the way I use computers might be changed completely. Most people think of a computer system as hardware and some software and data installed on a hard drive. With Wolvix, all the software resides on a CD, which is much more portable than a hard drive, and the data, along with the QEMU image, can be stored on a USB key. This "hybrid system" is highly portable, which might become a virtue when I take the next year off in Spain, without a half-decent system of my own, but with a lot of web cafes and maybe complimentary Internet access at the place I'll be staying. Wolvix, when used with QEMU, can run on Windows without any prerequisites, and the live CD doesn't even need Windows- or a hard drive, for that matter. One major problem: I'm using the pre-1.1.0 series of Wolvix, in which the provided NVidia driver (gefore.mo) doesn't work. I've tried it with several variations, but it still fails to work. :( Read more here. [EDIT: As you can see from the link, they're working on it. The beta versions of Wolvix 1.1.0 will, apparently, have working NVidia drivers.] As soon as that bug gets ironed out, I might use Wolvix as my primary system. Who knows where the possibilities end?

Labels: , , ,