pmpatrick

You can just su to root once you login as a regular user. Is there some reason you don't want to do this?

ianw1974: I meant that there is open source firmware available for the router that can greatly increase its functionality. Linksys routers use a stripped down version of linux on their routers and the code is available. The memory capacity of the wrt54g router is big eneough to allow for significant hacking and there is a whole community that has grown up around writing new firmware for this router. See this article for more details: http://www.wi-fiplanet.com/tutorials/article.php/3562391

You can configure a linksys in linux by opening a browser and typing in 192.168.1.1 in the address bar and hit "Enter". You will then be prompted for a username and password. On a new router, leave the username blank and use "admin" for the password. You will be at the router config page. Be sure to change your default password from admin. The linksys wrt54g routers are on sale now at a lot of places and you can get a pretty good deal. These have a linux OS at there core and most are hackable if you're into that. The new wrt54gx is linksys's new "pre 802.11n" version and is supposedly 8X faster than the G version when used with linksys's SRX adapters. These are pretty pricey. The standard wrt54g and the the other wireless G routers are on sale in anticipation of the new 802.11n routers which will come out later in 2006.

Linus and everyone else is entitled to influence, or attempt to influence, whomever they want when it comes to their choice fo DE, particularly when that "influence" is just a statement of personal opinion. I just don't see this as limiting choice in any way. His actions don't limit choice in any way other than people might listen to his opinion and agree with him. Also, Gowater wrote: The linux kernel is licensed under the GPL which would prohibit barring gnome from using the kernel or any part of the kernel; that type of restriction is just not allowed under the GPL. I suspect Reiver likes gnome and views Linus's criticisms as unfair or unfounded. If that's the case, point out how he's wrong instead of accusing him of limiting choice because that's a real stretch at best.

I don't get it. Linus expresses his preference for kde over gnome and that is anti-choice? Not really. It's his choice - he likes kde better than gnome. How does this limit anybody's choice?

Not necessarily. If you have both optical drives on the same ide channel, one bad drive can cause both drives to not work. A bad cable can also cause both drives to malfunction. You might want to check if the drives are comming up OK in your bios setup to see if this is a hardware problem. But the first step is to see if the drive(s) will work with another cd just to make sure it's not a scratched cd.

That's one step in the process. See AussieJohn's post here for a full discussion of the problem: https://mandrivausers.org/index.php?showtopic=29116&hl=kdmrc You have to get rid of the default kdm theme before your changes in Login Manager will work. The only way to do that is edit /etc/kde/kdm/kdmrc per the above post from AussieJohn.

The above is good advice. I would just add that the APIC stuff is the most likely culprit so I would do that first. Also, those graphical tools you are using generally edit two files, /etc/modprobe.conf(to load the driver for your nic on boot) and /etc/sysconfig/netwoork-scripts/ifcfg-eth0(set up network parameters such as dhcp, load on boot, etc etc). If the APIC stuff doesn't help, post those two files and we can take it from there.

The firewall, shorewall, is not installed by default IIRC. If you go into mcc>Security and click on the setup personal firewall icon, you will be prompted for the install cd(s) and shorewall will be installed. Either that or run: # urpmi shorewall

You might want to try a reinstall. Since gnome seems stable I suspect that your problems in kde are comming from "kat" , a kde desktop search engine that has caused problems for many. Kat is pretty buggy and installed by default on mdv 2006. After reinstall, just uninstall the kat package.

You really don't need antivirus on linux. There are many threads on this board fully discussing this issue. In a *nix environment, antivirus software is almost exclusively used in a network setting to scan for windows viruses to protect windows users on the network. All linux distros except redhat/fedorah can read ntfs partitions. Rh is very conservative on patent issues and refuses to enable ntfs read support in their kernel by default for purely legal, rather than technical reasons. Everyone else has it enabled. As noted above NTFS is read only in linux. Mandrake comes with a firewall called shorewall. You can graphically configure shorewall in the mandrake control center.

You can reinstall your windows bootloader and boot windows by following bvc's the procedure here: https://mandrivausers.org/index.php?showtopic=13744&hl=

Do you have libdvdcss installed? It's needed to playback any commercial dvd movie.

The quick hack answer is to put: chmod 666 /dev/dvb at the end of /etc/rc.d/rc.local. rc.local is an init script that runs at every boot with root privileges. In fact, rc.local is the last of many init scripts to run so generally, nothing else will mess with what you do there and all your device files should have been created when rc.local runs.

neddie: From the app menu go to System>Configuration>Monitoring>KwikDisk. That will put a little three cube icon on the right side of your kicker by the clock. Click on the icon and you will have a listing of all mounted and unmounted partitions in fstab by mount point. USB mounts are added as they come in(usually as /mnt/removablex) and by selecting them you can mount and unmount them even when no icon is put on your desktop which as you noted sometimes occurs. it's a very handy utility for removable media and if you have a lot of partitions that are not always set to mount at boot.

Did you run your ripper,Avidemux, as root? You will have to do that to access /dev/loop0 IIRC. I just tried mounting a dvd iso with loop and using dvdshrink on it, designating /dev/loop0 as the read device and it worked as root but gave an error message as an ordinary user. Edit: You may want to take a look at dvdshrink for your project. It will access /dev/loop0 as root and rip the dvd. In the process it creates a single mpeg of the entire dvd. Just be sure to save your working files. You could probably use that mpeg in avidemux.

When you mount the iso using loop, I believe you can access /dev/loop0 as a block device. Try pointing your dvd ripper to /dev/loop0 but I think you will have to be root to access it. Note, the first loop mount is through /dev/loop0, the second through/dev/loop1, etc.

I don't think you have to run down where lp loads from; you should be able to rmmod everything you need and modprobe in the desired order all in rclocal. However, if this is an order of loading problem, you have to find an order that works and your above effort did not. Try rmmod on both lp and ppa then modprobe ppa and then lp and see if that works. If not I would try rmmod on anything related to the parallel port and modprobing in different orders to see if I could get it working right. Once you know an order that works, you can reproduce it in rclocal.

Do you have anything else(printer?) on the parallel port? I notice you're loading the lp printer module from your lsmod output. From this howto: http://en.tldp.org/HOWTO/ZIP-Drive-4.html#ss4.1 It could be a problem with the order that ppa and lp are loading. You could test it by booting w/o a zip disk in the drive then running: # rmmod lp then modprobe ppa and related modules and see if it works. If it does, you can alter rc.local to rmmod lp and modprobe the modules in the right order.

I assume this is a usb zip drive; they are always assigned /dev/sda4 for a device file. Post your lsmod output her. You don't need ide-scsi for a usb zip drive but you do need usb-storage, among other things.

Following up on aioshin's suggestion, as long as you have ssh set up, you can also just type: fish://<insert ip of remote box> in the address bar of konqueror and do the smae thing. You will also be prompted for your user name and password. For the occasional simple file transfer, it's easier than setting up nsf.

Do you have any devices on the controller card when you try to boot up with the hard drive on hda? Most controller cards do not like optical drives to be connected to them. You are better off putting all opticals on the onboard ide ports and the hard drives on the controller card. The devices on the controller card should be listed starting with hde(primary, master), hdf(primary, slave), hdg(secondary, master) and hdh(secondary, slave). Also, you can get some anomolous results if you have nothing connected to the controller card. At least with the promise card I know that's true; mine won't boot with nothing connected to it.

This is really odd. I have a promise ultra 100 controller that I've used with linux for years with almost no problems(exception=mepis). Moving the drive from the controller card to the onboard card should have changed everything resulting in a unbootable system. Post your ide congfiruration at the time you did the linux install, i.e. what drives are where. If you initially installed without the controller card in and attempted to move your hard drive afterwards to the controller card, that won't work for linux without some significant changes to the config files.

Well, iso9660 has a max single file size limit of 4GB and that could be impacting mkisofs. A little googling revealed several people running into a 4GB single file size limit when trying to burn dvd data files.

Mdv 2006 is generally less stable than LE 2005 on my hardware. X issues using the nvidia driver re hangups, freezes and other erratic issues seems like the main problem to me. That kat thing seems to cause a lot of trouble as well and I just uninstalled it. Kat seems to be a solution in search of a problem. Do people really have that hard of a time organizing their files in folders? There are kernel issues as well that don't seem to be mandriva's fault. In particular, smp seems to have been radically reworked in the more recent kernels and some third party modules/patches will not work with the smp kernels any more. Ndiswrapper is one and the win4lin kernel patch is another that I'm aware of. I wouldn't be surprised if some other third party drivers didn't work with smp enabled. I have 2006 installed but I don't use it much, preferring LE 2005 instead. I'm waiting for the patches/updates to come on 2006 that will correct xorg and some of the other issues that people have mentioned.