Very Computer

I went out and shelled out CASH MONEY for CND 1.0...  I thought it would be a nice investment.  Well, in some ways, it was, but there were some things about it I just didn't like.

I have been working on recompiling the kernel for a while now.  Why?  Because each time I do, I get an error (or 100) that there's a parse error in this file, this other one came down with a serious case of malaria, yet another decided to move south for the winter.  The long and short of it, I have to edit all these files to correct the syntax errors that are in them.

Well, that's only part of it.  Heaven forbid you should compile, and then at another point, need to compile again... ALL OF THE HEADER FILES ARE WIPED CLEAR OUT OF EXISTENCE!

I've taken it to the point where I have a backup copy of the kernel source in its own ACCOUNT so that I should be able to retrieve the original files if this occurs...  Don't worry.  Still doesn't work.

If I'm the only one out there with this problem, I apologize for *ing and moaning like this.  It's just extremely frustrating.  If you're thinking about going CND, I post this as a warning.

After the $100+ dollars I spent on this *FREE* OS (between the Previews and CND 1.0), I have decided to do the "right" thing and go back to Slackware within a few weeks.

Oh well, had to get that off my chest.

Adam

re: CND cant compile kernel

There have to be two symlinks (see the README in /usr/src/linux)
for some header files.
If you frequently encounter file corruption (while is changed to w6ile or such),
maybe you are bitten by the SIG11 bug. If your compiler fails once or twice
'received SIG11' I am sure... file corruption can be caused by disk or
memory problems. Maybe get memtest86-1.1. from a sunsite mirror near you
(system/Misc if memory serves me).
Maybe get a clean kernel source from a funet/sunsite mirror, and try this.
Read the README, and if everything fails, report back with

  Hardware: board, controller, disk(s), memory...
  Software: kernel version, gcc version
  Logfiles: What was the error message?

Again: If it's not repeatable, think about HW problems.

Hartmut.