Scott Ellis <[EMAIL PROTECTED]> writes:
> Installing libc5 from hamm forces you to abandon your old libc5
> development system since it CONFLICTS (correctly) with libc5-dev. Not
> everyone is going that route yet.
True, so they can stay with bo for now.
> Okay there is a different utmp format. Lets try to list the packages from
> libc6 that care about utmp and would actually mangle it if running with
> the old libc5 utmp format:
>
> login
> telnetd (maybe, i think it hands off to login)
> sshd
> rlogind
> last (well, it will show the mangled data)
> who/w (ditto)
> ftpd
There's probably a few more, eg screen.
> The problem is that there are many people who don't have a problem with
> the minor issue of possible utmp corruption (which will only happen if you
> install something that is compiled with libc6 and does utmp stuff), but
> have a MAJOR PROBLEM being FORCED to ABANDON THEIR OLD DEVELOPMENT
> ENVIRONMENT.
Again, please desist from a flaming style of reply.
If they want to remain with a libc5 development environment, they have two
choices, stay with bo, or use altdev from hamm. You regard utmp corruption
as a minor issue, I would not, especially if I expected that staying with
mainly bo would give me a stable system. No one is forcing them to do
anything, however it is not unreasonable to expect them to upgrade some
packages, including replacing -dev with -altdev, if they want to have the
benefits of some newer packages.
Martin.
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
