Slackware TTY - that stupid penguin

Printable View

11-15-2009
sean

Slackware TTY - that stupid penguin

I'm using a bare bones install of slackware for my mess-with-the-kernel machine. I didn't install X, or anything - so I'm just in the raw tty console. There's a penguin covering the top 5 or 6 lines - and bash obviously expects those lines to be there, because it covers the top of the output from the man pages, vi, etc... How do I get rid of that, anyone know? I could find anything on any other forums or documentation.

Besides - it's a really freaky looking penguin!

edit: Some ncurses programs seem to get rid of it. The menuconfig program for the kernel gets rid of it, but vi doesn't seem to. So I guess my question is how to stop it from showing up at boot...
11-15-2009
MK27

That is very strange and I guess even more annoying. If you can, take a photo of the screen, I desperately want to see this (honest).
I would assume that it is bash that is responsible. Check /etc/profile, /etc/bashrc, ~/.profile, ~/.bashrc. I also assume it is ascii art, so maybe pick a unique line and grep the init scripts if the bash configs don't uncover anything.

ps. if you don't know about "mc" and you are working on the console, you definitely want to.
11-15-2009
SlyMaelstrom

Real slack users don't need to see behind the penguin because they always knows what's going on with their computer without even looking at the output text. They can feel the aura of a kernel panic.
11-17-2009
sean

Quote:

Real slack users don't need to see behind the penguin because they always knows what's going on with their computer without even looking at the output text. They can feel the aura of a kernel panic.

That's funny - Because a real slack user doesn't get kernel panics. The kernel just obeys.

So it turns out that it's not really a penguin - it's Tuz the Linux Tasmanian Devil masquerading as a penguin. It was a temporary change in mascot for the 2.6.29 kernel.

13.0 login console with "muzzled penguin" - LinuxQuestions.org
Linus' blog: New logo
11-17-2009
Kennedy

To get rid of it, you'll need to recompile the kernel. There is an option under:

Device drivers
->Graphics Support
--> Bootup logo

Recompile and install and boom, no more Tuz. -- Though, you can switch between FB's and get the same result (that'd be press ALT-F2).

. . . and dude, don't be talking smack about Slackware or I'll come through this computer on you!!!

Hey, get that look off your face. . . Don't think I cannot do it.
11-17-2009
abachler

Real users don't need anything more than BIOS you spoon fed noobs.
11-17-2009
Mario F.

Yeah. Bet this is one step forward in saving the Tasmanian Devil.
Raised awareness and all that.

And yet...

Quote:

Originally Posted by blog comment

David said...

Hey Linus, any chance of photoshopping a plastic snout on the image of a starving African child for 2.6.30?

You give then your hand and they want to take the whole arm. Insensitive pricks.
11-17-2009
Kennedy

Just rebooted to try something else. . . Ever heard of "clear"?
11-17-2009
sean

"clear" isn't even installed on my machine. I thought it was a shell command (like 'cd'), but the terminal doesn't recognize it. I have the A (base), AP (common programs), D (development), L (shared libaries), and N (and networking) software series' installed. Am I missing something key? That's been enough software to write and compile code, and surf the web. I just assumed clear was only available in virtual terminals, and not in the tty.

edit:

Quote:

don't be talking smack about Slackware

On the contrary, now that I've tried it, I find myself disgusted with every other OS. I love how the slackware install exposes tons of details, but gives you an explanation of what it is, what your choices are and why you'd choose them, and then tells you what the 'safe' option is, just in case you don't care enough to read it all.
11-17-2009
Mario F.

Quote:

Originally Posted by Kennedy

. . . and dude, don't be talking smack about Slackware or I'll come through this computer on you!!!

I sure hope you are not one of the regulars on Linus blog :D

- I love you!
- You are my hero.
- Oh it's so cute!
- I love Tux!
- Tuz and Tux. That's too cool!

The veritable who's who in Idiot's Land.
11-17-2009
Kennedy

I don't blog. I don't myspace, facebook, etc. . . at the moment, all I do is Fable (the first). . . I'll probably Oblivion later, but I just had to rebuild my Windows partition and I'm reinstalling slowly. -- probably due to the fable discs being found first.
11-17-2009
Kennedy

Quote:

Originally Posted by Mario F.

I sure hope you are not one of the regulars on Linus blog :D

- I love you!
- You are my hero.
- Oh it's so cute!
- I love Tux!
- Tuz and Tux. That's too cool!

The veritable who's who in Idiot's Land.

Wait a minute here. . . . I'm really confused. Did we convert you? I mean reading Linus's blog is a long way away from this.
11-17-2009
Mario F.

Quote:

Originally Posted by Kennedy

Wait a minute here. . . . I'm really confused. Did we convert you? I mean reading Linus's blog is a long way away from this.

That's my attempt at sarcasm.
As for converting me, I don't think I'm the convertible type. Not about religion, not about politics, not about soccer, and definitely not about operating systems. All operating systems suck equally.

In any case, I do like this or that a little bit more. And I do tend to appreciate Linux more than Windows. But along with the Mac community, there seems to exist a tendency for a representative portion of the Linux community to adopt a bend over stance towards a a bunch of bytes put together to form an OS and the ones who made it.

One thing you can say about the Windows community: Most hate Windows.

I find that a smarter move.

...

As for the Tasmanian devil... Nice move and all, but someone should really inform Linus that really doesn't look like a Tasmanian Devil with a penguin snout. That looks like some kind of animal with a plastic snout. Of course, if this was Windows everybody would be complaining how Microsoft can't even draw a tasmanian devil with a plastic snout and how everybody at Redmond sucks for having ruined their terminal window. But being this Linus, "everybody" finds the Some Kind Of Animal with a Plastic Snout really cute and not a big deal.
11-17-2009
cyberfish

Most people I know who are proficient with both Windows and Linux (so have a real choice) use Linux. Or at least prefer Linux, but use Windows out of necessity.

I certainly find Linux a lot more comfortable to use, but am forced to use Windows on my laptop for now.

More on topic -
I never knew people still use Linux without X! (for a desktop machine, not server)

I find myself typing into a virtual terminal most of the time (more efficient), but still have X running for Firefox, IM client, OpenOffice, GIMP, and... not much else actually.

Do you do image editing on command line, too?
11-17-2009
sean

Quote:

Most people I know who are proficient with both Windows and Linux (so have a real choice) use Linux. Or at least prefer Linux, but use Windows out of necessity.

Yeah - I have to use Windows at work - and with Windows 7 I've been very satisfied, but I still think it's pretty sad that it takes a cutting edge quad-core server / workstation to make Windows feel as responsive as my bottom-of-the-range single core, 900MB RAM laptop running Ubuntu. And even then - I only use Ubuntu because of it's support for my laptops drivers - there's more stuff I'd prefer to be cutting out for my dream get-stuff-done machine.

Quote:

I never knew people still use Linux without X! (for a desktop machine, not server)

I forced myself to get used to working on the command-line and using ncurses programs so that when I ssh into my machine - that's almost no difference. The particular computer in question that started this thread, however, is purely for my hobbyist-kernel-hacking. So it frequently needs a reinstall - and I'd prefer not to be installing stuff I don't use. It makes the reinstall a lot faster, and makes debugging any problems MUCH simpler. Even so, on my laptop I spend most of my time in vim and the terminal - but I have GNOME there for when school dictates I submit homework as Word documents, for instance.

Quote:

Do you do image editing on command line, too?

No I use GIMP, and often.... I'm ashamed to say this... MS Paint.
11-17-2009
MK27

Quote:

Originally Posted by sean

The particular computer in question that started this thread, however, is purely for my hobbyist-kernel-hacking. So it frequently needs a reinstall -

Not that I do any kernel hacking, but why would this lead to a reinstall? You do know you can use grub to select a kernel at boot time (and so always have access to a working kernel), right?

When I use to do weird things, I just had a set of boot floppies (then later, a boot cd) with a console only repair set-up (vim, mc, rpm, chroot, etc.). If I did something to a system file, I backed it up first. Then if I couldn't boot, it was just a matter of using the rescue CD to mount the filesystem and swap the files back (or whatever). That'd also allow you to resolve any "mystery" there might be about how you wrecked the system -- which if you reinstall, all such evidence is gone.
11-17-2009
sean

Quote:

Not that I do any kernel hacking, but why would this lead to a reinstall?

In theory, it shouldn't. But I only recently started doing it, and while I was going through the process of recompiling and running a vanilla kernel from scratch - I frequently did something wrong because I didn't understand it all and accidentally screwed it up. I'd call "make install" not really understanding everything it would do - and it would overwrite my lilo config file and thus - the option to boot into a working kernel. Now that I'm more familiar with the process and Lilo, it almost never happens.
11-17-2009
MK27

Quote:

Originally Posted by sean

I'd call "make install" not really understanding everything it would do -

Yeah, quite often when I make a kernel I will just use "make bzImage" then copy the kernel image (it's in arch/x86/boot/bzImage) into the boot directory and manually add lines to grub config (grub is much nicer and easier than lilo IMO, but if you are already getting comfortable with lilo the it doesn't make much dif, you can manually edit lilo's config too). So everything remains the way I want. If you also need some modules, you can do the same with them using "make modules" (instead of "make modules-install"). "make install" doesn't have any further significance.

Oh and you have to use mkinitrd if your distro uses an intial ramdisk. But the whole affair doesn't take more than a couple of minutes.
11-17-2009
sean

Yeah that's what I started doing. My problem was that every half-decent tutorial did some things slightly differently and didn't explain any of their thinking - so I had to a ton of reading and playing before I got it.
11-17-2009
Kennedy

In the olden days I had this same issue with the lilo.conf file and make install. Then, after about the 20th time I screwed myself up (I could still get to it via any boot disk and chroot to the filesystem, then run lilo) I read the manual on lilo.conf and the documentation about make install in the Linux kernel -- WOW, what a difference. You only have to make changes to your lilo.conf file to keep you other stuff protected -- that'd be don't name your kernel images either /boot/vmlinuz or /boot/vmlinuz.old and you never get a problem.

I like /boot/vmlinuz.setup for the initial kernel image (the one that I put out there with the really big initrd.img too so that Justin Case can get back into my computer) and /boot/vmlinuz.orig for a ____WORKING____ kernel.