ianw1974

Well, it'll be fixed whenever the new kernel release comes out. Just have to sit and wait.....

My mistake, happening to me also.

I updated my system yesterday, saw the kernel update, and my skype is working :) I'm using the skype-static package though, not any rpm from their site.

You don't need to move the ordering in grub, but what you do need to do is look at the line that says: default 0 0 = first grub entry 1 = second grub entry 2 = third grub entry and so on. So, if you set it to the Vista option, then it can only be booting Vista. There's no other way it can boot Mandriva if the default is Vista. If Mandriva is still the default, then you have something wrong in your grub config. You can always post the grub config here from /boot/grub/menu.lst and we can take a look and help.

Edit the first post in full edit mode, and then edit the subject. However, I've done it for you :)

A quick google search shows up some info on how to do it: http://www.google.co.uk/#hl=en&source=hp&q=password+protect+grub&meta=&aq=f&aqi=g1g-m1&aql=&oq=&gs_rfai=&fp=af53484c05009a1c This was the first result: http://ubuntuforums.org/showthread.php?t=7353 Of course, the grub config itself in the very first post is not distro specific. So whilst this is on the Ubuntu forum, it will apply to pretty much all grub configs. Now for the edits. When you see your system booting, and you see the grub menu, you have a certain amount of time before it selects the default entry. Now, you can just press any key to then see the list of all the menu options, and choose the one you want to boot or even edit. Press the "E" key, and it will then show the grub config underneath this. You then go to the kernel line and press "E" again. At the end of the line, just add the word "single" without the quotes. Then, accept your edits, and it will return back and you press "B" to boot the system.

Yes, you can edit the line in grub and boot it one time without permanent change. The password option stops you making edits, and so cannot boot single user mode.

My peeve is that no matter what distro I use, something is always wrong somewhere. CentOS, I can use Xen, but I have old packages, and thus can't get anything nice and new without causing some problems. Mandriva, can install Xen, but then I can't get into my X server so my machine is unusable and no console access either just black screens. SUSE, Xen works and has nice new kernel, but then it won't shut down properly because of some ACPI problem, and so I must power off with 5 second press of power button. Ubuntu/Debian, no Xen kernel, so I can't use Xen without having to search around a find it easily (why is it not in the repos). Gentoo, Xen support and everything in the repo, but you can't even get it working because of some conflicts or another.

You can also password protect grub, so that you can't edit any entry and then boot single mode this way without requiring the password. Also make sure that the hard disk appears in boot order before the cdrom, then they can't boot from cd, and password protect the bios too. Then there's no way for them to get around it all.

If I remember correctly, if you boot single user mode, it will ask you for the maintenance (root) password, or CTRL-D to reboot the system. At least, this is what I think, I've not done it for a while to be 100% sure of it.

I didn't click any ads :)

I don't think so, SSH won't stop you getting into a console window, only via connection with SSH. The empty file is why.

Just like last time, badly designed yet again with you having to go to the last page before you can vote. Why don't they have it on the first page, that would make sense :huh: I voted Mandriva of course.

Have you tried running memtest? Before you do this, go into the BIOS and choose Load Optimised Defaults (if your BIOS has this), and then run memtest.

Can you tell me what the contents of your /etc/securetty file is? This is how mine looks: [ian@esprit ~]$ cat /etc/securetty tty0 tty1 tty2 tty3 tty4 tty5 tty6 vc/1 vc/2 vc/3 vc/4 vc/5 vc/6 maybe yours is empty and why cannot login. Just a guess, because I can't figure out why.

Well, they couldn't have Blue Coat, as this is already in use :D Maybe Blue Trousers, pants, scarf, gloves Or, Big Blue Linux (since IBM known as Big Blue).

Hi, I guess maybe you need this: [ian@esprit ~]$ urpmf --provides pecl php-pear:pear(peclcmd.php) php-pear:pear(peclcmd.php) eclipse-phpeclipse:eclipse-phpeclipse[== 1.2.1-0.2.0mdv2009.1] eclipse-phpeclipse:eclipse-phpeclipse(x86-64)[== 1.2.1-0.2.0mdv2009.1] probably the php-pear package for you to use this command.

Could be a bad burn or crappy CD/DVD media. What speed did you burn at? Maybe burn at a slower speed to make sure the DVD is OK.

What's your pam configuration? Changed this recently attempting to authentication through other sources than passwd? Incidently, you don't need to comment root out of /etc/passwd and /etc/shadow. Once you've booted the live cd, you just simply chroot into your Mandrake install and then use passwd in the normal way for resetting the root password.

Just make sure wherever you are creating the ISO has plenty of space. pauls example has your user home directory as the location for the output, but you can change this where necessary, or just sit in the directory where you want to create it and then do: dd if=/dev/cdrom of=isoimage.iso note the difference versus pauls. Also, you can create an ISO image with K3B as well if you prefer to do it the GUI method. I'm sure in Gnome also with Brasero.

Aye, agree and voted for paul's post.

You don't need multiple gateways. If all your internal machines, freenas etc are all on the same network 192.168.0.x, then you just have the gateway on your machine set to the internet as it was originally. The machine will know that all machines from subnet 192.168.0.x are via eth0 and so it will be able to connect. If it cannot, then you either have a firewall on the other machines, or a problem with that link. The only reason why you would need another route is if you had multiple ethernet segments on your internal LAN. For example, the machine has 192.168.0.x, and your other servers somewhere else have 192.168.10.x for example. Then you would not create a default route via eth0, because you can't really have two, but you would do this: route add -net 192.168.10.0/24 gw 192.168.0.x where the gateway 192.168.0.x is either a router on your LAN that your main server can see, or machine that is acting as a router between the two segments. There are some other complicated ways for routing, but you don't even need the one I've listed as an example here. So, remove the additional default route you have added, and leave it pointing to the internet, access will work on the internal LAN, and if not, then you have a problem elsewhere because all your LAN machines are in the same subnet, and so don't need a default route because they are all connected to the same switch.

I just installed this too, as I have Mandriva 2010 x86_64. I also have the same problem. So there's obviously something not right with the program.

That will work if perl-base is installed, however, if it's not installed and you're trying to find a package that you need, you can do this: urpmf --provides libperl.so then you can see what package is listed and then install it, thus: urpmi perl-base for example.

If you modprobe -r the new driver, and then modprobe the old one, does it work? If so, then how are you trying to blacklist the other one? Under /etc/modprobe.d by creating a new file? Or some other way?