Thinstation

Téléchargement et démarrage

A partir la page d'accueil du site .

Copier l'archive Thinstation-2.2.2.tar.gz dans un répertoire, puis la décompresser

tar -zxvf Thinstation-2.2.2.tar.gz

.

Un nouveau répertoire Thinstation est créé contenant divers fichiers et répertoire.

Utiliser thinstation 2.3 permet d'accéder aux fonctions wake on lan

utilisation de base

Les fichiers importants

Pour préparer un noyau, il faut taper la commande ./build. Avant cela, il faut renseigner le fichier build.conf en enlevment le commentaire (#) devant les lignes nécessaires.

Ce fichier se décompose en trois parties:

  1. Les modules (drivers) nécessaires au bon fonctionnement du client.
  2. Les packages, qui sont des programmes ou utilitaires que l'on peut charger de différentes façons, soit intégrés au noyau (package) , soit téléchargé depuis le serveur tftp (pkg)
  3. Les fichiers de configuration divers (mot de passe root et autres)

un deuxième fichier ficher permet de configurer le comportement de la station: il s'appelle thinstation.conf.buildtime.

Un fichier exemple se trouve ici

On peut ajouter divers configuration en fonction des modules choisis, par exemple ici on indique qu'il faut se connecter sur un serveur X externe

SESSION_0_TYPE=x
SESSION_0_AUTOSTART=on
SESSION_0_type_SERVER=192.168.254.1

En troisième lieu, on peut placer des fichiers de configuration supplémentaires dans le répertoire du serveur tftp. Mais cela dépend du système de chargement choisi.

Quand les noyaux sont prêts, on peut trouver les différentes versions dans le répertoire boot-images.

Le boot de type etherboot

Il semblerait que le boot de type pxe soit préférable ! avis aux amateurs

Comment procéder

On suppose que le serveur est prêt (connexion graphique externe possible, serveur dhcp, tftp)

Le plus simple est de partir d'un exemple précis:

ceci n'est qu'un exemple qui ne représente pas forcément la meilleure solution.

Dans le répertoire thinstation , le fichier build.conf contient les drivers, le fichier thinstation.conf.buildtime contient les trois lignes :

SESSION_0_TYPE=x
SESSION_0_AUTOSTART=on
SESSION_0_type_SERVER=192.168.254.1

a la fin du fichier buil.conf, la ligne suivante a été modifier (histoire de comprendre un peu)

param basepath       cl 

La commande ./build a été lancée .

Dans le répertoire sur le serveur : /var/lib/tftpboot : On trouve les deux fichiers thinstation.nbi thinstation.nbi.zpxe ainsi que le répertoire cl.

Dans le répertoire cl, on trouve:

  • thinstation.hosts
# HOST		MAC		GROUPS			COMMENTS
tx01	 	001E0B3A750E	215	 		# Salle college

Je pense que c'est le premier fichier externe lu par le client, quand il démarre.

  • thinstation.conf.group-215, qui ne contient rien, mais dans lequel on peut mettre des instructions pour les groupes de machines définies dans host
  • thinstation.conf.network qui doit être lu par toutes les stations
KEYBOARD_MAP=fr_fr
SCREEN_RESOLUTION="1280x1024 | 1024x678 | 800x600 | 640x480 | *"
SCREEN_COLOR_DEPTH="16 | 8 | 24 | *"
  • thinstation.conf-tx01 qui n'est lu que par la station
SAMBA_USB=On
SAMBA_SERVER_ENABLED=On
SAMBA_WORKGROUP=BigPeople
SAMBA_SECURITY=Server
SAMBA_SERVER=192.168.254.1
SAMBA_HARDDISK=Off

Ces trois fichiers peuvent se paramétrer en tilisant les exemples donnés dans ce ficher , attention toutefois, certaines instructions ne sont valables que pour le fichier thinstation.conf.buildtime , ce qui est indiqué par :

# -- For use in thinstation.conf.buildtime only:

Fonctions supplémentaires

Wake et stop on lan

Pour activer le wake on lan sur les clients (qui doivent posséder cette fonction, par exemple, regarder si une fois les client hors tension , les cartes réseaux d'être actives) Il faut installer un paquet nomme etherwake sur le serveur . Pour que les clients puissent être réveillé, il faut qu'il soit éteints correctement .

Dans le répertoire packages/base/bin il faut créer un fichier nommé par exemple stop

#! /bin/sh
/bin/ethtool -s eth0 wol g
/bin/poweroff

Qui permet d'éteindre le client en laissant actif la carte réseau pour le wake on lan. Ce script sera à lancer sur le client depuis le serveur, pour ce faire, il faut activer sshd sur le client. Décommenter la ligne

package sshd   

dans le fichier build.conf

Ensuite, il faut installer un système de clef entre le client et le serveur , puis faire en sorte que l'ensemble fonctionne après chaque démarrage du client , voici une piste, par forcément la meilleure,mais qui fonctionne :

Démarrer le client, sur le serveur lancer au nom de l'utilisateur qui se connectera la commande qui va générer les clefs:

ssh-keygen -t rsa

Ne pas entrer de passe phrase

copier la nouvelle clef sur le client 
ssh-copy-id -i ~/.ssh/id_rsa.pub root@ip-du-client
le mot de passe root est demandé (par defaut pleasechangeme, à modifier dans le fichier build.conf)

On peut peut-être copier directement la clef .ssh/id_rsa.pub en Thinstation-2.3/packages/sshd/etc/.model/authorized_keys à voir …

Ensuite, il faut copier sur une clef usb ou par le lan le fichier /root/ssh/authorized_keys présent sur le client dans le répertoire Thinstation-2.3/packages/sshd/etc/.model/ présent sur le serveur, à la prochaine construction d'image, on pourra se loguer depuis le serveur sur le client et lancer la commande .

ssh root@ipclient stop

pour éteindre la machine et pour la démarrer :

etherwake -i ethx adressemac:client

ethx est la carte qui point vers le lan des clients légers

Si on prépare l'ensemble sur un serveur de test et qu'on veut le récupérer sur une autre machine

accès au périphériques type dd ou usb

Attention, en cours d'écriture

Sur le serveur, on modifie avant compilation le fichier /home/directeur/Bureau/Thinstation-2.3/packages/samba-base/lib/smb.conf.tpl

pour lui donner ce contenu:

[global]

# workgroup = NT-Domain-Name or Workgroup-Name
   workgroup = $SAMBA_WORKGROUP

# server string is the equivalent of the NT Description field
   server string = TS $TS_VERSION - $CLIENT_IP
	netbios name = %m

# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
;   hosts allow = 192.168.1. 192.168.2. 127.

# if you want to automatically load your printer list rather
# than setting them up individually then you'll need this
   printcap name = $LPR_ROOT/etc/printcap
   load printers = yes
#   load printers = no

# It should not be necessary to spell out the print system type unless
# yours is non-standard. Currently supported print systems include:
# bsd, sysv, plp, lprng, aix, hpux, qnx
   printing = lprng

# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
;  guest account = pcguest

# this tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba.log

lock directory = /var/lock

# Put a capping on the size of the log files (in Kb).
   max log size = 10

# Security mode. Most people will want user level security. See
# security_level.txt for details.
   security = $SAMBA_SECURITY

# Use password server option only with security = server
# The argument list may include:
#   password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
#   password server = *
   password server = $SAMBA_SERVER

# Password Level allows matching of _n_ characters of the password for
# all combinations of upper and lower case.
;  password level = 8
;  username level = 8

# You may wish to use password encryption. Please read
# ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation.
# Do not enable this option unless you have read those documents
   encrypt passwords = yes
   smb passwd file = /lib/smbpassword

   private dir = /lib
   lock directory = /var/lock
   pid directory = /var/lock

# Unix users can map to different SMB User names
;  username map = $LPR_ROOT/lib/smbusers

# 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 = $SAMBA_ROOT/lib/smb.conf.%m

# This parameter will control whether or not Samba should obey PAM's
# account and session management directives. The default behavior is
# to use PAM for clear text authentication only and to ignore any
# account or session management. Note that Samba always ignores PAM
# for authentication in the case of encrypt passwords = yes

;  obey pam restrictions = yes

# Most people will find that this option gives better performance.
# See speed.txt and the manual pages for details
   socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192

# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
;   interfaces = 192.168.12.2/24 192.168.13.2/24 

# Configure remote browse list synchronisation here
#  request announcement to, or browse list sync from:
#	a specific host or from / to a whole subnet (see below)
;   remote browse sync = 192.168.3.25 192.168.5.255
# Cause this host to announce itself to local subnets here
;   remote announce = 192.168.1.255 192.168.2.44

# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
   local master = no

# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
;   os level = 33

# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
;   domain master = yes 

# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
;   preferred master = yes

# Enable this if you want Samba to be a domain logon server for 
# Windows95 workstations. 
;   domain logons = yes

# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
;   logon script = %m.bat
# run a specific logon batch file per username
;   logon script = %U.bat

# Where to store roving profiles (only for Win95 and WinNT)
#        %L substitutes for this servers netbios name, %U is username
#        You must uncomment the [Profiles] share below
;   logon path = \\%L\Profiles\%U

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
;   wins support = yes

# 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_ON   wins server = $SAMBA_WINS

# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one	WINS Server on the network. The default is NO.
;   wins proxy = yes

# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The built-in default for versions 1.9.17 is yes,
# this has been changed in version 1.9.18 to no.
   dns proxy = no 

# Case Preservation can be handy - system default is _no_
# NOTE: These can be set on a per share basis
;  preserve case = no
;  short preserve case = no
# Default case is normally upper case for all DOS files
;  default case = lower
# Be very careful with case sensitivity - it can break things!
;  case sensitive = no

print command =      $LPR_ROOT/bin/lpr  -P%p -r %s
lpq command   =      $LPR_ROOT/bin/lpq  -P%p
lprm command  =      $LPR_ROOT/bin/lprm -P%p %j
lppause command =    $LPR_ROOT/bin/lpc hold %p %j
lpresume command =   $LPR_ROOT/bin/lpc release %p %j
queuepause command = $LPR_ROOT/bin/lpc  stop %p
queueresume command = $LPR_ROOT/bin/lpc start %p

#============================ Share Definitions ==============================

$SAMBA_PRINTER[printers]
$SAMBA_PRINTER    comment = All Printers
$SAMBA_PRINTER    path = /var/spool/samba
$SAMBA_PRINTER    browseable = no
$SAMBA_PRINTER    public = $SAMBA_PUBLIC
$SAMBA_PRINTER    printable = yes

$SAMBA_HARDDISK[harddisk]
$SAMBA_HARDDISK    comment = Hard disk
$SAMBA_HARDDISK    path = /mnt/disc
$SAMBA_HARDDISK    read only = no
$SAMBA_HARDDISK    public = $SAMBA_PUBLIC

$SAMBA_CDROM[cdrom]
$SAMBA_CDROM    comment = CDROM
$SAMBA_CDROM    path = /mnt/cdrom
$SAMBA_CDROM    read only = yes
$SAMBA_CDROM    public = $SAMBA_PUBLIC

$SAMBA_FLOPPY[floppy]
$SAMBA_FLOPPY   comment = Floppy
$SAMBA_FLOPPY   path = /mnt/floppy
$SAMBA_FLOPPY   read only = no
$SAMBA_FLOPPY   public = $SAMBA_PUBLIC

$SAMBA_USB[usb]
$SAMBA_USB   comment = USB Device
$SAMBA_USB   path = /mnt/usbdevice
$SAMBA_USB   read only = no
$SAMBA_USB   public = $SAMBA_PUBLIC

En réalité, l'authentification de fait sur le serveur , voici le fichier de conf du serveur /etc/samba/smb.conf

#
# 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 in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this 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 this with caution if your smb.conf file contains nested
# "include" statements. See Debian bug #483187 for 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 = reseau-215

# server string is the equivalent of the NT Description field
   server string = %h server (Samba, Ubuntu)

# 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 set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names 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
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for 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 <<kahan@informatik.tu-muenchen.de> 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 set this to 'no'; otherwise, the default behavior is recommended.
#   domain master = auto

# Some defaults for winbind (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 #368251 for 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

#======================= 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 directory 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

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
;   create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
;   directory mask = 0700

# 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
# 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
;   share modes = no

# 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 for this 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   0 0
#
# 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

une fois le client lancé et la clef usb introduite dans le port, le client peut récupérer les données de la clef si, sur le serveur on lance la commande :

smbmount ipduclient/usb /mnt/toto -o username=root,password=rootpasswd

 
clientleger/thinstation.txt · Dernière modification: 2014/10/23 08:30 (modification externe)
 
Sauf mention contraire, le contenu de ce wiki est placé sous les termes de la licence suivante : GNU Free Documentation License 1.3
Recent changes RSS feed Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki