scoonma

In "emergency" situations like this, you can always open a terminal (text mode) by hitting these keys together: "Ctrl-Alt-F1". You can exchange F1 with any other from F2-F6. Do a normal user login, then type "su" to get root access on your machine if needed. You can switch back to graphical mode at any time by pressing "Ctrl-Alt-F7". Cycling back and forth between these modes is fully supported. Thus you can run additional sessions at the same time in parallel, only exception is the X Session (graphical mode), which is singular (well, who knows how to overcome this limitation may experience problems at other complexity levels... ;)).

Depending on your Windows version, you have to enter "fdisk /mbr" instead (Win 2000).

Just saw that with Windows XP, you can't write to MBR while the system is running. However, you can use "fixmbr" from recovery console (boot from XP CD).

Sorry, if insisting inadequately, but which sources package did you install? The rpm kernel-laptop-devel-2.6.22.9-1mdv should be suitable. You may also check wich location the symbolic link /usr/src/linux points to.

Yeah, yet the very number of postings should make every geek's bell ring to indicate some kind of "error" ... :)

If you click on "Show all articles by this user", there's only one hit. Nice finding, though!

Nice to hear it works! :-)

You could restrict connections to your server using /etc/hosts.deny on that machine. Description and syntax are here:

http://linux.about.com/od/commands/l/blcmdl5_hostsde.htm

Okay, got it working again. :-) The trick - at least here is - to explicitely pass the full user dir. This would probably be /home/joe at yours.

I also took a glance at the /etc/ssh/sshd_config file on my server. The line

Subsystem	   sftp	/usr/lib/ssh/sftp-server

will likely be importatant, too.

Good luck!

This is - errr - interesting: For testing purpose I unmounted the device pointing to the network resource on my GNOME desktop. The result: When trying to reenable the connection, the same type of error is displayed here as in your case. Aaargh!

Do you have gnomevfs-mount installed?

Edit: Seems to be gnome-vfs in Ubuntu...

Hm, I'm not sure wether GNOME/Mandriva 2008 and GNOME/Ubuntu are that different, but probably you're making it too complex. Within the mask presented here I'd enter:

Type of service: ssh

Server: 192.168.0.2

Port: (leave empty)

Folder: joe

User: joe

Connection name: My pretty server

I didn't even install sshfs-fuse and it works flawlessly...

it seems to be, but if you have a special method i can use to verify it, i'm all about it!

Typing "service smb status" as root will help.

A top amount of recent video cards is either built on Nvidia or Ati gfx chips, for which linux 3d acceleration is available (direct hardware support). In general, chip vendors make sure hardware acceleration can be used for a given OS.

I found this link here indicating it could be done, but it's quite old and doesn't seem to be that easy:

http://www.linuxquestions.org/questions/li...-savage-168951/

So, if you want a fast and easy solution and enjoy good gfx performance, you should go for a Ati or Nvidia based AGP card.

"Im not doing that terminal crap!!!" :D

You don't have to - and still can use ssh. I'm doing so for more than a year now. :-)

Don't know how it's done with KDE, but with GNOME very simple: Menu:Locations/Connect to server; select properties and off you go. Much easier than samba :)

Hi Arak,

the problem is *not* a small root partition or missing/insufficient root access, but your /home directory. As you did not allocate /home to a single partition on it's own (which is always a good idea), /home is now located in the normal root directory tree - which is denoted by /.

? 403: access forbidden...

Please follow this thread. In case you're still having trouble, we should have a look at your /etc/fstab file.

The name sl0 refers to a SLIP device, i.e. a networking device to use serial line protocol. SLIP has mostly been abandoned in favor of PPP (see also Linux Networking HOWTO).

Hm, did you enter "unmask" or "umask"? Only the latter would be correct... ;)

Hi deadlock,

welcome to Mandrivausers!

Your question is already answered quite well here: https://mandrivausers.org/index.php?showtopic=43701

The referred file is /etc/fstab, you can edit it as user root with your favourite text editor (kwrite, gedit, nano, joe, ...). So you just have to open a terminal window, enter the "su" command and provide your root password afterwards. Then do "gedit /etc/fstab" for example. A valid line would look like the following:

/dev/hda1 /mnt/win_c ntfs umask=0022,users,nls=utf8,rw 0 0

If you want to be able to do full editing, you'll have to replace "ntfs" by "ntfs-3g" above, and - also as root - install the according package by entering "urpmi ntfs-3g" in a terminal. Don't forget to reboot at last.

Good luck! :-)

The error indicates some rpm dependancy missing or pointing to a different (mostly newer) version. In your case it seems to be glibc, which is a vital component to the system in general. So it would be most wise to use a standard repository rpm to update nasm and wait until the corresponding glibc package is available there.

You'll also need a full 64 bit environment (since using correct glibc version) to use the 64 bit version of nasm (suppose cross compiling is not possible this way...).

Hm, this looks really bad. Sorry, I've no more ideas than to file a bug report to qa.mandriva.com and wait for a fix.

The --prefix option is used to determine an install path for compiled binaries after building them. So it's done correctly. BTW, I saw version 1.0.1 is recent for 2007.1 and also for 2008, ready to install with urpmi. Why not use that one?

A new beta driver for Nvidia gfx cards is available here. It fixes a problem with Compiz after vt-switching and contains support for some more card types (Quadro FX and NVS series).

Hi Brady,

welcome to Mandrivausers!

Regarding your script, I'd consider a better fitting solution to integrate within the boot process. Do you actually need your script to be run from rc.local? Probably you'll get a better result when you redesign it to run as a "normal" start script from /etc/init.d. As have noticed, most of these give user feedback during execution, and it seems to pose no problem to display more than a single line of text (as the shorewall service does here, for example).

HTH,

scoonma

Unfortunately still nothing. The options are inactive as they were before :sad:

Okay, last chance? The configure program said kde is installed to /usr, most normal user generated installations (i.e. without giving params to ./configure) go into /usr/local. So you could (as normal user!) do a

./configure --prefix=/usr

to insure KMyFirewall will go into the normal KDE tree, afterwards "make" (as normal user again!) and finally "make install" as root.

Good luck!