ianw1974

Yes, it will mount under media. But once you've assigned the rights, it will be OK after that. Sometimes what I do is label a media also. So, another thing you can do is this: mke2fs -j -L usbdisk /dev/sdb1 for example, will create ext3 on /dev/sdb1 with label usbdisk. When you connect it to system, it will mount as /media/usbdisk. Then you can assign rights as before: chmod 777 /media/usbdisk or own it as your user: chown user:user /media/usbdisk if it will be just for yourself. Sometimes I also had to set a sticky: chmod g+s /media/usbdisk so see how you go. This is usually what I do for my pendrives, I have freecom, kingston, etc, and label them accordingly as per this. So that they mount as /media/freecom or /media/kingston.

If you want a user to mount it, in the options where you have defaults, you need to add user as well, so it would be like this: defaults,user then the user can mount it. If you had a FAT32 filesystem it would be OK. Now, I do it slightly differently. For example, if I have /dev/hdb1 only as the partition on my disk, then I would do this from the console: mke2fs -j /dev/hdb1 mkdir /mnt/mynewdisk mount /dev/hdb1 /mnt/mynewdisk chown user:user /mnt/mynewdisk first command formats it ext3. second command creates directory mynewdisk third commant mounts it to mynewdisk fourth command assigns ownership of that disk to my username - in this instance user - change this to what you want. If you want multiple users to access the disk, then: chmod 777 /mnt/mynewdisk then all users have full world read/write access. I usually only do it for one user, but I don't know if you want for one user, or multiple users. Alternatively, you can do for groups, but then users have to be members of that group across all your systems, and the group must have the same GID on all machines. So the chmod command just gives full access irrelevant of group or user.

Tom Berger :) It's on the main index page when you come to the forum ;) Click here https://mandrivausers.org/

If it's using the new version of GDM, then no, you cannot change it. This is becoming more commonplace now, and is the same for Ubuntu and OpenSUSE which are some distros I've used recently which are using the new version of GDM. No theming support, and I don't know if there will be but I hope so, because I liked also changing the themes.

I've done that once as well :)

Someone else recently had a problem with K3B. Try Gnomebaker or Brasero - I know these are native to Gnome normally, but see if they work. If that is the case, then we know that mostly everything is OK, and that something is just broken with K3B.

It's a pity that a firm has to do this. It would be much better just to leave it all as OpenSolaris or MySQL or OpenOffice than just make matters confusing.

I'm assuming you had an md2 array for the two disks. So you need to use the mdadm command to assemble this (assemble parameter) and will build the array, and then mount the array in the usual manner. My post on my website covers this: http://www.linuxsolutions.org/index.php?option=com_content&task=view&id=25&Itemid=26 lower down you will find: mdadm --assemble --scan providing of course you have a correct /etc/mdadm.conf.

Also check lost+found directory in case it all got moved under here. Sounds bad though :(

A shame IBM didn't get hold of Sun when it was being sold off. Things would have been a much better place. Three projects here, OpenSolaris, Java and OpenOffice. Also MySQL which has now been forked to MariaDB because of the Oracle thing. Don't forget, IBM have Lotus Symphony which is OpenOffice based.

Fixed :) Thanks for pointing it out.

Spam removed.

I got started on nano when installing Gentoo :) Someone asked me the other day do I use vi. I said yes, sometimes :) I like vi if I need to delete a lot of lines.

Did you try deleting the .k3b config directory as well, in case something was amiss with the config? I suppose as there is always an alternative, gnome-baker or brasero it should be fine. I'm generally using Gnome, so I don't tend to use many KDE apps so that I don't end up installing all the associated required libraries and dependencies just for K3B or something similar. If of course I was using KDE, then I'd do the opposite and stick with KDE based apps instead of using Gnome ones.

The thing about an existing forum, it has history and these posts are invaluable to resolutions to problems. Starting the mageia forum from scratch, there's nothing. So what happens? The same old questions get asked over and over again. It's like reinventing the wheel. Will be good to see what it's like when Mageia gets off the ground and up and running.

So in your last post are you saying it's working now? I'm guessing so as one of your previous posts says it's working with Gnomebaker just not with K3B. Could be some weird configuration with K3B or something. You can remove K3B, and then try again. And search for perhaps a .k3b folder under your home directory and remove this, and start with a fresh config. If not, I guess the only thing to do is stick with Gnomebaker and forget about K3B. I sometimes had problems with Gnomebaker because of the way the distro was built, and so ended up using Brasero which seems to be a default now in Gnome. Does everything I need to do which I used to do with K3B.

Yup strange and weird. But then Mandriva wasn't any different setting up their own forum instead of utilise one that had a huge userbase already. I guess some thing don't change.

Aye, maybe so, but you still have the problem that you're building a deb against a Mandriva system and it's libraries and hence would be built for the appropriately installed libraries. I'm pretty sure that's important for the building part, especially if someone is then going to use that on a Debian system. I believe it should be built on the system it's intended for.

Yes, it's an SSL connection, and chances are that the certificate is self-signed or generated by an untrusted certificate authority - or doesn't match the url it's being used for. In this case it's been generated from zarb.org - which as we know are the easyurpmi dudes. I would say it's safe to add an exception in Firefox, but I'm not responsible for anything that might happen to your system (legal disclaimer :D ).

The biggest problem here are the dependencies. Each distro has different dependencies and naming conventions. Building an rpm on a non rpm-based system is likely to cause problems. The same with building debs on an rpm-based distro. The dependencies for that particular package are relying on the system you built them on. People building packages build them on a system that they are targeting. Therefore, if rpms for Mandriva, they are built on a Mandriva system. If debs for Debian, they are built on Debian. If rpms for Red Hat, they are built on a Red Hat system. And so on. Attempting to use an rpm from a build system other than where it is meant to be installed is generally going to cause problems. That's like me attempting to use a Fedora or OpenSUSE rpm on a Mandriva system. Might work, but mostly it won't.

Aye, welcome back Chris :)

Interesting, I just read it myself now in the man page :) I've never been a fan of cfdisk (personal preference), although I've seen some distros use it by choice for partitioning the disk during installation. Even though I see that stated in the man page, I'll continue to use fdisk. As you are generally using it when creating partitions, you don't actually have any data on the disk at this point. Therefore, once I've created partitions, I check them to see if they look how they should be, and then continue as normal with whatever else I'm doing. At this point in time, even if it does something wrong it's not going to be a major problem because either you'll have a partition how it should be or not. If not, then another tool can be used, to ensure it's done correctly this time, and it's dealt with in a matter of seconds or minutes. If I'm resizing partitions, which I've done in the past and from the CLI as well, using the tools to resize the filesystem, and then fdisk after that, it's also worked good for me. Of course, when doing this kind of thing, you should have a back up in case something goes wrong when you resize the filesystem and also when you resize the partition in whichever partitioning tool you use. Of course, with something like this, if something goes wrong, then you are looking at a much longer recovery time to restore the disk to it's previous state, but then this could happen for various reasons, for example a problem with the file system, or the partition when resized (had this before a long time ago but user error not fdisk error :D ). If of course I ever come across a situation where fdisk does something bad I'll stop using it, as it's been 100% reliable and accurate for me so far :) In a nutshell, messing around with partitions is risky no matter what tools you are using. There's always a chance something can go wrong. But the warning on fdisk is well worth pointing out to everyone, as chances are not everybody knew about the possibilities that it is buggy.

I've never had any problems with fdisk whatsoever. Never heard of it being buggy in the slightest. Any problems generally come from misuse and user error when repartitioning. Normally, the partitions should follow on from each other, so I guess it's just not been partitioned to well when it was set up but I couldn't explain why, or if the manufacturer was sloppy or not. The Mandriva installer can free the space for you, but check the disk for errors in Windows first, and defrag it and then go for the install with Mandriva.

You can use clonezilla for making an image of your hard disk. Another method, but does a sector backup, which means if a 160GB disk, then a 160GB image is using the dd command. But clonezilla will be better.

I use Dropbox for synchronising files. You get 2GB for free, and if you recommend someone you both get an extra 250MB for free. So of course, pays to recommend :) I have it installed on a number of machines, and my files get synchronised to the internet, encrypted when stored on the server (standard), and then when I turn on another computer, all the files are then synchronised to the next one. Or, if all machines are on at the same time, it happens immediately. Also, if my hard disk dies, and I have all my important stuff in dropbox, then I just need to reinstall my system and then dropbox, and they all download again. Neat :) You can also login from any web browser and access your documents - download them if you need to.