Actually, no conflict of interest exists. I shelved plans for thisQuote:> Shortly after the LGX alpha release started shipping, Jordan
>Hubbard announced his plans to do his own 386bsd/Linux CDROM, which I
>assume is still in the works. I am not accusing Jordan of
>deliberately lying in order to clear a path for his product, but I do
>think readers should read his complaints with an awareness of this
>potential conflict of interest. Also, for the sake of full
CDROM some time ago and have since gone on to work on a 386bsd only CD
for Walnut Creek. I have no plans to compete with Adam, or in the
Linux arena, at all. My criticisms are strictly those of a
dissatisfied customer, and there is no venal motive whatsoever.
Well, that's far friendlier than I would have been in response to theQuote:>disclosure, I should mention that in my college days I worked for
>Jordan for about three months (he was the full time sysadmin for whom
>I and three other students worked). I have had friendly contact with
>Jordan since then, and I believe that Jordan is basically a good guy.
broadsides I fired off. Since we're being candid here, let me say
that I did break one of my own 'cardinal rules' of posting, which was
posting something while in the full heat of frustration. I don't
necessarily feel that all the criticisms I leveled against Yggdrasil
were unwarranted, but I could certainly have posed them a little less
But since I have Adam's ear, I might ask that his next release of
documentation be more oriented towards step-by-step problem resolution
and less towards describing third party packages. Also, an index
would be really nice! Thanks.
Understood. That's why even a small acknowledgement from you thatQuote:> Also in the way of background, it is important to realize that
>the current release of LGX is a beta release. The whole point of a
>beta release is that adventurous users are supposed to find, report and,
>occasionally even fix bugs. If you're not so adventurous, wait for
you'd received my mail would have been appreciated (and probably would
have staved this whole thing off altogether). I agree that the format
of my message didn't make it all that obvious that it was a bug
report, but a quick read would have shown you that I was bringing up
the kind of 'I tried this and it broke' information you're soliciting
for the beta.
This has since been confirmed in followups. I could have sworn IQuote:> Since Jordan didn't identify what kind of SCSI controller, CDROM
>drive or hard disk drive he is using, I cannot respond specifically
>to this problem, which was not mentioned in Jordan's original letter.
mentioned the fact that I was using a 1742 in my message. Yes, I did.
Not so. Try configuring it for your particular configuration, first.Quote:> If you install the beta release, you definitely can build a
> new kernel without errors by typing:
> cd /usr/src/linux
I did the make dep and the make clean, too. No workie.
Ok. If you can point me at a newer source tree somewhere for ftp,Quote:> This is true. When people have called about this, I've
>offered to mail them a floppy with the 0.99.7A+ kernel source tree and
that doesn't entail wading through the MCC or SLS releases, I'd be
more than happy to take you up on this kind offer of assistance.
Or you can mail me a floppy. Your choice.
Well, it's not just a question of 'living in emacs' - try asking forQuote:> Emacs runs fine both in character mode and as a window under
>X. What is true is that somehow some of the byte-compiled lisp files
>on the CD were corrupted. If you use emacs simply as a text editor,
>you generally won't notice this, but you will if you live in emacs. I
info, as any novice user would do after reading the tutorial.
When can we expect to see the production release?