JFS actually came from AIX to OS/2 and not the other way around. Do a google search on "JFS OS/2 AIX" and you can confirm this.
Or you can go straight to the source (no pun intended).
The relevant portion:
Historically, the JFS1 file system is very closely tied to the memory manager of AIX. This design is typical of a closed-source operating system, or a file system supporting only one operating system.
The new Journaled File System, on which the Linux port was based, was first shipped in OS/2 Warp Server for eBusiness in April, 1999, after several years of designing, coding, and testing. It also shipped with OS/2 Warp Client in October, 2000. In parallel to this effort, some of the JFS development team returned to the AIX Operating System Development Group in 1997 and started to move this new JFS source base to the AIX operating system. In May, 2001, a second journaled file system, Enhanced Journaled File System (JFS2), was made available for AIX 5L. In December of 1999, a snapshot of the original OS/2 JFS source was taken and work was begun to port JFS to Linux.
Also the test machine seems to have been an AMD, while I believe most distros put in a Intel optimised Kernel (atleast RH does) and the author mentions that it runs slower than a source distro.Shouldnt he have recompiled the kernel ideally
No need to recompile the kernel. SuSE provides an Athlon-optimized kernel which one can chose during the install.
The big changes were the loss of the ability to edit the configuration files; especially in regards to selecting which services start during boot. It proved almost impossible, for instance, to keep portmap from starting without mucking about in the bowels of the boot sequence.
So, does typing insserv -r portmap or using the YaST2 Runlevel editor count as "mucking about in the bowels of the boot sequence"?
Or you can go straight to the source (no pun intended).
The relevant portion:
Well, you gotta admit that, right now, IBM is the shit.
> > > > post by default.
Which brings to mind a Usenet post I saw a little while ago (in ahbou, I believe):
No need to recompile the kernel. SuSE provides an Athlon-optimized kernel which one can chose during the install.
The big changes were the loss of the ability to edit the configuration files; especially in regards to selecting which services start during boot. It proved almost impossible, for instance, to keep portmap from starting without mucking about in the bowels of the boot sequence.
So, does typing insserv -r portmap or using the YaST2 Runlevel editor count as "mucking about in the bowels of the boot sequence"?