Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
I don't know how many of you subscribe to the perl journal (you all should, it's a good magazine) but in the latest issue, there is an article on Perlix, a unix OS using only perl, such as GNU/Linux uses C. The state this OS was in had it currently sitting on top of a Linux kernel, and the writer asked for anyone willing to take the challenge to write a kernel in Perl.

I would like to start some sort of project to write this kernel in Perl. I know quite a bit of perl, but hardly enough to truly lead this project, let alone even try to write the kernel on my own. I have always wanted to learn low level programming (like device drivers) and this sounds like a fun thing in which i could partake. What i would need is for a monk that is very knowledgable to lead this (someone who knows how to actually write a kernel. I don't) I would help as much as I could, i think I could get the hang of it quite quickly. The kernel should be POSIX compliant of course, and will use perlfs. Any interested parties, email me with information on experience, knowledge, etc. Newbies are of course welcome (I being one myself) and I will try to organize some way that we can discuss working on this. I hope this idea can get organized enough to work. It would be alot of fun if it did.


In reply to Perlix Kernel project by Rydor

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others learning in the Monastery: (4)
As of 2024-04-13 10:37 GMT
Find Nodes?
    Voting Booth?

    No recent polls found