(Solved) Anyone Know how to fix this?

[loukingjr]

I changed fstab to...
# Entry for /dev/sda1 :
UUID=fc136849-3c01-496f-88fa-97ab0c9  / ext4 defaults 1 1
none /proc proc defaults 0 0
none /dev/pts devpts defaults 0 0
68dcf / ext4 defaults 1 1
# Entry for /dev/sda6 :
UUID=de242e12-f479-4ef2-8b72-4553798fe639 /home ext4 defaults 1 2
none /proc proc defaults 0 0
# Entry for /dev/sda5 :
UUID=a87ca906-76ae-42a4-988f-e729a288556c swap swap defaults 0 0
none /dev/pts devpts defaults 0 0

and it works also. I don't know why it was different in the first place. I know I didn't change it.

do I have to change fstab.old or fstab~ ?

and what about the lines I marked in blue? should they be there? if so, are they correct?

I've been around and/or used computers since the early 70s and I never had to do this stuff... lol

[Old-Polack]

I changed fstab to...
# Entry for /dev/sda1 :
UUID=fc136849-3c01-496f-88fa-97ab0c9  / ext4 defaults 1 1
none /proc proc defaults 0 0
none /dev/pts devpts defaults 0 0
68dcf / ext4 defaults 1 1
# Entry for /dev/sda6 :
UUID=de242e12-f479-4ef2-8b72-4553798fe639 /home ext4 defaults 1 2
none /proc proc defaults 0 0
# Entry for /dev/sda5 :
UUID=a87ca906-76ae-42a4-988f-e729a288556c swap swap defaults 0 0
none /dev/pts devpts defaults 0 0

and it works also. I don't know why it was different in the first place. I know I didn't change it.

do I have to change fstab.old or fstab~ ?

and what about the lines I marked in blue? should they be there? if so, are they correct?

I've been around and/or used computers since the early 70s and I never had to do this stuff... lol

And I've been using Linux for 12 years and do this kind of stuff all the time.  

You don't need to change the other files, as they are just backups of the old file. What you have now is correct in form, except for the lines I highlighted in red. Delete those lines, and you should have no further problems. This is good!  

[loukingjr]

lol well thank you and texstar for your help.

My father worked for IBM for 35 years and used to ask me why I didn't like to program etc. and insisted it was fun! lol

I use computers as a tool to do graphics which is why I've own Macs since 1985 and tend to avoid messing with 'puters' 

[Old-Polack]

lol well thank you and texstar for your help.

My father worked for IBM for 35 years and used to ask me why I didn't like to program etc. and insisted it was fun! lol

I use computers as a tool to do graphics which is why I've own Macs since 1985 and tend to avoid messing with 'puters' 

Just wanted to point out I was modifying my previous post when you posted the above reply. I noticed that there were two repeated lines, which could cause the system confusion, so should be removed from your fstab.

[loukingjr]

lol well thank you and texstar for your help.

My father worked for IBM for 35 years and used to ask me why I didn't like to program etc. and insisted it was fun! lol

I use computers as a tool to do graphics which is why I've own Macs since 1985 and tend to avoid messing with 'puters' 

Just wanted to point out I was modifying my previous post when you posted the above reply. I noticed that there were two repeated lines, which could cause the system confusion, so should be removed from your fstab.

the first two "none" lines? I should take them both out?

[loukingjr]

oops, I see, I typed too soon lol

[loukingjr]

I guess this all means I should take a look at my other four PCLinux guests (sigh) lol. I used to have 7

[Old-Polack]

I guess this all means I should take a look at my other four PCLinux guests (sigh) lol. I used to have 7

It's a very rare occurrence that something like this happens, without the user directly causing the problem. It happens, but not often. More than likely the other guests are fine, but it wouldn't hurt to check, just to be on the safe side.

[loukingjr]

I guess this all means I should take a look at my other four PCLinux guests (sigh) lol. I used to have 7

It's a very rare occurrence that something like this happens, without the user directly causing the problem. It happens, but not often. More than likely the other guests are fine, but it wouldn't hurt to check, just to be on the safe side.

I kind of figured. It probably has to do with VirtualBox or specifically the Mac version of it. The Mac version seems to have more problems than the Linux or Windows versions.

Now if I could only get OpenGL/Hardware acceleration to work in a PCLinuxOS guest, I can die a happy man.