Re: modem for potato
On Sat, 1 Jan 2005 01:09:02 +0100, Gerard Robin [EMAIL PROTECTED] wrote: On Thu, Dec 30, 2004 at 08:44:19PM -0600, John Hasler wrote: Gérard writes: When we buy a modem we get the driver for this modem but unfortunetly it is for windows not for linux. External modems do not require drivers. My problem for the moment is to find a second-hand modem which works fine with a 486 and potato.(i.e. such that potato contains the suitable driver) External modems do not require drivers. If I was able to write a driver... External modems do not require drivers. They merely require appropriate configuration. I suspect that the modems you were unable to get to work had their internal registers loaded with wonky values so that they did not respond properly. The fix for this is to connect to the modem with a program such as minicom and reconfigure it. What about external USB modems? And PCMCIA modems. Some still are winmodems or require drivers. All I'm saying is that your statement is a bit too broad. --Jonathan
Re: 2 GB RAM support in woody
On Wed, 29 Dec 2004 07:49:07 -0800 (PST), saravanan ganapathy [EMAIL PROTECTED] wrote: I have done recompile using kernel-source-2.4.18 and after reboot I got the following error EXT3-fs: mounted filesystem with ordered data mode VFS: Mounted root (ext3 filesystem) readonly Freeing unused kernel memory: 288k freed kernel panic no init found , try passing init= option to kernel How to solve this problem? Please help me Sarav Well, obviously your kernel cannot find init. On my box it is in /sbin/init, and is likely the same for yours. What is happening is that your kernel is looking somewhere for init and not finding it, either as a result of an improperly mounted filesystem or lack of its existence. See what init other kernels find and try passing the path to one on a properly mounted root file system by passing a correct root= option (like root=/dev/hda1) and init option (like init=/sbin/init) and see where that might get you. I seem to remember that one could define where init is in the kernel configuration, or just pass it at boot time. --Jonathan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2 GB RAM support in woody
On Mon, 27 Dec 2004 23:06:39 -0800 (PST), saravanan ganapathy [EMAIL PROTECTED] wrote: Hai, I installed woody on my dual processor,2 GB RAM server. I have enabled smp support by installing kernel-image-2.4.18-smp. Now it shows dual processor. But the os detects my RAM as 900 MB only. How do I enable the os to detect actual RAM(2 GB)? Please help me Sarav --- Jonathan Lassoff [EMAIL PROTECTED] wrote: You need a kernel that supports large amounts of RAM. You could get the sources and compile it yourself which can take some time, but I personally found very easy to do. I would think that there is a .deb package of a kernel with this support as well, but I don't know that much about apt. Perhaps do: apt-cache search kernel and see if anything jumps out at you. I'd be happy to help you compile your own kernel. --Jonathan On Tue, 28 Dec 2004 01:58:46 -0800 (PST), saravanan ganapathy [EMAIL PROTECTED] wrote: I googled and couldn't find the .deb kernel package which supports highmem( its available in testing version only) So I think I need to use the latest 2.4.x kernel from kernel.org. If I am using debian kernel packages, then I can get security updates from debian. Is kernel.org provides security updates? If so , how to apply the updates without disturbing applications running on a production server? Please suggest me Sarav Sorry for the topposting above, that was my mistake. As to the security updates, those are provided by the Debian security team. They maintain software packages with the latest updates for security vulnerabilities. The kernel is the core piece of software on your system that handles all the system calls and a whole slew of other core stuff. Vulnerabilities for the Linux kernel are not as common as vulnerabilities for common pieces of Linux software, so you could roll your own kernel and still have all the great security updates from the Debian security team. As to getting your own kernel going, there are two big and easy ways to get the sources. One, you can get the sources from backports.org. This would consist of adding some lines to your /etc/apt/sources.list file to get a kernel-source package. Two, you can get the kernel source from kernel.org. I personally would go with the second as it is quicker to grab and use. As of this writing, the latest 2.4 kernel is 2.4.28, and can be had over HTTP at http://kernel.org/pub/linux/kernel/v2.4/linux-2.4.28.tar.bz2 Grab this and move it to /usr/src You will likely have to become root to do this. Then decompress the tarball in /usr/src. This should make /usr/src/linux-2.4.28. Then you should cd into this directory and proceed to configure your new kernel and compile it. There is ample documentation in the linux-2.4.28 directory under Documentation, and I don't really feel like rewriting some already great docs. There are plenty more online too if you poke around on google or something. Direct any questions here, and I'll do my best to help you out. Hope this works out for you. --Jonathan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: OT: the pain with crosslink cables
On Tue, 28 Dec 2004 19:13:52 +0100, martin f krafft [EMAIL PROTECTED] wrote: I have one of those D-Link USB network interfaces, which are wonderful. Plug it in, get a regular 10/100 Ethernet interface, supported by Linux and working just fine. However, right now I am in dire need to establish a link between two machines, and my beloved ethernet cable will, of course, not do the trick, and a hub is nowhere to be found. I used to have a crosslink cable too, but those things tend to grow legs very quickly, and all of the ones I've ever had always did. What I really want is a USB-attachable network interface that has a crosslink/normal switch, or automatically tries one after the other to find a link. Do you know if such a device exists? -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer, admin, user, and author `. `'` `- Debian - when you have better things to do than fixing a system I would just use a cross-over cable. What do you mean by grows legs? Crossovers work just fine for me all of the time. --Jonathan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Fwd: its a matter of ssh and its not working for me
On Tue, 28 Dec 2004 16:56:01 -0700, Kent Andersen [EMAIL PROTECTED] wrote: well sorta not working I have some automatic login stuff I want to do with rsync,etc.. one machine works the others (recent installs) do not heres the rundown I have the public keys placed in remote machines under the correct user account .ssh/ etc.. both sshd_conf files are identical (machines A,B). machine A will automatically ssh login (without password) and rysync doesnt ask for password either machine B requires me to login with password before the new command will work (ie rsync) but ssh session will not require password. I have been trying to figure out why this is happening if anyone can clue me in I would be forever in debt. I have been working on trying to solve this mystery for about a week now. ARRGH! Kent Have you compared the output of verbosity logs? I would try something like: ssh -v -l username hostname and compare the output between the two hosts. Also are both machines running the same version of the sshd server? --Jonathan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to access external USB hard drive?
On Tue, 28 Dec 2004 08:34:36 -0600, Matt Zagrabelny [EMAIL PROTECTED] wrote: Do I need hotplug installed for the kernel to see the drive? It's currently not installed. no, you shouldnt (although it is a good package), instead try a different kernel. (either compile your own from kernel.org or up/downgrade to either 2.6.7 or 2.6.9) -matt zagrabelny I'm not sure what was said above on this thread, as the archives for this are a mess, but I'm guessing you won't need to compile a whole new kernel. If you are using a stock kernel from debian, you can get the source and just compile USB Support (if you do not have it) and the usb-storage.ko (or .o if your on 2.4) module is all you should need to support most usb storage drives on the market. Hope you don't have to compile a new kernel, Jonathan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem with network after new kernel tryout
On Tue, 28 Dec 2004 13:46:07 +0200 (EET), [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: But when I booted It didn't work: When I booted I got graphical login screen where I entered username and password, but right after that I got error saying something like: Xsession lasted less than 10 seconds, ~/xsession.log has been writen. :)Marko I am curious to know what happened with X here. It would be interesting to find out what is in the xsession.log file. As to the broken interface, I would try it in another machine if you have one available to you. Or you might try something like Knoppix or some other bootable distro to see if those work. The broken-ness of your OS's should probably not be used to see if you have broken your card as you have just made some new kernels, and Windows XP is naturally just broken. Failing that I might try another card. --Jonathan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2 GB RAM support in woody
You need a kernel that supports large amounts of RAM. You could get the sources and compile it yourself which can take some time, but I personally found very easy to do. I would think that there is a .deb package of a kernel with this support as well, but I don't know that much about apt. Perhaps do: apt-cache search kernel and see if anything jumps out at you. I'd be happy to help you compile your own kernel. --Jonathan On Mon, 27 Dec 2004 23:06:39 -0800 (PST), saravanan ganapathy [EMAIL PROTECTED] wrote: Hai, I installed woody on my dual processor,2 GB RAM server. I have enabled smp support by installing kernel-image-2.4.18-smp. Now it shows dual processor. But the os detects my RAM as 900 MB only. How do I enable the os to detect actual RAM(2 GB)? Please help me Sarav __ Do you Yahoo!? Yahoo! Mail - 250MB free storage. Do more. Manage less. http://info.mail.yahoo.com/mail_250 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
EXT3: Strange Disappearance
I have a box that has a vanilla Debian Woody install. I have two regular user
accounts, both in /home. One called jonathan and the other steven. Myself,
Jonathan was scp'ing some files to my workstation and noticed that my UID on the
Debian box was 1000. I thought this was odd, so I ssh'd into the Debian machine
and edited my /etc/passwd to reflect my UID on my workstation (500). Well, I
should have checked for steven's UID, which I am guessing was also 500. Oops.
/etc/passwd can make a nice pistol when attempting to coordinate UID's across
multiple machines. For some reason steven's home dir is plain gone. Very, very
odd. Any ideas as to what might have happened? Maybe how I could get those files
back?
I checked /var/log/{syslog,messages} but found nothing.
I searched in these for passwd and steven. Then, I just trolled through them
and found zilch. I'm stumped. I'm guessing that something in the init scripts
checks /etc/passwd for stuff like users that don't exist or something, but
deleteing home dirs, not ok in my book.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: unsubscribe
unsubscribe I think you want to send this to [EMAIL PROTECTED] Please don't leave! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Booting Caper.
I'm in a bit of a booting pickle. I've got two drives in a given box. Their geometry looks like: [hda] 70 Gb windoze xp partition 9.7 Gb Redhat 9 / (ext3) 0.3 Gb Redhat 9 swap [hdb] 9.7 Gb Debian Woody / (ext2) 0.3 Gb Debian Woody swap I want to boot the debian woody install on the second drive, and have been with a boot floppy for a few months now. Well I got the hankering to try this new 2.6.0 kernel, so I compiled it and figured that I could just replace the kernel image and initrd image on the disk. Well I was wrong. In theory this should have worked, but something went horribly wrong, and syslinux tells me Boot Failed: Insert another disk and press any key to continue while loading the kernel. So I got the idea that I'd just boot into my redhat install and do mkbootdisk with the kernel from the woody partition. Well the original disk reprted all kinds of bad sectors while writing it, so I found a floppy that works, and it still fails to boot. So then I thought I might have my first go at using GRUB on the command line. So I boot into my Redhat 9 install and switch to single user mode (init 1) and run grub. I set the root partition and specify my kernel with all the right options. Then I specify my initrd image and then run boot and the thing just just quits, it doesn't boot or do anything. It just sits there. Well, now I haven't a clue what to do as I can't boot my debian install and now I'm sad. Any ideas to get grub working or anything to boot it? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Booting Caper.
In theory, this sounds great, but it doesn't work out so well for me. When I install GRUB to /dev/hda it posts, clears the screen, puts something like GRUB and just sits there. I also still need to boot Windoze occasionally to play games. What I'm wondering is why when I do the boot command in grub, it justs dies and drops me to a command line. I'm going to try and boot off a CDRW with ISOLINUX and my kernel and initrd.img. Wish me luck, I'll be back in a few... On Mon, Dec 29, 2003 at 08:21:59PM -0800, Jonathan Lassoff wrote: [hda] 70 Gb windoze xp partition 9.7 Gb Redhat 9 / (ext3) 0.3 Gb Redhat 9 swap [hdb] 9.7 Gb Debian Woody / (ext2) 0.3 Gb Debian Woody swap Well, now I haven't a clue what to do as I can't boot my debian install and now I'm sad. Any ideas to get grub working or anything to boot it? Ok well first you need to get a working menu.lst file in grub. Mine looks like: title Debian bf2.4 root(hd0,0) kernel /boot/vmlinuz-2.4.18-bf2.4 root=/dev/hda1 hdc=ide-scsi title Debian 2.6.0 root(hd0,0) kernel /boot/vmlinuz-2.6.0 root=/dev/hda1 hdc=ide-scsi title Low-level Format root(hd0,3) chainload +1 But yours would look like: title Windows root(hd0,0) chainloader +1 title Redhat root(hd0,1) kernel /boot/name-of-redhat-kernel root=/dev/hda2 title Debian root(hd1,0) kernel /boot/name-of-debian-kernel root=/dev/hdb1 Then assuming grub is installed on redhat you would run grub in redhat and enter the following commands: root (hd0,1) This tells grub that /boot/grub/ is on /dev/hda2 setup (hd0) This tells grub to install itself on /dev/hda Bijan -- Bijan Soleymani [EMAIL PROTECTED] http://www.crasseux.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Booting Caper.
Thanks a bunch you guys. You cleared up a lot of issues and misconceptions I had. I thought that you could boot another kernel while another was running, although in hindsight, I don't know why I thought that as the current running kernel would alredy be in high memory and such... Well, I found a good floppy and installed a syslinux image by hand and copied the proper kernel and initrd image over and it boots now. But I still have one problem. I am trying to boot the new stable 2.6.0 kernel and it say s some error and that I need to pass an init= option to the kernel. I've never gotten this before in 2.4 kernels. What is the init option and how should I use it? Jonathan Lassoff [EMAIL PROTECTED] writes: I want to boot the debian woody install on the second drive, and have been with a boot floppy for a few months now. [...] Well the original disk reprted all kinds of bad sectors while writing it, so I found a floppy that works, and it still fails to boot. How are you making the boot floppy? I'd probably try to do this sort of thing by using a real bootloader... So then I thought I might have my first go at using GRUB on the command line. So I boot into my Redhat 9 install and switch to single user mode (init 1) and run grub. I set the root partition and specify my kernel with all the right options. Then I specify my initrd image and then run boot and the thing just just quits, it doesn't boot or do anything. Well, yeah, you've already booted the machine, the command-line grub isn't going to magically reboot your running kernel. You need to install grub on to some media (your hard disk or your known-good floppy) and boot from that, then this incantation would work. Read the GRUB manual. (I find a GRUB floppy to be a great rescue tool, BTW: if you have some clue of what's on the machine, you can use it to boot even if your MBR is broken, you can boot from partitions that the local boot loader doesn't know about, and if your system is really hosed, you can connect a null-modem cable to another machine, tell GRUB to use a serial console, and start catting files from the GRUB prompt. Not that I've had flaky hardware that requires this or anything. :-) so my recommendation would be to follow the procedure in the GRUB manual, and make a GRUB floppy, and either use that to boot your Debian partition or use it to install GRUB into your MBR. -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
