SuSE has been resisting me running it diskless. Actively resisting. The end result was that I had to build a custom kernel (we are using/supporting 220.127.116.11 right now), making sure to build nfs, and networking in, and not as modules. What I learned was that even if you think you have built everything, you could leave important little things off. And Murphy’s law dictates that those left off things are important.
Update 24-Dev-2007: One of the site owner listed below contacted me and asked me to remove their personal information which was contained in the site registration. I complied.
I have not checked whether or not their system is still an attack host. It is very important that people with good intentions protect their systems before placing them on the net. It is generally very hard to do this for windows, and fairly easy to do this for linux. For linux, look at the Firestarter package to make setting up a firewall fairly trivial.
[end of update]
Alrighty. I am sitting here fighting with a now mostly functional diskless SuSE 10.2 installation, when an email arrives. In my spam box. I check that about 4 times a day. Clean it out once a month or so. Usually with 8-9000 spam. Going to have to stop looking at it …
Ok, back to the story. So I get this email. It did something no other spam has done in a while. It got my attention.
Here is a snapshot.
“The education of an accidental CEO”. Very interesting read. It turns out a number of the folks whom have written about their experience running companies, all talk about the “gut feeling” about things. People, partners, etc.
So I am trying to get SuSE to PXE boot into a diskless session. In order to do this, first I have to get it to install into a directory. Next we have to do something about the kernel.
None of the above were used in DragonFly, though sometimes, sometimes, it feels like it.
DragonFly launched its first job this morning at 2am. 11 hours before the demo.
Nah, thats not cutting it close … not at all.
The job is the same ptb.exe job from before. On 4 cpus, with 100000 iterations (the other one finishes too quickly).
No, won’t get into detail. Sometimes in the course of business you realize that the people speaking to you have expectations that are entirely out of alignment with yours. After spending months in a careful and cautious dance to make sure that they are in fact in alignment. I learned a great deal today. Saddened … Read moreAnd yet another learning moment
A long time ago, on a computer not so far away, we built a program called “SICE”. Yeah, I am not known for naming things well. SICE’s entire purpose in life was to be a user centric interface to HPC systems. When users wanted to run jobs, they filled out a web form that described the job, and off it went.
This was not similar to other things out there in the market. This was designed not to sell queuing systems, or other bits. SICE was all about making peoples lives easier in using their systems. Odd concept that.
The arguments for vendor support of Linux are simple economics. In HPC this usually means that a vendor has a reasonable expectation of return on their investment if they support Linux. This is a valid view if you have something of value that people want at a price they are willing to pay.
The arguments for computer vendor support of Linux are again, simple economics. If Linux is driving business, you expect a vendor to pay attention. Revenue trumps ideology.