Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
BSD

Journal Journal: SectionTFSH/ThreeFarthingStone is Dead

I, SectionTFSH, also known as ThreeFarthingStone, am now dead. This means I will not be making any more posts to Slashdot, Gentoo Forums, or Zynot (new tiki-account was pending).

As I recently obtained OpenBSD, some will take this as confirmation of the BSD-is-dying (or BSD-causes-death) theory. This is not the case. BSD and *BSD are not responsible for this death. No computer operating system caused this death.

The death was caused because the maintenance of these accounts was too difficult. The death leaves several incompleted possessions:

The Party of Sinul - I wrote Episodes 4 and 5 of this Star Wars parody in the journal to provide a message about the SCO and Linux crisis. Because I was not exactly parodying Star Wars (there are to be more than 15 episodes) the next was to be Episode 2: The League Mobilizes. In it, a UN-like League of States would send military force against the Prosperous Revolutions that would form the Flag Empire.

Saturday Sequence - My personal biased news in this journal, saw one issue so far. It would contain some world news, and some news about myself, of course.

Interests in Programming Languages - My posts revealed that I knew some Java and shell scripting, but these interests are now also dead.

Logging out,


SectionTFSH/ThreeFarthingStone

News

Journal Journal: SectionTFSH Saturday Sequence *1

Today's Saturday Sequence includes Windows in the BIOS, blue helmets in Liberia, and other topics.

SATURDAY SEQUENCE
by SectionTFSH (ThreeFarthingStone
*1 of October 4th 2003

NEWS

Saturday Sequence appears in ThreeFarthingStone's Slashdot journal. I will post in sequence some information about the current situation on occasional Saturdays (in mainland USA time zones). Right now the Saturday Sequence has about zero readers.

The next episode to Party of Sinul is coming. Already posted in this journal are episodes four and five of a Star Wars parody with an obscure message about the SCO and Linux crisis. The next part, The League Mobilizes (Episode 2), in which the League of States enters the Kayongan War, is somewhat more difficult to write than the existing episodes. Episode 2 will be posted when it is ready.

The peacekeeping forces in Liberia put on blue helmets. This means that as of October 1st they are now under United Nations command. Unfortunately, my home country the United States of America has already pulled out most of its troops. Instead, the USA wants to encourage other countries to send troops to Iraq, where the USA leads an occupation. The USA-led coalition does not have blue helmets. I don't know why they are called "blue helmets".

OPINION

A move by Microsoft of parts of Windows to the firmware (BIOS) has advantages and disadvantages. Yesterday's Slashdot article mentioned the potential to make Windows-only computers and enforce Digital Rights Management. When a computer boots, it runs initially a firmware (sometimes called BIOS) contained in a small amount of read-only storage on the computer. This firmware decides which operating system to boot, boots it, and provides the operating system with access to the hardware. Moving the core parts of Windows into firmware could mean faster loading. However, almost no performance benefit will be gained because today's systems can copy the core of the latest Windows from disk into RAM memory. This is different from years ago when Apple placed the core parts of Mac OS in ROM.

Macintoshes once put the core OS into firmware. When a Macintosh was turned on, it boot Mac OS from the ROM. (Later Macs booted an incomplete version of Open Firmware, which booted the ROM.) The ROM would then search the disks for "blessed" System Folders containing the rest of Mac OS. Booting another OS besides Mac OS involved writing a program that shut down Mac OS and booted a kernel, or disguising the OS as Mac OS and trying to run it over the ROM. Otherwise only Mac OS would boot.

Recent Macs implemented the Mac OS ROM as a disk file. A good Open Firmware implementation searches for this file and boots it, and can be changed to boot another file, such as a bootloader for Mac OS X, which does not use the ROM. As a side effect a Linux, NetBSD, or OpenBSD bootloader can be used. Thus today's Macs can boot four or five operating systems. (Mac OS 9 is no longer updated and doesn't run on the newest Macs.)

Enforcing DRM could require a Windows computer to have a Windows-only BIOS. Digital Rights Management is supposed to restrict what the computer does, enforcing copyrights, and sometimes preventing fair use. Windows might implement system-wide DRM, making it completely impossible for any program to bypass DRM. Successfully booting a second DRM-less OS could bypass DRM. So, the firmware might only boot cryptographically signed Windows, and not Linux(1) disguised as Windows. A Windows bootloader program to boot Linux might not get the never get the necessary priveleges.

(1) I literally refer to a Linux kernel, as that is what must boot to use a system.

X

Journal Journal: XNote: OpenBSD ext2fs Problems

I have been trying to install OpenBSD (mirror). About a month ago, I tried running NetBSD, OpenBSD, and OpenDarwin in turn, looking for a OS to replace Gentoo Linux (which was having problems), before switching to Mac OS 9. However, I really wanted to be using the X Window System, so recently I reinstalled Gentoo by an ackward method.

As Gentoo is a constantly moving target (the portage tree is always being updated; only the stage tarballs and CDs are pinned by version numbers), I thought I'd try something more stable. The OpenBSD 3.3 release comes with a fixed 3.3 ports tree and associated precompiled packages. So I installed OpenBSD two days ago (21 August 2003). I accidentally deleted an important file, so I reinstalled yesterday. Then after having xdm/kdm problems, I reinstalled again today. Now, I'm finally running KDE, and I've given up on seeing an xdm or kdm login window, because there isn't a convenient script for starting it like Gentoo's /etc/init.d/xdm. This journal post is my first from OpenBSD.

In OpenBSD, I tried to mount_ext2fs /dev/wd0j /mnt my GNU/Linux partition. (I used the correct device.) Unfortunately I forgot to try -o ro (mount read-only) first. When I then tried ls /mnt I got an error.

When I rebooted into GNU/Linux, the yaboot bootloader (on a separate partition) couldn't find the Linux kernel. Next I rebooted into the Gentoo 1.4_rc7 KDE to try to use e2fsck to fix my partition. My Gentoo partition is an ext3 partition; this is the Linux standard ext2 format, with a journal attached. After a crash, the journal can be used to quickly fix the partition at the next mount without a full run of fsck, the file system checking program. The partition can be used both by ext3 software that updates the journal, and older ext2 software.

When I ran e2fsck, it told me not to use the -p option. I dropped the option and started tapping 'y' to make repairs. e2fsck told me that the root inode was missing. (OpenBSD had probably messed up trying to use it when I did ls /mnt.) It also told me that the journal was out-of-date. OpenBSD does not support the journal. So e2fsck deleted the journal. It then recreated the root inode, created /lost+found, and attached all the inodes that used to be my top-level directories (usr, tmp, etc.).

I mounted the partition (using the GNU/Linux on the Gentoo CD) and tried to move my lost directories into the right place. I looked inside each directory at its files to see what directory it should see. This requires some Linux filesystem layout knowledge. For example, the directory with "cache", "run", and "db" in it was moved to "var". The one with important libraries (including libc) became "lib". The one with the kernel "vmlinux" was moved back to "root". There was one directory with files I couldn't recognize. The sticky bit was set on this directory, so I thought it must be "tmp". I moved everything back except for three empty directories. Then I rebooted.

Now yaboot could find the kernel. The kernel started init. But the boot halted after mounting proc failed. I realized I forgot to put in the /proc mount point, which was probably one of three lost empty directories. I created a new /proc and rebooted.

Now my GNU/Linux system appears to be working. Why couldn't OpenBSD mount my ext2 (actually ext3) partition? I think it might be due to a change in the ext2 format that OpenBSD hasn't implemented yet... I thought ext2 was once limited to 2 GB partitions; my partition is larger than that. Maybe I'll try to find out later.

What were the two other missing empty directories? One was probably the old /lost+found (remember e2fsck had to create a new one). The other might have been the old root inode, but I'm not sure.

So, OpenBSD damaged my Linux partition but I fixed it. But Linux hasn't damaged my OpenBSD partition. Perhaps that is because I haven't tried mounting it, and I likely won't, because I think Linux has no ffs support.

X

Journal Journal: Copying Gentoo from KDE LiveCD

A quick binary install of Gentoo Linux is possible by copying the KDE LiveCD to the hard disk, if you know how. Scroll down for instructions.

Back a few months before the release of the Gentoo Reference Platform, the GNU/Linux distributor created GNOME and KDE LiveCDs for the PowerPC platform. The idea (similar to Knoppix) was to boot your computer, which had to be a New World Macintosh, off a CD, and use KDE or GNOME without having to install it on the hard drive. My downloaded copy of the Gentoo 1.4_rc7 KDE CD contains a bootable Gentoo Linux system. Boot it, log in as root (no password), use Xeasyconf to create the XFree86 config file, and use kdm to start, and one gets KDE 3.1.2 running over X Window System without any files installed on the hard drive!

The CD didn't work too well for me, so I did some experimenting. My problem was that I have a computer with only 64 MB of RAM. (Double that, 128, is recommended for Gentoo.) So I ran out of memory trying to start kdm. I fixed this by activating a swap partition on my hard disk.

Also, the Gentoo Compressed Loop filesystem is very slow. This is, I think, an ext2 filesystem compressed in a gzip file stored on the iso9660 CD. It would have been faster, except Linux the kernel had almost no memory to cache any files, because my 64 MB was being filled by RAM disks and KDE. So Linux kept rereading (and likely uncompressing again) the files.

So, I made the system faster by copying the system to my hard disk. Then I had a fallback system to boot in case my main Gentoo system, already installed, broke.

Then, I tried to reinstall Gentoo, failed, attempted NetBSD, OpenBSD, and OpenDarwin in turn, then in frustration switched to Mac OS 9 as my only operating system. My problem was that something wrong with my hard disk makes Linux crash under heavy extensive use, such as compiling software. I couldn't install Gentoo from source. NetBSD seemed immune to crashing, but the included XFree86 binary would not start. OpenBSD's XFree86 started; I tried to use the Ports Collection to compile KDE and it crashed on KMail. OpenDarwin's XFree86 wouldn't start. On Mac OS 9, the window system started, and I didn't compile anything from source because I could not obtain source code.

But Mac OS 9 did not satisfy, so I recopied Gentoo.

Instructions

Note: there might be a few errors below, I haven't checked it.

Caution: You probably will prefer using the new Gentoo Reference Platform instead of following this procedure.

  1. Boot your Macintosh from the Gentoo 1.4_rc7 KDE CD. (The GNOME CD might work also. Once the Gentoo 1.4 final KDE-GNOME CD is released, it might work a bit differently. Apparently a CD for i386 systems might be created also.)
  2. Log in (root, no password).
  3. Use mac-fdisk to create partitions, if necessary. The Gentoo CD will copy to one partition (I will call it /dev/GENTOO); I used a 3.5 GB partition. Also create a swap partition and bootstrap partition if needed.
  4. Format the partitions with mkswap and mke2fs -j (if you want an ext3 filesystem). Use swapon to enable swap if you want.
  5. Create a mount point (mkdir /mnt/gentoo). Mount the partition (mount /dev/GENTOO /mnt/gentoo). The mount points are as follows:
    • /mnt/cdrom contains the iso9660 filesystem on the CD.
    • /mnt/initrd contains the initial RAM disk, a layer needed because /mnt/iso is too big.
    • /mnt/iso is the mounted Gentoo compress loop. A lot of symlinks in / point into here. These are the files we want to copy.
  6. Copy the files. The command is cp -av /mnt/iso/* /mnt/gentoo (-a to preserve attributes exactly, -v to show the names of the files as they are copied). Do not use -x (one file system) because /mnt/iso/lib/modules is a separate filesystem (a RAM disk).
  7. The system you copied includes everything from the Linux kernel to KDE, but needs a bit of configuration. First edit /mnt/gentoo/etc/fstab. Make sure you know the fstab format! The file only contains a line for proc, so add a line placing /dev/GENTOO on /. Also add a line for swap. These are the only lines needed; I also added a line for my CD drive.
  8. When you boot your system, it will mount the root filesystem read-only and later encounter errors, because it does not have the normal scripts for checking filesystems and remounting root read-write. Fix this by adding a line to the start() function in /mnt/gentoo/etc/init.d/checkroot. That script is already in the boot runlevel.

    mount -n -o remount,rw,noatime /dev/root /

    Here, -n suppresses lockfile creation (root fs isn't read-write yet), -o provides options. The remount option is needed of course; rw means read-write. Replace noatime with whichever options you want (presumably the ones in /mnt/gentoo/etc/fstab). The convenient symlink /dev/root was created by devfs.

  9. If you just created a new bootstrap partition and do not have yaboot installed, you need to set up yaboot. Run yabootconfig -t /mnt/gentoo (do not use chroot).
  10. Use umount and swapoff to unmount everything, and reboot.
  11. If you have an existing yaboot partition, use it to boot your existing GNU/Linux system and add your new Gentoo CD copy to yaboot (one method is to edit /etc/yaboot.conf and run ybin). You might need to copy the kernel image, /boot/vmlinux on your new Gentoo CD copy partition, to somewhere on your existing system's root partition.
  12. Boot into your new Gentoo CD copy. If it complains about the root filesystem being readonly, then log in, remount the system read-write, and edit /etc/init.d/checkroot again.
  13. Configure the system. Things you might want to do:
    • Set up networking (/etc/conf.d/net, /etc/hosts, /etc/hostname, rc-update add net.eth0 default)
    • Replace /etc/localtime with symlink into /usr/share/zoneinfo
    • Edit /etc/rc.conf and do rc-update add xdm default
    • Add users. (useradd -m -G wheel,audio username )

I am running my Gentoo CD copy now, and it works. I need to fix the log-in message on my text consoles. The Konqueror from the CD has a problem displaying some images, so I have to use Mozilla to browse.

The next thing to do is get a portage tree working so I can replace/add software.

Space

Journal Journal: The Party of Sinul: Return Fire (Episode 5 * 2nd)

Read Episode 4 first

THE PARTY OF SINUL
Return Fire Episode 5

Long, long ago in a network far, far, away...

Emperor Clunis Bohandt, disappointed in the recent destruction of En\Tea, openly ordered an invasion of the Rebellion's distant base of libc-5.

But the invasion did not come. The Rebels under Commander Romstack were fortifying their base. Sinul, a pilot, was sleeping in his parked spacefighter during a break...

In his dream, he saw two soldiers from the Becdoh Revolutionary Guard.

"We must capture Sinul. He is on this planet," said one soldier.

"If he is not taken to Sasuri, he will be a threat to us. There he is!"

Sinul was captured. Then he remembered. Sasuri was not in Becdoh. It was one of the Realms. Also, he had survived Kayong without being captured. Sinul's dream changed setting.

"The Flag Empire is sending an invasion force to libc-5," said the Source. "Emperor Bohandt ordered it."

"It hasn't come yet," said the Penguin.

"We don't know if it will be another En\Tea, or something worse."

"Look. They are scaring us - the Rebellion - with an invasion force, but it hasn't come yet," remarked the Penguin. "With strength we will defeat them."

"Fear should not be ignored," said the Source. "We are uncertain what kind of attack we will get."

"We doubt we will get any attack at all."

The Source and the Penguin faded. In its place appeared the ship on which Sinul left Kayong, without being captured.

"The Flag Empire will be a threat," said Romstack. "But I have hidden some weapons. We can use them to start a Rebellion."

Romstack's speech was cut. Sinul woke. The real Commander Romstack was shaking him. "New intelligence that the Flag Empire's invasion might be coming," he said. "Get up. You must train."

==========

Romstack called a meeting. "The intelligence suggests that Brathe Fill has built another Electric-Nuclear Terrifying Explosion Apparatus."

"Another En\Tea!" shouted one. The audience recalled how the En\Tea could destroy the entire moon of libc-5, including the Rebellion's only base.

"He will have probably patched the hole," said the Commander. The first En\Tea had been destroyed when Sinul had shot a ping packet into a small hole.

"And there might be more than one." Two En\Tea units attacking. Even the precision aiming of the Floating-Point Computer might not be enough. "If one En\Tea survives it could destroy our base."

But Sinul heard the Penguin say, "The En\Tea is not as powerful as Brathe Fill says it is."

==========

Then the attack came. Four Death Oppression Ships approached. The Rebels were relieved. The DOS was a large and powerful spacefighter carrier and the backbone of the Empire's force, and many times the size of a spacefighter. The DOS that now attacked had only a few upgrades beyond the ancient units that the Rebellion was used to fighting. A DOS could be destroyed by blasting its weak points, which the Floating-Point Computer, a rebel invention, could easily target. The weak points were much easier to reach and hit than the hole on the En\Tea.

"In the days of the Empire's rise," Sinul heard the Source recall, "Rebel units fleeing toward the chosen planet of libc were blocked by DOS. But the Rebellion learned to defeat the DOS, and later defend libc-5 from DOS attacks."

"We will crush the DOS with our feet," said the Penguin.

A DOS launched spacefighters. While they struggled to aim at the Rebel spacefighters, Sinul and others were easily zapping enemies with the precision of the Floating Point Computer. Then the Floating Point Computer displayed for Sinul the weak points of a DOS.

"I would think that the Empire would modify its DOS," said Sinul. "They will lose just as they have lost many times in the past."

Sinul fired his blasters. The DOS was destroyed, leaving three. But look! Sinul now spotted two more DOS, making five on the battlefield.

Romstack came in by radio. "Sinul, go after the DOS. We have teams focussing on their spacefighters."

But before Romstack could finish speaking, Sinul had destroyed his second DOS, and one other had exploded. But six DOS appeared, making nine total.

Sinul flipped a ping packet at a cluster of enemy spacefighters, and destroyed his third DOS. The DOS were now exploding everywhere. But Sinul counted how many DOS were remaining, and there were at least twenty.

"They came with a large force," said the Source. "The Empire knew by now that a few DOS would not be sufficient."

"We could destroy three hundred DOS," said the Penguin. The battle continued.

Blast the DOS!
Packet toss!
We will destroy three hundred!
They explode!
Force erode!
Serial blow three hundred!

Thousands' op-
Ponents drop
People of DOS three hundred!
Massacre!
Rebels were
Defeating all three hundred!

Sinul had destroyed forty DOS, an impressive number. But scans were showing three hundred remaining.

"This will still be easy," said the Penguin. But Romstack was less optimistic. Over radio, "some of our pilots are out! We might not be able to destroy all these DOS!"

Sinul had destroyed eighty DOS, and eight hundred were on the battlefield. The Rebel pilots stood in shock and awe.

Was this not the entire Imperial Drove Force? How had the Empire managed to produce so many carriers? Sinul could tell that most of the DOS were far from fully loaded with spacefighters. But the DOS cannons, though technologically challenged, seemed working.

But Sinul picked up his DOS destruction rate. He was still counting. "297," he said after one explosion. "Almost 298, wait! Someone else got that one! Still 297." But there were two thousand DOS still out there.

"Two thousand!" screamed Romstack on the radio. "We must flee! Orders to abandon libc-5; we are being overwhelmed!"

It was up to Sinul to shoot his way out of the battle. So Sinul destroyed three more DOS, thus accomplishing the destruction of three hundred spacefighter carriers with one spacefighter.

Then his rate slowed. He was up to 311 when enemy spacefighters appeared ahead. He started destroying them rapidly while evading their return fire.

"Behind you!" yelled the Penguin. "Shoot him!" The Targetting Computer aimed a ping packet at a spacefighter which Sinul discovered was sneaking from behind.

"Don't shoot," instructed the Source suddenly. Sinul did not shoot.

But the other spacefighter shot, disabling Sinul's craft. Then a tractor beam shot out from the other spacefighter. The string attached to Sinul's craft, and towed him out of the battle. Sinul was prisoner.

==========

Sinul was led to an unmarked vessel, smaller than a DOS but with the ability to dock a few spacefighters. In that vessel the two ships parked. Out of one, Brathe Fill walked out.

Brathe Fill was high in the Imperial Drove Force and the evil behind the En\Tea. Why did he fly like a low pilot in a spacefighter, where he could easily become a battle casualty?

Brathe Fill forced Sinul out of his disabled spacefighter. "Sinul," said Fill. "You have destroyed many of our DOS."

"Three hundred and eleven," said Sinul.

"And with that you have killed tens of thousands of men! A crime!"

Sinul paused. He had murdered thousands, but the thousands had attacked him.

"But you, Sinul, may be spared. Your skill is useful. Come with me to Sasuri."

"I will not come," declared Sinul. Immediately he took out a concealed weapon. It was a dagger.

Sinul called it the Dagger Ans. Through it, he thought he read the Source more clearly. It was also his secret, and no person of the Rebellion knew it existed.

Ans lengthened into a sword. Sinul remembered a time when both the League of States and the Source Association were still in power. The two organizations worked for peace in the network. The League of States represented the galaxy's governments. The Source Association represented the wisdom and resources of four legendary people, the Faths.

Before the Empire, persons of knowledge could credit Fath Nul Sil, Fath Lir Leb, Fath Ap Ool, and Fath Om Kin for the welfare of the network.

Brathe Fill grabbed a staff. The elongated Dagger of Ans struck the staff. The battle begun.

"The Rebellion did not respect your power, Sinul."

"I was one of their most respected pilots."

"They intended to sacrifice you to the DOS while they fled."

"I was one of their most respected pilots," Sinul repeated.

"The Rebellion's plan is not really to maintain a pocket of freedom separate from the Empire, as you might think."

"The Rebellion encourages all to resist the Empire, as I do now."

"You would be part of the Rebellion's leadership, given your skill."

"I was desparately needed as a pilot."

"They stopped you from entering the leadership because you would have discovered the truth."

"You cannot know the truth."

The two fighters, evenly matched, stopped fighting as Brathe Fill announced, "I want to show you something."

With his staff, he wrote his name on the wall. BRATHE FILL. Then he waved his staff, and the letters shifted.

BRATHE FILL
BRFATHE ILL
FATH BRE ILL
FATH REB LIL
FATH LIR EBL
FATH LIR LEB

The wall now read, FATH LIR LEB. The man holding the staff said, "I am he."

Space

Journal Journal: The Party of Sinul: A New Parody (Episode 4 * 1st)

THE PARTY OF SINUL
A New Parody Episode 4

Long, long ago in a network far, far, away...

The power of the Flag Empire seemed unstoppable. Their forces crushed the freedoms of countless worlds. The Rebellion was forced into hiding.

The entire remaining force of the Rebellion lay hidden on the remote lunar land of libc-5. Meanwhile, Brathe Fill was pursuing Rebels with the secret weapon in order to find and destroy the Rebels. (Sound familiar?)

The Rebels' morale was low. Sinul was installing on to his spacefighter what may be the Rebellion's last hope, a new Floating-Point Computer...

Commander Romstack had briefed the pilots earlier. "The Empire's Death Oppression Ships, the backbone of their space force, are very effective at fighting and very difficult to destroy. But the DOS does have a few hard to hit weak spots. What we need are precise weapons.

"We have a working prototype Floating-Point Computer. This device will enable your weapons to hit very small targets. The DOS has a very primitive design."

Commander Romstack displayed a three dimensional model of the DOS. "To disable a DOS, you must hit most of these targets. After that it will be much easier to fight and destroy it."

Romstack approached Sinul with a box of hardware. "Sinul, here is the first floating point unit. I want you to test it."

Sinul was now wiring the box into his spacefighter. "Go get an int-to-long adapter," he ordered a nearby robot. The robot fetched the adapter. "Almost done," Sinul muttered.

"Time to turn the ship on," he said at last. "Weapon system check, good. Ready." With that he flew out of base.

Flying above the terrain of libc-5, Sinul wondered, "What do I test this thing on?" There seemed to be nothing on the ground but the occasional critter.

He remembered his hunger. Food rations on libc-5 were low. "Normally we hunt by foot," he recalled, "but now hunting may be the perfect way to test this Floating-Point Computer."

Just then, a rare, native libc-5 Giant Lunar Penguin came into view. "If I miss, it'll flee. Floating-Point Computer ready..." The computer targeted the Penguin.

Sinul fired his blasters. It was a direct hit. The Penguin fell immediately. Sinul landed his ship nearby.

"This thing is huge," he remarked. "It will provide many portions of meat, but how do I get it back to base? It won't fit on my small ship." He came up with an idea. Taking a spare parachute from his ship, he wrapped the Penguin. Leaving it outside, he rebooted his ship. "Now to try the Floating-Point Computer again."

The computer aimed at the top of the bag. "Tractor beam!" commanded Sinul. He pressed a button, and a primitive string-and-hook launched from the ship, latching perfectly on to the bag. Flying the ship, Sinul dragged the Penguin back toward base.

The approaching ship towing a dead Penguin attracted attention at base. Sinul landed to find himself before a crowd. His first words were, "The system works, and look what we have to eat!"

There was a great feast, celebrating the Floating-Point Computer, Sinul, and the Penguin.

==========

About a fifth of the spacefighters now carried Floating-Point Computers. Morale was significantly higher now that hunting was more successful. Sinul was flying for recreation near the base when he saw two strange, small objects flying high in the sky.

Now very skilled with the Computer, he shot one down. But the other quickly flew away. Sinul picked up the light wreck with his tractor beam and flew quickly back to base.

An awful report came from Commander Romstack a few hours later. "With Sinul's help, we have captured this," pointing to the wreck. "It is a probe of the Flag Empire."

The audience was shocked. They had been discovered. The Flag Empire knew now exactly where to send the DOS to destroy the last remnants of the Rebellion. "We have been discovered. Our force is not mobile enough to flee, nor is there any suitable destination close enough.

"But," said Romstack, "now that they know where we are, we can safely send scouting flights. We will send a team to check on the Empire's approaching force. We'll find out how many DOS there are."

"I can lead," said Sinul.

"You will stay here, Sinul. We need you to defend the base."

==========

But when the scout team came back, they were horrified. "It's no DOS," was the report. "The Empire has sent a new weapon. They intend to test their En\Tea on us."

Commander Romstack called the pilots to an emergency meeting. "Our scans have told us this much about the Flag Empire's new Electric-Nuclear Terrifying Explosion Apparatus, or En\Tea. There is a weapon on there powerful enough to destroy this entire moon. One charged shot and all the Rebellion will be destroyed."

The computer model of the En\Tea looked intimidating. The pilots were about to weap. "Pull yourselves together!" Romstack yelled suddenly. "There is hope!

"See this?" said Romstack, pointing to part of the model. "We have already found a security hole. If we can get a large ping packet into there, it will enter the En\Tea and destroy it. Normally we would have almost no chance, but now we have the Floating-Point Computer. A third of our spacefighters have the Computer. They will try to destroy the En\Tea. Meanwhile, the rest of the force can provide protection."

The pilots immediately went to work testing the ping weapons. The most recently reconditioned ping cannons were mounted on the ships with Computers. Soon it was time for the battle. The pilots took off from the base.

Brathe Fill was at window of the En\Tea, which was in orbit around libc. "Soon libc-5 will come into view; the En\Tea better be ready to fire by then!" But instead of the moon, Fill saw spacefighters approaching. "Send our own spacefighters to destroy them!" ordered Fill. "I will lead!"

The En\Tea was several times the size of a DOS, which would be much larger than a spacefighter. Sinul, part of a small formation of spacefighters, flew in parallel to the En\Tea's surface.

Brathe Fill, in his own spacefighter, started picking off Sinul's team. "This is easy!" he gloated. His aiming cursor was then pointed straight at Sinul. "This will finish him. Fire!"

"(A)bort? (R)etry? (F)ail?" prompted the screen. "What, the blaster system crashed?" fumed Fill. He steered his defenseless spacefighter away from the battle.

Meanwhile, Sinul, with theme music rushing through his head, was approaching the hole. "Use the Source!" he suddenly heard in his mind. He turned off the Floating-Point Computer.

Romstack radioed in. "Sinul, this is urgent, is there something wrong, your Floating-Point Computer is disabled!"

"No, I'm fine," Sinul radioed back. He fired. The ping packet approached the hole.

Miss.

Sinul swung the spacefigher away. "Romstack, I'll ready myself for another approach."

"Hurry! libc-5 will be in En\Tea's range soon!"

Sinul saw another Rebel spacefighter explode. He knew he had to hurry, or else there would be too few allies to protect him. Sinul went into another approach.

While evading fire, Sinul heard a sentence in his mind again. "Use the Penguin!" it said. Sinul turned on his Floating-Point Computer. The cursor aimed at the middle of the hole.

He fired.

The ping packet passed through the hole. It was inside the En\Tea. "Quick! Fly away!" Sinul radioed everyone. He turned upward, and distanced himself from the Empire's weapon.

There was a large explosion. The En\Tea was destroyed. For now, the Rebellion was saved.

Operating Systems

Journal Journal: Portage Wars 2

The Gentoo Linux distribution has forked. That's news for me, because I happen to be running Gentoo right now. The GWN (that's the Gentoo's official Weekly Newsletter) dutifully informed me of the fork, and I hurried off to the Zynot Foundation's web site to see what was going on. What will be the effect of the fork on portage - Gentoo's package manager?

Related Links

What is Gentoo?
(skip reading this section if you do not need background on Gentoo)

about Gentoo - It's all explained in About Gentoo Linux, although you should have some Linux experience first. Gentoo is a compile-from-source GNU/Linux distribution. By compiling the software yourself, you can use compiler flags that optimize for your computer, and make your own customizations.

portage - Gentoo's amazing package manager is portage, which I find an improvement over RPM. Like BSD ports, it will download, compile, and install a package given its name. Portage is written in python and has features that make it more powerful. Using portage's emerge command, one can search for, install, upgrade, and remove different versions of packages and dependencies, without first cd'ing to the correct directory. Portage maintains a database of installed packages, and who owns what files.

stages - To install Gentoo, one takes an existing Linux system (usually by booting from a Gentoo LiveCD), extracts the stage 1 tarball to an empty partition, and chroot's into a minimal system. Using the bootstrap script one rebuilds glibc and gcc to reach stage 2. Then one does emerge system to get basic programs like the shell to reach stage 3. From there they install a logger, cron, and the Linux kernel itself, and set up booting. It's also possible to skip steps by starting with a stage 2 or 3 tarball.

ebuilds - To upgrade Gentoo, one uses emerge sync to download the portage tree, which contains the latest ebuild files. The ebuilds contain bash (shell script) functions that describe how to build the software. The ebuilds also give the URL for downloading, the stable/unstable status on different architectures (x86, ppc, sparc, etc.), the required dependencies, etc. There is one ebuild for each version of each package.

Debate over Gentoo and Portage

users' actions - I am not a Gentoo developer; I only use their software, so I do not usually know much about Gentoo development. Users discuss Gentoo forums, where one can find an unofficial GentooBSD port (site) and HURD port (site). Such ports start by running portage on the BSD or HURD kernel.

developers' actions - Meanwhile, some other projects have more official status. The port to Mac OS X is an example. Thus, there are both official Gentoo projects and unofficial Gentoo-related projects.

debate of portage features - Thus, both developers and users do things to portage. They have debated topics like adding an SQL database to portage to speed it up, rewriting portage in C++, adding a progress bar to portage, all things that are very interesting. The current version of portage, as installed by emerge sync; emerge portage, already has nice features: emerge displays its help and other texts in color, it sets the titlebars of xterm windows to show progress, emerge -p lists what would be installed by an emerge command, emerge -U world upgrades whatever is installed on the computer.

control of portage - So who controls portage? The core Gentoo developers do, and how they handle it between themselves is not of my concern. Remember, for portage to have a feature, someone must actually write the code. Some people donate code. Some control whether it is accepted.

control of Gentoo - The same is true of the rest of Gentoo. The LiveCDs, the stage tarballs, etc.. But there apparently was a dispute over control which led to the creation of the Zynot Foundation. Zynot intends to fork the Gentoo distro; portage will be involved.

"yet-to-be-named Package Management System"

cause of the fork - On or before 1 July 2003, Zynot's web site was already featuring a lengthy description of why Zynot was forking Gentoo. My current understanding of the document's claims is that Zachary Welch did not like how Daniel Robbins was running the project. Robbins was steering the project in favor of his own "business interests" and not Welch's. Welch was frustrated at trying to support embedded devices in Gentoo. So he started the fork.

avoiding Gentoo control - Welch could have created another distro with closed management, like Gentoo, except the management would be controlled from him and could therefore serve his interests better. Instead, he chose an open model based on a non-profit foundation eventually to be controlled by all the Zynot users. Perhaps, by mistake or with reason, he associated one bad (for him) closed management structure with all closed structures. Perhaps he is just doing it to attract more users.

portage by any other name - In fact, by browsing the Zynot forums (there are now 313 users) it seems that the Zynot distribution will be much more then, for example, a small set of ebuilds to add to the portage tree, and an alternate C++ version of portage, all of which to be used on embedded devices. Instead, the new distro might be a complete fork, with its own package tree, stages, and liveCDs. The distro and the package manager still need a name.

new features - How different will Zynot's package manager be from portage? The Zynot forums package manager section contains a lot of proposals, a lot more than in the Gentoo forums. It seems the plan for a fork has created a desire to modify portage. Some of them sound interesting, such as multiple overlays of ebuild and recipes for multiple packages.

Bagheera - Geert Bevin was also dissatisfied with Gentoo and started work on a C++ portage before switching to Java. This could become Zynot's package manager, but it might not be. It could also become one of many, including a modification of python portage.

Incompatibilities Await

not like RPM - Does this mean that portage will get into a situation like RPM? RPM is used in Red Hat, Mandrake, and SuSE, and probably many other distros. But (under my impression) there aren't that many variations in RPM. In fact RPM is becoming standardized. The inability to install distro A's RPM package on distro B is usually because B has software older than in A, or B uses a slightly different package tree (packages with different names) than A. The first problem disappears for portage because portage compiles from source, against what software version you have, or upgrades dependencies for you. The second problem disappears as long as only the official Gentoo portage tree or slight modifications are used. If Zynot's distro makes significant modifications, there could be incompatibility.

Gentoo-Zynot compatibility question - Zynot forums has a page about compatibility. As it is not clear what Zynot's package manager will eventually look like (if a distro is actually created), it also is not clear how much compatibility there will be.

ebuild changes - The ebuilds might change in form, if features make that necessary. From my observation of the Zynot forums it seems most of the current ideas for a package manager do not require changes to the ebuild formats. Although ebuilds might need fixing (perhaps to not assume gcc as the compiler) the fixes could still be compatible with Gentoo. The few ebuilds that need it can have dependencies on other package managers, or a virtual package. Then there would be multiple package managers sharing one ebuild tree - you could pick a manager written in python or Java, or one that uses a client-server or database model.

Hatred and Intolerance

holy war? - It would be nice, then, if Gentoo and Zynot could agree to share ebuilds... but holy war could get in the way. If the two communities hate each other too much, they will insist on introducing incompatibilities in the ebuild format or the package names. They will try to make portage unable to co-exist with a Zynot package manager. They will attempt to unsuscribe each other from mailing lists. They will suspect a few of their own users of working for the other side and kick them away. All Gentoo users will switch to GNOME while Zynot users take KDE - or something like that.

target Microsoft - I don't believe in holy war. If you want to hate an OS, hate Microsoft Windows - but even I don't hate Windows anymore.

My Position

an account - I now have an account on Zynot's forums. My Gentoo forums account is a few months old. I created the Zynot account for the low user ID (I'm the 313th user, so my ID is 314). The forums look mostly dead, and no one else has signed up in the few hours since I did, which suggests the USA is an obscure timezone for Zynot.

my preference - I still use Gentoo. There is nothing wrong with it from my point of view; I wouldn't have forked the distro myself; I probably don't need any of the upcoming Zynot new features. A concern (that I have mostly avoided in this journal entry so far) is that Zynot will die without making a software release, so I don't have plans to switch yet. Zynot has not much of an identity (its OS distro does not even have a name) and I don't know if I want to switch. But Zynot interests me because there is potential for both improvement and disaster in portage. There could be portage alternatives with more features, and improved ebuilds for portage, or there could be hatred and destruction - a disaster for portage.

I wait for the future.

OS 9

Journal Journal: Mac Internet Explorer: Regarding the Death

Sure, the Mac OS version of Internet Explorer had the pathetic inability to be a file manager. But it was great and it will be missed. (Reminds me of Mir.)

When I used software, before it died

Long ago, my OS was Mac OS 9, my browser was Netscape Communicator 4.X, and my office suite was AppleWorks 5. That was in 2000, when I decided to explore this "Linux" I was hearing about.

In 2001, I installed a copy of LinuxPPC and started playing with it. I had GNOME running quickly. It was a long and difficult time, but eventually I had a working Internet connection and printer. I discovered KDE. I ended up switching to Konqueror and KOffice by the end of 2001. The switch was good for me, because Mac OS 9 was dying.

I continued using other Macs, and sometime in 2003 I switched over from Netscape 4.X to Internet Explorer 5.X. IE was smaller and faster, and its Java was better.

In January 2003 when I deleted all my OS to switch to Gentoo Linux, I also restored Mac OS, and used Internet Explorer as my preferred browser. The death of IE pains me.

(In fact, the OS 9 version of IE is already dead after version 5.1. The OS X version continued to reach 5.2, but will never reach 6.)

Parade of dead software

  • Netscape 4.X - AOL made me wait too long for Netscape 6, and I didn't like the result. I tried Mozilla, but didn't like it. But IE version 5 was ready, so I used it.
  • Mac OS 9 - In 2001, as I was trying Linux, Mac OS X was released. In 2002, Apple stopped booting OS 9 by default on Macs. Now that the last major program is ported the Mac OS 9 is pretty much a dead system.
  • LinuxPPC - The death of the LinuxPPC, Inc. distro was strange and unexpected. I found myself compiling KDE 3 from source. Then I decided to get Gentoo.
  • Internet Explorer - The disappearance of the Mac's most popular browser will hurt. Safari is not much of a competitor as long it doesn't run on Mac OS older than 10.2.
  • Linux kernel - It isn't dead yet. Assuming SCO doesn't kill it, it won't be dead soon. Some day, though, microkernel systems like Mach or L4 could finally displace it, something they have long failed to do. But Mac OS 9 fell to a Mach-backed Mac OS X. Now Internet Explorer for Mac, the most popular Mac browser, is going away. Listen, for there could be a day when

    emerge sync && emerge -u world

    doesn't give me a reasonably up to date system.

Slashdot Top Deals

Center meeting at 4pm in 2C-543.

Working...