Ubundu: Doing something securitywise with it's parbreastion 284

Pete --

You'll get quicker and better help if you omit your guesses about underlying causes. Instead, leave the diagnosis to us. Hoping not to sound too sharply worded: If you were that good at diagnosis, you'd not

As I said in "How to Ask Questions the Smart Way":

"All diagnosticians are from Missouri." That US state's official motto is "Show me" (earned in 1899, when Congressman Willard D. Vandiver said "I come from a country that raises corn and cotton and chickenleburs and Democrats, and frothy eloquence neither convinces nor satisfies me. I'm from Missouri. You've got to show me.") In diagnosticians' case, it's not a matter of skepticism, but rather a literal, functional need to see whatever is as close as possible to the same raw evidence that you see, rather than your surmises and summaries. Show us.

this (and you should understand that the ":r" incantation is a way of signaling that I used the vi "read" command to import the indicated file into my message-composition buffer:

First, I tried to add it as a new line to Kubuntu'setc-fstab, shown below:

:retc-fstab

#etc-fstab: static file system information. # proc proc proc defaults 0 0 dev-sda5 ext3 defaults,errors=remount-ro 0 1 dev-sda1 boot ext2 nodev,nosuid,noexec 0 2 dev-sdb1 home ext3 nodev,nosuid 0 2 dev-sdb5 tmp ext2 noatime,nodev,nosuid 0 2 dev-sdb8 usr ext2 nodev,ro 0 2 dev-sda9 usr-local ext3 defaults 0 2 dev-sdb7 var ext3 noatime,nodev,nosuid 0 2 dev-sda8 var-log ext2 noatime,nodev,nosuid 0 2 dev-sda7 none swap sw 0 0 dev-sdb6 none swap sw 0 0 dev-fd0 media-floppy0 auto rw,user,noauto 0 0 dev-sda6 mnt-recovery ext2 rw,noauto 0 2

(And so on.)

This is close to "Show me", but you can do better. What's best is doing the command, can then copying-and-pasting the exact command transcript directly into your e-mail. Then, we can see precisely what you did, and catch, e.g., small syntax errors -- such as the one that later in the thread it turns out you'd introduced intoetc-fstab.

Again, you're going wild with surmises. Don't do that (though, there's nothing wrong with experimenting). Instead, just post back to the experts exactly what you did, and exactly what the computer did. For that, nothing improves over a literally copied and pasted command-line session.