deb http://mirrors.163.com/debian/ jessie main non-free contrib deb http://mirrors.163.com/debian/ jessie-updates main non-free contrib deb http://mirrors.163.com/debian/ jessie-backports main non-free contrib deb-src http://mirrors.163.com/debian/ jessie main non-free contrib deb-src http://mirrors.163.com/debian/ jessie-updates main non-free contrib deb-src http://mirrors.163.com/debian/ jessie-backports main non-free contrib deb http://mirrors.163.com/debian-security/ jessie/updates main non-free contrib deb-src http://mirrors.163.com/debian-security/ jessie/updates main non-free contrib
# Wheezy
deb http://mirrors.163.com/debian/ wheezy main non-free contrib deb http://mirrors.163.com/debian/ wheezy-updates main non-free contrib deb http://mirrors.163.com/debian/ wheezy-backports main non-free contrib deb-src http://mirrors.163.com/debian/ wheezy main non-free contrib deb-src http://mirrors.163.com/debian/ wheezy-updates main non-free contrib deb-src http://mirrors.163.com/debian/ wheezy-backports main non-free contrib deb http://mirrors.163.com/debian-security/ wheezy/updates main non-free contrib deb-src http://mirrors.163.com/debian-security/ wheezy/updates main non-free contrib
# Squeeze
deb http://mirrors.163.com/debian/ squeeze main non-free contrib deb http://mirrors.163.com/debian/ squeeze-updates main non-free contrib deb http://mirrors.163.com/debian/ squeeze-lts main non-free contrib deb-src http://mirrors.163.com/debian/ squeeze main non-free contrib deb-src http://mirrors.163.com/debian/ squeeze-updates main non-free contrib deb-src http://mirrors.163.com/debian/ squeeze-lts main non-free contrib deb http://mirrors.163.com/debian-security/ squeeze/updates main non-free contrib deb-src http://mirrors.163.com/debian-security/ squeeze/updates main non-free contrib deb http://mirrors.163.com/debian-backports/ squeeze-backports main contrib non-free deb-src http://mirrors.163.com/debian-backports/ squeeze-backports main contrib non-free
deb http://ftp.cn.debian.org/debian/ jessie-proposed-updates main contrib non-free
deb-src http://ftp.cn.debian.org/debian/ jessie-proposed-updates main contrib non-free
deb-amd64http://ftp.cn.debian.org/debian-security jessie/updates main contrib non-free
阿里云的源
1 2 3 4
deb http://mirrors.aliyun.com/debian/ wheezy main non-free contrib deb http://mirrors.aliyun.com/debian/ wheezy-proposed-updates main non-free contrib deb-src http://mirrors.aliyun.com/debian/ wheezy main non-free contrib deb-src http://mirrors.aliyun.com/debian/ wheezy-proposed-updates main non-free contrib
对于Debian7.8的版本，被归档了，我试了一下只有下面的这个可以用
1
deb http://archive.debian.org/debian/ wheezy main contrib non-free
Reading UV FITS file: 3C219.L(A.butDefinitelyB).postProc.uvf AN table 1: 2454 integrations on 406 of 406 possible baselines. Apparent sampling: 0.732128 visibilities/baseline/integration-bin. Found source: 3C219
There are 2 IFs, and a total of 2 channels:
IF Channel Frequency Freq offset Number of Overall IF origin at origin per channel channels bandwidth ------------------------------------------------------------- (Hz) 01 1 1.385e+09 2.5e+07 1 2.5e+07 02 2 1.665e+09 2.5e+07 1 2.5e+07
IF Channel Frequency Freq offset Number of Overall IF origin at origin per channel channels bandwidth ------------------------------------------------------------- (Hz) 01 1 1.385e+09 2.5e+07 1 2.5e+07 02 2 1.665e+09 2.5e+07 1 2.5e+07
Data characteristics: Recorded units are UNCALIB. Recorded polarizations: RR LL RL LR Phases are rotated 0 mas East and 0 mas North. UVW coordinates are rotated by 0 degrees clockwise. Scale factor applied to FITS data weights: 1 Coordinate projection: SIN
Summary of overall dimensions: 1 sub-arrays, 2 IFs, 2 channels, 2454 integrations 4 polarizations, and up to 406 baselines per sub-array
Time related parameters: Reference date: 1986 day 249/00:00:00 (1986 Sep 06) Julian Date: 2446679.50, Epoch J1986.678 GAST at reference date: 22 59 10.041 Coherent integration time = 0.0 sec Incoherent integration time = 0.0 sec Sum of scan durations = 26460 sec UT range: 249/09:51:21 to 249/23:30:22 Mean epoch: JD 2446680.195 = J1986.680
此时在启动目录会生成一个log文件difmap.log，这个文件记录了你在DIFMAP交互环境中输入的所有命令。 It will also include selected output lines though they will be preceded by a ! in order to comment them out. 这个log文件可以通过一种脚本的形式来使用，可以通过在交互命令中输入 @difmap.log来执行这个脚本。 但需要注意的是这个脚本无法与PGPLOT进行交互，所以交互式的flagging都不会发生。所以要特别注意这一点。
The next step is to choose the Stokes parameter you are interested in:
1 2 3 4
0> select i
Where i refers to the Stokes I parameter. You can select any Stokes parameter (e.g. select q or u) to work with.
Host remote HostName 192.168.254.123 Port 22 Userhero IdentityFile ~/.ssh/id_rsa
The Ultimate Guide to SSH - Setting Up SSH Keys
Welcome to our ultimate guide to setting up SSH (Secure Shell) keys. This tutorial will walk you through the basics of creating SSH keys, and also how to manage multiple keys and key pairs.
Create a New SSH Key Pair
Open a terminal and run the following command:
1
ssh-keygen
You will see the following text:
1 2
Generating public/private rsa key pair. Enter file in which to save the key (/home/username/.ssh/id_rsa):
Press enter to save your keys to the default /home/username/.ssh directory.
Then you’ll be prompted to enter a password:
1
Enter passphrase (empty for no passphrase):
It’s recommended to enter a password here for an extra layer of security. By setting a password, you could prevent unauthorized access to your servers and accounts if someone ever gets a hold of your private SSH key or your machine.
After entering and confirming your password, you’ll see the following:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Your identification has been saved in /home/username/.ssh/id_rsa. Your public key has been saved in /home/username/.ssh/id_rsa.pub. The key fingerprint is: SHA256:/qRoWhRcIBTw0D4KpTUyK6YepyL6RQ2CQrtWsaicCb4 username@871e129f767b The key's randomart image is: +---[RSA 2048]----+ | .o=+.... | |+.*o+o . | |+X.=o o | |@.=.oo . | |=O ...o S | |o.oo . . | |.E+ . . . . | |oo . ... + | |=.. .o. . . | +----[SHA256]-----+
You now have a public and private SSH key pair you can use to access remote servers and to handle authentication for command line programs like Git.
Manage Multiple SSH Keys
Though it’s considered good practice to have only one public-private key pair per device, sometimes you need to use multiple keys or you have unorthodox key names. For example, you might be using one SSH key pair for working on your company’s internal projects, but you might be using a different key for accessing a client’s servers. On top of that, you might be using a different key pair for accessing your own private server.
Managing SSH keys can become cumbersome as soon as you need to use a second key. Traditionally, you would use ssh-add to store your keys to ssh-agent, typing in the password for each key. The problem is that you would need to do this every time you restart your computer, which can quickly become tedious.
A better solution is to automate adding keys, store passwords, and to specify which key to use when accessing certain servers.
SSH config
Enter SSH config, which is a per-user configuration file for SSH communication. Create a new file: ~/.ssh/config and open it for editing:
1
nano ~/.ssh/config
Managing Custom Named SSH key
The first thing we are going to solve using this config file is to avoid having to add custom-named SSH keys using ssh-add. Assuming your private SSH key is named ~/.ssh/id_rsa, add following to the config file:
1 2 3 4 5
Host github.com HostName github.com User git IdentityFile ~/.ssh/id_rsa IdentitiesOnly yes
Next, make sure that ~/.ssh/id_rsa is not in ssh-agent by opening another terminal and running the following command:
1
ssh-add -D
This command will remove all keys from currently active ssh-agent session.
Now if you try closing a GitHub repository, your config file will use the key at ~/.ssh/ida_rsa.
Here are some other useful configuration examples:
1 2 3 4 5
Host bitbucket-corporate HostName bitbucket.org User git IdentityFile ~/.ssh/id_rsa_corp IdentitiesOnly yes
Now you can use git clone git@bitbucket-corporate:company/project.git
1 2 3 4 5
Host bitbucket-personal HostName bitbucket.org User git IdentityFile ~/.ssh/id_rsa_personal IdentitiesOnly yes
Now you can use git clone git@bitbucket-personal:username/other-pi-project.git
1 2 3 4 5 6 7
Host myserver HostName ssh.username.com Port 1111 IdentityFile ~/.ssh/id_rsa_personal IdentitiesOnly yes User username IdentitiesOnly yes
Now you can SSH into your server using ssh myserver. You no longer need to enter a port and username every time you SSH into your private server.
Password management
The last piece of the puzzle is managing passwords. It can get very tedious entering a password every time you initialize an SSH connection. To get around this, we can use the password management software that comes with macOS and various Linux distributions.
For this tutorial we will use macOS’s Keychain Access program. Start by adding your key to the Keychain Access by passing -K option to the ssh-add command:
1
ssh-add -K ~/.ssh/id_rsa_whatever
Now you can see your SSH key in Keychain Access:
But if you remove the keys from ssh-agent with ssh-add -D or restart your computer, you will be prompted for password again when you try to use SSH. Turns out there’s one more hoop to jump through. Open your SSH config file by running nano ~/.ssh/config and add the following:
1 2 3
Host * AddKeysToAgent yes UseKeychain yes
With that, whenever you run ssh it will look for keys in Keychain Access. If it finds one, you will no longer be prompted for a password. Keys will also automatically be added to ssh-agent every time you restart your machine.
Now that you know the basics of creating new SSH keys and managing multiple keys, go out and ssh to your heart’s content!
图标，会打开如下所示的界面，在左侧中选择keymap即可。
