Live data from Hacker News

Alan Cox announces Fuzix OS

plus.google.com

41–50 of 93 posts

Re: Alan Cox announces Fuzix OS

#43
post #25

Earlier quoted context omitted.

And, interestingly enough, a senior maintainer who quit because he got sick of Linus' behaviour.

That's not true at all, Alan Cox stated himself > I'm leaving the Linux world and Intel for a bit for family reasons. I'm aware that "family reasons" is usually management speak for "I think the boss is an asshole" but I'd like to assure everyone that while I frequently think Linus is an asshole (and therefore very good as kernel dictator) I am departing quite genuinely for family reasons and not because I've fallen…

This is a much more recent incident. The time he abruptly resigned as maintainer of the tty code was clearly a "fuck this, if you don't like the way I'm doing it, fix it yourself" resignation in direct response to some classic (if mild) Linus-in-your-face criticism.

Re: Alan Cox announces Fuzix OS

#44
post #28
post #25

Earlier quoted context omitted.

And, interestingly enough, a senior maintainer who quit because he got sick of Linus' behaviour.

https://lkml.org/lkml/2009/7/28/373

Yes, I'm familiar with the incident. I was reading LKML when it happened. It's a counterpoint to the usual "Linus's style doesn't cause any problems."

Re: Alan Cox announces Fuzix OS

#46
post #27

When I first read this, I thought this was meant to be a sarcastic statement on SystemD haters, but this is for real? I would assume this is all geared to scratching some kind of retro computing itch?

People used to learn programming by learning assembly language. Here's one example for the 68000: First page of contents: http://imgur.com/1XCLrsQ Example instruction description: http://imgur.com/MV6Le34 Hello world: http://imgur.com/5yKJlQ9 Off topic but if anyone is ever in Cheltenham UK (or is prepared to pay postage) I have some old books I want to get rid of. http://imgur.com/AWV9HLn

Hmmm, bet international postage would be a killer

Re: Alan Cox announces Fuzix OS

#48
post #35
post #19

Earlier quoted context omitted.

It could also be an exercise in open computing, hailing back to an era before legal attacks and ubiquitous surveillance. Being released in 1976, the Z80 architecture is well known and unencumbered by patents. It's also simple with fixed instruction timing, meaning it can be well tested, leaving few places for a back door to hide. The original hardware probably predates any surveillance programs (edit: and the silicon…

The original ARM was inspired by and designed on the 6502 (in the sense of they visited Western Digital and realized the designing a CPU was actually feasible for a small team, them emulated the design on a BBC Micro with 2nd processor) but IIRC Sophie Wilson stated they have no actual technology in common.

Very informative thanks. My dad still has a hefty collection of Micros (A, B, B+ and Master) and even has a second processor tucked away in his loft.

Re: Alan Cox announces Fuzix OS

#49
post #27

When I first read this, I thought this was meant to be a sarcastic statement on SystemD haters, but this is for real? I would assume this is all geared to scratching some kind of retro computing itch?

People used to learn programming by learning assembly language. Here's one example for the 68000: First page of contents: http://imgur.com/1XCLrsQ Example instruction description: http://imgur.com/MV6Le34 Hello world: http://imgur.com/5yKJlQ9 Off topic but if anyone is ever in Cheltenham UK (or is prepared to pay postage) I have some old books I want to get rid of. http://imgur.com/AWV9HLn

Those books look good. I've emailed you about a few of them.

Re: Alan Cox announces Fuzix OS

#50
post #44
post #28

Earlier quoted context omitted.

https://lkml.org/lkml/2009/7/28/373

Yes, I'm familiar with the incident. I was reading LKML when it happened. It's a counterpoint to the usual "Linus's style doesn't cause any problems."

It may be a counterpoint, but it is also one of the milder rants from Linux: No expletives; no colourful descriptions.

Yes, it's critical, but is the criticism unwarranted? He is questioning why one of the most senior maintainers is directly contradicting one of the most central "edicts" from Linus on the kernel development: Don't break user-land. In the message, Linus directly quotes Alan as arguing that breaking userland is ok.

Of course Alan was/is free to disagree, but he should have known very well that Linus would never let that fly. Not least because Linus had told him it wouldn't, and he kept pressing for it.

What was the alternative? From the outside, it looks like Alan repeatedly avoided doing what Linus told him needed doing. Linus could not have backed off without sacrificing the guarantee of not breaking userland.

Post reply on HN