Medicine for a Sick Linux Box

Squidgee writes "This is the site for "LIAP: Linux In A Pillbox". It is an interesting recovery distro made in the vein of pharmaceuticals; each floppy based 'minidistro' cures one specific Linux ailment. Or, as Luke Komasta (The creator of LIAP) puts it: "My Linux project contains "pills". Each of them is good for one disease, but it doesn't work good enough for another. When you know what you need a Linux for, you may choose a good pill. And of course, as you know, there is no drug which is good for treating all diseases." It's an extremely interesting approach to Linux recovery, and one that appears to be more effective than the other varieties of floppy/mini-cd based recovery systems. Worth downloading in case you ever need it!"

Comments

What Pill

[AvitarX]

What pill does it nead for a good slashdotting?

Re:What Pill

[mocktor]

iptables -A INPUT -p tcp -s ! 127.0.0.1 -j DROP

or possibly

echo "please upgrade my connection to an OC3 immediately and bill to uberadmin@slashdot.org" | mail -s "SOS!" admin@$isp

Diagnostic disk?

[Dr. Spork]

Well, for those who don't have enough experience to correctly diagnose what ails their box, it seems logical to make a diagnosis diskette, one that doesn't fix anything, but might give them a clue which pill has the best chance of fixing their problem.

Re:Diagnostic disk?

[Psiren]

Where the hell would you start? There could be a million and one things go wrong. I guess you could do something along the lines of the Microsoft troubleshooter. But whenever I've had need to use that, 90% of the time it ends up telling me it doesn't know how to fix the problem. Which is about as much use as tits on a bull :/

blue pill ?

[tiwason]

And does the blue pill disk install windows ??

Re:blue pill ?

[discogravy]

...a bitter pill to swallow, indeed.

A pill for . .

[borg05]

What disk do you use if your floppy disk drivers break?

Pills?

[Soko]

Don't tell me. Lemme guess.

The "Blue pill" returns your Linux machine back to normal function. The "Red pill" puts a trace on the kernel, and "shows you just how deep the rabbit hole goes...."

Soko

Hardly new

[forged]

Slackware has had a rescue root disk for as long as I can remember (somewhere ~1995 possibly). It provided most rescue tools that you needed on a single floppy.

I still occasionnally download a boot+rescue root disk to repair a screwed-up system that fails to boot, even when said machine isn't running Slack.

Re:Hardly new

[bhsx]

It's a new approach at building those emergency boot disks, so that you get exactly what you need/want. I dont' care what you can fit on two floppies; there will be times when you don't have what you need. This tries to address that problem in a rather interesting(if not terribly intuitive) way.

Re:Hardly new

[Tony-A]

Where the developers strive to reinvent the wheel, hundereds of times over.
Yeah, and you're thinking the first wheel was perfectly round and smooth?

Naw..

[FreeLinux]

I'd rather have everything I need at once, rather than having to switch floppies and reboot for a different function.

For me a bootable CD solution like Knoppix is a much better choice for a recovery disk.

Re:Naw..

[bogie]

Yea I just downloaded it last week and I'm really impressed. Things you can do with it off the top of my head.

Emergency disk repair via a nice gui!
Network scanning via nmap and ethereal. How cool is it to be able to plug into a compromised network and scan it without worrying about your system.
Ssh and vnc for admin without having to install it on your machine. This is great if you only have access to windows machine and don't want to have to download/install and software.
Secure web surfing. Want to check your email or do something else online that won't leave cookies etc on the local machine?
Great way to demo for people new to linux and let them learn linux without fear of them destroying their machine. This really would work great in a classroom setting and sure as hell beats having to reghost the machines every day.

You get a usuable full featured linux system on any machine with a cdrom. It really is very usuable as a desktop on any half decent machine. The only time it felt slow was when launching Open Office. Every other app launched faster than I though it would.

I know its not a new concept and others are available but its the best I've used so far,and should go in any admin's toolkit.

Dear god

[screwballicus]

I'd always thought, to a large extent, the frustration of dealing with Windows and Mac had been due to their perverse propensity for the use of abstract metaphors which complicate rather than explicate problems. That may be helpful for new users, but new users Linux users do not tend to be. Do Linux users want to be treated like babies all of a sudden? I know I certainly don't. And, somehow, I don't believe the linux community in general is going to be too impressed with useful utility encased in meaningless, obfuscating metaphors.

What about making it....

[ketamine-bp]

put all of them into a CD, which is bootable with isolinux and each remedy (that is the pills) is a root file system to mount - easier to use, faster, isn't it. i think that almost all recent years (5 years old computers) are ok with bootable CDs.

The windows version....

[Alien Being]

suppositories

what we need now...

[mad_cow]

Is LOASC (Linux On A Street Corner). The first one's free... and so are all the ones after.

Instead of lecithin, vitamin and insulin, we could have crack, lsd and heroin. You could even have a marijuana distro, which of course would be a gateway distro.

Not enought

[Bastian]

You can't fit everything you might need on one floppy, so it's hard to create a Swiss Army Rescue Disk.

Of course, that's why God gave us zipdisks. . .

Would like comparison disk

[Krellan]

More than a recovery disk/CD, of which several already exist, I would love a comparison disk. It would be for use after suspecting an attack.

It would boot from floppy or CD, guaranteeing that it would be in control and not trusting the hard drive for anything at all.

It would contain Tripwire-style keys for every system-installed file in the distribution. When booted, it would check each file against these keys, and output a list of files that do not match.

So, if one has been rooted with a good rootkit that modifies the operating system to cloak hacked files, one could then boot this disk/CD and be sure of being completely in control with a known good operating system. All files on the hard disk would be able to be accessed honestly, for a true comparison!

Does such a tool exist already?

It would be fairly easy to add this to the Red Hat installer. In addition to having an option to install, it would have an option to compare an existing system. It would go through the standard installation steps (choosing partitions, etc.) but compare instead of copy. A byte-for-byte comparison could then be done, for true honesty. If any mismatches are found, it would complain loudly, and give you the option at the end of simply overwriting the changed files (under your control, of course, and on an individual basis).

What do you think? Does such a tool already exist? I would love to use it if it does.

Re:Would like comparison disk

[lpontiac]

You can implement this yourself easily enough.

Let's say you want to do it for all the files in /root, /bin, /usr/local/bin and /etc. The following will get you a list of md5sums:

#!/bin/sh
find -s /root /bin /etc /usr/local/bin | while read x ; do
md5 $x
done;

Put the output of that into a file after a fresh install. Save it to disk. At any later point, do it again into another file. Use diff to find the differences.

The wonderful thing about Unix is that you can do this sort of thing with the standard shell and 5 lines of script :P

Re:Would like comparison disk

[Anonymous Coward]

Note: While this is a good idea, a kernel module can get around this technique (infiltrate the kernel, and any program on the system can do whatever you want- including md5sum).

Be sure to boot from a known good floppy/cdrom rescue disk for full effectiveness.

Re:Would like comparison disk

[lpontiac]

Except, of course, that the code you posted does not work

Works fine for me on FreeBSD. YMMV.

With xargs, you'll need it to run several instances of the md5 command to avoid having an arguments list that's too long. I'm not sure if this is standard behaviour. Of course, "find .. -exec md5 {}" should also work. Sorry, it was rather late :)

You're right about the -s, that's BSD specific. I guess you could run the overall output through sort.

"md5sum" is a GNU utility (found on most Linux systems), "md5" is the name of a utility written by Rivest (found on FreeBSD systems). Neither is standard.

meaningless, obfuscating metaphors

[Bastian]

kernel, mount, daemon, zombie, thread, named pipe, kill (especially Kill : The Command), jiffies, etc, etc.

link missing

[jsse]

The link to its ftp server seems to be missing...

If you want some working linux distro in a floppy you may look at Tom's. It's my favourite, it helps me install Gentoo Linux on some boxes cannot boot from CDROM.

Besides, you can find list of Linux floppy/CD distros here

Mandrake

[bigjocker]

The install CD for Mandrake can boot using a "rescue" image, which mounts a full system. It's got all I need to get my system up and running again.

I dont know who should ever need this thing, most distros already have a failsafe way of booting the machine (from cd, floppy or even hd).

"Full" system

[fireboy1919]

Unless, of course, you need reiserfs. I'm not sure they've added ext3 support to that, either. No devfs, either, AFAIK. This might have changed since last time I checked.

Of course, there aren't many systems that actually do include these things yet, so that could be the only reason.

Re:Appropriate Packaging

[dattaway]

I see real marketing potential: a boxed set of flourescent colored disks, labeled to look like prescription bottles. If a salesman at a floppy manfucaturing plant had a lunchtime to spare with the engineers, it could be possible to buy floppies with different colored sides on the front and back, just like a pill. I can see the possibilities with this and how easy it is to bring a package together. ..

SuperRescue

[meff]

Personally I prefer SuperRescue http://www.kernel.org/pub/dist/superrescue/ for system recovery, works remarkably well on a system with a CD-ROM. Give it a shot :)

they're metaphors

[Bodrius]

They are metaphors, they were meant as metaphors and they are still primarily used as metaphors.

Jargon does not start as jargon, only after it's used has been established in their technical context are they considered the "jargon" or idioms of the field.

Jargon terms have only three origins:
- Metaphors: process, kill, zombie, kernel, pipe, thread, batch, stack, etc.
- Codes and Acronyms: tcp, lisp, java, pc, minix, perl, etc.
- Idiotic Puns: more, less, archie, most shell commands.

Some, like GIMP, UNIX or GNU have mixed origins, but I'll let you decide which origins are present in the mix.

Not only are most computer science terms based on metaphors, very few people expect you to understand them properly without the metaphors. That makes learning concepts more difficult, and makes knowledge incomplete and not-portable.

Re:they're metaphors

[timster]

That's not my point exactly, and it isn't what I said. In the case of a zombie process, it's certainly true that the name "zombie process" was established from metaphor ("hmm, we have a situation where a process won't die... we'll call that a zombie, makes sense") but what I'm saying is that it isn't intended to be understood as a metaphor. You have to assign a name to the condition - it's inconvienient to say "process that has terminated but whose parent hasn't read its result code yet" every single time - but the name "zombie process" isn't really an attempt to convey any kind of understanding of what it IS. All the name conveys is that the process is sort of dead but not really; it doesn't purport to suggest how it came about, or what you could do about it.

A metaphor for a zombie process would be if you called it a "dead limb still hanging to a live tree" or something like that. It's certainly the case that the "process tree" is a metaphor, as the concept is usually taught and understood as a metaphor.

The reason for my response was to express that there's a difference between concepts that are understood as metaphors and concepts that are only named as metaphors. If you attempt to understand a complex concept using a metaphor, your understanding is limited to the quality of the metaphor. But jargon, merely naming a concept after a convenient metaphor, is not the same thing. No Unix I've seen has a "shotgun" command to do away with zombie processes. Imagine if they did, though; that would result in sysadmins who said "zombie process? just click on the shotgun" and they wouldn't have any clue what was really going on. That's what the concern is.

Re:they're metaphors

[Tony-A]

The metaphor starts the conceptualization. The term becomes jargon after it has obtained a more precise meaning. I would guess that a zombie process is one that is dead, or should be dead, but for some reason has not made itself disappear. One reason for a zombie to stick around is that somebody should maybe do an autopsy.

Doctor, it hurts when I do this!

[Reziac]

Tell me if I'm imagining unlikely things, but for those of us for whom linux is still mostly a mystery, how about a diagnostic that checks to see what's wrong, then applies the right "pill(s)" ??

Re:I took the:

[The Bungi]

You really do need to get a life.

A better name?

[Alien Being]

"The Linux Apothecary"

so which pill do you take to...

[glwtta]

Each of them is good for one disease, but it doesn't work good enough for another.

Which pill do you take if you want to learn to read good and do other things good too?

Re:What the F**K??

[Tony-A]

Linux recovery? What would I ever need that for?
Well if my experience is anything to go by, broken Microsoft Windows systems
Otherwise it's like you don't do away with the fire department just because you have flameproof shingles on the roof.

for the non-programmers

[Bastian]

A zombie process sticks around until either its parent dies without it being assigned a new parent or until its parent checks its exit status (the 'performing an autopsy' the previous poster mentioned).

The metaphor extends a bit more, because you can't kill a zombie process the way you can kill normal processes - because you can't kill something that's already dead =)

Re: Metaphors for New Users - Linux Dissent

[BigBlockMopar]

Do Linux users want to be treated like babies all of a sudden? I know I certainly don't. And, somehow, I don't believe the linux community in general is going to be too impressed with useful utility encased in meaningless, obfuscating metaphors.

I will be.

If Linux is ever going to replace Windows as a viable desktop operating system - which I think the majority of the Linux community rightly wants - then it's time to get your head out of the sand and look at the reality.

I'm typing this on a Windows XP box at work. It's not by choice that I am using Windows, in fact, I have defenestrated my home computers despite several problems with Linux as a viable desktop operating system.

This XP box is insipid, insulting, cartoonish, wasteful of CPU cycles and hardware resources. And, I think, Windows is almost at the point where any idiot can use it.

If you've ever done a stint in tech support, you know how the operating system must pander to the idiot who doesn't realize that a case sensitive password must be entered with the Caps Lock in the same mode as it was when the password was created.

Linux should not go this way by default, or else we will drive away both power users and developers.

But there's plenty of room for distributions and tools which are designed to make Linux easy for the proles to handle.

Don't knock them, applaud them. Unless you want to see all Internet protocols commoditized by The Borg.

www.glowingplate.com/dissent