mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "Daniel Cegiełka" <daniel.cegielka@gmail.com>
To: musl@lists.openwall.com
Subject: Re: filesystem layout
Date: Tue, 25 Sep 2012 15:51:03 +0200	[thread overview]
Message-ID: <CAPLrYETa_JAsggXV9f-+3jj3h5YmbSUo2t-0OjaXhaSCqSv=Ag@mail.gmail.com> (raw)
In-Reply-To: <5061B496.9020807@gentoo.org>

2012/9/25 Luca Barbato <lu_zero@gentoo.org>:
> On 09/25/2012 03:09 PM, Christian Neukirchen wrote:
>> Luca Barbato <lu_zero@gentoo.org> writes:
>>
>>> On 09/25/2012 01:26 PM, Kurt H Maier wrote:
>>>> On Tue, Sep 25, 2012 at 01:22:44PM +0200, Luca Barbato wrote:
>>>>>
>>>>> Static linking could be dangerous from a security/maintainance
>>>>> standpoint, but that is me looking at the specific scenarios in which
>>>>> Gentoo shines.
>>>>
>>>>
>>>> This is a common myth.  lazy or ineffective system management is a
>>>> danger regardless of the linking type.
>>>
>>> Spending lots of time unbundling dependencies from packages so they
>>> could use the up-to-date shared version might bring you to have a bias.
>>>
>>> Any system management that force you to reinstall all your packages
>>> because zlib had a bug doesn't seem efficient.
>>
>> Note that you need to *restart all programs using zlib* anyway.
>> So what's the difference between
>>
>> tar xzpf base.tar.gz
>> and
>> tar xzpf zlib.tar.gz
>
> I guess the whole thing is derailing. You assume that you have a daemon
> or some kind of permanent program, I'm considering all the programs,
> permanent and transient.
>
> Even in your scenario
>
> sys-libs/zlib-1.2.5.1-r2: 31 files, 16 non-files, 767.242 KB
>
> Updating zlib would take less than 1mb uncompressed.
>
> Updating a whole system few order of magnitude.

not the whole :)

scanelf -qyRF '%p %n' /bin/ | grep libz.so

This can be done automatically by the installer (package manager).

> Again, we are derailing the purpose of this mailing list.

yup.

Daniel


  reply	other threads:[~2012-09-25 13:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-25  9:58 Daniel Cegiełka
2012-09-25 10:53 ` Luca Barbato
2012-09-25 11:09   ` Daniel Cegiełka
2012-09-25 11:22     ` Luca Barbato
2012-09-25 11:26       ` Kurt H Maier
2012-09-25 11:35         ` Luca Barbato
2012-09-25 11:58           ` Daniel Cegiełka
2012-09-25 12:31             ` Luca Barbato
2012-09-25 12:50           ` Kurt H Maier
2012-09-25 13:08             ` Luca Barbato
2012-09-25 13:09           ` Christian Neukirchen
2012-09-25 13:41             ` Luca Barbato
2012-09-25 13:51               ` Daniel Cegiełka [this message]
2012-09-25 11:35     ` Szabolcs Nagy
2012-09-25 17:44   ` Rich Felker
2012-09-26  8:13     ` Daniel Bainton
2012-09-25 13:01 ` Christian Neukirchen
2012-09-25 13:42   ` Daniel Cegiełka
2012-09-25 17:40 ` Nathan McSween

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='CAPLrYETa_JAsggXV9f-+3jj3h5YmbSUo2t-0OjaXhaSCqSv=Ag@mail.gmail.com' \
    --to=daniel.cegielka@gmail.com \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).