Linux-kernel mailing list archive 1998-25,: Re: 2.1.107: logo ???

# Re: 2.1.107: logo ???

Ragnar Hojland Espinosa (root@lightside.ddns.org)
Thu, 25 Jun 1998 20:51:01 +0200 (MET DST)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Alan Cox: "Re: (reiserfs) Re: LVM / Filesystems / High availability"
- Previous message: Martin Mares: "Re: Thread implementations..."
- In reply to: Adam Sulmicki: "Re: 2.1.107: logo ???"
- Next in thread: Tigran Aivazian: "Re: 2.1.107: logo ???"

> Thomas Quinot writes:
> ->Can someone explain what interesting magic makes an utterly
> ->useless feature such as an horrible penguin bitmap relevant
> ->in a code-frozen kernel ???
>
> As I see it is side effect of adding framebuffer to x86 which in turn
> is side effect of having framebuffers on other architectures already,
> so it kind of made sense to have uniform framebuffer across all
> architectures.

I really dont want to push up another logo thread again, but wouldnt it
actually make more sense to REMOVE the logo in other architectures? Does
the _kernel_ benefit in something? Does it really need to be there? Any
reason why it's not in user space?

.. Or are we trying to `catch up' with those 25M source code lines of NT?

____/| Ragnar Hojland (ragnar@lightside.ddns.org) Fingerprint 94C4B
\ o.O| 2F0D27DE025BE2302C
=(_)= "Thou shalt not follow the NULL pointer for 104B78C56 B72F0822
U chaos and madness await thee at its end." hkp://keys.pgp.com

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu

- Next message: Alan Cox: "Re: (reiserfs) Re: LVM / Filesystems / High availability"
- Previous message: Martin Mares: "Re: Thread implementations..."
- In reply to: Adam Sulmicki: "Re: 2.1.107: logo ???"
- Next in thread: Tigran Aivazian: "Re: 2.1.107: logo ???"