From: "Måns Rullgård" <mans@mansr.com>
To: "Ryan C. Gordon" <icculus@icculus.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: FatELF patches...
Date: Sun, 01 Nov 2009 21:15:07 +0000 [thread overview]
Message-ID: <yw1xhbte0wx0.fsf@unicorn.mansr.com> (raw)
In-Reply-To: <alpine.OSX.1.10.0911011540400.53392@caridad.local> (Ryan C. Gordon's message of "Sun, 1 Nov 2009 15:59:56 -0500 (EST)")
"Ryan C. Gordon" <icculus@icculus.org> writes:
>> Am I the only one who sees this as nothing bloat for its own sake?
>
> I posted a fairly large list of benefits here: http://icculus.org/fatelf/
I've read the list, and I can't find anything I agree with. Honestly.
> Some are more far-fetched than others, I will grant. Also, I suspect most
> people will find one benefit and ten things they don't care about, but
> that benefit is different for different people. I'm confident that the
> benefits far outweigh the size of the kernel patch.
It's not the size of the kernel patch I'm worried about. What worries
me is the disk space needed when *all* my executables and libraries
are suddenly 3, 4, or 5 times the size they need to be.
There is also the issue of speed to launch these things. It *has* to
be slower than executing a native file directly.
>> Did I miss a massive drop in intelligence of Linux users, causing them
>> to no longer be capable of picking the correct file themselves?
>
> Also known as "market saturation." :)
>
> (But really, there are benefits beyond helping dumb people, even if
> helping dumb people wasn't a worthwhile goal in itself.)
It's far too easy to use computers already. That's the reason for the
spam problem.
Besides, clueless users would be installing a distro, which could
easily download the correct packages automatically. In fact, that is
what they already do. The bootable installation media would still
need to be distributed separately, since the boot formats differ
vastly between architectures. It is not possible to create a CD/DVD
that is bootable on multiple system types (with a few exceptions).
>> As an embedded systems guy, I'm more concerned about precious flash
>> space going to waste than about some hypothetical convenience.
>
> I wouldn't imagine this is the target audience for FatELF. For embedded
> devices, just use the same ELF files you've always used.
Of course I will. The question is, will everybody else? I'm seeing
enough bloat in the embedded world as it is without handing out new
ways to make it even easier.
--
Måns Rullgård
mans@mansr.com
next prev parent reply other threads:[~2009-11-01 21:25 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-30 2:19 Ryan C. Gordon
2009-10-30 5:42 ` Rayson Ho
2009-10-30 14:54 ` Ryan C. Gordon
2009-11-01 19:20 ` David Hagood
2009-11-01 20:28 ` Måns Rullgård
2009-11-01 20:59 ` Ryan C. Gordon
2009-11-01 21:15 ` Måns Rullgård [this message]
2009-11-01 21:35 ` Ryan C. Gordon
2009-11-02 4:58 ` Valdis.Kletnieks
2009-11-02 15:14 ` Ryan C. Gordon
2009-11-03 14:54 ` Valdis.Kletnieks
2009-11-03 18:30 ` Matt Thrailkill
2009-11-01 22:08 ` Rayson Ho
2009-11-02 1:17 ` Ryan C. Gordon
2009-11-02 3:27 ` Rayson Ho
2009-11-02 0:01 ` Alan Cox
2009-11-02 2:21 ` Ryan C. Gordon
2009-11-02 6:17 ` Julien BLACHE
2009-11-02 18:18 ` Ryan C. Gordon
2009-11-02 18:59 ` Julien BLACHE
2009-11-02 19:08 ` Jesús Guerrero
2009-11-02 6:27 ` David Miller
2009-11-02 15:32 ` Ryan C. Gordon
2009-11-02 9:16 ` Alan Cox
2009-11-02 17:39 ` david
2009-11-02 17:44 ` Alan Cox
2009-11-02 19:56 ` Krzysztof Halasa
2009-11-02 20:11 ` david
2009-11-02 20:33 ` Krzysztof Halasa
2009-11-03 1:35 ` Mikael Pettersson
2009-11-02 15:40 ` Diego Calleja
2009-11-04 16:40 ` package managers [was: FatELF patches...] Mikulas Patocka
2009-11-04 16:54 ` Alan Cox
2009-11-04 17:25 ` Mikulas Patocka
2009-11-04 17:48 ` Martin Nybo Andersen
2009-11-04 18:46 ` Mikulas Patocka
2009-11-04 19:46 ` Alan Cox
2009-11-04 20:04 ` Mikulas Patocka
2009-11-04 20:27 ` david
2009-11-04 20:02 ` Valdis.Kletnieks
2009-11-04 20:08 ` Mikulas Patocka
2009-11-04 20:41 ` Valdis.Kletnieks
2009-11-04 21:11 ` Mikulas Patocka
2009-11-04 21:32 ` kevin granade
2009-11-04 22:05 ` Mikulas Patocka
2009-11-04 22:19 ` Marcin Letyns
2009-11-04 22:28 ` david
2009-11-04 22:43 ` Martin Nybo Andersen
2009-11-04 23:55 ` Mikulas Patocka
2009-11-05 2:24 ` Valdis.Kletnieks
2009-11-05 2:52 ` Mikulas Patocka
[not found] ` <f42384a10911050134t37a0a812hd85ff5541423dc9f@mail.gmail.com>
2009-11-05 9:35 ` Fwd: " Marcin Letyns
2009-11-10 11:40 ` Enrico Weigelt
2009-11-04 23:11 ` Valdis.Kletnieks
2009-11-05 0:05 ` Mikulas Patocka
2009-11-10 11:57 ` Enrico Weigelt
2009-11-04 17:36 ` Valdis.Kletnieks
2009-11-04 20:28 ` Ryan C. Gordon
2009-11-02 17:52 ` FatELF patches Ryan C. Gordon
2009-11-02 18:53 ` Alan Cox
2009-11-02 20:13 ` Ryan C. Gordon
2009-11-04 1:09 ` Ryan C. Gordon
2009-11-10 11:27 ` Enrico Weigelt
2009-11-10 12:40 ` Bernd Petrovitsch
2009-11-10 13:00 ` Enrico Weigelt
2009-11-10 13:19 ` Alan Cox
2009-11-02 16:11 ` Chris Adams
2009-11-01 20:40 ` Ryan C. Gordon
2009-11-10 10:04 ` Enrico Weigelt
-- strict thread matches above, loose matches on Subject: below --
2009-11-03 6:43 Eric Windisch
2009-11-03 11:21 ` Bernd Petrovitsch
2009-11-10 10:10 ` Enrico Weigelt
2009-11-10 12:15 ` Bernd Petrovitsch
2009-11-10 10:21 ` Enrico Weigelt
[not found] <dAPfP-5R6-1@gated-at.bofh.it>
[not found] ` <dBOhH-uY-9@gated-at.bofh.it>
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=yw1xhbte0wx0.fsf@unicorn.mansr.com \
--to=mans@mansr.com \
--cc=icculus@icculus.org \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®