Ok, so I left off yesterday satisfied with branching from bazaar repositories on the network, but not with file mounting. I'll figure it out!
mkdir <local directory>
sudo mount -t nfs <network>:/<share name> <local directory>
Great! But when I try to cd into the <local directory>, I get permission denied. Apparently this is an id problem.
Running id at the command line gives me a uid and a gid. These need to be the same as my uid and gid on my network account. I also need to make my own computer be a member of the lab group.
To check id's locally or after ssh'ing into the network:
id
getent passwd <username>
I logged in as root and changed the id's following instructions from l0b0 and Esteis:
http://askubuntu.com/questions/16700/how-can-i-change-my-own-user-id
Alternatively, you can edit the documents directly:
cd /etc
sudo gedit group
sudo gedit passwd
Important!
To unmount drives:
umount <path to drive>
Don't delete the directory.... that really deletes it from the network.
Thursday, August 29, 2013
Wednesday, August 28, 2013
Network File Access
One of the most frustrating things about my existence as a graduate student is figuring out how to access files that are on the schools network. My desktop was helpfully set up by trusty Tom. BUT, I want to be able to use my new laptop to smoothly deal with network files. So, here is how the setup goes:
1) I set up an ssh key pair and places the public half on in my home directory on the network
I know this worked because I can: ssh rperry@login.<network name>
ssh -v rperry@login.<network name> shows you more verbose information about the completed process of logging into the ssh session
The ssh key is important for almost all ways of accessing the network.
2) bzr with network files. There is a paper written in latex that is on the group share in a bazaar repository that I would like the edit. I thought bzr+ssh would work, but it did not since the server doesn't have bazaar installed. Instead, I can use sftp:
after cd'ing to the directory where I wanted to put the branch:
bzr branch sftp://<username>@login.<network name>/group/<rest of path to directory>
Ok, so now I want to make this tied back to the main repository so that I can make changes and check them in:
Workflow:
In my lab, we use a "decentralized with shared mainline" workflow:
bzr pull
...[make changes]...
bzr commit -m "commit message here"(commits to local branch)
bzr push :parent --remember (pushes to main branch, can just use bzr push in the future)
...[if there are conflicts it will tell you]...
bzr merge (or if you are the sole owner and are confident that you want your version, bzr push --overwrite)
This main repository shouldn't have a working tree associated with it, but it does and it tells me that it will not be updated since I am pushing remotely. If you want to update it and work from there (not suggested), then you can update the working tree by doing something like this:
ssh rperry@login.<network name>
cd <repository>
bzr update
In practice, you should just branch from the main repository rather than accessing the main repository to see the files.
Yay!!!!! I can work on tex files from the lab network share from anywhere!
3) When on campus, it would be really nice just to have the whole network folder mounted. For this, I'm going to figure out how to do NFS or CIFS... but that's for the next post.
1) I set up an ssh key pair and places the public half on in my home directory on the network
I know this worked because I can: ssh rperry@login.<network name>
ssh -v rperry@login.<network name> shows you more verbose information about the completed process of logging into the ssh session
The ssh key is important for almost all ways of accessing the network.
2) bzr with network files. There is a paper written in latex that is on the group share in a bazaar repository that I would like the edit. I thought bzr+ssh would work, but it did not since the server doesn't have bazaar installed. Instead, I can use sftp:
after cd'ing to the directory where I wanted to put the branch:
bzr branch sftp://<username>@login.<network name>/group/<rest of path to directory>
Ok, so now I want to make this tied back to the main repository so that I can make changes and check them in:
Workflow:
In my lab, we use a "decentralized with shared mainline" workflow:
bzr pull
...[make changes]...
bzr commit -m "commit message here"(commits to local branch)
bzr push :parent --remember (pushes to main branch, can just use bzr push in the future)
...[if there are conflicts it will tell you]...
bzr merge (or if you are the sole owner and are confident that you want your version, bzr push --overwrite)
This main repository shouldn't have a working tree associated with it, but it does and it tells me that it will not be updated since I am pushing remotely. If you want to update it and work from there (not suggested), then you can update the working tree by doing something like this:
ssh rperry@login.<network name>
cd <repository>
bzr update
In practice, you should just branch from the main repository rather than accessing the main repository to see the files.
Yay!!!!! I can work on tex files from the lab network share from anywhere!
3) When on campus, it would be really nice just to have the whole network folder mounted. For this, I'm going to figure out how to do NFS or CIFS... but that's for the next post.
Monday, August 26, 2013
Zenbook Surgery
I bought an ASUS Zenbook UX32VD! My toughest criteria in picking an ultrabook was that I need an NVIDIA graphics card for parallel computing. I think it's awesome that I have this parallel computing power in a light little ultrabook! Here are the specs as it arrived, but I quickly did some surgery to upgrade it!
I had never opened up a laptop before, but I wanted to upgrade the HD to completely SSD and replace one of the 2GB RAM sticks with an 8GB stick for a total of 10GB of RAM. (good instructions here: http://youtu.be/8xC-osS0scU) I installed Ubuntu 13.04 on this new hard drive and had no trouble booting!
Checked the ram with this terminal command:
free -m
and I have 9.999 GB. It's recognizing the new RAM!
When it was installing it asked if I wanted to use the 250.1 GB drive. So, it's recognizing that too!
| Screen Size | 13.3 inches |
| Screen Resolution | 1366 x 768 |
| Max Screen Resolution | 1920x1080 pixels |
| Processor | 1.9 GHz Core i7-3517U |
| RAM | 4 GB DDR3 |
| Memory Speed | 1600 MHz |
| Hard Drive | 500 GB |
| Graphics Coprocessor | NVIDIA_GeForce_GT_620M |
| Chipset Brand | Intel, NVIDIA |
| Wireless Type | 802.11bgn |
| Number of USB 3.0 Ports | 3 |
| Brand Name | Asus |
| Series | UX32VD |
| Item model number | UX32VD-DH71 |
| Hardware Platform | PC |
| Operating System | Windows 8 |
| Item Weight | 3.2 pounds |
| Item Dimensions L x W x H | 12.80 x 8.78 x 0.71 inches |
| Color | Silver Aluminum |
| Processor Brand | Intel |
| Processor Count | 2 |
| Computer Memory Type | DDR3 SDRAM |
| Flash Memory Size | 24 |
| Hard Drive Interface | Serial ATA |
| Hard Drive Rotational Speed | 5400 RPM |
| Optical Drive Type | No |
| Audio-out Ports (#) | 1 |
| Battery Type | Lithium Polymer (LiPo) |
| Batteries: | 1 Lithium ion batteries required. (included) |
I had never opened up a laptop before, but I wanted to upgrade the HD to completely SSD and replace one of the 2GB RAM sticks with an 8GB stick for a total of 10GB of RAM. (good instructions here: http://youtu.be/8xC-osS0scU) I installed Ubuntu 13.04 on this new hard drive and had no trouble booting!
Checked the ram with this terminal command:
free -m
and I have 9.999 GB. It's recognizing the new RAM!
When it was installing it asked if I wanted to use the 250.1 GB drive. So, it's recognizing that too!
Subscribe to:
Posts (Atom)