From: Cruz Julian Bishop <cruzjbishop@gmail.com>
To: Rich Lawlman <richlawlman@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Various things Linux doesn't have/doesn't need
Date: Thu, 13 Sep 2012 10:30:06 +1000 [thread overview]
Message-ID: <5051290E.1000001@gmail.com> (raw)
In-Reply-To: <CAOqfy0W67ZZ59+jUjEG8dLc9BSyqnYnnP+TpB7kz6VJVnYchsA@mail.gmail.com>
On 13/09/12 10:18, Rich Lawlman wrote:
> It is by fine, unbiased analysis I propose the following:
>
> For one, drop all support for cpu archs except ARM. Dropping support
> will reduce development strain, and x86 has no foreseeable future
> anyways. This will allow Linux to accelerate its development pace on
> the one thing it currently has potential in; low-powered devices such
> as mobile/embedded, as Linux on the desk is a virtual wasteland.
>
> In addition, no one cares about the true state or existence of their
> files, and the assumption they do is why Linux scares new guys and the
> iPhone became popular. The kernel should instead make the filesystem
> "invisible" to the user; by default making only user files visible
> from a file manager and making only files related to a particular app
> available in that app. More secure, more simple, easier for the
> simpleton.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
I'm sorry, I have to ask this.
Do you guys get paid (or are part of a bet) when you make
suggestions like these, or do you just do it for, as a friend
tells me, "shits and giggles"?
OT: Or rename x86 to LEG, and watch all the others turn into
EYE and BodyFS, etc. ...Nope, still doesn't make sense,
but at least it doesn't sound too crazy. Just a bit whacko :)
next prev parent reply other threads:[~2012-09-13 0:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 0:18 Various things Linux doesn't have/doesn't need Rich Lawlman
2012-09-13 0:30 ` Cruz Julian Bishop [this message]
2012-09-13 2:50 ` Theodore Ts'o
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5051290E.1000001@gmail.com \
--to=cruzjbishop@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=richlawlman@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.