Everything works smoothly. I am delighted. I am very happy that we are flanked by so many experts on linux issues.

There is a minor problem. I have file called '' Bill1 ''. It is a text document written in the word for windows. It is a huge document. It has probably 300 pages. I have been working with some other online forums for more than 10 years. 'This particular document contains some important data belongs to forum work. I can' t afford to loose it.

My Open office program sees it. When I tried to open, it just tells me trying to open. This message lasted for 3 hours.

Do you have any clue to open it and save on my linux side*?

My open office can't open it. All the other documents could open.


-------------------------------------------------------------------------------------------------

mount -t ntfs -o ro,umask=222 /dev/hda5 /mnt
I have a question on the above command. I understand most of it.
What is the meanig of ' - o and - ro '' ?

Well, if nothing else helps, you could take it to a Windows machine with Word and save it in some other format, such as RTF, or divide it to pieces and try again. Generally I would suggest using open, standard formats in the future. Closed, proprietary formats have these problems by design.

The -o argument simply tells the mount command that a list of options follows. In this case the options are ro and umask=222. The ro option means the filesystem is to be mounted read-only, which means it won't be writable. NTFS doesn't support UNIX style file permissions (I think), so umask=222 tells Linux to pretend the permissions for all files in the partition are r-xr-xr-x. That is good for directories, but the files will have unnecessary execute permissions.

Because NTFS isn't fully supported, I think it's mounted read-only by default, so the ro option might not have been necessary.

Ok, Gins, let me "punish" you a bit. As I see you're here from Jul '04. And you don't know how to mount a partition (probably, you don't know what's "fstab"), or whatever. I'M SURE, YOU HADN'T TRIED ANY OTHER DISTRO except Mdk. Well, I repeat over and over again (but in other words): Mdk IS NOT for newbies. It makes you think: "Oh, my KDE. Oh, my GNOME. I could do nothing without you". And that's really bad. What if your X breaks? You should know the command-line basics. But I'm sure you won't follow my advice until... until you install a better distro than Mdk... The problem is that people are lazy to handle difficulties until they face them. I know that myself Try, e.g., Slackware (yeah, I repeat every second). Before you'll be able to use GUI, you'll have to configure it. I promise: while this process you will learn MUCH MORE in 1 day, what you didn't know for half a year "using" Mdk... you will face MANY difficulties... but after you go through them, you'll understand why "not lazy" people prefer Linux. I don't say Mdk is s**t (but I thought that way in previous time). I just say that the first thing to do IS TO KNOW THE BASICS. It's true for all. AND ONLY THEN YOU CAN ALLOW YOURSELF TO BE LAZY
Thanks.

Thanks lakefall


I just want to know what '' ip '' is doing in the following:
mkdir ~/doc
cp -ip * ~/doc


I understand all the other words or commands except '' ip ''.

----------------------------------------------------------------------------
kornerr

You seem to be a bit angry with me. I am learning everyday by browsing this forum as well as asking questions. I have a very little time to do these things. I am going to school and studying networking.

I would consider changing onto Slackware.

It seems you are in Russia. I speak some Russian too. I have been to Russia several times and like the vast country. I was in Russia during the cold war period too. Russians are said to be clever at computer software and related matters.

Gins, thanks for warm words... or how it's called in English. But still: get ANY Linux book and try Slack (I have RH7 book). BTW, I study at University. But actually I do nothing useful there and here And I'm really serious about getting knowledge first day of configuring Slack - I know it myself. And I thankful Slack for that.
Thanks again. Was nice to here you. C U

BTW: what "-ip" flags mean? Well, almost every command has such flag (argument, or whatever): "--help". E.g.:
This option always describes command's possible arguments. Have a look at it. Another useful cmd:
That's a manual page. Almost all cmds have its own mans.
Good luck.

"-ip" is the same as "-i -p". I used -p for the timestamps, which you probably didn't care about, though. I think it's often a good idea to use -i just in case, but perhaps I'm just being overly careful.

Lakefall

Are you based in Finland? You write English like a native English speaker, as far as I am concerned.

I know some Finns. Their English is different from yours.

You should see my Swedish.

Lakefall

You haven't wriiten anything in Swedish.

Jag också kan svenska. Du har inte skrivit nånting på svenska.

Gins
We should forget all the irrelevant things. Let bygones be bygones
...joke