Recently I learned to build a Linux server as a cross-compilation host. The server side chose the Ubuntu 12.04 LTS desktop version, the client uses the Windows XP platform, and the SSH tool software putty is used to log in to the Linux host, and the scrathbox2 cross-compilation environment tool is established. Chain, simulated arm environment.
The main steps are as follows:
**1. Install Ubuntu 12.04 LTS desktop version using U disk. **
Use UtralIOS Floppy to make a USB boot disk for Ubuntu 12.04 desktop version, and then install Ubuntu 12.04 on the computer.
You can refer to these two articles: [U disk installation Ubuntu12.04] (http://www.cnblogs.com/zjfdbz/archive/2012/10/15/2725263.html) and [Ubuntu 12.04 hard disk installation and U disk installation (graphic)] (http://www.bjwilly.com/archives/325.html)
The most important thing is partitioning. This depends on the specific situation. Since it is used as a Linux host, the hard disk size is 500G and 4G memory, so I chose the three partition scheme:
Disk partition Mount directory Size File system
sda1 / 50G ext4
sda5 /swap 4G ext4
sda6 /home 446G ext4
**Second, configure the network, apt-get agent installation software, company Internet agent, etc. **
I followed the method similar to this blog post ubuntu12.04 server configuration network to modify the network configuration file /etc/network/interfaces without success, and finally edited the network directly, using the [System Settings]->[NetWork] interface The way to edit the network configuration is to enter the IP address, subnet mask, gateway, DNS server address, etc. You can refer to this article in Baidu Library: How to manually set IP under Ubuntu 11.04.
In addition, because our company has set up a proxy, you can only surf the Internet through the proxy, and you need to set the proxy URL in the proxy.
In addition, about setting up apt-get agent to install related software, please refer to this article: Ubuntu 12.04 apt-get/wget/gem using agent installation software
Three, configure NFS, TFTP
(1) Configure nfs
First install nfs, use the following command:
sudo apt-get install nfs-kernel-server
Mainly modify the /etc/exports file, you can refer to this article: NFS configuration of ubuntu12.04
My modified /etc/exports configuration file is as follows:
# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes hostname1(rw,sync,no_subtree_check)hostname2(ro,sync,no_subtree_check)
#
# Example for NFSv4:
# /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)
# /srv/nfs4/homes gss/krb5i(rw,sync,no_subtree_check)
#
# /*(ro,sync,no_subtree_check,no_root_squash)/home *(rw,sync,no_subtree_check,no_root_squash)
(2) Configure tftp
Install tftp client
sudo apt-get install tftpd
Then modify the /etc/inetd.conf configuration file.
You can refer to this article: Installation, setting, and debugging of tftp server built on ubuntu 12.04
Mainly modify the two configuration files /etc/xinetd.d/tftp and /etc/inetd.conf:
A、/etc/xinetd.d/tftp
service tftp
{
disable = no
socket_type = dgram
protocol = udp
wait = yes
user = root
server =/usr/sbin/in.tftpd
server_args =/
source =11
cps =1002
flags =IPv4
}
B 、/etc/inetd.conf
# /etc/inetd.conf: see inetd(8)for further informations.
#
# Internet superserver configuration database
#
#
# Lines starting with"#:LABEL:" or "#<off>#" should not
# be changed unless you know what you are doing!
#
# If you want to disable an entry so it isn't touched during
# package updates just comment it out with a single '#' character.
#
# Packages should modify this file by using update-inetd(8)
#
# < service_name><sock_type><proto><flags><user><server_path><args>
#
#: INTERNAL: Internal services
# discard stream tcp nowait root internal
# discard dgram udp wait root internal
# daytime stream tcp nowait root internal
# time stream tcp nowait root internal
#: STANDARD: These are standard services.
#: BSD: Shell, login, exec and talk are BSD protocols.
#: MAIL: Mail, news and uucp services.
#: INFO: Info services
#: BOOT: TFTP service is provided primarily for booting. Most sites
# run this only on machines acting as"boot servers."
# tftp dgram udp4 wait nobody /usr/sbin/tcpd /usr/sbin/in.tftpd --tftpd-timeout 300--retry-timeout 5--mcast-port 1758--mcast-addr 239.239.239.0-255--mcast-ttl 1--maxthread 100--verbose=5/srv/tftp
#: RPC: RPC based services
#: HAM-RADIO: amateur-radio services
#: OTHER: Other services
# tftp dgram udp wait nobody /usr/sbin/tcpd /usr/sbin/in.tftpd /home
tftp dgram udp wait nobody /usr/sbin/tcpd /usr/sbin/in.tftpd /
4. Assign accounts to all employees in the department under the /home directory
Mainly use the adduser command, you will be prompted to assign a password for each account.
Five, configure Samba service
Create a Samba service for ordinary users in the fourth step, so that they can share their ordinary user directories in the /home directory under Ubuntu 12.04 under windows.
Install samba, the command is as follows:
samba installation
sudo apt-get install samba
sudo apt-get install smbfs
Modify the /etc/samba/smb.conf configuration file.
You can refer to this blog post: Configure Samba Sharing Service on Ubuntu 12.04
My /etc/samba/smb.conf configuration file is as follows:
#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown inthis example
#
# Some options that are often worth tuning have been included as
# commented-out examples inthis file.
# - When such options are commented with";", the proposed setting
# differs from the default Samba behaviour
# - When commented with"#", the proposed setting is the default
# behaviour of Samba but the option is considered important
# enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# " testparm" to check that you have not made any basic syntactic
# errors.
# A well-established practice is to name the original file
# " smb.conf.master" and create the "real" config file with
# testparm -s smb.conf.master >smb.conf
# This minimizes the size of the really used smb.conf file
# which, according to the Samba Team, impacts performance
# However, use thiswith caution if your smb.conf file contains nested
# " include" statements. See Debian bug #483187for a case
# where using a master file is not a good idea.
#
#======================= Global Settings =======================[global]
## Browsing/Identification ###
# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = CSDN_WorkGroup
# server string is the equivalent of the NT Description field
server string = MyServer
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
# wins support = no
# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z
# This will prevent nmbd to search for NetBIOS names through DNS.
dns proxy = no
# What naming service and in what order should we use to resolve host names
# to IP addresses
; name resolve order = lmhosts host wins bcast
#### Networking ####
# The specific setof interfaces / networks to bind to
# This can be either the interfacename or an IP address/netmask;
# interfacenames are normally preferred
; interfaces =127.0.0.0/8 eth0
# Only bind to the named interfaces and/or networks; you must use the
# ' interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However,this
# option cannot handle dynamic or non-broadcast interfaces correctly.; bind interfaces only = yes
#### Debugging/Accounting ####
# This tells Samba to use a separate log file for each machine
# that connects
log file =/var/log/samba/log.%m
# Cap the size of the individual log files(in KiB).
max log size =1000
# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
# syslog only = no
# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
syslog =0
# Do something sensible when Samba crashes: mail the admin a backtrace
panic action =/usr/share/samba/panic-action %d
####### Authentication #######
# " security = user" is always a good idea. This will require a Unix account
# inthis server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc packagefor details.
security = user
# You may wish to use password encryption. See the section on
# ' encrypt passwords'in the smb.conf(5) manpage before enabling.; encrypt passwords = yes
# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.; passdb backend = tdbsam
obey pam restrictions = yes
# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
unix password sync = yes
# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set(thanks to Ian Kahan <<[email protected]>for
# sending the correct chat script for the passwd program in Debian Sarge).
passwd program =/usr/bin/passwd %u
passwd chat =*Enter\snew\s*\spassword:*%n\n *Retype\snew\s*\spassword:*%n\n *password\supdated\ssuccessfully*.
# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# ' passwd program'. The default is 'no'.
pam password change = yes
# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
map to guest = bad user
########## Domains ###########
# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
#
; domain logons = yes
#
# The following setting only takes effect if'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server(see below); logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# ( this is Samba's default)
# logon path = \\%N\%U\profile
# The following setting only takes effect if'domain logons' is set
# It specifies the location of a user's home directory(from the client
# point of view); logon drive = H:
# logon home = \\%N\%U
# The following setting only takes effect if'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in'DOS' file format convention
; logon script = logon.cmd
# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe. The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script =/usr/sbin/adduser --quiet --disabled-password --gecos ""%u
# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe.
# The following assumes a "machines" group exists on the system
; add machine script =/usr/sbin/useradd -g machines -c "%u machine account"-d /var/lib/samba -s /bin/false%u
# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.; add group script =/usr/sbin/addgroup --force-badname %g
########## Printing ##########
# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
# load printers = yes
# lpr(ng) printing. You may wish to override the location of the
# printcap file
; printing = bsd
; printcap name =/etc/printcap
# CUPS printing. See also the cupsaddsmb(8) manpage in the
# cupsys-client package.; printing = cups
; printcap name = cups
############ Misc ############
# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include =/home/samba/etc/smb.conf.%m
# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
# SO_RCVBUF=8192 SO_SNDBUF=8192
# socket options = TCP_NODELAY
# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.; message command =/bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s'&
# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC(a secondary logon server), you
# must setthis to 'no'; otherwise, the default behavior is recommended.
# domain master = auto
# Some defaults forwinbind(make sure you're not using the ranges
# for something else.); idmap uid =10000-20000; idmap gid =10000-20000; template shell =/bin/bash
# The following was the default behaviour in sarge,
# but samba upstream reverted the default because it might induce
# performance issues in large organizations.
# See Debian bug #368251for some of the consequences of*not*
# having this setting and smb.conf(5)for details.; winbind enum groups = yes
; winbind enum users = yes
# Setup usershare options to enable non-root users to share folders
# with the net usershare command.
# Maximum number of usershare.0(default) means that usershare is disabled.; usershare max shares =100
# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
usershare allow guests = yes
username map =/etc/samba/smbusers
; guest ok = no
; guest account = nobody
#======================= Share Definitions =======================
# Un-comment the following(and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home director as \\server\username
[ homes]
comment = Home Directories
browseable = no
# By default, the home directories are exported read-only. Change the
# next parameter to 'no'if you want to be able to write to them.; read only = yes
read only = no
# File creation mask is set to 0700for security reasons. If you want to
# create files with group=rw permissions,set next parameter to 0775.; create mask =0700
create mask =0775
# Directory creation mask is set to 0700for security reasons. If you want to
# create dirs.with group=rw permissions,set next parameter to 0775.; directory mask =0700
directory mask =0775
# By default, \\server\username shares can be connected to by anyone
# with access to the samba server. Un-comment the following parameter
# to make sure that only "username" can connect to \\server\username
# The following parameter makes sure that only "username" can connect
#
# This might need tweaking when using external authentication schemes
; valid users =%S
# Un-comment the following and create the netlogon directory for Domain Logons
# ( you need to configure Samba to act as a domain controller too.);[netlogon]; comment = Network Logon Service
; path =/home/samba/netlogon
; guest ok = yes
; read only = yes
# Un-comment the following and create the profiles directory to store
# users profiles(see the "logon path" option above)
# ( you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[ profiles]; comment = Users profiles
; path =/home/samba/profiles
; guest ok = no
; browseable = no
; create mask =0600; directory mask =0700;[printers]; comment = All Printers
; browseable = no
; path =/var/spool/samba
; printable = yes
; guest ok = no
; read only = yes
; create mask =0700
# Windows clients look forthis share name as a source of downloadable
# printer drivers
;[ print$]; comment = Printer Drivers
; path =/var/lib/samba/printers
; browseable = yes
; read only = yes
; guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin'with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
; write list = root, @lpadmin
# A sample share for sharing your CD-ROM with others.;[cdrom]; comment = Samba server's CD-ROM
; read only = yes
; locking = no
; path =/cdrom
; guest ok = yes
# The next two parameters show how to auto-mount a CD-ROM when the
# cdrom share is accesed. For this to work /etc/fstab must contain
# an entry like this:
#
# /dev/scd0 /cdrom iso9660 defaults,noauto,ro,user 00
#
# The CD-ROM gets unmounted automatically after the connection to the
#
# If you don't want to use auto-mounting/unmounting make sure the CD
# is mounted on /cdrom
#
; preexec =/bin/mount /cdrom
; postexec =/bin/umount /cdrom
It is mainly based on the original /etc/samba/smb.conf configuration file to turn on some default comment switches. But the premise is to install the samba service, that is, you need to install samba
And smbfs.
6. Install and develop related software
The software list is as follows:
1、vim
2、subversion
Svn client version control tool software, after installation, you can use svn and other commands to check out or update the project to perform version control management on the source code of the project
3、pulseaudio
4、tftpd
5、tftp
6、nfs-kernel-server
7、openbsd-inetd
8、samba
9、openssh-server
You can use the sudo apt-get installvim command to install the vim editor, and other software installation methods are the same.
Note: If you use a company agent, you must modify the /etc/apt/apt.conf configuration file, otherwise the software cannot be installed smoothly.
**Seven, build scraphbox2 cross-compilation tool chain, including qemu, arm-gcc, rpm, kernel, etc. **
Things like these are best written as Shell automatic scripts, including the initialization of the scrathbox environment, the production of rootfs for the root file system of a specific development board, rpm software packaging, libtool tools, and so on.
to sum up
I feel that the difficulty of building a cross-compiler server lies in:
You should know which software and services should be installed according to actual needs, such as general tftp service, nfs service, samba service and so on.
Know how to modify the configuration file for the above services. This is also a difficult point. You need experienced people to guide or find relevant information online.
Recommended Posts