The debian-private mailing list leak, part 1. Volunteers have complained about Blackmail. Lynchings. Character assassination. Defamation. Cyberbullying. Volunteers who gave many years of their lives are picked out at random for cruel social experiments. The former DPL's girlfriend Molly de Blanc is given volunteers to experiment on for her crazy talks. These volunteers never consented to be used like lab rats. We don't either. debian-private can no longer be a safe space for the cabal. Let these monsters have nowhere to hide. Volunteers are not disposable. We stand with the victims.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Let's focus on the right issues (was Re: FSF negociations)

Guy Maor:
 > G> My /bin + /usr/bin is 18 megs.  I'm guessing it would be about
 > G> double with symbols, or an increase of 18 megs.  My / + /usr
 > G> partitions are 174 megs used, so about a 10% increase in
 > G> installed size.

Rob Browning:
 > Isn't there a bunch of libraries in /usr/lib, or does that stuff
 > not have to be stripped?  Also doesn't having unstripped binaries
 > have implications for memory usage which is substantially more
 > expensive than disk?

First off, we really shouldn't be having this discussion right now.
It's a distraction from getting 1.1 released.

I've wasted a lot of time recently hand-holding people stuck with info
magic slackware releases.  I can't tell you how agonizing this is.
[Here's a start: linux 1.2.8 won't recognize the ide/atapi cdrom, gcc
2.6.0 won't recompile the kernel, the readme on 1.3.94 recommended gcc
2.5.8 or later but apparently this wouldn't do the networking support
right, options for importing fixes are "lots of floppies" and
"download over modem and compile".]

There are real problems to be solved, and while administration issues
are important, they should be gotten out of the way so that other real
problems issues can be dealt with.

			      * * * * *

However, since you've raised some technical issues, here's my take on
them:

There are libraries in /usr/lib, but these are roughly equivalent to
unstripped binaries if they are ELF.

Also, linux only brings in the part of the executable that it needs to
execute it, and symbols are stored in a different section, so memory
use shouldn't be a problem.

Also, when measuring the size of a binary on disk, it's better to
measure it in disk blocks (for typical e2fs file system) than it is in
bytes.  Disk blocks are the relevant unit of storage for management
purposes.

But none of this is particularly relevant for getting 1.1 out.

			      * * * * *

Now, what needs to be done for 1.1?

What would be nice to do for 1.1 that we shouldn't necessarily
guarantee will be done?

What are we explicitly deferring for after 1.1?

-- 
Raul