DebianThis forum is for the discussion of Debian Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am in the process of building a dedicated debian 3.1 box for ham radio AX.25 use only, I'll be running a host of apps just for that on this box, so I decided to build a custom kernel and strip out what I don't need, and compile in support directly for what I do need.
I downloaded the latest 126.96.36.199 sources from kernel.org, unpacked it, did a make menuconfig, selected my options, and then did a make-kpkg kernel-image. All was well with that, I installed the corresponding .deb package and was able to reboot the box no problem with the new kernel.
Everything appears to work as intended, but for some reason I can not log in locally, but I can via SSH. After init, I get a message complaining about ID's 1-6 starting too fast or something to that effect(I'm at work atm, so the exact error escapes me) and I think it is talking about these entries in /etc/inittab/:
# /sbin/getty invocations for the runlevels.
# The "id" field MUST be the same as the last
# characters of the device (after "tty").
# Note that on most Debian systems tty7 is used by the X Window System,
# so if you want to add more getty's go ahead but skip tty7 if you run X.
1:2345:respawn:/sbin/getty 38400 tty1
2:23:respawn:/sbin/getty 38400 tty2
3:23:respawn:/sbin/getty 38400 tty3
4:23:respawn:/sbin/getty 38400 tty4
5:23:respawn:/sbin/getty 38400 tty5
6:23:respawn:/sbin/getty 38400 tty6
I'm not entirely sure, but I believe this is what it's complaining about. I hit the enter key a couple of times on the keyboard, and it doesn't appear to respond, even though I have core input support compiled in.
Any ideas? I can post my new config if needed. Hopefully this is the only problem I have, everything else appears to be working (that I have tested so far anyhow)
By the way, is there some reason that you are using a 2.4 kernel and not a 2.6 kernel?
Well no reason in particular, other than I just don't need any of the newer features in the 2.6 kernel as opposed to the 2.4, all I'm really using this box for is for AX.25 stuff on ham radio, it's going to be a gateway of sorts and I stuck with 2.4 because that's what Debian came with
I'll have to look in my config, I thought tty support was in there, but I'll doublecheck and make sure that's the case......
Yes, I'm quite aware of that, but read my post again and maybe it will make sense to you, I think you misunderstood me. I have no use for a 2.6 kernel, debian by default installs with a 2.4 kernel so I didn't want to change because it was working just fine.
Back OT, I looked at my config and I don't see anywhere where this could be impacted. I see no reference of tty, but I do see a pty option and that is compiled in.
I thought about going to etch, but this box is just going to sit in the corner doing my packet/aprs chores so I didn't think it would be beneficial to upgrade to etch, besides aren't they still considering unstable? I thought sarge was the latest stable release?
I don't know about identifying myself on message boards, but that's up to you. I've always preferred to stay anonymous, except on a ham list. Funny, I guess.
"besides aren't they still considering unstable? I thought sarge was the latest stable release?"
Etch is as stable as it's going to get on Intel/AMD platforms. It's the really oddball stuff that's holding up the release. I've been using etch for a couple of months and I've only noticed one problem, but I'm strongly suspicious that the madwifi driver is at the root of it.
I haven't been too active lately - been playing with this damned linux. Gotta fix that, though. At least I turned on the KWM-2A last nite for a bit before going to bed, so that's a start, I guess. What are you going to use Linux for? I looked at the SSTV stuff a few months ago, but it seemed pretty primitive, and the SSTV/Digital stuff has gotten so pornish that I pretty much gave up on that, anyway.
Oh duh, I just reread and you mentioned packet and APRS.
and the SSTV/Digital stuff has gotten so pornish that I pretty much gave up on that, anyway.
Take a look at fldigi if you haven't already for digital stuff, it can't do SSTV, but you can xfer pictures using MFSK. fldigi is under heavy development right now, but it's extremely stable and does every digital mode under the sun, plus he just released a 64 bit binary, I believe that is the first ever 64 but ham radio software.
I run fldigi on my Ubuntu box and I absolutely love it. For SSTV, even though it's a windows app, I have had success running mmsstv under wine or hamscope which I believe does SSTV as well.
I think I've just given up on SSTV altogether. I was interested in the technology mostly. I'm not a shutterbug, so I don't have a lot of pics I've taken that I want to share. And really if you watch the SSTV nets, a lot of them are just sending girls in bikinis or less. I really don't want to support that in any way on ham radio.