jboy

OK, I think I see the problem. IF the SATA drive is now the boot drive, and IF WinXP is installed on the /dev/sda1 partition on this drive, then the "windows1" section (WinXP) of /etc/lilo.conf need to change as follows: Change this section in your /etc/lilo.conf from: other=/dev/sda1 label="windows1" table=/dev/sda map-drive=0x80 to=0x81 map-drive=0x81 to=0x80 to this instead: other=/dev/sda1 label="windows1" table=/dev/sda Now XP should boot ok. Those two map-drive statements need to be deleted and that should do the trick. Then, as the root user, execute the following command in a terminal: lilo -v That will write the updated lilo.conf info the the MBR on the SATA drive. Also note that instead of: label="windows1" you can use: label="XP" or label="WinXP" so that it's clear on the boot menu what that menu selecton really is. Just don't put any embedded spaces in the label.

Assumptions: 1. The lilo bootloader is now written to the SATA drive and it's the boot drive 2. XP is installed on the IDE drive and still has the XP bootloader installed on it 3. You want XP to show as a boot menu option on the SATA lilo menu 4. You have NO windows partitions on the SATA drive - dos, fat32(vfat), ntfs, etc (because your WinXP on the IDE HD needs to be the C: drive for this to work). 5. Your IDE HD is assumed to be /dev/hda I think the following will work (but no guarantees as I can't test it on my setup). Boot into linux. You will need to edit /etc/lilo.conf. As the root user, edit /etc/lilo.conf to include the following section: other=/dev/hda1 label="WinXP_IDE" table=/dev/hda boot-as=0x80 If the IDE HD is not /dev/hda, then adjust the above accordingly. Save /etc/lilo.conf, then execute the following command as the root user in a terminal: lilo -v This will write the updated lilo bootloader to the MBR on the SATA drive. Then when you reboot, you will have a menu option that says: WinXP_IDE

I know nothing about the DansGuardian package but I can give you two ways to find out what files it installs and where they are. As the root user in a terminal, issue either of the following commands: (1) using urmpq urpmq -ilr DansGuardian (2) using locate updatedb locate dansguardian Using the 1st command, I see that it's probably installed into /usr/sbin/dansguardian. Note that there are a lot of files in /etc/dansguardian. Note that the packagename is in Mixed Case but the installed files themselves are lowercase. After installation, you can also read it's manual: man dansguardian It may not necessarily show up in the menu structure. Some packages don't.

Menu -> System -> Configuraton -> Packaging -> Install Software You'll be prompted for the root password. The package name is kdenetwork-kppp. So you can use the Search feature for that or even just using kppp as the Search term. Then it will find the RPM package from your configured software media (repository) sources. Have you configured your Software Media Sources, so that you can check for and install updates? If not, the Software Media Manager from the Packaging menu will allow you to do that. Use the Easy-Urpmi tools at the top of this page to determine the ftp or http sources for a mandrake mirror of your choice.

Personally I like firefox, which is the default browser on Mandriva's LE2005. The RPM package name is mozilla-firefox. The answer is somewhat subjective, though. Others here have mentioned Opera, Epiphany (seen on gnome desktops), etc. Heck, there's even Links and Lynx which are browsers for the console - don't laugh, what if you can't start X but you still need to browse until you get X fixed!

If I understand this right, you currently boot Linux on the 20gb IDE, but want to install XP on the 200gb SATA, and then select which drive to boot from in the BIOS when you want to change from one boot drive to the other. OK, if that's right, I believe your scheme will work as you described. But first, I doubt that you need to disconnect the 20 gb drive to install XP. Just select the SATA as the boot drive in the BIOS, then boot from the XP Install CD (e.g., I can press F11 with my BIOS to tell it to boot from alternate device, such as CD) and then tell XP which partition you want to install it on. So now SATA is your boot drive and you're set to boot into XP. Then, as I understand it, you intend to change boot drives in the BIOS when you want to boot Linux on the 20gb IDE. After you get this set up, you will have other options if you get tired of changing the boot drive in the BIOS all the time. You could choose either drive to be the boot drive and set up lilo or grub on that drive to boot into XP or Linux (even multiple Linux installs) from the lilo or grub boot menu. If you want to go into that procedure after you get set up according to your plan, post a message at that time.

To get a sorted list of your package written to a file, execute the following command in a terminal session: rpm -qa | sort >afilename.txt Export firefox bookmarks: Booksmarks -> Manage Bookmarks -> Export You might poke around in the files and directories in your home directory that begin with a period. For example: ~/.kde/share/config/kickerrc ~/.kde/share/config/kmailrc

Personally, I like kontact. But either kontact or evolution should do nicely as a PIM.

Greetings John. This morning I tried setting up the scanner on my Epson multi-function USB printer and had similar problems to yours. I am on 2006 Beta 3 with all updates applied from the 2006 sources. I have not applied any updates from cooker. The scanner works perfectly in LE2005. In 2006 Beta 3, Harddrake reports that a scanner is available, properly detects it as an Epson, and lists a port for it. But after running the Config tool, xsane says that no scanner devices are available. So I don't get as far you've gotten. The only thing that I see in /var/log/messages that suggests a problem is a message that "DEVNAME IS NOT SET" during the mfp device detection. Scannerdrake does seems to detect the scanner ok because it creates a config file for it as shown below in /var/log/messages. Sep 6 08:43:35 scannerdrake[8276]: created file /etc/sane.d/epson.conf My USB flash drive is detected and I can mount it, so at least that is working ok. Those are the only USB devices I have. Perhaps the scanner issues have been corrected in the latest cooker packages, I don't know, but Beta 3 sure looks like it has problems in this area. The Beta 4 presumably will be out soon, so maybe it will be corrected in there. EDIT: forgot to mention that the USB printer itself works fine on my Beta 3 install, but not the scanner.

My debug messages are similar to yours up through: debug1: Offering public key: /local/home/yves/.ssh/id_rsa But then, instead of getting this following line: debug1: Authentications that can continue: publickey,password,keyboard-interactive here's my output: debug1: Offering public key: /home/jboy/.ssh/id_dsa debug2: we sent a publickey packet, wait for reply debug1: Server accepts key: pkalg ssh-dss blen 433 debug2: input_userauth_pk_ok: debug1: read PEM private key done: type DSA debug1: Authentication succeeded (publickey). debug1: channel 0: new [client-session] debug2: channel 0: send open debug1: Entering interactive session. debug2: callback start debug2: client_session2_setup: id 0 debug2: channel 0: request pty-req confirm 0 debug2: channel 0: request shell confirm 0 debug2: fd 3 setting TCP_NODELAY debug2: callback done debug2: channel 0: open confirm rwindow 0 rmax 32768 debug2: channel 0: rcvd adjust 131072 <... received login prompt ...> So I don't know what could be wrong. I'm also not using ssh-agent so no passphrase is involved. I used this reference to set up the ssh keys: http://www.linuxquestions.org/questions/an...ticle&artid=288 The procedures you used look functionally equivalent. I've used the same procedure on 4 different distros and can connect on all of them, so I'm stumped as to what could be the problem. If I think of anything else that might be helpful, I'll post a new message.

Greetings, Cariabes! I think you may have put the /usr/local/RealPlayer/realplay command in the wrong place. Right-click on that desktop icon, select Properties, then click the Application tab, and put that command in the input box that says Command.

I think you're talking about starting firefox with the Profile Manager. The instructions below are from: http://www.mozilla.org/support/firefox/profile#new On Linux or Mac, start Firefox with the the -profilemanager switch, e.g. ./firefox -profilemanager (this assumes that you're in the firefox directory). You should now see the Profile Manager window... I'm not in Mandriva Linux right now so I can't test this, but you may be able to just do this: Menu button -> Run Command... -> type this in the command input box: mozilla-firefox -profilemanager (and press Enter)

Yes, that's right. That's an RJ-45 connector. You would use CAT5, CAT5e, or CAT6 ethernet cable to connect it to the ADSL modem/router. The cable might even come with the modem but if not they're fairly cheap. See http://www.homenethelp.com/web/howto/HomeNet-ethernet.asp So, your setup would look like arctic described in https://mandrivausers.org/index.php?showtop...ndpost&p=203422 Computer/Ethernet card||----RJ45 ethernet cable----||modem/router||----RJ11 cable----||WallJack||-->Internet

Well, have you tried public key authentication? http://www.linuxquestions.org/questions/an...rticle&artid=79 This way you authenticate by use of a key rather than a password. I've used it and it works nicely, but just on my local network though. theYenYeti is now setting it up on his machine: https://mandrivausers.org/index.php?showtopic=27929

If UsePAM had previously been YES then it's quite possible that PasswordAuthentication was set to NO. That pairing goes together. If UsePAM is now NO, is PasswordAuthentication now set to YES? These settings go together. And of course do an sshd restart after editing.

No, it should be in /etc/ssh/sshd_config

There's a section in /etc/sshd_config about PAM authentication. Do you need to have UsePAM set to yes? # Set this to 'yes' to enable PAM authentication, account processing, # and session processing. If this is enabled, PAM authentication will # be allowed through the ChallengeResponseAuthentication mechanism. # Depending on your PAM configuration, this may bypass the setting of # PasswordAuthentication, PermitEmptyPasswords, and # "PermitRootLogin without-password". If you just want the PAM account and # session checks to run without PAM authentication, then enable this but set # ChallengeResponseAuthentication=no UsePAM no

This is a possiblity: Check sshd_config on the server and remove the line "PubkeyAuthentication no" if it exists then restart sshd. That tip is from http://www.linuxquestions.org/questions/answers/79

Could iptables be running and blocking access? Like I said, grasping at straws!

If you go to a port scanning site like ShieldsUp!, does it show tcp port 22 as open? Maybe temporarily you could try this in the /etc/hosts.allow file for the machine you're trying to ssh into. ALL:<ip_of_ssh_client_machine>:ALLOW or, corresponding, for your machine that others are trying to ssh into: ALL:<their_ip>:ALLOW

Yeah, that line from the netstat output looks fine. Could there be anything in these files causing the problem? /etc/ssh/denyusers /etc/ssh/ssh_config /etc/ssh/sshd_config

Hmmm, whenever I had that connection refused problem, it was because /etc/hosts.allow didn't allow sshd to accept the ip address of the client machine trying to ssh in. Just grasping at straws here (you've probably checked all this out): sshd running? sshd listening on port 22 (netstat -anpt) Can you have the admin of the machine you're trying to ssh into send you their /etc/hosts.allow to verify that it's configured correctly to allow your machine's access? Some other tcpwrapper that's running that needs to be configured? Does /var/log/messages on the machine you're trying to ssh into provide any clues? I dunno, I'm out of ideas.

You probably just need a line in /etc/hosts.allow like this: sshd:<ip address of client machine>:ALLOW You can use wildcards, netmasks, etc. See: man hosts.allow If you want, you could also do: sshd:ALL:ALLOW (undoubtedly a poor idea security-wise, I'm just showing some examples of the syntax) Also, if there's a firewall running on those machines, check if it's configured to open tcp port 22.

Very strange! Those steps should create a desktop icon that opens RealPlayer when you click on it. Works on my LE2005 install. Please double-check the command (presumably /usr/local/RealPlayer/realplay, from what you posted earlier) that you put in the icon Application tab. Are you getting any error messages?

Good job, FoulPlay! And please stick around and participate further. You may find that this is a great spot to enrich your knowledge and enjoyment of linux.