Linked by Barry Smith on Mon 1st Dec 2003 18:34 UTC
Debian and its clones This is the second in my series of reviews for debian-based commercial distros that might be appropriate for SOHO use. The first article covered my exploration of Lindows, and this one is focused on Libranet. Before I get started with Libranet I want to clarify a couple of points.
Permalink for comment
To read all comments associated with this story, please click here.
RE: Grub
by B. Smith on Mon 1st Dec 2003 21:16 UTC

Mark Brophy Wrote:

"If one does not make any software changes and all of a sudden the software does not work, it is more than likely NOT the fault of the software! Normally I wouldn't defend GRUB (as I've had problems myself), but when it comes to Libranet, I have no choice. While I don't use it now, I have to admit that it's one of the most pleasant and usable distros in existence. But that's irrelevant... the rest of the review after this folly is filled with feelings of distrust and distaste for a company that did everything RIGHT!
-Mark"

Mark,

Apparently I touched a nerve. Do you dispute the accuracy of my report? DO you think I am lying? Or is it simple resentment because I dared to say something less than complimentary about Libranet? You stated that you have had problems with Grub yourself, did you not?

BTW, if you believe that LIbranet did everything right, why are you no longer using it?

I like many things about Libranet. I never said, nor did I imply, that I disliked or distrusted Libranet. I said that I distrusted that particular installation and therefore removed it. I also said that I might have received help from Libranet, had I asked. This assumes that I would have been capable of understanding the solution had they offered one.

All I know is that I had previously installed Libranet 2.7, RedHat 7.3, 8.0 & 9.0, Mandrake 8.0, 8.1, 8.2, 9.0 & 9.1, Knoppix 3.2 HD install, Lycoris Rel. 2 & 3, Morphix (various) on that same system with the same hardware and never had any problems at all. I also know that I replaced Libranet 2.8.1 on that system with Lindows 4.0 and I had no additional trouble. I am currently using Mepis on that system, and there has been no sign of any problems.

So if it was a hardware issue, it must have been a hardware issue that apeared out of nowhere without warning, and then fixed itself when I wasn't looking, because there is no evidence of any trouble now.

I also stated, repeatedly, that it is quite possible one of you knowledgeable types could have fixed it, but I couldn't fix it.

When you are in a high mountain forest, sitting under a tree with a broken leg, it doesn't offer much comfort to reflect that a doctor could fix things easily. If you are on your own, then you need to be able to cope with it yourself. When I am on my own with my systems, I need to be able to fix them myself.

And I do not have the luxury of deep cash reserves or a dozen backup systems to draw upon, unlike large enterprises.

B. Smith