pmpatrick

It's probably the kernel in mdv2007 vs mdv2007.1. That board uses the jmicron sata/pata controller which was a real problem for earlier kernels along the lines you are experiencing, i.e. pata opticals and sata hard drives not detected after the kernel loads. It's very difficult to figure out what's in a mandriva kernel since they are heavily patched with backports but I would guess the newer mdv2007.1 kernel has been patched to deal with the jmicron controller whereas the older mdv2007 kernel was not.

In my experience, it happens more on ext2 or ext3 than on reiserfs. ext* does not like hard shutdowns but you usually can recover because there are really good repair utilities for ext*. I suspect you either didn't use the fsck utilities properly or you're just unlucky. Reiserfs is more resilient to hard shutdowns than ext* but if reiserfs gets corrupted, you can forget about getting your data back as the filesystem repair utilities aren't nearly as good as ext*. The worst of the lot for hard shutdowns is xfs. If there is any disk I/O to an xfs partition when the power goes off, the filesystem is generally, irreparably damaged. I've never had a reiserfs go bad after a hard shutdown. I've had several ext3 partitions go bad after a hard shutdown but they were able to be repaired in every case but one. I only use xfs for backup partitions because this filesystem is very good at handling large files like archive or disk image files. I never leave an xfs mounted when not backing up so I have no personal experience on how xfs handles hard shutdowns but xfs's problems with hard shutdowns are well known and widely reported. If you don't want to get a UPS and your area is prone to power outages, I would recommend making your / paritition reiserfs. I also second tyme's suggestion about checking your hard drive out with the manufacturer's test utilities.

That generally means that the bootloader can't find or mount the root filesystem. This would be consistent with the above problem. That sounds really bad. I suspect that the root filesystem is trashed. Do you know what caused the original problem, eg hard shutdowns? This is normal. the first extended/logical drive is hda5; hda1-4 are reserved for primary partitions. Even if you don't have a second or third primary partition, the first logical partition is hda5. Is your home partition on hda6 OK, i,e, can you mount it and read the files normally? If so the easiest solution at this point may be to reinstall. If you do that, designate hda6 as your home partition and direct the install program to not format your home partition on hda6. That way all your personal data and settings on your home partition will be saved. Just to be sure, you may want to back up hda6 to some external media before you reinstall.

Zdnet is a business and they get a significant portion of their revenue from MS adds - enough said.

The successor to kanotix is a distro called sidux. It's based on debian sid and has excellent hardware detection: http://sidux.com/index.html If you liked kanotix you will like sidux. Some of the main devs from kanotix broke away to form sidux and they put out regular updates.

Use i810. I tried adamw's way with mine and it didn't work but try that first as it's a lot easier. If it doesn't work, try generating a mode line and see if that helps. Open a console and run: $ gtf 1024 768 60 You should get some output that looks something like this: # 1024x768 @ 60.00 Hz (GTF) hsync: 47.70 kHz; pclk: 64.11 MHz Modeline "1024x768_60.00" 64.11 1024 1080 1184 1344 768 769 772 795 -HSync +Vsync Cut and paste that output into your "Monitor" section of xorg.conf like so: Section "Monitor" Identifier "monitor1" VendorName "Plug'n Play" ModelName "InFocus X1a-A" HorizSync 31.5-80 VertRefresh 50-85 # 1024x768 @ 60.00 Hz (GTF) hsync: 47.70 kHz; pclk: 64.11 MHz Modeline "1024x768_60.00" 64.11 1024 1080 1184 1344 768 769 772 795 -HSync +Vsync # TV fullscreen mode or DVD fullscreen output. # 768x576 @ 79 Hz, 50 kHz hsync ModeLine "768x576" 50.00 768 832 846 1000 576 590 595 630 # 768x576 @ 100 Hz, 61.6 kHz hsync ModeLine "768x576" 63.07 768 800 960 1024 576 578 590 616 EndSection Next, go into XFdrake and select the higher resolution of 1024x768 for your output. When it asks if you want to restart the X server, say no. Check and make sure XFdrake doesn't edit out your inserted modeline in xorg.conf. I don't think it will but you never know. If it did, just cut and paste the modeline back in. In the "Display" subsection you should see new listings for "1024x768" for the various color depths. Log out and when you see the login screen hit Ctrl-Alt-Backspace just to make sure the X server has been restarted. Log back in and see if the whole thing works OK. Your modeline should force 60Hz refresh rate at 1024x768. The modeline method was the only way I could get my refresh rate down from 75Hz.

First thing to do is make sure you have the correct monitor chosen for your system and that you have selected the intel "i810" driver not the 830 one you used before. That should get you to higher resolution. Then post your /etc/X11/xorg.conf file as configured for the i810 driver. If you know the horizontal sync and vertical refresh rate specs for your monitor, post that as well. I have the same intel 965 chipset motherboard with intel integrated graphics and had to generate a custom modeline to get my refresh rate down to 60Hz. You may wind up having to do the same but it's not that hard. Also, i810 is he correct driver for this graphics chipset for the several distros I've tried. I believe in fedora 7 they offered the intel 830 as an alternative but it was marked "experimental" and not recommendedm i.e. it's still in development. The older i810 worked much better for me and that's what was auto-configured on every distro I tried.

Nope. It fixes the problen after the fact. I think that's a good idea; the problen probably lies in the initrd you made.

If Mandrake 10.1 has an /etc/modprobe.preload file, try putting: sym53c8xx at the end of the file. If that doesn't work, you can always put the following at the end of /etc/rc.d/rc.local: modprobe -r sym53c8xx modprobe sym53c8xx or whatever are the commands you run after a boot to get the scsi drives detected. That's probably the easiest since this appears to be a timing issue with something interfering with the sym53c8xx locking onto the the scsi adapter but apparently goes away later in the boot process. Since rc.local is the last init script to run, the conflict should be gone when you run the commands from there.

Didn't do anything special, neddie. That's just the way it was set up after install. Here's the fstab entries for my two optical drives: /dev/hda /media/cdrom auto umask=0,users,iocharset=utf8,noauto,ro,exec 0 0 /dev/hdb /media/cdrom2 auto umask=0,users,iocharset=utf8,noauto,ro,exec 0 0 I think my problem is an issue with udev or hal since a manual mount fixes the problem. Also, the problem is erratic so it's difficult to troubleshoot but I have the identical issue on two separate machines, one of them being a laptop, so I know it's not just some hardware quirk on one box. I was going to attach a screenshot but of course I can't get it to do that just now. At any rate a manual mount fixes the problem which is why I suggested the original poster give that a try.

Just for the heck of it I tried installing the windows version of AcrossLite using CodeWeaver's CrossOver-Linux which is an easy to use implementation of wine. It installed fine and seems to be running OK. I installed the WinXP,Win2000,WinMe,Win98 version. I'm fairly certain you could get this to run under wine.

I've had similar problems with mdv2007 and mdv2007.1 except the cd mounts and sometimes shows garbage files. However, if I unmount the drive in a console and remount it there, the cd works OK: $ umount /media/cdrom $ mount /media/cdrom Try mounting in a console and see if you get better results.

The procedure is given in detail here: http://feraga.com/library/howto_use_crypts..._luks_support_0 But in general, you create the container using the dd command and set the size there, eg: # dd if=/dev/urandom of=containerfile bs=1M count=<number of megabytes> This has been adequate for my purposes but you may need a more dynamic system that can change size on the fly. For that take a look at encfs: http://en.wikipedia.org/wiki/EncFS EncFS is a user space encrypted filesystem that uses the FUSE library. I'm not that familiar with encfs but it may be more what you are looking for. The encfs rpm is available for mdv2007.1. There's also a kde front end for encfs, K-EncFS: http://www.kde-apps.org/content/show.php/K...S?content=54078 Again, I haven't used this tool so I can't be of much help here but it may be worth checking out. Don't see an rpm for it so you would have to compile from source.

In effect, yes. You don't have to encrypt an entire partition with cryptsetup. You can create encrypted "containers" inside an existing partition with cryptsetup and move whatever sensitive stuff, including folders, into the encrypted container. You can also grant different users access to the container and give them separate passwords for access and revoke a user's password/access without effecting the other authorized users. Cryptsetup is also faster and less resource intensive than cryptoloop in my experience. Finally, cryptoloop is deprecated, meaning it is no longer being actively maintained as of kernel 2.6.4. As such, sooner or later, cryptoloop support will be dropped from the kernel. You are much better off using dm-crypt/crypsetup/LUKS going forward. mcrypt can't directly do folders either as it will only encrypt a single file. Typically with mcrypt, you tar up a folder or several files making the collection into one large tar file and then encrypt that single tar file with mcrypt. It's more for archiving since to access the data you have decrypt and then untar the resulting tar file to get at the original data.

I haven't tried mcc in a while, but it used to use cryptoloop for the encryption. Cryptoloop has been deprecated as it had some security problems, was slow and relatively inflexible. The modern approach to encryption in linux is with cryptsetup with LUKS support. Here are two articles that discuss the topic in detail: http://polishlinux.org/howtos/encrypted-ho...ition-in-linux/ http://feraga.com/library/howto_use_crypts..._luks_support_0 It uses the dm-crypt kernel module which has been part of the kernel from 2.6 onward so you have excellent native kernel support and don't need to compile any kernel modules. You can do entire partitions or file containers with cryptsetup as more fully discussed in the above articles. I believe cryptsetup is installed by default in mdv2007.1 but if not the rpm is available if you have setup the usual urpmi repos(main, contrib, plf-free, plf-nonfree). Cryptsetup has been available for every distro I've tried recently except slackware and there I used the static tarball: http://luks.endorphin.org/dm-crypt You just unpack it and put the executable in path as it is entirely self-contained.

The hardware specs look like vanilla intel centrino chipset with intel graphics and wlan. That stuff runs fine on most modern linux distros in my experience. I wouldn't expect any trouble with mandriva. Not sure the 7" screen is enough real estate for websurfing but it has to be better that trying to do that on your cell phone. The price is certainly right but like many mobile devices, I'm not sure what I need it for other than the coolness factor.

In kde, keyboard shortcuts are not restricted to those items appearing on the "start menu". Go into Control Center>Regional & Accessibility>Input Actions. Create a new group by hitting the "New Group" button; name it "MyGroup" or anything else you want. Select MyGroup from the list and then hit the "New Action" button select a name for your new action and select "Keyboard Shortcut" in the Action Type drop down menu. From there, it's pretty self explanatory - you create the key combination for the shortcut by ticking the Keyboard Shortcut tab and then you designate the command you want by going to the "Command/URL Settings" tab. You can go anywhere in your filesystem in that tab. If you just want to open your home directory type in /home/<username> in the field provided.

You probably just have to install the two rpms since mandriva is rpm based like fedora. Just click on the rpm files and you will be prompted for the root password. Then the install will complete or you may get an error message explaining why the install was aborted. That's the first thing to try.

Here's a recent article on rsync usage: http://www.linux.com/feature/117236 You should also not that if you are backing up a linux filesystem to a FAT32 filesystem you can run into problems since FAT32 does not support owners, groups, symbolic links, etc. To get around these problems and not get a ton of error messages use this: rsync -rvt --modify-window=1 --delete instead of: rsync -av --delete when backing up a linux filesystem to a FAT32 fielsystem with rsync.

Also, make sure that the very first space on the first line of your script starts with: #!/bin/bash You can't have any whitespace(or anything else) before that or the script won't execute with a mouse click although it will execute fine from the command line. At least that's true for more recent versions of kde. Apparently, kde doesn't pick up the script as executable unless #!/bin/bash are the very first characters.

A longshot, but if you are using VirtualBox to run windows in an emulated environment and have usb devices enabled, I get that type of anomalous usb detection at times after shutting down VirtualBox.

Download the source rpm, krename-3.0.14-1.src.rpm, to your home directory from here: http://www.krename.net/Stable.6.0.html The open a console and as root run: # rpmbuild --rebuild krename-3.0.14-1.src.rpm That will automatically build a krename rpm for from the source and dump it in /usr/src/rpm/RPMS/i586. It will also build a "debug" rpm that you don't need. Install the krename rpm by double clicking on it and entering the root password when prompted. Did this myself and it built and installed fine without errors.

Since no one has responded, I'll give you what I know about this problem. It sounds like you want to duplicate an installation with specific packages on multiple PCs. Mandrake used to have a system for doing that called "auto-install"; I assume they still do. While I have never done this myself, IIRC the process did not involve having to remaster the cd or dvd. At some point at the end of the installation there was an option to create an installation configuration file which could be used to duplicate the install you just did on multiple PCs. Here's a link to someone that has gone into the auto-install process in great detail: http://members.shaw.ca/mandrake/ You should be able to find some useful info there.

If you are booting to a gui like kde or gnome with mandriva, you can use a graphical text editor like kwrite or gedit. Just open a console and run: $ kdesu kwrite /boot/grub/menu.lst Enter the root password when prompted and kwrite will come up with root privileges displaying menu.lst. It works just like an ordinary word processor.

In a single user, desktop environment there are not a lot of advantages for using a separate /usr, /tmp, /var, etc. In fact for newbies, this usually ends in one partition or another being too small somewhere down the road. Having a separate /home is useful since you can keep all your individual settings when you install an updated version of mandriva by directing the install routine to not format /home. Other than that, there is not any good reason not to have only one / partition with everything on that and one swap partition. For servers, you will frequently want a separate /var and /tmp since these can fill up in a server environment which can cause problems if they are part of the / partition. In a multiuser environment, most admins will have separate /usr, /home, /boot, maybe /tmp and /var as well. This is done for ease of backup, security and other administrative ease reasons.