Re: Bakit ako gagamit ng linux? anu ba advantage nito at ano ba ang mapapal
mga ka sym kapag ba nag dual boot ako ng linux mint ma a acces ko parin b ung mga drive ko?
for example s windows ko meron c:/ and D:/ then gumawa ako ng parition n E:/ at dun ko ininstall ung linuxmint kapg b pumasok nako s mint makikita ko parin ung drive c: at d: ko? sorry noob pa e
nasa drive d ko ksi ung mga files for web dev and balak ko sana e access s loob ng linxmint os para ma run ko rin dun ung nasa xammp'
Ano linuxmint gamit mo? XFCE? Cinnamon? MATE? or KDE?
For this purpose, I think it will help if your drive C and D will automatically mount on boot.
And here's how you can make your Windows Partition (Drive C & D) to automatically mount on boot.
Meaning, hindi mo na kelangan imount everytime na kelangan mo yung mga partition na yun. As if, parang kasama na tlaga sya sa buong FS ng distro mo.
You will be editing the fstab file located at /etc to do this.
1. First, backup the fstab so that in case we made a mistake, we still have a copy of our original fstab file.
Open a terminal and type this command:
sudo cp -p -i /etc/fstab /etc/fstab.backup
This command will create a backup of fstab and name it as fstab.backup
2. We need the UUID of the Windows partition you want to automount, Linux Systems use UUID to recognize our partitions, though
labels can also be used. To know the UUID of the partitions you need, run this command.
sudo blkid
You may recognize your windows partitions from the output of this command via their labels (if they have) or via the "TYPE=" w/c
indicates the type of filesystem the partition is, and because these are windows partition, they will have a "TYPE" of either FAT or NTFS.
So remember, whenever you make partitions, always give it a label and never use NTFS or FAT for linux partitions.
3. Lets make a mount point. Its your choice. But I recommend to always put files inside your home directory. So you may do it this way:
mkdir -p ~/windows
or
mkdir -p ${HOME}/windows
This 2 commands are the same. They will create a folder named windows on your home directory.
4. Now open the fstab file located at /etc.
Now add this line to fstab:
# Add a comment so that you'll remember things.
UUID=<xxxxx> /home/username/windows <type> rw,auto,users,exec,nls=utf8,umask=003,gid=46,uid=1000 0 0
5. Explanation.
# Add a comment so that you'll remember things.
Any line that starts with a
"#" on the fstab file is considered as a comment. Its a good practice to always put comments for future reference.
UUID=<xxxxx>
Replace this with the correct UUID you got from the command
blkid.
/home/username/windows
Replace this with your preferred mount point. If your a Bash Script writer, keep in mind that fstab is being read by the system on boot, so
bash variables like
${HOME} or symbols like
"~" wont work. So dont use those on your fstab file.
<type>
Replace this with the correct type of filesystem of the partition you want to auto mount. This could be ntfs or fat. This info can be also
found from the output of your
blkid command.
rw,auto,users,exec,nls=utf8,umask=003,gid=46,uid=1000 0 0
You dont have to care for this. But if you want to know what this arcane parameters are, you may read
this.
There are two important things here that must be pointed out though, first is the
auto which tells the system to automatically mount this partition at the given mount point. The other is
uid=1000 which is simply your user ID. It will help to check your correct UID, run this command on the terminal:
sudo id
A sample output would be like this:
uid=1000(pclogger) gid=1000(pclogger) groups=1000(pclogger),4(adm),7(lp),20(dialout),24(cdrom),
46(plugdev),112(lpadmin),120(admin),122(sambashare)
Make sure the output of
id command has
46(plugdev) output which is the equivalent of the
gid=46 parameter above.
6. Save fstab then issue this command:
sudo mount -a
7. If things work well, your done. If not, retrieve your fstab backup:
cp -p -f /etc/fstab ~/fstab.mod
cp -p -f /etc/fstab.backup /etc/fstab
The modified fstab that didnt work was saved at your home directory and was named fstab.mod while your last working copy
of fstab was restored. You may now review fstab.mod for any errors and try again.