aRTee

nick0, thanks for your input. Moving images, hmmmm, difficult. But I have added some pics for some stuff that I had trouble explaining, so it has become slightly more colourful. If you have concrete ideas on other images/screenshots that I could add, don't hesitate. On my lack of 'rabid anti-MS tone', I certainly have that, but try to keep it off my site. Beating people away is for other sites/pages/people, I try to lure them over to linux.. :D And actually, I'm trying most to help people who want to make the conversion, who are ready to put in some effort. If you read my 'switching' article, you'll see that I don't try to talk people into linux; I do in real life at times (at work most people have loads of unix experience, I just know they'd love linux; they already have adverse feelings to any MS OS or program as it is... ). Anyway, please find the new version in the old place, and for reference the old version is still on the web; new/latest (last??): http://www.mandrake.tips.4.free.fr/learninglinux.html and old: http://www.mandrake.tips.4.free.fr/learnin...ux.pre-nos.html

Hey, good for you, and good for me :D Enjoy your system, and I'm happy someone found some use for my site! :)

It's not like it doesn't work or so, it's just that it freaked me out that my athlon 2400+ @ 154x13MHz (so faster than a normal 2400+ system) had a load of more than 60%.... For copying a cd, I'd prefer to copy via the harddrive. But hey, if it works for you... All I can say: I have made 1 copy like this (don't often make copies anyway) and may make a copy like it again (the copy did work fiine), but never directly of an audio cd.

Check my website (see link below), go to the config page, where I explain how to set up readers as scsi devices too. BTW after going through the trouble of making my dvd-rom a scsi emulated device (for disc to disc copying, instead of via the harddisk) I realised that it's not really so practical. But you will find all data, including my lilo.conf and other files (also on my spec page, see .sig), for comparison reasons.

Ok guys, please give it another go, I have just updated (finally!) the article. Let me know if you like it this way. I know that I haven't taken every bit of comment into account, but one can't make the world happy. I did put a link at the top for those newbies that want to get practical, and I put a small WIFM (what's in it for me) to try to still motivate them to read the background piece. Also, mostly due to my girlfriend's (fiancee, actually, hence the delay, other things to do and plan.... ;) ) remarks, I made GNU and other acronyms clickable, so there would be some explanation of what it is (GPL, OSS etcetc). I would like your input soon, if I don't get any 'no-go' comments, I'll try to get this article linked at the usual places, linux today, PCLO, who knows maybe this time osnews may even link to it (even though I doubt it, but then I don't care about that site anyway).

Some advantages of dvd+rw: it has more precise (over)write capabilities, is technically 'better'. Read also: http://fy.chalmers.se/~appro/linux/DVD+RW/ scroll to the end to get the technically interesting info. In other words, there is no difference on a dvd+rw written in multiple goes with some parts exchanges etc and a DAO (disc at once), as far as afterwards reading goes. This is a 'really good point' which shows the excellence of the format. Check the links of steve_s, very interesting comparisons there too. For me it is clear: dvd+ is the technology to go. It is more advanced in several ways, more interesting... 1- faster rw write speeds (2.4 instead of 2, will soon be 4x) 2- soon to have 8x +r write speeds 3- formatting done in background 4- can be used as arbitrary file system, mount rainier compliant (drag and drop etc is possible, just as on a hard/floppydisk) And don't worry about compatibility, just check with the last link of steve's post if your current drive is compatible. As long as people pay attention now, there won't be any drive in the near future that can't read both dvd+ and - discs. Just as you can't buy a cd-rom drive that doesn't read cd-rw discs anymore. If people keep buying drives that don't read both, too bad... then it will be like the sony dvd-players that very often don't read cd-rw discs.. So for future compatibility, there's no big worry. And if you buy a drive for your own system, you don't even care if your current dvd-rom can or cannot read your discs, since you'll have your burner. Somehow, people are blowing the issues out of proportion. This is NOT a repeat of the Video2000 vs Betamax vs VHS events. The discs are physically compatible (at least on the read level, not on the writing level), they all fit in the same drives, and it is up to the firmware to make sense of the data. Compatibility is not so difficult to have (for the manufacturer). Except for dvd- video recorders that have to be set to compatibility mode when recording, ... Note that for video applications, the dvd+ format is clearly better, you don't have to decide in advance if you want to make a disc with the best quality or with compatibility... It seems that dvd+ clearly has the edge lately in terms of sales, and especially in terms of rampup of sales. Don't forget that dvd+ video recorders and data drives came onto the market a year or so after dvd- recorders/drives. And already they seem to be on par. So for me it will clearly be dvd+ As an aside: Apple is in the dvd- camp, mostly pushed and developed by Panasonic. But even panasonic has a dvd-/+ drive now. Dell and HP/Compaq are in the dvd+ camp (and only +), as is: PLEXTOR. Dell and HP are not yet selling as many dvd+ drives as apple, since on apples they are standard, but their numbers are increasing and that will tip the scale. BTW that Microsoft is on the dvd+ side has no relevance in the greater light of things, it merely means drag and drop will eventually work on an MSWin system. Big deal. Now you can do that with packet writing through a 3rd party app. Small difference, so no relevance there. Dell and HP backing dvd+ is much much more important. Drives that do only - are getting rare, and there are still plenty of drives that do only + Also, drives that do + and - are more expensive since they have to pay for both types of royalties. In the end, the only thing that matters is the speed you can get (which will likely not be very different on + or - ) and the price you pay. And don't worry too much, if you get a dvd+ drive today and that format fails, in 2 years (or whenever the drive wears out or the difference in price of the media gets too big) you just buy a drive that is the right format, or you buy the next drive in the evolution, which is Blue-Ray based. Remember, in 2 years the drives are going to be about the same price as the cd-burners are today. That's right, about 50 to 80 dollars. So in the end, the price of the empty media is most important, and that depends on the quantity of sales/production. Basically, per MB either dvd recording format is already cheaper or in the same range as cd-r(w). If dvd+ is more sold (which it apparantly is in my part of the world), dvd+ discs will drop fastest and more in price.

Hay Lord_ ehhh .... Gowator.... Anna, it may be that the usb-storage is not properly implemented in your camera. This happens sometimes, check google groups for that. In that case, it's really the cam that's the problem -- too bad. Let us know how this ends, ok?

Strange that the text only files are about the same size in .ps and .pdf; .pdf should use compression and that should help a lot in reducing file size. If a file is .pdf or .ps: check the header: head [filename].ps (or .pdf) if it's postscript, it will tell you in the first couple of lines. Maybe konqueror will also tell you what type it is; and I can imagine there are straightforward linux/unix commands that give info on a file, I just don't know them. In any case, if a file is not postscript, but you can open it in kghostview it's a pdf, since those are the only formats (afaik) that kghostview reads. The 'no-filesize-difference' with screen, printer and press (yes, to me I would say those files are the same size, there is no significant difference in those few bytes, that's just some minor formatting structuring in a slightly different way) could be explained in that there SHOULD BE NO difference; after all, it's just text, why would you expect any difference if you don't have any bitmap graphics or so?? And yes, 200KB seems big for 20 pages of text,.... that makes for 10KB per page... each character is one byte, so one page should be less than 1KB..... beats me, no clue there. You could have a look into the .ps file to see why it is so big; normally a ps file has some formatting info and then the text, almost as is. Are you using a standard font or something special? That could explain something too...

Anna, try doing both mknod commands: mkmod /dev/sda b 8 0 mknod /dev/sda1 b 8 1 ... then if necessary: mkdir /mnt/usb and mount with: mount -t vfat /dev/sda1 /mnt/usb I've seen most references making both the 8 0 and 8 1 node, so it seems to be necessary for it to work. Worth a try IMO.

Shot in the dark, .... it's not supermount, it's not usb or kernel problems... All you may need to do is do a mknod [significant node and other data that I don't know] to create the right device, and you will be able to read the cam contents. Since the usb-storage gets loaded, and your usb device gets detected, all you need is to have the device as a file (meaning: in the filetree, as a device in /dev, probably as /dev/sda ..), and mknod is the command to fix/create that. I had to do that the other day to create the /dev/lirc/0 device, all modules were loaded, all config files in place, but I just didn't have the device... I did a google: http://groups.google.com/groups?hl=en&lr=&...%3DN%26tab%3Dwg or: http://groups.google.com/groups?hl=en&lr=&...%3DN%26tab%3Dwg So I guess your mknod command should be: mknod /dev/sda 8 0 b ....then followed by the french stuff on mounting... [edit] Maybe/possibly you have to do both mknod commands as shown in the french message, I see the same thing here (meaning: doing both mknod commands, creating /dev/sda and /dev/sda1 .....) : http://groups.google.com/groups?hl=en&lr=&...%3DN%26tab%3Dwg

Hmmm, could you mention actual sizes? Like: 3 page document, text only, 25KB in .ps format and 14KB in .pdf....? If you have no images, .ps is actually not extremely large format; btw you can read it, it's just ascii, formatting info and text.. (unlike .pdf)

Good news, seems they haven't been sitting still after all. But wasn't HP the one offering Mandrake before (at that time only on high volumes)? Now on nice laptops and I'm buying! Go Mandrake! Go! ;)

Size of pdf's often depends on the quality (screen or press) and whether there are any bitmaps involved. If there are, press will give a much bigger file than screen...

I hate to say it (and not contribute anything useful) ;) ) but it seems like you have angered the linux god Mandy for stepping away and worshipping the heathen god Genone (or was it Gentwo) :lol: Seriously, I've had my fair share of scanner problems, so I wish you good luck...

Another thing to try: what happens if you select shutdown from the login menu? Once logged in you won't get there if the choice 'login as different user' doesn't work without killing X, but it's worth a try: ctrl-alt-backspace should get you back to the login menu, where you can do shutdown/reboot.

Huh i have heard linus pronounce it as lin as in lindows nix as in unix in the mp3 file("Hello, this is Linus Torvalds, and I pronounce Linux as Linux!").http://www.paul.sladen.org/pronunciation/t...-says-linux.mp3 No that is correct, the problem is with the western/latin transcription of Lee as in Bruce Lee. In any case, it should not sound like (big fat) LIE - nucks...

On the pronounciation of our beloved OS, the main man has his say here: http://groups.google.com/groups?selm=1992A...sinki.FI&rnum=3 which leads to LEE-NUCKS (Bruce Lee nuckles or so..), not LIE-NUX (it's a lie) Or maybe I am messing up between another life I have/had on the side...

JaseP, I don't see what you mean with the first part, 'repopulating' stuff from backup. Why couldn't that be done easy and conveniently on the commandline? cp -pr or so would do nicely, keeping all file attributes (ownership, timestamp and last access time etc) the same; man cp for the exact command (because I may be off on the -pr.. If you have to change usernames/ownership because a user had a different accountname in the past, chown and chgrp come in handy). I would never do such a thing with a filemanager, don't see why. If you find it more convenient, fine, but it doesn't have to be done that way at all. No UNIX sysop would ever think of doing it other than on the command line. Linux is for all practical purposes a unix. Weird permissions that would allow only root to run gui-- I wouldn't know, wouldn't find out, because if my normal user can't run X, the system is crippled and should be repaired... ;) Ok, you may check if root too cannot run X+gui, so you find out it is a permission problem. But I don't class that as having to run a WM or DE as root to perform a certain task. So once more, I see no situation where you HAVE TO run a wm/de as root, or log on graphically as root. BTW yes you are right, if you su to root and run konqueror, all kde stuff that konq needs also gets loaded; and all settings get stored in /root too. But my point is, even that you don't have to do. I never run konqueror as root. I disagree with this: First: there still isn't any example of where it is really necessary. Second: why wouldn't it be possible to do even if you shouldn't? Should they block the command rm -rf / too? Even though there is no single example that I can think of where that is actually helpful? If you want to wipe your system, you are easier off to reinstall whatever OS and in the process format/delete your partitions. Linux (unix, bsd) as a system really doesn't protect the root user from himself. Therefore, you should do the least as possible as root, which includes that you shouldn't log on graphically as root...

BTW if you are installing an rpm, just use urpmi, as in: urpmi package.rpm if the package is where you are giving the command, urpmi doesn't try to download it from anywhere (so it doesn't have to be in the database), it just assumes the one there is what you want, and resolves the dependencies that it finds in the .rpm package headers. Since this one problem may be more related to the nvidia stuff, this may not apply. But in short: urpmi rocks.

To join in the naysaying: Never log in graphically as root! Since the invention of the GUI the 'undo' button has become a must. Viz. your drag and drop indications can lead to big problems; just imagine you're browsing and by accident put /etc into /home or so..... When you type at the console, you can also make grave errors, but you can check and doublecheck before hitting enter -- although rm -rf / home/[user]/somefile as root can still wipe your box clean as a newly polished mirror (note the space), it can also be checked before sending the command... (One way to avoid this kind of stuff is just never use long absolute paths in such commands, but first cd into the right place; and never use rm -rf when you are in a hurry ;) ) JaseP, if you mess up your system so that you have to unmount the /home partition (to check it or so), just go to the console, there you can log on as root (non grahically), do a telinit 3 and umount /home, then fsck or whatever, then mount /home and telinit 5, then ctrl-d to log off your root logon. Logging on graphically as root is Never Necessary. Please give me examples as to where that would be necessary, I don't see any situation where it cannot be avoided to log on graphically as root; I've been using linux straight since over 2 years (dualbooting somewhat in the beginning), have a headless server running too, and never had to log in graphically anywhere as root. Canonfodder, and anyone else, feel free to do it anyway. The point, I guess is: - if you don't know why you shouldn't log in as root, you shouldn't - if you have to ask how to do it, you shouldn't - if you know why you shouldn't but really want to, sure. You are wise enough to know that if in doing so, you should not blame linux for letting you screw up your system. Hmm,... I once started a Taoistic poem about this: Those who know how to log on graphically as root don't want to those who want to log on graphically as root don't know how to (never got to finish it though....)

Currently (since 9.1) I have the following .imwheelrc in my home dir: [robert@zurich robert]$ cat .imwheelrc ".*" None, Down, Alt_L|Left None, Up, Alt_L|Right and: [robert@zurich robert]$ cat .kde/Autostart/muisxmodmap #!/bin/sh killall /usr/bin/imwheel xmodmap -e "pointer = 1 2 3 7 6 4 5" imwheel -k -b "67" also, the relevant lines in my XF86Config are: Section "InputDevice" Identifier "Mouse1" Driver "mouse" Option "Protocol" "ExplorerPS/2" Option "Device" "/dev/usbmouse" Option "ZAxisMapping" "6 7" EndSection Hope this helps!

Did you go to the xfree setup during the installation? Was it troublefree? Some nvidia boards have problems with the stock 'nv' driver, I had the exact same problem with mdk9.0 (well, same problem description), which was fixed after installing the nvidia proprietary drivers. Check the nvidia website for that, and install those drivers. (and how to adapt the /etc/X11/XF86Config-4 to use the new 'nvidia' driver instead of the 'nv' driver) It may also be that your xfconfig file is just not ok. What you could also try is to go to a different resolution, just do a ctrl-alt-+ or ctrl-alt-- (minus) and see if that helps. Also, check with ctrl-alt-F1 if you can switch to the console, ctrl-alt-F7 to go back to the graphical stuff (that doesn't work currently..).

Check on my site and compare lilo.conf www.mandrake.tips.4.free.fr/sysspec.html also have a look at my config page, where I describe the setup for direct cd-rom to cd-rw copying, you will get more info and hints there. /var/log/dmesg will tell you how your drives are linked into your system by the kernel at boot.

I have a P1 200MHz 120MB (yes 120, not 128) running as a headless file download and internet server. The dma on the second channel switches off after half a day or so, and I reboot less than once a month (well, reboot, my girlfriend sometimes pulls the plug by accident or so)... If not I would use it as a backup server as well, but with a sustained datarate of 1.8MB/s this is no fun... I do stream my .avi's directly from it, it's fast enough for that. You could also attach a webcam and use it as a security system. I recently found out you can switch off the light on the webcam, sort of 'silent mode'. Of course then you really do need to upload each image to the net, because they might steal the machine and then what good would it be... ;)

About the system: it must be quite rugged if in the same place/room you also serve alcohol. Howabout xstations from whatever hardware, or at least a logon server? Or don't you want to keep track of the time that one and the same person uses a system? Xboxes could well do the trick. Have you checked for sponsoring of displays (15inch tft all around or so), local shops or producers (philips, lg, samsung, sony)..? Maybe you won't get them for free (surely not), but they may give you their 'insider' price (the price that their own personnel must pay), which can be quite a bit cheaper than even the cheapest shop. Make sure the guests can send SMS messages for free to any french operator. They will have to be able to SMS their friends who are on their way that they are waiting. BTW, I lived in Paris for almost 3 years, no smoking bars?? or places with no alcohol?? Yeah right. Anyway, about smoking: recent research in Switzerland (where they smoke more than in France or the Netherlands, though possibly not as many 'funny' cigarets as in Holland (or maybe they do..) has shown that non-smokers actually consume more and tip more. My take: smoking should be allowed, but air refreshment systems should make sure the annoyance is kept low. Even smokers agree that the bad smell of their clothes is disgusting..... Have a side that is smoking, another that is non-smoking, and good air refreshment, so that non-smokers can happily join smokers without too many problems. I'll post more if more ideas come up.