Not just Debian. Another two persons interested in porting mksh to anything possible and then some, as well as I, are trying to get an A/UX box running.

Also, whatâ(TM)s the leading GNU/Linux distribution on cris (ETRAX 100)? Debian doesnâ(TM)t support that⦠(also, I dab in klibc and dietlibc a bit, and the formerâ(TM)s got cris support code that warrants testing.)

Right, but we are doing this âoethe Debian wayâ, that is, running a native compilation and package generation in clean throw-away chroots. Debian package generation is not just compilation, itâ(TM)s a bunch of other stuff (dependency management, shared library management, etc.) and, personally *and* from my experience with the BSDs and FreeWRT, I am of the opinion that cross-compiling is only good for initially bootstrapping a port.

Besides, natively compiling forced us to fix lots of bugs in the kernel, eglibc and gcc, and backport other stuff to gcc, and to eat our own dogfood.

My goal with this was *not* just to have a system running Linux/m68k, but to have the process of auto-building packages working. (If you research, youâ(TM)ll find out that Iâ(TM)m a die-hard x86 and GW-BASIC fan, so I have no history with m68k other than eyeing them strangely for having the wrong endianness.) Also, I learned a lot of how Debian works in the process ;-)

The latter approach is the better one in the long term.

You are expected to learn any programming language to actually use
by yourself. The university gives you the basics, a broad overview,
and the tools you need to learn these.

It is also a common mis-conception that youâ(TM)ll be employed immediately
after finishing university. No, really not. University does not prepare
for the workplace. You need more real-life experience than that, which
is why universities (donâ(TM)t know about America, but over here they do)
require at least one internship be passed before the diploma can be
achieved. You will learn real-life work skills there, and (in case of
a programming job) get real-life programming experience, which is dif-
ferent from merely learning a programming language.

Trust me if I say that, with some shell languages such as mksh, you
can both _script_ and _program_ in shell, such huge is the difference.
Most never see the latter niveau.

Iâ(TM)d suggest you use the university time to _really_ get to know the
basics of as many languages as you can â" including functional and
other âoeweirdâ languages. Gwydion Dylan, Haskell, LISP, you name it.
Then, do your assignments in various languages for play; youâ(TM)ll find
out which ones you like/dislike and which ones are better/worse suited
for the task at hand. Bonus points (to you only) if you do some of the
assignments in two languages (probably using *different* algorithms â"
tailor the algorithm to the language used, not to the theory related
to the assignment, as academics want to make you).

Note I know both the academic world and that of âoecraftmanshipâ, Iâ(TM)ve
seen both sides.

I first wondered IF I want to actually read about it
then I said what the hey, lets look at it, know your
enemy and all that.

All I get is an IBM Notice:

Our apologies...
The page you requested cannot be displayed

    Suggested actions
    If you are looking for IBM Systems or Grid computing content on developerWorks, that content is no longer available. We suggest that you visit the following links for related content: IBM Systems, Systems, servers, and storage, or IBM Grid computing.
If you typed the address, make sure the spelling is correct.
Note: Most addresses are also case sensitive.
If you clicked on a link, there may be a problem with that link. You can use "Get assistance" below.
To navigate the IBM developerWorks Web site, start from IBM developerWorks.
Use the search box at the top of this page.
Or return to the previous page.

Get assistance
    To tell us about a broken link, go to the IBM developerWorks Feedback page.

404 Not Found