Re: [arch-dev-public] Kernel framebuffer logo
Thursday 24 January 2008, Damir Perisa wrote:
we ARE having the arch logo in the kernel replacing the linux 2.0 pinguin (i made it). so i'm not getting the point in discussing if we want it or not. its just that somebody has to transform the new logo to the kernel-usable formats and rebuild the kernel. quite easy if you have the logo in good enough quality (or svg).
My apologies Damir, I wasn't aware that a final decision had been made yet. My method for making the kernel logo: 1. Extract a png from the svg sources 2. Resize and optimize the colour depth with GIMP/Fireworks 3. Use pngtopnm (after patching our netpbm package) 4. Use pnmtoplainpnm to finish it off I didn't realize there was so much passion behind the inclusion of a framebuffer logo; it's on my screen for all of about 20 seconds. I see a number of aesthetic problems with using such a logo, and they are as follows: 1. Limited use of colour makes it less than ideal for 'fancy graphics' 2. Users must customize their fb to be widescreen and like someone else pointed out, 1680x1050 and other widescreen resolutions are not supported even when customized. 3. The icon is fairly small and limiting in its scope Bootsplashes such as splashy, suffer from the same distortion problem unless fine-tuned. This means that out-of-the-box there's a potential that it will look 'fugly' or unprofessional at best. To counter this, I created a logo-less splashy theme that used a simple progress bar--it looks fine in any resolution. I agree that having the logo appear in the fb is a good idea--in theory at least--I only wish it could be done better. For example, it might be great to have the full logo (with text) appear at the top of the screen, but at the size we're dealing with that wouldn't be practical--it'd also look silly for us dual cpu/core owners to have two logos mirrored side by side. In my opinion, there are better ways to brand the distro; whether through the use of GDM/KDM/SLiM themes, wallpapers, or even desktop icons. I'm not going to lose any sleep about it either way...I just thought I'd share my take if it was still being decided--which apparently it isn't =) If anybody wants to have a go with the white logo, you can grab the ppm version here: http://dev.archlinux.org/~thayer/art/logo_linux_clut224.ppm
http://dev.archlinux.org/~thayer/art/logo_linux_clut224.ppm Hi could you provide the mono and vga16 logo too :) i start building now new .24 kernel with your 224 logo just to get the new logos in during the testing period, thanks.
greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
2008/1/25, Thayer Williams <thayerw@gmail.com>:
it'd also look silly for us dual cpu/core owners to have two logos mirrored side by side.
Yeah, that annoys me too. I wonder why it was done by kernel devs at all (probably they thought that 8 penguins on some server look cool :-D). -- Roman Kyrylych (Роман Кирилич)
Am Freitag, 25. Januar 2008 03:10:28 schrieb Thayer Williams:
If anybody wants to have a go with the white logo, you can grab the ppm version here:
Wouldn't it be better to have a logo with colors? Most users have a highcolor fb anyway. btw: afaik Gimp can export as ppm directly. -- archlinux.de
Am Freitag, 25. Januar 2008 03:10:28 schrieb Thayer Williams:
If anybody wants to have a go with the white logo, you can grab the ppm version here:
Wouldn't it be better to have a logo with colors? Most users have a highcolor fb anyway. btw: afaik Gimp can export as ppm directly. Hi I am fine with any logo, please just provide me 3 files as i need them.
Am Freitag, 25. Januar 2008 schrieb Pierre Schmitz: thanks greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
On Jan 25, 2008 12:53 AM PST, Tobias Powalowski <t.powa@gmx.de> wrote:
Hi I am fine with any logo, please just provide me 3 files as i need them. thanks greetings tpowa
All three versions of the kernel logo are available here: http://dev.archlinux.org/~thayer/art/kernel/archer-80x80-white/ I am not able to test the vga16 or monochrome versions, but it looks to me like we're not even building the kernel with support for these formats. For example, the kernel config in abs says: # CONFIG_FB_VGA16 is not set CONFIG_FB_VESA=y The CONFIG_FBCON_MFB flag (for monochrome support) appears to be missing entirely. Anyway, the new logos are 80x80, adhering to the default tux dimensions. Let me know if you guys have any questions or requests. Cheers
Friday 25 January 2008, Thayer Williams wrote: | On Jan 25, 2008 12:53 AM PST, Tobias Powalowski <t.powa@gmx.de> wrote: | > Hi | > I am fine with any logo, please just provide me 3 files as i | > need them. thanks | > greetings | > tpowa | | All three versions of the kernel logo are available here: | | http://dev.archlinux.org/~thayer/art/kernel/archer-80x80-white/ | | I am not able to test the vga16 or monochrome versions, but it | looks to me like we're not even building the kernel with support | for these formats. For example, the kernel config in abs says: | | # CONFIG_FB_VGA16 is not set | CONFIG_FB_VESA=y | | The CONFIG_FBCON_MFB flag (for monochrome support) appears to be | missing entirely. | | Anyway, the new logos are 80x80, adhering to the default tux | dimensions. | | Let me know if you guys have any questions or requests. | | Cheers hi Thayer, hi Tobias, hi all, i've made the 224 and 16 colour logo file for the kernel26 in colour (yours is white, i would say that if we have colours and the logo is in colour, we should use them - you agree?) and have tested both. they work, Tobias, you can find them here for replacement of the old logo in kernel26: http://dev.archlinux.org/~damir/temp/new_logo/ with the mono logo i have serious trouble: i cannot make the new logo look nice in 1-bit space, it has edges and slopes that are hard to show nicely in 120 x 120 px without aesthetic errors. but as the monochrome framebuffer is anyway not built, i would not see this as something urgent. @Tobias: feel free to replace the old logo by the new one have a nice weekend you all, Damir -- .·´¯`·.¸.·´¯`·.¸¸.·´¯`·.¸.·´¯`·.¸.·´¯`·.¸.·´¯`·.¸¸.·´ ° ° ° ° ° ° ><((((º> ° ° ° ° ° <º)))>< <º)))><
On Jan 25, 2008 4:49 PM, Damir Perisa <damir.perisa@solnet.ch> wrote:
Friday 25 January 2008, Thayer Williams wrote: | On Jan 25, 2008 12:53 AM PST, Tobias Powalowski <t.powa@gmx.de> wrote: | > Hi | > I am fine with any logo, please just provide me 3 files as i | > need them. thanks | > greetings | > tpowa | | All three versions of the kernel logo are available here: | | http://dev.archlinux.org/~thayer/art/kernel/archer-80x80-white/ | | I am not able to test the vga16 or monochrome versions, but it | looks to me like we're not even building the kernel with support | for these formats. For example, the kernel config in abs says: | | # CONFIG_FB_VGA16 is not set | CONFIG_FB_VESA=y | | The CONFIG_FBCON_MFB flag (for monochrome support) appears to be | missing entirely. | | Anyway, the new logos are 80x80, adhering to the default tux | dimensions. | | Let me know if you guys have any questions or requests. | | Cheers
hi Thayer, hi Tobias, hi all,
i've made the 224 and 16 colour logo file for the kernel26 in colour (yours is white, i would say that if we have colours and the logo is in colour, we should use them - you agree?) and have tested both. they work, Tobias, you can find them here for replacement of the old logo in kernel26:
http://dev.archlinux.org/~damir/temp/new_logo/
with the mono logo i have serious trouble: i cannot make the new logo look nice in 1-bit space, it has edges and slopes that are hard to show nicely in 120 x 120 px without aesthetic errors. but as the monochrome framebuffer is anyway not built, i would not see this as something urgent.
@Tobias: feel free to replace the old logo by the new one
Uh, hold the phone here. I thought we explicitly brought Thayer on as our resident graphics guy.
Saturday 26 January 2008, Aaron Griffin wrote: | Uh, hold the phone here. I thought we explicitly brought Thayer on | as our resident graphics guy. he might be the graphics guy, i just took his logo and pre-packed it for the kernel26 pkg. no manipulation on the logo itself and the technical process is only technical, not at all artistic. - D -- .·´¯`·.¸.·´¯`·.¸¸.·´¯`·.¸.·´¯`·.¸.·´¯`·.¸.·´¯`·.¸¸.·´ ° ° ° ° ° ° ><((((º> ° ° ° ° ° <º)))>< <º)))><
On Jan 25, 2008 3:24 PM PST, Damir Perisa <damir.perisa@solnet.ch> wrote:
Saturday 26 January 2008, Aaron Griffin wrote: | Uh, hold the phone here. I thought we explicitly brought Thayer on | as our resident graphics guy.
he might be the graphics guy, i just took his logo and pre-packed it for the kernel26 pkg. no manipulation on the logo itself and the technical process is only technical, not at all artistic.
Manipulation is required however to remove the artifacts and ensure minimal loss of detail. It is for this reason that I have remade the color framebuffer logo. Both versions may be downloaded here: http://dev.archlinux.org/~thayer/art/kernel/ As mentioned before, we are not compiling the kernel with support for the vga16 or monochrome versions, but I have included a white logo for these formats in case we do so at a later time. Cheers
hi Thayer, Friday 25 January 2008, Thayer Williams wrote: | My method for making the kernel logo: | 1. Extract a png from the svg sources | 2. Resize and optimize the colour depth with GIMP/Fireworks | 3. Use pngtopnm (after patching our netpbm package) | 4. Use pnmtoplainpnm to finish it off i use the following: 1 export png in inkscape 2 flatten image (gimp) 3 gaussian blur ~=1/100 of image width = pixel (120px final wide pic has 1.2 px gaussian blur - makes it easier to dither sharp edges later) 4 resize to 120x120 px 5 put in indexed colourspace, use FS dithering 6 export image to ppm respectively to pbm 7 build kernel to test it (i'm compiling right now) | I didn't realize there was so much passion behind the inclusion of | a framebuffer logo; it's on my screen for all of about 20 seconds. humans can find passion behind anything - even breathing and sex. | I see a number of aesthetic problems with using such a logo, and | they are as follows: | | 1. Limited use of colour makes it less than ideal for 'fancy | graphics' any good fancy graphics can be showed under limits if the technique used is optimal. after all, a logo is made in black/white, grey and outline versions only because of this reasons - to be able to simplify it and put it somewhere else as an element. ascii art may even be considered also fancy: MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMo MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM M "MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM M M MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM M M M MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM M M M ""MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM M M M M ""MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM M M M M M ""MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM"o"o M M M M "MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM "o"o M M "o"o MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM M "o"o M M M "o MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM o" M "o" M "o"o"o MMMMMMMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMoM M "o"o M M o"o "MMMMMMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMMMMMMM ""MMoo"o "o "o M "o" "MMMMMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMMMMM"o" M ""Mo"o" M "o M "o" "MMMMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMMMM"o "o "o" """o" M "o M o"o" MMMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMMM"o "o "o "o" M "o "o "o M o" "MMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMM"o "o "o "o "o "o "o "o "o M "o MMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMM"o "o "o "o "o "o "o "o "o " M o "MMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMM M M M o"o M M M "M M M Mo M o" MMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMM M "o M M M M M M M M M M M M M M "MMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMM M M M M M M M M M M M M M M M M M M "MMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMM" M M M M M M M M M M M M M M M M M M M M MMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMM M M M M M M M M MoMoMoM M M M M M M M M M MMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMM M M M M M M M M MoMMMMMMMMMoM M M M M M M M "MMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMM"o"o"o"o"o"o"o"o"oMMMMMMMMMMMMoM M M M M M M M "MMMMMMMMMMMMMMMM MMMMMMMMMMMMMMM M M M M M M M M MMMMMMMMMMMMMMMoM M M M M M M M M"MMMMMMMMMMMMMM MMMMMMMMMMMMMMo"o"o"o"o"o"o"o"o"MMMMMMMMMMMMMMMMoM M M M M M M M M"MMMMMMMMMMMMM MMMMMMMMMMMMMo M M M M M M M M MMMMMMMMMMMMMMMMMM M M M M M M M M M"MMMMMMMMMMMM MMMMMMMMMMMM M M M M M M M M M MMMMMMMMMMMMMMMMMM"o"o"o"o"o"o"oMoM M"MMMMMMMMMMM MMMMMMMMMM"o"o"o"o"o"o"o"o"o"o"MMMMMMMMMMMMMMMMMM"o"o"o"o"o"o"o""MMoMMMMMMMMMMMM MMMMMMMMMM"o"o"o"o"o"o"o"o"o"o"MMMMMMMMMMMMMMMMMMM M M M M M M "M M"MMMMMMMMMMMM MMMMMMMMM M M M M M M M M M M "MMMMMMMMMMMMMMMMMM M M M M M M M M M ""MMMMMMMMMM MMMMMMMM M M M M M M M M M MoMMMMMMMMMMMMMMMMMMMMMoMoM M M M M M M M"o"o"MMMMMMM MMMMMM"o"o"o"o"o"o"o"oMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMoM M M M M M M M MMMMMM MMMMM"o"o"o"o"o"oMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMoM M M M M M MMMMM MMMM M M M MoMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMoMo"o"o"o"MMMM MMM"o"o"oMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMoM M M MMM MMo"oMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMoM "MM MoMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMoM | 2. Users must customize their fb to be widescreen and | like someone else pointed out, 1680x1050 and other widescreen | resolutions are not supported even when customized. users must customize their computer to enable fb anyway. default arch is not using fb, so when they do so, they should do it right. | 3. The icon is fairly small and limiting in its scope the icon is just a symbol, not a poster presentation in 32bit colourspace. it stands for one cpu and is originally a penguin. we replace it for our logo because we like symbols to be arch-shaped. viva la archisation! viva el arch! - D -- .·´¯`·.¸.·´¯`·.¸¸.·´¯`·.¸.·´¯`·.¸.·´¯`·.¸.·´¯`·.¸¸.·´ ° ° ° ° ° ° ><((((º> ° ° ° ° ° <º)))>< <º)))><
On Fri, January 25, 2008 20:06, Damir Perisa wrote:
hi Thayer,
Friday 25 January 2008, Thayer Williams wrote: | My method for making the kernel logo: | Â 1. Extract a png from the svg sources | Â 2. Resize and optimize the colour depth with GIMP/Fireworks | Â 3. Use pngtopnm (after patching our netpbm package) | Â 4. Use pnmtoplainpnm to finish it off
i use the following:
1 export png in inkscape 2 flatten image (gimp) 3 gaussian blur ~=1/100 of image width = pixel (120px final wide pic has 1.2 px gaussian blur - makes it easier to dither sharp edges later) 4 resize to 120x120 px 5 put in indexed colourspace, use FS dithering 6 export image to ppm respectively to pbm 7 build kernel to test it (i'm compiling right now)
As said above, gimp exports fine: http://iphitus.loudas.com/arch/ck/misc/logo.png Did that a few years ago as a bit of a joke. Out of curiosity, I did one later that was big enough to only allow 1 line of text. Made a nice fake bootsplash, but of course wasnt remotely practical.
On 1/25/08, Damir Perisa <damir.perisa@solnet.ch> wrote:
hi Thayer,
Friday 25 January 2008, Thayer Williams wrote: | My method for making the kernel logo: | 1. Extract a png from the svg sources | 2. Resize and optimize the colour depth with GIMP/Fireworks | 3. Use pngtopnm (after patching our netpbm package) | 4. Use pnmtoplainpnm to finish it off
i use the following:
1 export png in inkscape 2 flatten image (gimp) 3 gaussian blur ~=1/100 of image width = pixel (120px final wide pic has 1.2 px gaussian blur - makes it easier to dither sharp edges later) 4 resize to 120x120 px 5 put in indexed colourspace, use FS dithering 6 export image to ppm respectively to pbm 7 build kernel to test it (i'm compiling right now)
| I didn't realize there was so much passion behind the inclusion of | a framebuffer logo; it's on my screen for all of about 20 seconds.
humans can find passion behind anything - even breathing and sex.
| I see a number of aesthetic problems with using such a logo, and | they are as follows: | | 1. Limited use of colour makes it less than ideal for 'fancy | graphics'
any good fancy graphics can be showed under limits if the technique used is optimal. after all, a logo is made in black/white, grey and outline versions only because of this reasons - to be able to simplify it and put it somewhere else as an element.
ascii art may even be considered also fancy:
MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMo MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM M "MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM M M MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM M M M MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM M M M ""MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM M M M M ""MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM M M M M M ""MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM"o"o M M M M "MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM "o"o M M "o"o MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM M "o"o M M M "o MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM o" M "o" M "o"o"o MMMMMMMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMoM M "o"o M M o"o "MMMMMMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMMMMMMM ""MMoo"o "o "o M "o" "MMMMMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMMMMM"o" M ""Mo"o" M "o M "o" "MMMMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMMMM"o "o "o" """o" M "o M o"o" MMMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMMM"o "o "o "o" M "o "o "o M o" "MMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMM"o "o "o "o "o "o "o "o "o M "o MMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMM"o "o "o "o "o "o "o "o "o " M o "MMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMM M M M o"o M M M "M M M Mo M o" MMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMM M "o M M M M M M M M M M M M M M "MMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMM M M M M M M M M M M M M M M M M M M "MMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMM" M M M M M M M M M M M M M M M M M M M M MMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMM M M M M M M M M MoMoMoM M M M M M M M M M MMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMM M M M M M M M M MoMMMMMMMMMoM M M M M M M M "MMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMM"o"o"o"o"o"o"o"o"oMMMMMMMMMMMMoM M M M M M M M "MMMMMMMMMMMMMMMM MMMMMMMMMMMMMMM M M M M M M M M MMMMMMMMMMMMMMMoM M M M M M M M M"MMMMMMMMMMMMMM MMMMMMMMMMMMMMo"o"o"o"o"o"o"o"o"MMMMMMMMMMMMMMMMoM M M M M M M M M"MMMMMMMMMMMMM MMMMMMMMMMMMMo M M M M M M M M MMMMMMMMMMMMMMMMMM M M M M M M M M M"MMMMMMMMMMMM MMMMMMMMMMMM M M M M M M M M M MMMMMMMMMMMMMMMMMM"o"o"o"o"o"o"oMoM M"MMMMMMMMMMM MMMMMMMMMM"o"o"o"o"o"o"o"o"o"o"MMMMMMMMMMMMMMMMMM"o"o"o"o"o"o"o""MMoMMMMMMMMMMMM MMMMMMMMMM"o"o"o"o"o"o"o"o"o"o"MMMMMMMMMMMMMMMMMMM M M M M M M "M M"MMMMMMMMMMMM MMMMMMMMM M M M M M M M M M M "MMMMMMMMMMMMMMMMMM M M M M M M M M M ""MMMMMMMMMM MMMMMMMM M M M M M M M M M MoMMMMMMMMMMMMMMMMMMMMMoMoM M M M M M M M"o"o"MMMMMMM MMMMMM"o"o"o"o"o"o"o"oMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMoM M M M M M M M MMMMMM MMMMM"o"o"o"o"o"oMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMoM M M M M M MMMMM MMMM M M M MoMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMoMo"o"o"o"MMMM MMM"o"o"oMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMoM M M MMM MMo"oMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMoM "MM MoMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMoM
| 2. Users must customize their fb to be widescreen and | like someone else pointed out, 1680x1050 and other widescreen | resolutions are not supported even when customized.
users must customize their computer to enable fb anyway. default arch is not using fb, so when they do so, they should do it right.
| 3. The icon is fairly small and limiting in its scope
the icon is just a symbol, not a poster presentation in 32bit colourspace. it stands for one cpu and is originally a penguin. we replace it for our logo because we like symbols to be arch-shaped.
viva la archisation! viva el arch!
lolwut? This thread, and this post in particular..... lets just say i had a bout of face-palm-itus this morning.
On Jan 24, 2008 8:10 PM, Thayer Williams <thayerw@gmail.com> wrote:
Thursday 24 January 2008, Damir Perisa wrote:
we ARE having the arch logo in the kernel replacing the linux 2.0 pinguin (i made it). so i'm not getting the point in discussing if we want it or not. its just that somebody has to transform the new logo to the kernel-usable formats and rebuild the kernel. quite easy if you have the logo in good enough quality (or svg).
My apologies Damir, I wasn't aware that a final decision had been made yet.
To be clear here, Damir overstepped his bounds. No final decision was made But, more to the point, after re-reading this, I would like to say this: Meh I just don't really care that much about the logo. I see if for all of 3 seconds about once a week, but 'wc -l' on this thread is larger than the discussion of the Mozilla /usr move. Priorities are awesome, aren't they? It's easier to remove the logo anyway, so lets just add it for now. If it looks assy, we can remove it later. It's not really a big deal.
Friday 25 January 2008, Aaron Griffin wrote: | On Jan 24, 2008 8:10 PM, Thayer Williams <thayerw@gmail.com> wrote: | > Thursday 24 January 2008, Damir Perisa wrote: | > > we ARE having the arch logo in the kernel replacing the linux | > > 2.0 pinguin (i made it). so i'm not getting the point in | > > discussing if we want it or not. its just that somebody has to | > > transform the new logo to the kernel-usable formats and | > > rebuild the kernel. quite easy if you have the logo in good | > > enough quality (or svg). | > | > My apologies Damir, I wasn't aware that a final decision had | > been made yet. | | To be clear here, Damir overstepped his bounds. No final decision | was made i did not decide anything. the logo was in the kernel26 pkg replacing the penguin since years. i was just stating that, as we have another, new official logo that we decided on, we should replace the old with the new anyway now. THEN we can discuss matters of removing things and adding things and changing anything. hostility goes up, motivation down have a nice evening - D -- .·´¯`·.¸.·´¯`·.¸¸.·´¯`·.¸.·´¯`·.¸.·´¯`·.¸.·´¯`·.¸¸.·´ ° ° ° ° ° ° ><((((º> ° ° ° ° ° <º)))>< <º)))><
On Jan 25, 2008 11:54 AM, Damir Perisa <damir.perisa@solnet.ch> wrote:
i did not decide anything. the logo was in the kernel26 pkg replacing the penguin since years. i was just stating that
Then I apologize. The wording seems more like... "we will do this" instead of "we are doing this" to me. I read it as more of a demand. Sorry for misinterpreting.
Friday 25 January 2008, Aaron Griffin wrote: | On Jan 25, 2008 11:54 AM, Damir Perisa <damir.perisa@solnet.ch> wrote: | > i did not decide anything. the logo was in the kernel26 pkg | > replacing the penguin since years. i was just stating that | | Then I apologize. The wording seems more like... "we will do this" | instead of "we are doing this" to me. I read it as more of a | demand. Sorry for misinterpreting. ah ok ... no problem, sorry for my english - will be more exact next time :) have a nice weekend, - D -- .·´¯`·.¸.·´¯`·.¸¸.·´¯`·.¸.·´¯`·.¸.·´¯`·.¸.·´¯`·.¸¸.·´ ° ° ° ° ° ° ><((((º> ° ° ° ° ° <º)))>< <º)))><
participants (8)
-
Aaron Griffin
-
Damir Perisa
-
eliott
-
James Rayner
-
Pierre Schmitz
-
Roman Kyrylych
-
Thayer Williams
-
Tobias Powalowski