Tabla de contenidos
This is the manual for the Debian Edu Stretch 9+edu0 release.
The version at http://wiki.debian.org/DebianEdu/Documentation/Stretch is a wiki and updated frequently.
Las Traduccionesson parte del paquete
debian-edu-doc
que puede ser instalado en
un servidor web, y que está disponible en línea.
Debian Edu a.k.a Skolelinux es una distribución basada en Debian, proporcionando un ambiente "fuera de la caja", completamente configurado para una red escolar.
Directly after installation of a school server all services needed for a school network are set up (see the next chapter details of the architecture of this setup) and the system is ready to be used. Only users and machines need to be added via GOsa², a comfortable Web-UI, or any other LDAP editor. A netbooting environment using PXE has also been prepared, so after initial installation of the main server from CD, Blu-ray disc or USB flash drive all other machines can be installed via the network, this includes "roaming workstations" (ones that can be taken away from the school network, usually laptops or netbooks) as well as PXE booting for diskless machines like traditional thin clients.
Múltiples aplicaciones educativas como celestia, drgeo, gcompris, kalzium, kgeography, solfege y scratch, han sido incluidas en el escritorio predeterminado, el cual puede fácilmente ser extendido casi ilimitadamente, vía el universo Debian.
Skolelinux es una distribución de Linux, hecha por el proyecto Debian Edu. Siendo una distribución mezclada de Debian es un sub-proyecto oficial de Debian
Lo que esto significa, es que Skolelinux es una versión de Debian que proporciona un ambiente "out of the box" de una red escolar completamente configurada.
The Skolelinux project in Norway was founded on July 2nd 2001 and about the same time Raphaël Hertzog started Debian-Edu in France. Since 2003 both projects are united, but both names stayed. "Skole" and (Debian-)"Education" are just two well understood terms in these regions.
En Noruega, donde Skolelinux se inició, el grupo principal de alcance son las escuelas con grupos de estudiantes desde los 6 a 16 años. Actualmente, el sistema es utilizado en muchos países alrededor del mundo, con un número mayor en Noruega, España, Alemania y Francia.
Esta sección del documento describe la arquitectura de red y los servicios proporcionados por una instalación Skolelinux.
The figure is a sketch of the assumed network topology. The default setup of a Skolelinux network assumes that there is one (and only one) main server, while allowing the inclusion of both normal workstations and LTSP servers (with associated thin clients and/or diskless workstations). The number of workstations can be as large or small as you want (starting from none to a lot). The same goes for the LTSP servers, each of which is on a separate network so that the traffic between the clients and the LTSP server doesn't affect the rest of the network services.
The reason that there can only be one main server in each school network is that the main server provides DHCP, and there can be only one machine doing so in each network. It is possible to move services from the main server to other machines by setting up the service on another machine, and subsequently updating the DNS configuration, pointing the DNS alias for that service to the right computer.
Para simplificar la configuración estándar de Skolelinux, la conexión a Internet va sobre un router separado. Se puede configurar Debian con un módem o una conexión RDSI, sin embargo no se ha intentando hacer tal configuración para Skolelinux por defecto.(las modificaciones necesarias para ajustar la configuración por defecto a esta situación deberían documentarse por separado).
El DHCP en el servidor «Tjener» sirve la red 10.0.0.0/8 vía PXE Boot, en la que recibirá un menú de syslinux done podrá seleccionar si instalar un servidor nuevo / estación de trabajo, iniciar un cliente delgado, estación sin disco, prueba de memoria o iniciar desde disco local.
This is designed to be modified - that is, you can have the NFS-root in syslinux pointing to one of the LTSP servers or change the DHCP next-server option (stored in LDAP) to have clients directly boot via PXE from the terminal server.
El servicio DHCPD en el servidor LTSP únicamente ofrece una red dedicada en la segunda interfaz (las opciones preconfiguradas son 192.168.0.0/24 y 192.168.1.0/24) y raramente necesitan ser cambiadas.
La configuración de todas las subredes es almacenada en LDAP.
A Skolelinux network needs one main server (also called "tjener" which is Norwegian and means "server") which per default has the IP address 10.0.2.2 and is installed by selecting the Main Server profile. It's possible (but not required) to also select and install the LTSP Server and Workstation profiles in addition to the Main Server profile.
With the exception of the control of the thin clients, all services are initially set up on one central computer (the main server). For performance reasons, the LTSP server(s) should be separate (though it is possible to install both the Main Server and LTSP Server profiles on the same machine). All services are allocated a dedicated DNS-name and are offered exclusively over IPv4. The allocated DNS name makes it easy to move individual services from the main server to a different machine, by simply stopping the service on the main server, and changing the DNS configuration to point to the new location of the service (which should be set up on that machine first, of course).
Para garantizar la seguridad, siempre q ue se transmitan contraseñas por la red, se hace en canal encriptado. Por tanto, no se envía ninguna contraseña en texto plano.
Abajo se encuentra una lista de los servicios que se tienen por defecto en una red Skolelinux, con el nombre de DNS en cada servicio, Si es posible, todos los archivos de configuración harán referencia al servicio por su nombre (sin el nombre del dominio), haciendo más fácil para las escuelas el cambio de dominio (si se tiene un dominio DNS) o la dirección IP que utilizan.
Table of services | ||
Descripción de servicios |
Nombre común |
Nombre de servicio DNS |
Registros centralizados |
rsyslog |
syslog |
Sistema de Nombre de Dominio |
DNS (BIND) |
domain |
Configuración automática de equipos |
DHCP |
bootps |
Sincronización de reloj |
NTP |
ntp |
Directorios de usuarios vía sistema de archivos de red |
SMB / NFS |
homes |
Correo Electrónico |
IMAP (Dovecot) |
postoffice |
Servicio de Directorio |
OpenLDAP |
ldap |
Administración de usuarios |
GOsa² |
--- |
Servidor Web |
Apache/PHP |
www |
Respaldo Central |
sl-backup, slbackup-php |
backup |
Caché Web |
Proxy (Squid) |
webcache |
Impresión |
CUPS |
ipp |
Inicio de sesión remoto seguro |
OpenSSH |
ssh |
Configuración Automática |
Cfengine |
cfengine |
LTSP Server/s |
LTSP |
ltsp |
Network Block Device Server |
NBD |
--- |
Monitoreo de servicios y equipos, reportes de fallas, histórico vía web. Reportes de fallos vía correo. |
Munin, Icinga and Sitesummary |
sitesummary |
Cada usuario almacena sus archivos personales en su directorio home que está disponible en el servidor. Los directorios Home están accesibles desde todas las máquinas, dando a los usuarios acceso independientemente del puesto que estén usando. El servidor opera sin importar el sistema operativo. Ofrece tanto NFS para clientes UNIX, como SMB para Windows y clientes Macintosh.
By default email is set up for local delivery (i.e. within the school) only, though email delivery to the wider Internet may be set up if the school has a permanent Internet connection. Clients are set up to deliver mail to the server (using 'smarthost'), and users can access their personal mail through IMAP.
Todos los servicios usan el mismo nombre de usuario y contraseña, gracias a la base de datos centralizada para autenticación y autorización de usuarios.
Para incrementar el rendimiento al acceder frecuentente a los mismos sitios de internet hay un proxy que cachea localmente los archivos (Squid). Junto al bloqueo de tráfico web en el router este también permite el control de acceso a Internet individualmente para cada puesto.
Network configuration on the clients is done automatically using DHCP. All types of clients can be connected to the private 10.0.0.0/8 subnet and will get according IP addresses; LTSP clients should be connected to the corresponding LTSP server via the separate subnet 192.168.0.0/24 (this is to ensure that the network traffic of the LTSP clients doesn't interfere with the rest of the network services).
El registro de sucesos está centralizado, de forma que todas las computadoras envían sus mensajes al servidor. El servicio syslog está configurado para aceptar sólo mensajes entrantes desde la red local.
Por defecto, el servidor de DNS está configurado con un dominio para uso interno (*.intern), contra un servidor de DNS real ("externo") que puede configurarse. El servidor de DNS actua como un caché de DNS, de forma que todos los puestos de la red pueden usarlo como su servidor de DNS principal.
Los alumnos y profesores pueden publicar sitios web. El servidor web proporciona mecanismos para autenticar los usuarios, y para limitar el acceso a páginas individuales y subdirectorios a ciertos usuarios y grupos. Los usuarios pueden crear páginas web dinámicas, ya que el servidor web puede ejecutar programas del lado del servidor.
La información sobre las computadoras y los usuarios se puede cambiar en una ubicación central y es accesible a todos los ordenadores de la red automáticamente. Para conseguirlo, hay un servidor de directorio centralizado. El directorio tendrá información sobre los usuarios, grupos, máquinas y grupos de máquinas. Para evitar confusión entre los usuarios no habrá ninguna diferencia entre los grupos de archivos, listas de correo y grupos de red. Esto implica que los grupos de máquinas que tengan que estar en grupos de red, tienen el mismo tipo de nombre que los grupos de usuarios y listas de correo.
La administración de los usuarios y servicios se hace mediante web, y sigue estándares establecidos. Son funcionales en los navegadores que incluye Skolelinux. Es posible delegar algunas tareas a usuarios o grupos de usuarios mediante los sistemas de administración.
Para evitar algunos problemas con NFS, y hacer más simple la depuración de errores, es necesario sincronizar los relojes de todas las máquinas. Para lograr esto, el servidor Skolelinux tiene configurado un servidor NTP, y todas las estaciones y clientes se configuran para sincronizar sus relojes con el servidor. El servidor debe sincronizar su propio reloj mediante NTP con alguna de las máquinas disponibles en Internet para asegurarse de que toda la red tenga la hora correcta.
Printers are connected where convenient, either directly onto the main network, or connected to a server, workstation or LTSP server. Access to printers can be controlled for individual users according to the groups they belong to; this will be achieved by using quota and access control for printers.
A Skolelinux network can have many LTSP servers (which we called "thin client servers" in releases before Stretch), which are installed by selecting the LTSP Server profile.
The LTSP servers are set up to receive syslog from thin clients and workstations, and forward these messages to the central syslog recipient.
Please note: Thin clients are using the programs installed on the
server. Diskless workstations are using the programs installed in the
server's LTSP chroot, the client root filesystem is provided using NBD
(Network Block Device). After each modification to the LTSP chroot the
related NBD image has to be re-generated; run
ltsp-update-image
on the LTSP server.
Una configuración de cliente ligero permite a un PC ordinario funcionar como un terminal (X). Esto significa que la computadora arranca desde un disquete o desde el servidor a través de la red (usando network-PROM o PXE) sin usar el disco duro local. La configuración de cliente ligero que se usa es la de Linux Terminal Server Project (LTSP).
Thin clients are a good way to make use of older, weaker machines as they effectively run all programs on the LTSP server. This works as follows: the service uses DHCP and TFTP to connect to the network and boot from the network. Next, the file system is mounted from the LTSP server using NBD, and finally the X Window System is started. The display manager (LDM) connects to the LTSP server via SSH with X-forwarding. This way all data is encrypted on the network. For very old thin clients which are too slow for the encryption this can be set to the behavior from former versions, which is to use a direct X connection via XDMCP.
Las estaciones sin disco, también reciben los nombres de "clientes delgados", "clientes livianos", "estaciones tontas". Para efectos de claridad de este manual utilizaremos el término "estaciones sin disco".
Una estación sin disco, ejecuta todas las aplicaciones localmente, sin necesidad de un S.O instalado. Esto significa que el equipo, inicia las aplicaciones desde el servidor, sin necesidad de tener software instalado en un disco local.
Diskless workstations are an excellent way of reusing older (but powerful) hardware with the same low maintenance cost as with thin clients. Software is administered and maintained on the server with no need for local installed software on the clients. Home directories and system settings are stored on the server too.
Las estaciones sin disco, fueron presentadas como parte del proyecto LTSP (Linux Terminal Server Project) versión 5.0
All the Linux machines that are installed with the Skolelinux installer will be administrable from a central computer, most likely the server. It will be possible to log in to all machines via SSH (by default, root is not allowed to log in with password), and thereby have full access to the machines.
Toda la información de los usuarios se guarda en un directorio LDAP. Las actualizaciones de las cuentas de usuario se hacen contra esta base de datos, que es la que usan los clientes para autenticarse.
Actualmente hay dos medios de instalación: instalación por red desde un CD e instalación multi arquitectura desde un dispositivo USB. Ambos medios pueden ser cargados desde memorias USB.
The aim is to be able to install a server from any type of medium once, and install all other clients over the network by booting from the network.
Solo la instalación en red necesita acceso a Internet durante la instalación.
The installation should not ask any questions, with the exception of desired language (e.g. Norwegian Bokmål, Nynorsk, Sami) and machine profile (main server, workstation, LTSP server, ...). All other configuration will be set up automatically with reasonable values, to be changed from a central location by the system administrator subsequent to the installation.
Cada cuenta de usuario de Skolelinux tiene asignada una sección del sistema de archivos en el servidor de archivos. Esta sección (directorio home) contiene los archivos de configuración del usuario, documentos, correos electrónicos y páginas web. Algunos de los archivos deberían tener acceso de lectura para otros usuarios del sistema, algunos podrían ser de lectura para todos a través de Internet, y algunos no deberían ser accesibles por nadie que no fuera el usuario.
Para asegurar que todos los discos serán utilizados para directorios de
datos de los usuarios o directorios compartidos, pueden poseer nombres
únicos entre todas los ordenadores durante la instalación al ser montados
como /skole/host/directory/
. Inicialmente,
un directorio es creado en el servidor de archivos,
/skole/tjener/home0/
en el que todas las
cuentas de usuarios son creadas. Más directorios pueden ser creados cuando
sea necesario acomodar grupos de usuarios particulares o patrones
particulares de uso.
Para habilitar el acceso compartido de archivos según el sistema de permisos de UNIX, los usuarios necesitan ser parte de un grupo compartido adicional (como "students") así como al grupo inicial al que pertenecen de manera predeterminada.Si los usuarios tienen una umask apropiado para hacer artículos de nueva creación para compartir archivos en grupos accesibles (002 o 007), y si los directorios que están trabajando en son setgid para asegurar que los archivos hereden el grupo de la propiedad correcta, el resultado es controlada entre el miembros de un grupo.
The initial access settings for newly created files are a matter of
policy. The Debian default umask is 022 (which would not allow group-access
as described above), but Debian Edu uses a default of 002 - meaning that
files are created with read access for everybody, which can later be removed
by explicit user action. This can alternatively be changed (by editing
/etc/pam.d/common-session
) to a umask of
007 - meaning read access is initially blocked, necessitating user action to
make them accessible. The first approach encourages knowledge sharing, and
makes the system more transparent, whereas the second method decreases the
risk of unwanted spreading of sensitive information. The problem with the
first solution is that it is not apparent to the users that the material
they create will be accessible to all other users. They can only detect this
by inspecting other users' directories and seeing that their files are
readable. The problem with the second solution is that few people are likely
to make their files accessible, even if they do not contain sensitive
information and the content would be helpful to inquisitive users who want
to learn how others have solved particular problems (typically configuration
issues).
Hay diferentes formas de usar una solución Skolelinux. Puede instalarse en un sólo PC o en una amplia región con muchas escuelas operadas centralmente. Esta variedad de configuraciones hace una gran diferencia en la forma de configurar las cosas dependiendo de los elementos de red, servidores y puestos de cliente.
El propósito de los diferentes perfiles es explicado en el capítulo Arquitecturas de red.
If LTSP is intended to be used, take a look at the LTSP Hardware Requirements wiki page.
The computers running Debian Edu / Skolelinux must have either 32 bit (Debian architecture 'i386', oldest supported processors are 686 class ones) or 64 bit (Debian architecture 'amd64') x86 processors.
At least 12 GiB RAM for 30 thin clients and 20 GiB RAM for 50-60 thin clients are recommended for the main and LTSP server profiles.
Thin clients with only 256 MiB RAM and 400 MHz are possible, though more RAM and faster processors are recommended.
La paginación de memoria por red esta habilitada por defecto, tiene un
tamaño de 512Mb. Si necesita más, puede modificarlo desde la variable SIZE,
en el archivo /etc/ltsp/nbdswapd.conf
.
Si sus terminales tienen disco duro, se recomienda que sean utilizados para paginación, ya que resulta ser más rápida que la paginación por medio de la red.
For workstations, diskless workstations and standalone systems, 1000 MHz and 512 MiB RAM are the absolute minimum requirements. For running modern webbrowsers and LibreOffice at least 1024 MiB RAM is recommended.
En estaciones de trabajo con poca memoria RAM, el verificador ortográfico podría causar que LibreOffice deje de funcionar si el espacio de intercambio es demasiado pequeño. Si esto ocurre frecuentemente, puede ser deshabilitado por los administradores del sistema.
El requerimiento mínimo de espacio depende del perfil que sea instalado.
combined main server + LTSP server: 70 GiB. As usual with disk space on a main server, "the bigger the better".
LTSP server: 50 GiB.
Estación de trabajo, o independiente: 30 Gb
LTSP servers need two network cards when using the default network architecture:
eth0 conectada a la red principal (10.0.0.0/8),
eth1 is used for serving LTSP clients (192.168.0.0/24 as default), but others are possible.
Las laptops son estaciones de trabajo móviles, por lo que tienen los mismos requerimientos de las estaciones de trabajo regulares.
Una lista de hardware probado esta en http://wiki.debian.org/DebianEdu/Hardware/ . Esta lista no está
completa
http://wiki.debian.org/InstallingDebianOn es un esfuerzo para documentar el proceso de instalación, configuración y uso de Debian en hardware específico. Por lo tanto los potenciales compradores sabrán si su hardware es soportado y los propietarios podrán saber como obtener el máximo de sus equipos.
Una excelente base de datos sobre hardware soportado por Debian esta disponible en http://kmuto.jp/debian/hcl/.
Se aplican las siguientes reglas cuando se usa la arquitectura de red por defecto:
Necesita exactamente, un servidor principal, el tjener.
Puede tener hasta cientos de estaciones de trabajo en la red principal.
Puede tener muchos servidores LTSP en la red principal; dos subredes diferentes son preconfiguradas en LDAP, aunque pueden agregarse más.
Puede tener cientos de clientes ligeros y/o estaciones de trabajo sin disco en cada red de servidores LTSP.
Puede tener cientos de otras computadoras que tendrán direcciones IP asignadas de manera dinámica.
Para acceder a Internet necesita un enrutador/pasarela (ver más abajo).
Un enrutador/pasarela conectado a Internet en la interfaz externa y con la dirección IP 10.0.0.1 y máscara de red 255.0.0.0 en la interfaz interna, es necesario para conectarse a internet.
El enrutador no debería ejecutar un servidor DHCP, puede ejecutar un servidor DNS, aunque no es necesario y no será usado.
In case you already have a router but are unable to configure it like needed (not allowed to, technical reasons), a system with two network interfaces could be turned into a gateway if the Debian Edu 'Minimal' profile is installed.
After the installation:
Adjust the /etc/network/interfaces file.
Change the hostname permanently to 'gateway'.
Enable IP forwarding and NAT for the 10.0.0.0/8 network.
As an option install a firewall and / or a traffic shaping tool.
#!/bin/sh # Turn a system with profile 'Minimal' into a gateway/firewall. # sed -i 's/auto eth0/auto eth0 eth1/' /etc/network/interfaces sed -i '/eth1/ s/dhcp/static/' /etc/network/interfaces echo 'address 10.0.0.1' >> /etc/network/interfaces echo 'netmask 255.0.0.0' >> /etc/network/interfaces hostname -b gateway hostname > /etc/hostname service networking stop service networking start sed -i 's#NAT=#NAT="10.0.0.0/8"#' /etc/default/enable-nat service enable-nat restart # You might want a firewall (shorewall or ufw) and traffic shaping. #apt update #apt install shorewall # or #apt install ufw #apt install wondershaper
In case you are looking for a complete router firewall solution capable of running on an old PC, we recommend IPCop or floppyfw.
If you need something for an embedded router or accesspoint we recommend using OpenWRT, though of course you can also use the original firmware. Using the original firmware is easier; using OpenWRT gives you more choices and control. Check the OpenWRT webpages for a list of supported hardware.
Es posible usar una configuración diferente de red (existe un proceso documentado para hacer esto), pero si usted no tiene una infraestructura de red preexistente, le recomendamos abstenerse de hacerlo, y mantener la configuración predeterminada de la arquitectura de red.
We recommend that you read or at least take a look at the release notes for
Debian Stretch before you start installing a system for production
use. Please give Debian Edu/Skolelinux a try, it should just work.
Asegúrese de leer el capítulo Iniciando con
Debian Edu de este manual, ya que explica como iniciar sesión por
primera vez.
Even more information about the Debian Stretch release is available in its installation manual.
The netinstall CD, which also can be used for installation from USB flash drives, is suitable to install i386 and amd64 machines. As the name implies, internet access is required for the installation. It's available via
rsync -progress
ftp.skolelinux.org::skolelinux-cd/debian-edu-9+edu0-CD.iso
./debian-edu-9+edu0-CD.iso
The multi-architecture ISO image is 5.5 GiB large and can be used for installation of amd64 and i386 machines. Like the netinstall image it can be installed on USB flash drives or disk media of sufficient size. Please note that internet access is needed during installation if the 'LTSP Server' profile is chosen. Like the others it can be downloaded over HTTP or rsync via:
rsync
ftp.skolelinux.org::skolelinux-cd/debian-edu-9+edu0-USB.iso|debian-edu-9+edu0-USB.iso
For those without a fast Internet connection, we can offer a CD or DVD sent
for the cost of the CD or DVD and shipping. Just send an email to cd@skolelinux.no and we will discuss
the payment details (for shipping and media). Recuerde incluir la dirección a la que desea le sea envíado su CD / DVD
dentro del email.
When you do a Debian Edu installation, you have a few options to choose from. Don't be afraid; there aren't many. We have done a good job of hiding the complexity of Debian during the installation and beyond. However, Debian Edu is Debian, and if you want there are more than 52,000 packages to choose from and a billion configuration options. For the majority of our users, our defaults should be fine.
Installer boot menu on 64-bit Hardware
Instalador gráfico usa el instalador GTK donde puede usar el ratón.
Install uses text mode.
Advanced options > gives a sub menu with more detailed options to choose.
32-bit install options > allows a 32-bit installation on 64-bit hardware.
Help gives some hints on using the installer; see screenshot below.
Back.. brings back to the main menu.
Graphical expert install gives access to all available questions, mouse usable.
Graphical rescue mode makes this install medium become a rescue disk for emergency tasks.
Instalación automática gráfica necesita un archivo preconfigurado.
Instalación experta le da acceso a todas las opciones disponibles en modo texto.
Rescue mode text mode; makes this install medium become a rescue disk for emergency tasks.
Automated install text mode; needs a preseed file.
Installer boot menu on 32-bit Hardware
Explanations are similar to those for 64-bit hardware.
Help screen
This Help screen is self explaining and enables the <F>-keys on the keyboard for getting more detailed help on the topics described.
Add or change boot parameters for installations
In both cases, boot options can be edited by pressing the TAB key in the boot menu; the screenshot shows the command line for Graphical install.
Puede utilizar un servicio proxy HTTP existente en la red para agilizar la
instalación del servidor principal desde CD. Agregue
mirror/http/proxy=http://10.0.2.2:3128/
como un parámetro adicional de carga.
Si ya tiene instalador el perfil de servidor principal en una computadora, futuras instalaciones se podrían hacer vía PXE, ya que utilizará automáticamente el proxy del servidor principal.
To install the GNOME desktop instead of
the default KDE Plasma desktop, replace
kde with gnome in the desktop=kde
parameter.
To install the LXDE desktop instead, use
desktop=lxde
. (Recommended if LTSP is
intended to be used.)
To install the Xfce desktop instead, use
desktop=xfce
.
And to install the MATE desktop instead,
use desktop=mate
.
Remember the system requirements and make sure you have at least two network cards (NICs) if you plan on setting up an LTSP server.
Choose a language (for the installation and the installed system).
Elige un lugar que normalmente sería el lugar donde vives.
Choose a keyboard keymap (the country's default is usually fine).
Elige el(los) perfil(es) de la siguiente lista:
Main Server
This is the main server (tjener) for your school providing all services pre-configured to work out of the box. You must install only one main server per school! This profile does not include a graphical user interface. If you want a graphical user interface, then select Workstation or LTSP Server in addition to this one.
Workstation
Una computadora que inicia desde su disco duro, y funciona con todos los programas y dispositivos localmente como una computadora común, pero el usuario será autenticado por el servidor principal, donde los archivos de los usuarios y las configuraciones para escritorio son guardados.
Roaming workstation
Same as workstation but capable of authentication using cached credentials, meaning it can be used outside the school network. The users' files and profiles are stored on the local disk. For single user notebooks and laptops this profile should be selected and not 'Workstation' or 'Standalone' as suggested in earlier releases.
LTSP Server
A thin client (and diskless workstation) server, is called an LTSP server. Clients without hard drives boot and run software from this server. This computer needs two network interfaces, a lot of memory, and ideally more than one processor or core. See the chapter about networked clients for more information on this subject. Choosing this profile also enables the workstation profile (even if it is not selected) - an LTSP server can always be used as a workstation, too.
Standalone
Una computadora común que puede funcionar sin un servidor (esto quiere decir, que no necesita estar en la red). Incluye laptops.
Minimal
Este perfil instalará los paquetes básicos y configurará la computadora para integrarse en la red Debian Edu, pero sin ningún servicio ni aplicaciones. Es útil como plataforma para servicios simples manualmente migrados desde el servidor principal.
The Main Server, Workstation and LTSP Server profiles are preselected. These profiles can be installed on one machine together if you want to install a so called combined main server. This means the main server will be an LTSP server and also be used as a workstation. This is the default choice, since we assume most people will install via PXE afterwards. Please note that you must have 2 network cards installed in a machine which is going to be installed as a combined main server or as an LTSP server to become useful after the installation.
Seleccione "si" o "no" para particionamiento automático. Este consciente que al seleccionar sí, ¡se eliminarán todos los datos en el disco duro!, al seleccionar no, se requerirá más trabajo y necesitará que las particiones requeridas sean creadas y tengan suficiente espacio.
Por favor, seleccione "sí" para enviar información a http://popcon.skolelinux.org/ para permitirnos saber que paquetes
son populares y deberían de mantenerse para futuras versiones. Usted no esta
obligado a hacerlo, pero es la manera más fácil de que colabore.
Wait. If the selected profiles include LTSP Server then the installer will spend quite some time at the end, "Finishing the installation - Running debian-edu-profile-udeb..."
Después de introducir la contraseña de root, se le solicitará crear una cuenta de usuario normal "para tareas no administrativas". Para Debian Edu esta cuenta de usuario es muy importante: es la cuenta que se usará para administrar la red Skolelinux.
La contraseña para este usuario debe
tener una longitud de al menos 5
caracteres, de los contrario, el ingreso al sistema no será
posible (aunque el instalador acepte una contraseña menor).
Sonríe :)
Most likely you will want to use the 'Roaming workstation' profile (see above). Be aware that all data is stored locally (so take some extra care over backups) and login credentials are cached (so after a password change, logins may require your old password if you have not connected your laptop to the network and logged in with the new password).
Después de instalar desde una imagen multiarquitectura USB / Blu-ray,
/etc/apt/sources.list
contendrá fuentes de
esa imagen. Si tiene conexión a Internet, le sugerimos agregar las
siguientes lineas para que las actualizaciones de seguridad disponible se
puedan instalar:
deb http://ftp.debian.org/debian/ stretch main deb http://security.debian.org/ stretch/updates main
Una instalación por red (que es el tipo de instalación que ofrece nuestro CD) tomará algunos paquetes del CD y el resto lo tomará de Internet. El monto de paquetes tomados desde la red varia de perfil en perfil pero se mantiene menor a un gigabyte (al menos que elija instalar todos los escritorios posibles). Una vez que tiene instalado el servidor principal (ya sea un servidor principal o un servidor combinado), futuras instalaciones usarán el proxy para prevenir la descarga de los mismos paquetes muchas veces desde Internet.
Providing the kernel boot parameter
edu-skip-ltsp-make-client
makes it possible
to skip one step which converts the LTSP chroot from a thin-client chroot
into a combined thin-client/diskless workstation chroot.
This is useful in certain situations, such as if you want a pure thin client chroot or if there is already a diskless chroot on another server, which can be rsynced. For these situations skipping this step will cut down the installation time considerably.
Excepto por el extenso tiempo de instalación, no hay problema en crear un chroot combinado y por eso se hace de forma predeterminada.
Desde el lanzamiento de Squeeze es posible copiar directamente las imágenes
.iso
de CD/DVD/BD a una unidad USB (también
conocido como "memoria USB") e iniciar desde ellos. Solamente ejecute un
comando como este, ponga el nombre del archivo y la ruta al dispositivo que
desee instalar.
sudo dd if=debian-edu-amd64-i386-XXX.iso of=/dev/sdX
bs=1024
Dependiendo de la imágen seleccionada, la unidad USB se comportará como un CD o Blu-ray.
Para este método de instalación es necesario que el servidor principal esté
encendido. Cuando los clientes cargan a través de la red principal, un nuevo
menú PXE con un instalador y opciones de selección de carga se mostrará. Si
la instalación PXE falla con un mensaje de error mencionando que un archivo
XXX.bin no se encuentra, es más probable que la tarjeta de red del cliente
requiera un firmware no libre. En este caso el initrd del instalador de
Debian debe ser modificado. Esto se puede lograr ejecutando el comando
/usr/share/debian-edu-config/tools/pxe-addfirmware
en el servidor.
This is how the PXE menu looks with the Main-Server profile only:
This is how the PXE menu looks with the Main Server and LTSP Server profiles:
To install a desktop environment of your choice instead of the default one, press TAB and edit the kernel boot options (like explained above).
Esta configuración permite iniciar a las estaciones sin disco y clientes ligeros a través de la red principal. A diferencia de las estaciones de trabajo, las estaciones de trabajo sin disco no necesitan ser agregadas a LDAP con GOsa², pero pueden agregarse, si necesita forzar el nombre del host.
Más información acerca de los clientes de red puede ser encontrada en el capítulo clientes de red.
La instalación PXE utiliza un archivo de preconfiguración para debian-installer, que puede ser modificado y solicitar más paquetes para instalar.
Una línea como esta debe ser agregada
atjener:/etc/debian-edu/www/debian-edu-install.dat
d-i pkgsel/include string my-extra-package(s)
La instalación PXE usa el archivo
/var/lib/tftpboot/debian-edu/install.cfg
y
el archivo de preconfiguración
/etc/debian-edu/www/debian-edu-install.dat
.
Estos archivos pueden modificarse para ser ajustados a la configuración
usada durante la instalación y así evitar las preguntas cuando se realicen
instalaciones por red. Otra manera de lograr esto es agregar configuraciones
extras a los archivos
/etc/debian-edu/pxeinstall.conf
y
/etc/debian-edu/www/debian-edu-install.dat.local
y ejecutar /usr/sbin/debian-edu-pxeinstall
para actualizar los archivos generados.
Further information can be found in the manual of the Debian Installer.
Para desactivar o cambiar el uso del proxy cuando instale vía PXE, necesita
cambiar las lineas que contengan
mirror/http/proxy
,
mirror/ftp/proxy
y
preseed/early_command
en el archivo
tjener:/etc/debian-edu/www/debian-edu-install.dat
. Para desactivar el uso de proxy cuando instale, anteponga
el signo '#' al inicio de las primeras dos lineas y elimine
"export http_proxy="http://webcache:3128";
" de la última linea.
Algunas configuraciones no pueden preconfigurarse porque son necesiarias
antes que el archivo de preconfiguración sea descargado. Estas son
configuradas en los argumentos de carga PXElinux-based disponibles en
/var/lib/tftproot/debian-edu/install.cfg
.
Idioma, disposición del teclados y escritorio son algunas de estas
configuraciones.
Creating custom CDs, DVDs or Blu-ray discs can be quite easy since we use the Debian Installer, which has a modular design and other nice features. Preseeding allows you to define answers to the questions normally asked.
So all you need to do is to create a preseeding file with your answers (this is described in the appendix of the Debian Installer manual) and remaster the CD/DVD.
El modo de texto y modo gráfico de instalación son idénticos, sólo la apariencia es diferente. El modo gráfico le ofrece la oportunidad de utilizar un ratón y por supuesto, el modo gráfico se ve mucho mejor y más moderno. A menos que el hardware presente problemas con el modo gráfico, no hay razón para no usarlo.
So here is a screenshot tour through a graphical 64-bit Main Server + Workstation + LTSP Server installation and how it looks at the first boot of the main server, a PXE boot on the workstation network and on the LTSP client network:
Durante la instalación del servidor principal, fue creada una primera cuenta
de usuario. A continuación, esta cuenta se llamará "primer usuario". Esta
cuenta es especial, ya que no existe una cuenta de Samba (puede agregarse
vía GOsa²), los permisos para el directorio del usuario están establecidos
en 700 (es necesario ejecutar chmod o+x ~
para que el sitio web personal sea accesible), el primer usuario puede usar
sudo
para convertirse en root.
See the information about Debian Edu specific file system access configuration before adding users.
Después de la instalación, las primeras cosas que necesita hacer como usuario son:
Iniciar sesión en el servidor. Con la cuenta de roor puede ingresar en modo gráfico.
Agregar usuarios con GOsa²
Agregar estaciones de trabajo con GOsa² - clientes ligeros y estaciones de trabajo sin disco pueden ser usados directamente sin ser agregados.
Adding users and workstations is described in detail below, so please read this chapter completely. It covers how to perform these minimum steps correctly as well as other stuff that everybody will probably need to do.
There is additional information available elsewhere in this manual: the New features in Stretch chapter should be read by everyone who is familiar with previous releases. And for those upgrading from a previous release, make sure to read the Upgrades chapter.
If generic DNS traffic is blocked out of your network and you need to use
some specific DNS server to look up internet hosts, you need to tell the DNS
server to use this server as its "forwarder". Update
/etc/bind/named.conf.options and specify the IP address of the DNS server to
use.
El capítulo HowTo describe más trucos, pistas y algunas preguntas de uso frecuente.
GOsa²es una herramienta de administración web, que le ayudará a administrar algunas de las partes importantes de su configuración de Debian Edu. Podrá administrar (agregar, modificar o eliminar) estos principales grupos:
Administración de usuarios
Administración de grupos
Administración de grupos de red NIS
Administración de computadoras
Administración DNS
Administración DHCP
For GOsa² access you need the Skolelinux main server and a (client) system with a web browser installed which can be the main server itself if it was installed as a so called combined server (Main Server + LTSP Server + Workstation profiles). If all of the mentioned before is not available, see: Installing a graphical environment on the main-server to use GOsa².
Desde un navegador web, utilice https://www/gosa para acceder a GOsa² e ingrese por primera vez.
If you are using a new Debian Edu Stretch machine, the site certificate will be known by the browser.
Caso contrario, obtendrá un mensaje de error sobre certificado SSL equivocado. Si sabe que solamente usted se encuentra conectado a la red, acepte e ignórelo.
Para información general sobre GOsa², revise: https://oss.gonicus.de/labs/gosa/wiki/documentation
After logging in to GOsa² you will see the overview page of GOsa².
Next, you can choose a task in the menu or click any of the task icons on the overview page. For navigation, we recommend using the menu on the left side of the screen, as it will stay visible there on all administration pages offered by GOsa².
In Debian Edu, account, group, and system information is stored in an LDAP directory. This data is used not only by the main server, but also by the (diskless) workstations, the LTSP servers and the Windows machines on the network. With LDAP, account information about students, teachers, etc. only needs to be entered once. After information has been provided in LDAP, the information will be available to all systems on the whole Skolelinux network.
GOsa² es una herramienta de administración que usa LDAP para almacenar su información y provee una estructura jerárquica por departamento. Para cada "departamento" puede agregar cuentas de usuario, grupos, sistemas, grupos de red y demás. En dependencia de la estructura de su institución, puede usar la estructura en GOsa²/LDAP para transferir su estructura organizacional al árbol de datos LDAP del servidor principal Debian Edu.
A default Debian Edu main server installation currently provides two "departments": Teachers and Students, plus the base level of the LDAP tree. Student accounts are intended to be added to the "Students" department, teachers to the "Teachers" department; systems (servers, Skolelinux workstations, Windows machines, printers etc.) are currently added to the base level. Find your own scheme for customising this structure. (You can find an example how to create users in year groups, with common home directories for each group in the HowTo/AdvancedAdministration chapter of this manual.)
En dependencia de la tarea que desee realizar (administrar usuarios, grupos, sistemas, etc) GOsa² le mostrará una vista diferente en el departamento seleccionado (o el nivel básico).
En primer lugar, haga clic en "Usuarios" en el menú de navegación de la izquierda. El lado derecho de la pantalla cambiará para mostrar una tabla con las carpetas de departamento para "Estudiantes" y "maestros" y la cuenta GOsa² Super-Administrador (el primer usuario creado). Por encima de esta tabla se puede ver un campo llamado Base que le permite navegar a través de su estructura de árbol (mueva el ratón sobre esa zona y aparecerá un menú desplegable) y seleccione una carpeta de base para sus operaciones previstas (por ejemplo, la adición de un nuevo usuario).
Al lado de ese elemento de navegación de árbol se puede ver el menú "Acciones". Mueva su ratón sobre este ítem y un submenú aparecerá en la pantalla; seleccione "Crear", y luego "Usuario". Desde aquí será guíado por el asistente de creación de usuarios.
Lo más importante es el agregar un perfil (nuevoestudiante o nuevoprofesor) y el nombre completo del usuario (ver imágen)
As you follow the wizard, you will see that GOsa² generates a username automatically based on the real name. It automatically chooses a username that doesn't exist yet, so multiple users with the same full name are not a problem. Note that GOsa² can generate invalid usernames if the full name contains non-ASCII characters.
If you don't like the generated username you can select another username
offered in the drop-down box, but you do not have a free choice here in the
wizard. (If you want to be able to edit the proposed username, open
/etc/gosa/gosa.conf
with an editor and add
allowUIDProposalModification="true"
as an
additional option to the "location definition".)
When the wizard has finished, you are presented with the GOsa² screen for your new user object. Use the tabs at the top to check the completed fields.
After you have created the user (no need to customise fields the wizard has left empty for now), click on the "Ok" button in the bottom-right corner.
As the last step GOsa² will ask for a password for the new user. Type that
in twice and then click "Set password" in the bottom-right corner. Some characters may not be allowed as part of the password.
If all went well, you can now see the new user in the user list table. You should now be able to log in with that username on any Skolelinux machine within your network.
To modify or delete a user, use GOsa² to browse the list of users on your system. On the middle of the screen you may open the "Filter" box, a search tool provided by GOsa². If you don't know the exact location of your user account in your tree, change to the base level of the GOsa²/LDAP tree and search there with the option marked "Search in subtrees".
When using the "Filter" box, results will immediately appear in the middle of the text in the table list view. Every line represents a user account and the items farthest to the right on each line are little icons that provide actions for you: cut entry, copy entry, edit user, lock account, set password, take snapshot (not usable) and remove user.
Una nueva página se mostrará donde podrá modificar la información pertinente al usuario directamente, cambiar su contraseña y modificar la lista de grupos a los que pertenece.
Los estudiantes pueden cambiar sus contraseñas ingresando a GOsa² son sus propios usuarios. Para facilitar el acceso a GOsa², un acceso directo llamado Gosa se encuentra en el menú escritorio (o en configuración del sistema). Una sesión de estudiante tendrá una versión mínima de GOsa² que solamente le brinda acceso a la hoja de información del usuario y a la opción de cambio de contraseña.
Los profesores que ingresan con sus propios nombres de usuarios, tienen privilegios especiales en GOsa². Ellos poseen una vista con más privilegios y pueden cambiar la contraseña de todas las cuentas de estudiantes. Esto puede ser muy practico durante clases.
Para establecer una nueva contraseña para el usuario
Busque el usuario que desea modificar, tal como se explicó anteriormente
Haga clic en la flecha al final del usuario
En la siguiente página, puede escribir la nueva contraseña
¡Tenga cuidado con las consecuencias a la seguridad, debido a la facilidad de las contraseñas!
Es posible crear usuarios masivamente con GOsa² usando un archivo CSV, que
puede ser creado con un software de hoja de cálculo
(localc
por ejemplo). Se deben proveer, al
menos, datos para los siguientes campos: uid, last name (sn), first name
(givenName) y password. Asegúrese de no duplicar datos en el campo uid. Note
que la revisión de duplicados debe incluir los registros ya existentes en
LDAP (que puede ser obtenido ejecutando getent passwd | grep
tjener/home | cut -d":" -f1
en la linea de comando).
These are the format guidelines for such a CSV file (GOsa² is quite intolerant about them):
Use "," como separador de campos
Do not use quotes
El archivo CSV no debe contener un encabezado (no debe tener el nombre de la columna)
El orden de los campos no es relevante, y puede ser definido en GOsa² durante la importación masiva
Los pasos para importe masivo son:
Haga clic en el enlace "LDAP Manager" en el menú de navegación a la izquierda
Haga clic en la pestaña "Importar" al lado derecho de la pantalla
Busque en su disco local el archivo CSV con la lista de usuarios que desea importar
Eliga una plantilla de usuarios disponible que se aplicará durante la importación masiva (como NewTeacher o NewStudent)
Haga clic en el botón "Importar" en la esquina inferior derecha
Es una buena idea el hacer pruebas antes, de preferencia con un archivo CSV con usuarios ficticios, que pueden ser eliminados después.
La gestión de grupos es muy similar a la gestión de usuarios.
Puede ingresar un nombre y una descripción por grupo. Asegúrese de elegir el nivel correcto en el árbol LDAP cuando cree un nuevo grupo.
By default, the appropriate Samba group isn't created. If you forgot to check the Samba group option during group creation, you can modify the group later on.
Adding users to a newly created group takes you back to the user list, where you most probably would like to use the filter box to find users. Check the LDAP tree level, too.
Los grupos incluidos en el manejo de grupos, son también grupos regulares de Unix, así que pueden utilizarse también para los permisos de archivos.
Machine management basically allows you to manage all networked devices in your Debian Edu network. Every machine added to the LDAP directory using GOsa² has a hostname, an IP address, a MAC address and a domain name (which is usually "intern"). For a fuller description of the Debian Edu architecture see the architecture chapter of this manual.
Diskless workstations and thin-clients work out-of-the-box when connected to the main network. Only workstations with disks have to be added with GOsa², but all can.
To add a machine, use the GOsa² main menu, systems, add. You can use an IP address/hostname from the preconfigured address space 10.0.0.0/8. Currently there are only two predefined fixed addresses: 10.0.2.2 (tjener) and 10.0.0.1 (gateway). The addresses from 10.0.16.20 to 10.0.31.254 (roughly 10.0.16.0/20 or 4000 hosts) are reserved for DHCP and are assigned dynamically.
To assign a host with the MAC address 52:54:00:12:34:10 a static IP address
in GOsa² you have to enter the MAC address, the hostname and the IP;
alternatively you might click the Propose
ip
button which will show the first free fixed address in
10.0.0.0/8, most probably something like 10.0.0.2 if you add the first
machine this way. It may be better to first think about your network: for
example you could use 10.0.0.x with x>10 and x<50 for servers, and
x>100 for workstations. Don't forget to activate the just added
system. With the exception of the main server all systems will then have a
matching icon.
If the machines have booted as thin clients/diskless workstations or have
been installed using any of the networked profiles, the
sitesummary2ldapdhcp
script can be used to
automatically add machines to GOsa². For simple machines it will work out of
the box, for machines with more than one mac address the actually used one
has to be chosen, sitesummary2ldapdhcp -h
shows usage information. Please note, that the IP addresses shown after
usage of sitesummary2ldapdhcp
belong to the
dynamic IP range. These systems can then be modified to suit your network:
rename each new system, activate DHCP and DNS, add it to netgroups if
needed, reboot the system afterwards. The following screenshots show how
this looks in practice:
root@tjener:~# sitesummary2ldapdhcp -a -i ether-00:04:76:d3:28:b7 -t workstations info: Create GOsa machine for auto-mac-00-04-76-d3-28-b7.intern [10.0.16.21] id ether-00:04:76:d3:28:b7. Enter password if you want to activate these changes, and ^c to abort. Connecting to LDAP as cn=admin,ou=ldap-access,dc=skole,dc=skolelinux,dc=no enter password:
A cronjob updating DNS runs every hour; su -c
ldap2bind
can be used to trigger the update manually.
Buscar computadoras para ser eliminadas, es bastante similar a buscar usuarios para eliminar, por lo que esa información no se repite aquí.
After adding a machine to the LDAP tree using GOsa², you can modify its properties using the search functionality and clicking on the machine name (as you would with users).
The format of these system entries is similar to the one you already know from modifying user entries, but the fields mean different things in this context.
For example, adding a machine to a NetGroup
does not modify the file access or command execution permissions for that
machine or the users logged in to that machine; instead it restricts the
services that machine can use on your main-server.
La instalación por defecto proporciona la Grupo de
Red
cups-queue-autoflush-hosts
cups-queue-autoreenable-hosts
fs-autoresize-hosts
ltsp-server-hosts
netblock-hosts
printer-hosts
server-hosts
shutdown-at-night-hosts
winstation-hosts
workstation-hosts
Actualmente, la funcionalidad de NetGroup
se utiliza para
NFS.
The home directories are exported by the main-server to be mounted by the
workstations and the LTSP servers. For security reasons, only hosts within
the workstation-hosts, ltsp-server-hosts and server-hosts
NetGroups
can mount the exported NFS
shares. So it is rather important to remember to configure these kinds of
machines properly in the LDAP tree using GOsa² and to configure them to use
static IP addresses from LDAP.
Remember to configure workstations and LTSP servers properly with GOsa², or
your users won't be able to access their home directories. Diskless
workstations and thin clients don't use NFS, so they don't need to be
configured.
fs-autoresize
Los equipos con Debian Edu en este grupo, automáticamente acondicionarán las particiones LVM que estén próximas a quedarse sin espacio disponible.
shutdown at night
Los equipos con Debian Edu en este grupo, se apagarán automáticamente por las noches para ahorrar energía.
CUPS (cups-queue-autoflush-hosts and cups-queue-autoreenable-hosts)
Debian Edu machines in these groups will automatically flush all print queues every night, and re-enable any disabled print queue every hour.
netblock-hosts
Debian Edu machines in this group will be allowed to connect to machines only on the local network. Combined with web proxy restrictions this might be used during exams.
Another important part of machine configuration is the 'Samba host' flag (in the 'Host information' area). If you plan to add existing Windows systems to the Skolelinux Samba domain, you need to add the Windows host to the LDAP tree and set this flag to be able to join the Windows host to the domain. For more information about adding Windows hosts to the Skolelinux network see the HowTo/NetworkClients chapter of this manual.
For Printer Management point your web browser to https://www:631 and accept the self-signed certificate. This is the
normal CUPS management interface where you can add/delete/modify your
printers and can clean up the printing queue. By default only root is
allowed but this can be changed: Open /etc/cups/cups-files.conf with an
editor and add one or more valid group names matching your site policy to
the line containing SystemGroup
lpadmin
. Existing GOsa² groups that might be used are
gosa-admins
and
printer-admins
(both with the first user as
member), teachers
and
jradmins
(no members after installation).
The default configuration in Debian Edu is to keep the clocks on all machines synchronous but not necessarily correct. NTP is used to update the time. The clocks will be synchronised with an external source by default. This can cause machines to keep the external Internet connection open if it is created when used.
Si usa conexión dialip o ISDN y paga por minuto, es posible que desee
cambiar esta configuración predeterminada.
To disable synchronisation with an external clock, the file /etc/ntp.conf on
the main-server and all clients and LTSP chroots need to be modified. Add
comment ("#") marks in front of the server
entries. After this, the NTP server needs to be restarted by running
/etc/init.d/ntp restart
as root. To test
if a machine is using the external clock sources, run ntpq
-c lpeer
.
Because of a possible bug with automatic partitioning, some partitions might
be too full after installation. To extend these partitions, run
debian-edu-fsautoresize -n
as root. See
the "Resizing Partitions" HowTo in the administration HowTo
chapter for more information.
This section explains how to use apt-get
upgrade
.
Using apt-get
is really simply. To update a
system you need to execute two commands on the command line as root:
apt-get update
(which updates the lists of
available packages) and apt-get upgrade
(which upgrades the packages for which an upgrade is available).
As Debian Edu uses libpam-tmpdir, setting a per user TMP directory, it is a good idea to run apt-get without the TMP and TMPDIR variables set in the LTSP chroot. It is also a good idea to upgrade using the C locale to get known output and sorting order, even though that making a difference is a bug in a package.
LC_ALL=C apt-get update ; LC_ALL=C TMP= TMPDIR= ltsp-chroot apt-get update LC_ALL=C apt-get upgrade -y LC_ALL=C TMP= TMPDIR= ltsp-chroot -p apt-get upgrade -y ltsp-update-kernels # If a new kernel was installed
It is important to run
ltsp-update-kernels
if a new kernel was installed in the LTSP chroot, to keep the kernel and
kernel modules in sync. The kernel is handed out via TFTP when the machine
does PXE boot, and the kernel modules are fetched from the LTSP chroot.
Run
ltsp-update-image
to re-generate the
NBD image(s).
También es buena idea instalar cron-apt
y
apt-listchanges
y configurarlos para que le
envíe corre electrónico.
cron-apt
will notify you once a day via
email about any packages that can be upgraded. It does not install these
upgrades, but does download them (usually in the night), so you don't have
to wait for the download when you do apt-get
upgrade
.
Automatic installation of updates can be done easily if desired, it just
needs the unattended-upgrades
package to be
configured as described on wiki.debian.org/UnattendedUpgrades.
On new installations security updates are enabled by default.
apt-listchanges
can send new changelog
entries to you via email, or alternativly display them in the terminal when
running aptitude
or
apt-get
.
Running cron-apt
as described above is a
good way to learn when security updates are available for installed
packages. Another way to stay informed about security updates is to
subscribe to the Debian
security-announce mailinglist, which has the benefit of also telling
you what the security update is about. The downside (compared to
cron-apt
) is that it also includes
information about updates for packages which aren't installed.
For backup management point your browser to https://www/slbackup-php. Please note that you need to access this site via SSL, since you have to enter the root password there. If you try to access this site without using SSL it will fail. Note: the site will only work if you temporarily allow ssh root login on the backup server (main server 'tjener' by default).
By default tjener will back up
/skole/tjener/home0
,
/etc/
,
/root/.svk
and LDAP to /skole/backup which
is under the LVM. If you only want to have spare copies of things (in case
you delete them) this setup should be fine for you.
Tome en cuenta que este esquema de respaldo no le protege de daños en el
disco duro.
If you want to back up your data to an external server, a tape device or another hard drive you'll have to modify the existing configuration a bit.
Si quieres restaurar un directorio, la mejor opción es usar la línea de comandos:
$ sudo rdiff-backup -r <date> \ /skole/backup/tjener/skole/tjener/home0/user \ /skole/tjener/home0/user_<date>
Esto pondrá el contenido de
/skole/tjener/home0/user
para
<date>
en el directorio
/skole/tjener/home0/user_<date>
.
Si desea restablecer un archivo, debería de ser capaz de seleccionar el archivo (y la versión) de la interfaz web y descargar solamente ese archivo.
Si desea deshacerse de los respaldos viejos, elija "Maintenance" en el menú de la página respaldo y seleccione la instantánea más vieja que desee conservar:
Los reportes de Munin están disponible en https://www/munin/. Le provee gráficos de medición en una vista diaría, semanal, mensual y anual. Además le provee ayuda al administrador de sistemas al momento de buscar cuellos de botella y el origen de problemas en el sistema.
The list of machines being monitored using Munin is generated automatically,
based on the list of hosts reporting to sitesummary. All hosts with the
package munin-node installed are registered for Munin monitoring. It will
normally take one day from a machine being installed until Munin monitoring
starts, because of the order the cron jobs are executed. To speed up the
process, run sitesummary-update-munin
as
root on the sitesummary server (normally the main server). This will update
the /etc/munin/munin.conf
file.
The set of measurements being collected is automatically generated on each
machine using the munin-node-configure
program which probes the plugins available from
/usr/share/munin/plugins/
and symlinks the
relevant ones to /etc/munin/plugins/
.
Information about Munin is available from http://munin-monitoring.org/.
Icinga system and service monitoring is available from https://www/icinga/. The set of machines and services being
monitored is automatically generated using information collected by the
sitesummary system. The machines with the profile Main-server and
LTSP-server receive full monitoring, while workstations and thin clients
receive simple monitoring. To enable full monitoring on a workstation,
install the nagios-nrpe-server
package on
the workstation.
The username is icingaadmin
and the default
password is skolelinux
. For security
reasons, avoid using the same password as root. To change the password you
can run the following command as root:
htpasswd /etc/icinga/htpasswd.users icingaadmin
By default Icinga does not send email. This can be changed by replacing
notify-by-nothing
with
host-notify-by-email
and
notify-by-email
in the file
/etc/icinga/sitesummary-template-contacts.cfg
.
The Icinga configuration file used is
/etc/icinga/sitesummary.cfg
. The
sitesummary cron job generates
/var/lib/sitesummary/icinga-generated.cfg
with the list of hosts and services to monitor.
Extra Icinga checks can be put in the file
/var/lib/sitesummary/icinga-generated.cfg.post
to get them included in the generated file.
Information about Icinga is available from https://www.icinga.com/ or in the
icinga-doc
package.
Here are instructions on how to handle the most common Icinga warnings.
La partición (/usr/ en el ejemplo) está llena. Existen dos maneras para
resolver esto: (1) elimine algunos archivos o (2) aumente el tamaño de la
partición. Si la partición es /var/, purgando el caché de APT ejecutando
apt-get clean
debería eliminar algunos
archivos. Si hay más espacio disponible en el volumen LVM, ejecutar el
programa debian-edu-fsautoresize
para
aumentar las particiones debería ayudar. Para ejecutar este programa cada
hora, el equipo debe de ser añadido al grupo de red
fsautoresize-hosts
.
New package are available for upgrades. The critical ones are normally
security fixes. To upgrade, run 'apt-get upgrade && apt-get
dist-upgrade' as root in a terminal or log in via ssh to do the same. On
LTSP servers, remember to also update the LTSP chroot using
ltsp-chroot apt-get update && ltsp-chroot apt-get
upgrade
.
If you do not want to manually upgrade packages and trust Debian to do a
good job with new versions, you can configure
unattended-upgrades
to automatically
upgrade all new packages every night. This will not upgrade the LTSP
chroots.
Para actualizar el chroot LTSP, puede usar ltsp-chroot
apt-get update && ltsp-chroot apt-get upgrade
. En
servidores de 64 bits, tendrá que agregar como argumento a ltsp-chroot
-a i386
. Es buena idea actualizar el chroot
cuando actualice el sistema de la computadora.
El kernel en ejecución es más viejo que el kernel más actual instalado, y un reinicio del equipo es necesario para ejecutar el kernel más nuevo instalado. Normalmente esto es urgente, ya que los nuevos kernels corrigen fallos de seguridad en Debian Edu.
The printer queues in CUPS have a lot of jobs pending. This is most likely
because of a unavailable printer. Disabled print queues are enabled every
hour on hosts that are member of the
cups-queue-autoreenable-hosts
netgroup, so
for such hosts no manual action should be required. The print queues are
emptied every night on hosts that are member of the
cups-queue-autoflush-hosts
netgroup. If a
host have a lot of jobs in their queue, consider adding this host to one or
both of these netgroups.
Sitesummary es usado para obtener información de cada computadora y enviarla
al servidor principal. La información obtenida se encuentra disponible en
/var/lib/sitesummary/entries/
. Scripts en
/usr/lib/sitesummary/
, están disponibles
para generar reportes.
Un reporte sencillo de sitesummary sin de talles se encuentra disponible en https://www/sitesummary/.
Documentación sobre sitesummary se encuentra disponible en http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
Más información sobre personalizaciones de Debian Edu útil para administradores de sistema puede encontrarse en el capítulo Administración y en el capítulo Administración avanzada
Antes de leer está guía de actualización, tenga en cuenta que las
actualizaciones en su servidor en producción la hace bajo su propio
riesgo.Debian Edu/Skolelinux no tiene ABSOLUTAMENTE
NINGUNA GARANTÍA más allá de las que indique la ley aplicable.
Please read this chapter and the New features in Stretch chapter of this manual completely before attempting to upgrade.
Upgrading Debian from one distribution to the next is generally rather easy. For Debian Edu this is unfortunately not yet true as we modify configuration files in ways we shouldn't. (See Debian bug 311188 for more information.) Upgrading is still possible but may require some work.
En general, actualizar los servidores es más difícil que las estaciones de trabajo y el servidor principal es el más difícil de actualizar. Las estaciones de trabajo sin disco son más faciles, ya que su entorno chroot puede ser eliminado y recreado si no lo ha modificado. Si lo ha modificado, el chroot es básicamente un chroot de estación de trabajo, así que es bastante fácil de actualizar.
Si quiere asegurase de que después de la actualización todo va como antes, debería probarlo en un sistema de pruebas o en un sistema configurado igual que su servidor en producción. Ahí puede probar la actualización sin riesgo y ver si todo funciona como debiera.
Asegúrese de leer la información sobre la versión estable de Debian actual en el manual de instalación.
También sería inteligente esperar un poco y seguir con la versión anterior durante algunas semanas más, para que otros prueben la actualización y documenten algunos problemas que experimenten. La versión estable anterior de Debian Edu continuará recibiendo soporte por algún tiempo después de la publicación de la siguiente versión estable, pero cuando Debian cese el soporte a la versión estable anterior, Debian Edu hará lo mismo.
Be prepared: make sure you have tested the upgrade from Jessie in a test
environment or have backups ready to be able to go back.
Please note that the following recipe applies to a default Debian Edu main server installation (desktop=kde, profiles Main Server, Workstation, LTSP Server). (For a general overview concerning jessie to stretch upgrade, see: https://www.debian.org/releases/stretch/releasenotes)
Don't use X, use a virtual console, log in as root.
Please note one difference between apt
and
apt-get
in Stretch: By default
apt-get
keeps downloaded packages,
apt
removes them from the cache (after
successful installation).
If apt
finishes with an error, try to fix
it and/or run apt -f install
and then
apt -y full-upgrade
once again.
Start by making sure the current system is up-to-date:
apt update apt full-upgrade
Cleanup the package cache:
apt-get clean
Prepare and start the upgrade to Stretch:
# First, adjust for a changed profile name: sed -i 's/Thin-Client-Server/LTSP-Server/' /etc/debian-edu/config # Then it's best to use the new default mirror: sed -i 's/http.debian.net/deb.debian.org/g' /etc/apt/sources.list # Finally, replace jessie with stretch. sed -i 's/jessie/stretch/g' /etc/apt/sources.list apt update apt full-upgrade
apt-list-changes: be prepared for a lot of NEWS to read; press <return> to scroll down, <q> to leave the pager.
Read all debconf information carefully, choose 'keep your currently-installed version' unless stated differently below; in most cases hitting return will be fine.
You will see some prompts about package configurations:
icinga-cgi: Provide icingaadmin's password (same as used for nagiosadmin).
Just in case several display managers are installed: display-manager: Choose
lightdm
.
Configuring Kerberos Authentication: Enter
kerberos
as hostname.
Configuring icinga-common: Use external commands with Icinga: Choose <Yes>.
tftp (etc/inetd.conf): Choose <Yes>. (See atftpd bug 789667)
/etc/default/ldap2zone: Choose Y.
/etc/gosa/gosa.conf: Choose N. (Never accept a new gosa.conf version!)
Cope with the Squid3 to Squid renaming:
service squid stop # This usually takes some time! rm -rf /var/spool/squid umount /var/spool/squid3 sed -i 's#spool/squid3#spool/squid#' /etc/fstab mv /var/spool/squid3 /var/spool/squid mount -a rm /etc/squid3 -rf rm /etc/default/squid3 -rf
Modify LDAP to use the fully qualified domain name (FQDN) for sudo:
ldapvi -ZD '(cn=admin)' (Enter root password.) Search for 'sudoHost :tjener', replace 'tjener' with 'tjener.intern' (Enter 'y' to modify the LDAP data base.)
Apply and adjust configuration:
service autofs stop cfengine-debian-edu -D installation rm /etc/apache2/conf-enabled/nagios3.conf a2dismod userdir ln -s /etc/apache2/mods-available/userdir.load /etc/apache2/mods-available/debian-edu-userdir.load a2enmod debian-edu-userdir sed -i 's/udp4/udp/' /etc/inetd.conf # Debian Bug #789667 (atftpd) service squid start service apache2 restart
Install renamed metapackages:
apt update apt install education-networked-common apt install education-ltsp-server # Only if profile 'LTSP-Server' is installed.
Get the new Debian Edu Stretch artwork:
apt install debian-edu-artwork-softwaves
If the upgraded system fails to boot on qemu/kvm, see 844446. Changing the architecture away from Broadwell in QEMU might help.
After reboot, do some more cleanup:
apt purge linux-image-3.16.0-4-amd64 apt purge debian-edu-artwork-lines # Only if not wanted as an alternative theme. dpkg -P php5-imagick # Package might not be installed in all cases. rm -rf /etc/php5
Enable otherwise broken PHP 7.0 support:
a2enmod php7.0 service apache2 restart
Check if the upgraded system works:
Reboot; log in as first user and test
if the GOsa² gui is working,
if one is able to connect LTSP clients and workstations,
if one can add/remove a netgroup membership of a system,
if one can send and receive internal email,
if one can manage printers,
and if other site specific things are working.
Do all the basic things like on the main-server and without doing the things not needed. And then do this in addition.
To enable LDAP connection, renew the server certificate:
rm /etc/ldap/ssl/ldap-server-pubkey.pem service nslcd stop service fetch-ldap-cert restart service nslcd start
Make sure you have enough disk space. LTSP now uses Network Block Device (NBD). The NBD image file size is about 4 GiB (default installation). If the image is updated, another 4 GiB for a temporary file are needed.
ltsp-chroot -m -a i386 apt update ltsp-chroot -m -a i386 apt -y full-upgrade sed -i 's/jessie/stretch/g' /opt/ltsp/i386/etc/apt/sources.list ltsp-chroot -m -a i386 apt update ltsp-chroot -m -a i386 apt -y full-upgrade ltsp-chroot -m -a i386 apt -f install ltsp-chroot -m -a i386 apt -y full-upgrade
Cleaning up:
ltsp-chroot -m -a i386 apt --purge autoremove
Update LTSP support on the server side:
ltsp-update-kernels ltsp-update-sshkeys ltsp-update-image
To save disk space, ltsp-update-image -n
could be used instead; see man
ltsp-update-image
.
On the LTSP server(s) the LTSP chroot could also be recreated. The new chroot will still support both thin-clients and diskless workstations.
Elimine /opt/ltsp/i386
(o
/opt/ltsp/amd64
, dependiendo de su
configuración). Si tiene suficiente espacio en disco, considere respaldarlo.
Recreate the chroot by running debian-edu-ltsp --arch
i386
(or debian-edu-ltsp --arch
amd64
) as root.
To upgrade from any older release, you will need to upgrade to the Jessie based Debian Edu release first, before you can follow the instructions provided above. Instructions are given in the Manual for Debian Edu Jessie about how to upgrade to Jessie from the previous release, Wheezy. Likewise the Wheezy manual describes how to upgrade from Squeeze.
Guía para Administración general.
Guía para Administración avanzada.
Guía para el escritorio.
Guía para clientes en red.
Guía para Samba.
Guía para enseñar y aprender.
HowTos for users
Los capítulos Iniciando y Mantenimiento describen como empezar con Debian Edu y como realizar el trabajo de mantenimiento básico. Las guías en estos capítulos, tienen también trucos y recomendaciones más "avanzadas".
Con la introducción de etckeeper
en Debian
Edu Squeeze (las versiones anteriores utilizaban
etcinsvk
el cual fué removido de Debian),
todos los archivos en /etc/
son seguidos
utilizando git como sistema de
control de versiones.
Esto hace posible ver cuando un archivo es agregado, modificado o eliminado,
también ver lo que se cambió si el archivo es un archivo de texto. El
repositorio de git es guardado en
/etc/.git/
.
Cualquier cambio, es registrado cada hora, permitiendo tener un histórico de la configuración para ser extraído y revisado.
To look at the history, the command etckeeper vcs
log
is used. To check the differences between two points
in time, a command like etckeeper vcs diff
can be used.
Revise la salida de man etckeeper
para más
información.
Lista de comandos útiles:
etckeeper vcs log etckeeper vcs status etckeeper vcs diff etckeeper vcs add . etckeeper vcs commit -a man etckeeper
En un sistema recién instalado pruebe esto para ver todos los cambios realizados desde que el sistema fue instalado:
etckeeper vcs log
Vea que archivos no están siendo seguidos, o los que no están actualizados:
etckeeper vcs status
To manually commit a file, because you don't want to wait up to an hour:
etckeeper vcs commit -a /etc/resolv.conf
In Debian Edu, all partitions other than the
/boot/
partition are on logical LVM
volumes. With Linux kernels since version 2.6.10, it is possible to extend
partitions while they are mounted. Shrinking partitions still needs to
happen while the partition is unmounted.
It is a good idea to avoid creating very large partitions (over, say,
20GiB), because of the time it takes to run
fsck
on them or to restore them from backup
if the need arises. It is better, if possible, to create several smaller
partitions than one very large one.
The helper script debian-edu-fsautoresize
is provided to make it easier to extend full partitions. When invoked, it
reads the configuration from
/usr/share/debian-edu-config/fsautoresizetab
,
/site/etc/fsautoresizetab
and
/etc/fsautoresizetab
. It then proposes to
extend partitions with too little free space, according to the rules
provided in these files. If run with no arguments, it will only show the
commands needed to extend the file system. The argument
-n
is needed to actually execute these
commands to extend the file systems.
The script is executed automatically every hour on every client listed in
the fsautoresize-hosts
netgroup.
When the partition used by the Squid proxy is resized, the value for cache
size in etc/squid/squid.conf
needs to be
updated as well. The helper script
/usr/share/debian-edu-config/tools/squid-update-cachedir
is provided to do this automatically, checking the current partition size of
/var/spool/squid/
and configuring Squid to
use 80% of this as its cache size.
Logical Volume Management (LVM) enables resizing the partitions while they are mounted and in use. You can learn more about LVM from the LVM HowTo.
To extend a logical volume manually you simply tell the
lvextend
command how large you want it to
grow to. For example, to extend home0 to 30GiB you use the following
commands:
lvextend -L30G /dev/vg_system/skole+tjener+home0 resize2fs /dev/vg_system/skole+tjener+home0
To extend home0 by additional 30GiB, you insert a '+' (-L+30G)
If you (probably accidentally) installed a pure main-server profile and don't have a client with a web-browser handy, it's easy to install a minimal desktop on the main server using this command sequence in a (non-graphical) shell as the user you created during the main server's installation (first user):
$ sudo apt-get update $ sudo apt-get install gnome-session gnome-terminal firefox-esr xorg # after installation, start a graphical session for the first user $ startx
ldapvi es una herramienta para editar la base de datos LDAP con un editor de texto en la linea de comandos.
Lo siguiente necesita ser ejecutado:
ldapvi --ldap-conf -ZD '(cn=admin)'
Nota: ldapvi
usará el editor de texto
predeterminado. Ejecutar export EDITOR=vim
en el intérprete de comandos puede configurar el entorno para tener un clon
de vi como editor.
To add an LDAP object using ldapvi, use object sequence number with the
string add
in front of the new LDAP object.
Adevertencia:
ldapvi
es una herramienta
poderosa. Sea cuidadoso y no dañe la base de datos de LDAP, la misma
advertencia aplica para JXplorer.
If you prefer a GUI to work with the LDAP database, check out the
jxplorer
package, which is installed by
default. To get write access connect like this:
host: ldap.intern port:636 Base dn:dc=skole,dc=skolelinux,dc=no Security level: ssl + user + password User dn: cn=admin,ou=ldap-access Click "This session only" if asked for the certificate.
ldap-createuser-krb
is a small command line
tool to create LDAP users and set their passwords in Kerberos. It's mostly
useful for testing, though.
Since the Squeeze release in 2011, Debian has included packages formerly maintained in volatile.debian.org in the stable-updates suite.
While you can use stable-updates directly, you don't have to: stable-updates are pushed into the stable suite regularly when stable point releases are done, which roughly happens every two months.
You are running Debian Edu because you prefer the stability of Debian Edu. It runs great; there is just one problem: sometimes software is a little bit more outdated than you like. This is where backports.debian.org steps in.
Backports are recompiled packages from Debian testing (mostly) and Debian unstable (in a few cases only, e.g. security updates), so they will run without new libraries (wherever this is possible) on a stable Debian distribution like Debian Edu. We recommend you to pick out individual backports which fit your needs, and not to use all backports available there.
Usar backports es sencillo:
echo "deb http://deb.debian.org/debian/ stretch-backports main" >> /etc/apt/sources.list apt-get update
After which one can install backported packages easily, the following command will install a backported version of tuxtype:
apt-get install -t stretch-backports tuxtype
Backports are automatically updated (if available) just like other packages. Like the normal archive, backports has three sections: main, contrib and non-free.
If you want to upgrade from one version to another (for example from Stretch 9.1+edu0 to 9.3+edu1) but you do not have Internet connectivity, only physical media, follow these steps:
Inserte el CD/DVD/Disco Blu-ray/Dispositivo USB en la unidad, montelo y use el comando apt-cdrom:
mount /media/cdrom apt-cdrom add -m
Para citar el manual de referencia de apt-cdrom(8):
apt-cdrom is used to add a new CD-ROM to APTs list of available sources. apt-cdrom takes care of determining the structure of the disc as well as correcting for several possible mis-burns and verifying the index files.
It is necessary to use apt-cdrom to add CDs to the APT system, it cannot be done by hand. Furthermore each disk in a multi-CD set must be inserted and scanned separately to account for possible mis-burns.
Luego ejecute estos dos comandos para actualizar el sistema:
apt-get update apt-get upgrade
killer
is a perl script that gets rid of
background jobs. Background jobs are defined as processes that belong to
users who are not currently logged into the machine. It's run by cron job
once an hour.
Para instalarlo ejecuta el siguiente comando como root:
apt-get install killer
unattended-upgrades
is a Debian package
which will install security (and other) upgrades automatically. The package
is installed by default and preconfigured to install security upgrades. The
logs are available in
/var/log/unattended-upgrades/
; also, there
are always /var/log/dpkg.log
and
/var/log/apt/
.
It is possible to save energy and money by automatically turning client machines off at night and back on in the morning. The package will try to turn off the machine every hour on the hour from 16:00 in the afternoon, but will not turn it off if it seems to have users. It will try to tell the BIOS to turn on the machine around 07:00 in the morning, and the main-server will try to turn on machines from 06:30 by sending wake-on-lan packets. These times can be changed in the crontabs of individual machines.
Some considerations should be kept in mind when setting this up:
The clients should not be shut down when someone is using them. This is
ensured by checking the output from who
,
and as a special case, checking for the LDM ssh connection command to work
with LTSP thin clients.
To avoid blowing electrical fuses, it is a good idea to make sure all clients do not start at the same time.
There are two different methods available to wake up clients. One uses a
BIOS feature and requires a working and correct hardware clock, as well as a
motherboard and BIOS version supported by
nvram-wakeup
; the other requires clients to
have support for wake-on-lan, and the server to know about all the clients
that need to be woken up.
On clients that should turn off at night, touch
/etc/shutdown-at-night/shutdown-at-night
,
or add the hostname (that is, the output from 'uname
-n
' on the client) to the netgroup
"shutdown-at-night-hosts". Adding hosts to the netgroup in LDAP can be done
using the GOsa²
web tool. The clients might
need to have wake-on-lan configured in the BIOS. It is also important that
the switches and routers used between the wake-on-lan server and the clients
will pass the WOL packets to the clients even if the clients are turned
off. Some switches fail to pass on packets to clients that are missing in
the ARP table on the switch, and this blocks the WOL packets.
To enable wake-on-lan on the server, add the clients to
/etc/shutdown-at-night/clients
, with one
line per client, IP address first, followed by MAC address (ethernet
address), separated by a space; or create a script
/etc/shutdown-at-night/clients-generator
to
generate the list of clients on the fly.
Aquí tiene un ejemplo de
/etc/shutdown-at-night/clients-generator
para usar con sitesummary:
#!/bin/sh PATH=/usr/sbin:$PATH export PATH sitesummary-nodes -w
An alternative if the netgroup is used to activate shutdown-at-night on
clients is this script using the netgroup tool from the
ng-utils
package:
#!/bin/sh PATH=/usr/sbin:$PATH export PATH netgroup -h shutdown-at-night-hosts
To access machines behind a firewall from the Internet, consider installing
the package autossh
. It can be used to set
up an SSH tunnel to a machine on the Internet that you have access to. From
that machine, you can access the server behind the firewall via the SSH
tunnel.
En la instalación predeterminada, todos los servicios están ejecutándose en el servidor principal, tjener. Para mover algunos servicios a otra computadora de manera sencilla, existe un perfil mínimo de instalación disponible. Instalar con este perfil le proporcionará una computadora, que es parte de la red de Debian Edu, pero que no cuenta con un servicio ejecutándose (todavía)
Estos son los pasos que se deben seguir para configurar un servicio dedicado en una computadora:
Instale el perfil mínimo usando la opción de carga debian-edu-expert.
Instale los paquetes del servicio.
Configure el servicio.
Deshabilite el servicio en el servidor principal.
Actualice el servicio DNS (via LDAP/GOsa²) en el servidor principal.
FIXME: The HowTos from http://wiki.debian.org/DebianEdu/HowTo/ are either user- or developer-specific. Let's move the user-specific HowTos over here (and delete them over there)! (But first ask the authors (see the history of those pages to find them) if they are fine with moving the howto and putting it under the GPL.)
In this chapter advanced administration tasks are described.
In this example we want to create users in year groups, with common home directories for each group (home0/2014, home0/2015, etc). We want to create the users by csv import.
(as root on the main server)
Make the necessary year group directories
mkdir /skole/tjener/home0/2014
(como super usuarios en Gosa
Departamento
Main menu: goto 'Directory structure', click the 'Students' department. The 'Base' field should show '/Students'. From the drop box 'Actions' choose 'Create'/'Department'. Fill in values for Name (2014) and Description fields (students graduating in 2014), leave the Base field as is (should be '/Students'). Save it clicking 'Ok'. Now the new department (2014) should show up below /Students. Click it.
Grupo
Elije "Groups" del menú principal; "Actions"/Create/Group. Escriba el nombre del grupo (deje "Base", debería estar en /Students/2014) y haga clic en la caja de selección de la izquierda de "Samba group". "ok" para guardar.
Planitlla
Choose 'users' from the main menu. Change to 'Students' in the Base
field. An Entry NewStudent
should show up,
click it. This is the 'students' template, not a real user. As you'll have
to create such a template (to be able to use csv import for your structure)
based on this one, notice all entries showing up in the Generic, POSIX and
Samba tabs, maybe take screenshots to have information ready for the new
template.
Now change to /Students/2014 in the Base field; choose Create/Template and start to fill in your desired values, first the Generic tab (add your new 2014 group under Group Membership, too), then add POSIX and Samba account.
Importar usuarios
Choose your new template when doing csv import; testing it with a few users is recommended.
Con este script, el administrador puede crear directorios en cada directorio personal de usuario y establecer los permisos de acceso y propiedad.
In the example shown below with group=teachers and permissions=2770 a user can hand in an assignment by saving the file to the folder "assignments" where teachers are given write access to be able to make comments.
#!/bin/bash home_path="/skole/tjener/home0" shared_folder="assignments" permissions="2770" created_dir=0 for home in $(ls $home_path); do if [ ! -d "$home_path/$home/$shared_folder" ]; then mkdir $home_path/$home/$shared_folder chmod $permissions $home_path/$home/$shared_folder #set the right owner and group #"username" = "group name" = "folder name" user=$home group=teachers chown $user:$group $home_path/$home/$shared_folder ((created_dir+=1)) else echo -e "the folder $home_path/$home/$shared_folder already exists.\n" fi done echo "$created_dir folders have been created"
When users insert a USB drive or a DVD / CD-ROM into a (diskless) workstation, a popup window appears asking what to do with it, just like in any other normal installation.
When users insert a USB drive or a DVD / CD-ROM into a thin client there is only a notify-window showing up for a few seconds. The media is automatically mounted and it is possible to access it browsing to the /media/$user folder. This is quite difficult for many non experienced users.
It is possible to have the default KDE "Plasma" file manager Dolphin showing
up if KDE "Plasma" (or LDXE, if installed in parallel to KDE "Plasma") is in
use as desktop environment. To configure this, simply execute
/usr/share/debian-edu-config/ltspfs-mounter-kde
enable
on the terminal server. (When using GNOME, device
icons will be placed on the desktop allowing easy access).
In addition the following script could be used to create the symlink "media" for all users in their home folder for easy access to USB drives, CD-ROM / DVD or whatever media is connected to the thin client. This might come in handy if users want to edit files directly on their plugged in media.
#!/bin/bash home_path="/skole/tjener/home0" shared_folder="media" permissions="775" created_dir=0; for home in $(ls $home_path); do if [ ! -d "$home_path/$home/$shared_folder" ]; then ln -s /media/$home $home_path/$home/$shared_folder ((created_dir+=1)) else echo -e "the folder $home_path/$home/$shared_folder already exists.\n" fi done echo "$created_dir folders has been created"
Warning: When inserted into an LTSP server USB drives and other removable
media cause popup messages on remote LTSP clients.
If remote users acknowledge the popup or use pmount from the console, they can even mount the removable devices and access the files.
Take these steps to set up a dedicated storage server for user home directories and possibly other data.
Add a new system of type server
using GOsa²
as outlined in the Getting
started chapter of this manual.
This example uses 'nas-server.intern' as the server name. Once 'nas-server.intern' is configured, check if the NFS export points on the new storage server are exported to the relevant subnets or machines:
root@tjener:~# showmount -e nas-server Export list for nas-server: /storage 10.0.0.0/8 root@tjener:~#
Here everything on the backbone network is granted access to the /storage export. (This could be restricted to netgroup membership or single IP addresses to limit NFS access like it is done in the tjener:/etc/exports file.)
Add automount information about 'nas-server.intern' in LDAP to allow all clients to automatically mount the new export on request.
This can't be done using GOsa², because a module for automount is missing. Instead, use ldapvi and add the required LDAP objects using an editor.
ldapvi --ldap-conf -ZD '(cn=admin)' -b
ou=automount,dc=skole,dc=skolelinux,dc=no
When the editor shows up, add the following LDAP objects at the bottom of the document. (The "/&" part in the last LDAP object is a wild card matching everything 'nas-server.intern' exports, removing the need to list individual mount points in LDAP.)
add cn=nas-server,ou=auto.skole,ou=automount,dc=skole,dc=skolelinux,dc=no objectClass: automount cn: nas-server automountInformation: -fstype=autofs --timeout=60 ldap:ou=auto.nas-server,ou=automount,dc=skole,dc=skolelinux,dc=no add ou=auto.nas-server,ou=automount,dc=skole,dc=skolelinux,dc=no objectClass: top objectClass: automountMap ou: auto.nas-server add cn=/,ou=auto.nas-server,ou=automount,dc=skole,dc=skolelinux,dc=no objectClass: automount cn: / automountInformation: -fstype=nfs,tcp,rsize=32768,wsize=32768,rw,intr,hard,nodev,nosuid,noatime nas-server.intern:/&
Add the relevant entries in tjener.intern:/etc/fstab, because tjener.intern does not use automount to avoid mounting loops:
Create the mount point directories using
mkdir
, edit '/etc/fstab' as adequate and
run mount -a
to mount the new resources.
Enable access in case diskless workstations are used. This is a special case, because sshfs is used instead of NFS and automount:
Create the mount point directories in the LTSP diskless client's root
(default /opt/ltsp/i386/
) as well.
Add a line containing 'LOCAL_APPS_EXTRAMOUNTS=/storage' to
/opt/ltsp/i386/etc/lts.conf
(example).
Create a link in each user's home dir like 'ln -s /storage Storage' to help users find the resources.
Now users should be able to access the files on 'nas-server.intern' directly by just visiting the '/tjener/nas-server/storage/' directory using any application on any workstation, LTSP thin client or LTSP server, and visiting ~/Storage in case an LTSP diskless client is used.
There are several ways to restrict ssh login, some are listed here.
If no LTSP clients are used a simple solution is to create a new group (say
sshusers
) and to add a line to the
machine's /etc/ssh/sshd_config file. Only members of the
sshusers
group will then be allowed to ssh
into the machine from everywhere.
Managing this case with GOsa is quite simple:
Create a group sshusers
on the base level
(where already other system management related groups like
gosa-admins
show up).
Add users to the new group sshusers
.
Add AllowGroups sshusers
to
/etc/ssh/sshd_config.
Execute service ssh restart
.
The default LTSP client setup uses ssh connections to the LTSP server. So a different approach using PAM is needed.
Enable pam_access.so in the LTSP server's /etc/pam.d/sshd file.
Configure /etc/security/access.conf to allow connections for (sample) users alice, jane, bob and john from everywhere and for all other users only from the internal networks by adding these lines:
+ : alice jane bob john : ALL + : ALL : 10.0.0.0/8 192.168.0.0/24 192.168.1.0/24 - : ALL : ALL #
If only dedicated LTSP servers are used, the 10.0.0.0/8 network could be dropped to disable internal ssh login access. Note: someone connecting his box to the dedicated LTSP client network(s) will gain ssh access to the LTSP server(s) as well.
If LTSP clients were attached to the backbone network 10.0.0.0/8 (combi server or LTSP cluster setup) things would be even more complicated and maybe only a sophisticated DHCP setup (in LDAP) checking the vendor-class-identifier together with appropriate PAM configuration would allow to disable internal ssh login.
To install other desktop environments after installation, simply use apt:
apt update apt install education-desktop-gnome education-desktop-lxde education-desktop-xfce education-desktop-mate
Users will then be able to choose any of the five desktop environment via the login manager before logging in. Of course, you can also choose to give less choices. Keep in mind that there will be several programs for the same purpose (like file managers, editors, PDF viewers...) if more than one desktop environment is installed; this might confuse users.
The use of LXDE as default on thin clients can be forced; see networked clients for details.
If you don't want to do installations with the default desktop KDE Plasma, you can also install with one of the four alternative desktops, GNOME, LXDE, Xfce or MATE directly.
The free software flash-player gnash
is
installed by default. Please note that Firefox ESR will drop Flash support
early 2018.
libdvdcss is needed for playing most commercial DVDs. For legal reasons it's
not included in Debian (Edu). If you are legally allowed to use it, you can
build your own local packages using the
libdvd-pkg
Debian package; make sure
contrib
is enabled in
/etc/apt/sources.list
.
apt update apt install libdvd-pkg
Answer the debconf questions, then run dpkg-reconfigure
libdvd-pkg
.
Un término genérico para clientes ligeros y estaciones de trabajo sin disco es cliente LTSP. LTSP es el acrónimo en Inglés para Linux Terminal Server Project.
Cliente ligero
A thin client setup enables an ordinary PC to function as an (X-)terminal, where all software runs on the LTSP server. This means that this machine boots from a diskette or directly from the server using network-PROM (or PXE) without using a local client hard drive.
Estaciones de trabajo sin disco
A diskless workstation runs all software locally. The client machines boot directly from the LTSP server without a local hard drive. Software is administered and maintained on the LTSP server (inside of the LTSP chroot), but it runs on the diskless workstation. Home directories and system settings are stored on the server too. Diskless workstations are an excellent way of reusing older (but powerful) hardware with the same low maintenance cost as with thin clients.
LTSP defines 320MB as the default minimum amount of RAM for diskless
workstations. If the amount of RAM is less, the machine will boot as thin
client. The related LTSP parameter is
FAT_RAM_THRESHOLD
with the default value
300. So if (for example) the clients should only boot as diskless
workstations if they have 1 GB RAM, add
FAT_RAM_THRESHOLD=1000
to lts.conf (or set
this in LDAP). Unlike workstations diskless workstations run without any
need to add them with GOsa², because LDM is used to login and connect to the
LTSP server.
LTSP client firmware
LTSP client boot will fail if the client's network interface requires a non-free firmware. A PXE installation can be used for troubleshooting problems with netbooting a machine; if the Debian Installer complains about a missing XXX.bin file then non-free firmware has to be added to the initrd used by LTSP clients.
En este caso, ejecute los siguientes comandos en un servidor LTSP.
# First get information about firmware packages apt-get update && apt-cache search ^firmware- # Decide which package has to be installed for the network interface(s). # Most probably this will be firmware-linux-nonfree. # Things have to take effect in the LTSP chroot for architecture i386. ltsp-chroot -a i386 apt-get update ltsp-chroot -d -a i386 apt-get -y -q install <package name> # copy the new initrd to the server's tftpboot directory and update the NBD image. ltsp-update-kernels ltsp-update-image
Una manera más corta sería instalar todos los firmware disponibles y actualizar el directorio tftpboot, podría ejecutar:
/usr/share/debian-edu-config/tools/ltsp-addfirmware
Each LTSP server has two ethernet interfaces: one configured in the main 10.0.0.0/8 subnet (which is shared with the main server), and another forming a local 192.168.0.0/24 subnet (a separate subnet for each LTSP server).
En la subred principal tendrá el menú PXE completo; la sured separada para cada servidor LTSP le permite seleccionar solo clientes sin discos y ligeros LTSP.
Using the default PXE menu on the main subnet 10.0.0.0/8, a machine could be started as diskless workstation or thin client. By default clients in the separate subnet 192.168.0.0/24 will run as diskless workstations if the amount of RAM is sufficient. If all clients in this LTSP client subnet should run as thin clients, the following has to be done.
(1)Open the file /opt/ltsp/i386/etc/ltsp/update-kernels.conf with an editor and replace the line CMDLINE_LINUX_DEFAULT="init=/sbin/init-ltsp quiet" with CMDLINE_LINUX_DEFAULT="init=/sbin/init-ltsp LTSP_FATCLIENT=False quiet" (2)Execute 'ltsp-chroot -a i386 /usr/share/ltsp/update-kernels' (3)Execute 'ltsp-update-kernels' (4)Execute 'ltsp-update-image'
La configuración PXE se genera usando el script
debian-edu-pxeinstall
. Se permite que
algunas configuraciones sean reconfiguradas agregando el archivo
/etc/debian-edu/pxeinstall.conf
con los
valores que desea reemplazar.
The PXE installation option is by default available to anyone able to PXE
boot a machine. To password protect the PXE installation options, a file
/var/lib/tftpboot/menupassword.cfg
can be
created with content similar to this:
MENU PASSWD $4$NDk0OTUzNTQ1NTQ5$7d6KvAlVCJKRKcijtVSPfveuWPM$
The password hash should be replaced with an MD5 hash for the desired password.
The PXE installation will inherit the language, keyboard layout and mirror
settings from the settings used when installing the main-server, and the
other questions will be asked during installation (profile, popcon
participation, partitioning and root password). To avoid these questions,
the file
/etc/debian-edu/www/debian-edu-install.dat
can be modified to provide preselected answers to debconf values. Some
examples of available debconf values are already commented in
/etc/debian-edu/www/debian-edu-install.dat
.
Your changes will be lost as soon as
debian-edu-pxeinstall
is used to recreate
the PXE-installation environment. To append debconf values to
/etc/debian-edu/www/debian-edu-install.dat
during recreation with
debian-edu-pxeinstall
, add the file
/etc/debian-edu/www/debian-edu-install.dat.local
with your additional debconf values.
More information about modifying PXE installations can be found in the Installation chapter.
For adding a custom repository add something like this to
/etc/debian-edu/www/debian-edu-install.dat.local
:
#add the skole projects local repository d-i apt-setup/local1/repository string http://example.org/debian stable main contrib non-free d-i apt-setup/local1/comment string Example Software Repository d-i apt-setup/local1/source boolean true d-i apt-setup/local1/key string http://example.org/key.asc
y luego ejecute una vez
/usr/sbin/debian-edu-pxeinstall
The PXE menu allows network booting of LTSP clients, the installer and other
alternatives. The file
/var/lib/tftpboot/pxelinux.cfg/default
is
used by default if no other file in that directory matches the client, and
out of the box it is set to link to
/var/lib/tftpboot/debian-edu/default-menu.cfg
.
If all clients should boot as diskless workstations instead of getting the full PXE menu, this can be implemented by changing the symlink:
ln -s /var/lib/tftpboot/debian-edu/default-diskless.cfg /var/lib/tftpboot/pxelinux.cfg/default
If all clients should boot as thin clients instead, change the symlink like this:
ln -s /var/lib/tftpboot/debian-edu/default-thin.cfg /var/lib/tftpboot/pxelinux.cfg/default
See also the PXELINUX documentation at http://syslinux.zytor.com/wiki/index.php/PXELINUX .
For performance and security considerations it might be desired to set up a separate main server which doesn't act as LTSP server.
To have ltspserver00 serve diskless workstations on the main (10.0.0.0/8) network, when the main server is not a combined server, follow these steps:
copy the ltsp
directory from
/var/lib/tftpboot
on ltspserver00 to the
same directory on the main server.
copy
/var/lib/tftpboot/debian-edu/default-diskless.cfg
to the same directory on the main server.
edit
/var/lib/tftpboot/debian-edu/default-diskless.cfg
to use the IP address of ltspserver00; the following example uses 10.0.2.10
for the IP address of ltspserver00 on the main network:
DEFAULT ltsp/i386/vmlinuz initrd=ltsp/i386/initrd.img nfsroot=10.0.2.10:/opt/ltsp/i386 init=/sbin/init-ltsp boot=nfs ro quiet ipappend 2
set the symlink in
/var/lib/tftpboot/pxelinux.cfg
on the main
server to point to
/var/lib/tftpboot/debian-edu/default-diskless.cfg
.
As an alternative, you could use ldapvi
,
search for 'next server tjener' and replace tjener with ltspserver00.
192.168.0.0/24 is the default LTSP client network if a machine is installed
using the LTSP profile. If lots of LTSP clients are used or if different
LTSP servers should serve both i386 and amd64 chroot environments the second
preconfigured network 192.168.1.0/24 could be used as well. Edit the file
/etc/network/interfaces
and adjust the eth1
settings accordingly. Use ldapvi
or any
other LDAP editor to inspect DNS and DHCP configuration.
The debian-edu-config package comes with a tool which helps in changing the
network from 10.0.0.0/8 to something else. Have a look at
/usr/share/debian-edu-config/tools/subnet-change
.
It is intended for use just after installation on the main server, to update
LDAP and other files that need to be edited to change the subnet.
Note that changing to one of the subnets already used elsewhere in Debian
Edu will not work. 192.168.0.0/24 and 192.168.1.0/24 are already set up as
LTSP client networks. Changing to these subnets will require manual editing
of configuration files to remove duplicate entries.
There is no easy way to change the DNS domain name. Changing it would require changes to both the LDAP structure and several files in the main server file system. There is also no easy way to change the host and DNS name of the main server (tjener.intern). To do so would also require changes to LDAP and files in the main-server and client file system. In both cases the Kerberos setup would have to be changed, too.
To configure specific thin clients with particular features, you can add
settings in LDAP or edit the file
/opt/ltsp/i386/etc/lts.conf
. Please note
that ltsp-update-image
has to be run after
each change to lts.conf. The image update isn't needed if lts.conf is copied
to the /var/lib/tftpboot/ltsp/i386/ directory.
We recommend to configure clients in LDAP (and not edit
lts.conf
directly, however, configuration
webforms for LTSP are currently not available in GOsa², you have to use a
plain LDAP browser/explorer or ldapvi
), as
this makes it possible to add and/or replace LTSP servers without loosing
(or having to redo) configuration.
The default values in LDAP are defined in the
cn=ltspConfigDefault,ou=ltsp,dc=skole,dc=skolelinux,dc=no
LDAP object using the ltspConfig
attribute. One can also add host specific entries in LDAP.
Run man lts.conf
to have a look at
available configuration options (see
/usr/share/doc/ltsp/LTSPManual.html
for
detailed information about LTSP).
The default values are defined under
[default]
; to configure one client, specify
it in terms of its MAC address or IP address like this:
[192.168.0.10]
.
Example: To make the thin client ltsp010 use 1280x1024 resolution, add something like this:
[192.168.0.10] X_MODE_0 = 1280x1024 X_HORZSYNC = "60-70" X_VERTREFRESH = "59-62"
somewhere below the default settings.
To force the use of a specific xserver on an LTSP client, set the
XSERVER
variable. For example:
[192.168.0.11] XSERVER = nvidia
If a thin client comes up with a black screen the use of a specific color depth might help. For example:
[192.168.0.12] X_COLOR_DEPTH=16
Depending on what changes you make, it may be necessary to restart the client.
To use IP addresses in lts.conf
you need to
add the client MAC address to your DHCP server. Otherwise you should use the
client MAC address directly in your
lts.conf
file.
Make sure that LXDE is installed on the LTSP server; then add these lines
below [default]
in "lts.conf":
LDM_SESSION=LXDE LDM_FORCE_SESSION=true
It is possible to set up the clients to connect to one of several LTSP
servers for load-balancing. This is done by providing
/opt/ltsp/i386/usr/share/ltsp/get_hosts
as
a script printing one or more servers for LDM to connect to. In addition to
this, each LTSP chroot needs to include the SSH host key for each of the
servers.
First of all, you must choose one LTSP server to be the load-balancing server. All the clients will PXE-boot from this server and load the Skolelinux image. After the image is loaded, LDM chooses which server to connect to by using the "get_hosts" script. You will decide later how this is done.
The load-balancing server must be announced to the clients as the
"next-server" via DHCP. As DHCP configuration is in LDAP, modifications have
to be done there. Use ldapvi --ldap-conf -ZD
'(cn=admin)'
to edit the appropriate entry in LDAP. (Enter
the main server's root password at the prompt; if VISUAL isn't set, the
default editor will be nano.) Search for a line reading
dhcpStatements: next-server tjener
Next-server should be the IP address or hostname of the server you chose to
be the load-balancing server. If you use hostname you must have a working
DNS. Remember to restart the DHCP service.
Now you have to move your clients from the 192.168.0.0 network to the 10.0.0.0 network; attach them to the backbone network instead of the network attached to the LTSP server's second network card. This is because when you use load-balancing, the clients need direct access to the server chosen by LDM. If you leave your clients on the 192.168.0.0 network, all of the clients' traffic will go through that server before it reaches the chosen LDM server.
Now you have to make a "get_hosts" script which generates a list of server names for LDM to connect to. The parameter LDM_SERVER overrides this script. In consequence, this parameter must not be defined if the get_hosts is going to be used. The get_hosts script writes on the standard output each server IP address or host name, in random order.
Edite "/opt/ltsp/i386/etc/lts.conf" y agregue algo como esto:
MY_SERVER_LIST = "xxxx xxxx xxxx"
Replace xxxx with either the IP addresses or hostnames of the servers as a
space-separated list. Then, put the following script in
/opt/ltsp/i386/usr/lib/ltsp/get_hosts
on
the server you chose to be the load-balancing server.
#!/bin/bash # Randomise the server list contained in MY_SERVER_LIST parameter TMP_LIST="" SHUFFLED_LIST="" for i in $MY_SERVER_LIST; do rank=$RANDOM let "rank %= 100" TMP_LIST="$TMP_LIST\n${rank}_$i" done TMP_LIST=$(echo -e $TMP_LIST | sort) for i in $TMP_LIST; do SHUFFLED_LIST="$SHUFFLED_LIST $(echo $i | cut -d_ -f2)" done echo $SHUFFLED_LIST
Now that you've made the "get_hosts" script, it's time to make the SSH host
key for the LTSP chroots. This can be done by making a file containing the
content of
/opt/ltsp/i386/etc/ssh/ssh_known_hosts
from
all the LTSP servers that will be load-balanced. Save this file as
/etc/ltsp/ssh_known_hosts.extra
on all
load-balanced servers. The last step is very important because
ltsp-update-sshkeys runs every time a server is booted, and
/etc/ltsp/ssh_known_hosts.extra
is included
if it exists.
If you save your new host file as
/opt/ltsp/i386/etc/ssh/ssh_known_hosts
, it
will be erased when you reboot the server.
There are some obvious weaknesses with this setup. All clients get their image from the same server, which causes high loads on the server if many clients are booted at the same time. Also, the clients require that server to be always available; without it they cannot boot or get an LDM server. Therefore this setup is very dependent on one server, which isn't very good.
¡Sus clientes ahora deberían tener balanceo de carga!
LTSP thin clients use networked audio to pass audio from the server to the clients.
LTSP diskless workstations handle audio locally.
Attach the printer to the LTSP client machine (both USB and parallel port are supported).
Configure this machine to run a printer in lts.conf (default location:
/opt/ltsp/i386/etc/lts.conf
), see the LTSP
manual
/usr/share/doc/ltsp/LTSPManual.html#printer
for details.
Configure the printer using the web interface
https://www:631
on the main server; choose
network printer type AppSocket/HP JetDirect
(for all printers regardless of brand or model) and set
socket://<LTSP client ip>:9100
as
connection URI.
It is useful to upgrade the LTSP environment with new packages fairly often, to make sure security fixes and improvements are made available. To upgrade, run these commands as user root on each LTSP server:
ltsp-chroot -a i386 # this does "chroot /opt/ltsp/i386" and more, ie it also prevents daemons from being started apt update apt upgrade apt full-upgrade exit ltsp-update-image
To install additional software for an LTSP client you must perform the installation inside the chroot of the LTSP server.
ltsp-chroot -a i386 ## optionally, edit the sources.list: #editor /etc/apt/sources.list apt update apt install $new_package exit ltsp-update-image
Skolelinux has added several security features on the client network
preventing unauthorised superuser access, password sniffing, and other
tricks which may be used on a local network. One such security measure is
secure login using SSH, which is the default with LDM. This can slow down
some client machines which are more than about fifteen years old, with as
little as a 160 MHz processor and 32 MB RAM. Although it's not recommended,
you can add a line to
/opt/ltsp/i386/etc/lts.conf
containing:
LDM_DIRECTX=True
Warning: The above protects initial
login, but all activities after that use unencrypted networked X. Passwords
(except the initial one) will travel in cleartext over the network, as well
as anything else.
Note: Since such fifteen-year-old thin clients may also have trouble running newer versions of LibreOffice and Firefox due to pixmap caching issues, you may consider running thin clients with at least 128 MB RAM, or upgrade the hardware, which will also give you the benefit of being able to use them as diskless workstations.
For Windows clients the Windows domain "SKOLELINUX" is available to be joined. A special service called Samba, installed on the main server, enables Windows clients to store profiles and user data, and also authenticates the users during the login.
Joining a domain with a Windows client requires the steps described in the
Debian Edu Stretch Samba Howto.
Windows will sync the profiles of domain users on every Windows login and logout. Depending on how much data is stored in the profile, this could take some time. To minimise the time needed, deactivate things like local cache in browsers (you can use the Squid proxy cache installed on the main server instead) and save files into the H: volume rather than under "My Documents".
Users bringing in their XP laptops from home can still connect to the main server using their skolelinux credentials, provided the workgroup is set to SKOLELINUX. However, they may need to disable the Windows firewall before the main server will appear in Network Neighbourhood (or whatever it's called now).
Roaming profiles contain user work environments which include desktop items and settings. Examples include personal files, desktop icons and menus, screen colours, mouse settings, window size and position, application configurations, and network and printer connections. Roaming profiles are available wherever the user logs on, provided the server is available.
Since the profile is copied from the server to the machine during logon, and copied back to the server during logout, a large profile can make Windows login/logout painfully slow. There can be many reasons for a large profile, but the most common problem is that users save their files on the Windows desktop or in the "My Documents" folder instead of in their home directory. Also, some badly designed programs use the profile to store data and as scratch space.
The educational approach: one way to deal with overlarge profiles is to explain the situation to the users. Tell them not to store huge files on the desktop, and if they fail to listen, it's their own fault when login is slow.
Tweaking the profile: a different approach to dealing with the problem is to remove parts of the profile, and redirect other parts to regular file storage. This moves the workload from the users to the administrator, while adding complexity to the installation. There are at least three ways to edit the parts that are removed from the roaming profile.
FIXME: Maybe it is better to purge the examples. People who want to use roaming profiles should know what they are doing ...
Note The examples are outdated since in
wheezy kerberos was configured for samba too!
You might find an example smb.conf in your preferred language delivered by
the installation on the main server under
/usr/share/doc/debian-edu-config/examples/
.
The source file is in English and is called
smb-roaming-profiles-en.conf
; look for a
file with the appropriate code in the filename (the German translation, for
example, will be named
smb-roaming-profiles-de.conf
). Inside the
config file are a lot of explanations which you should have a look at.
Machine policies can be edited and copied to all the other computers.
Pick a freshly installed Windows computer, and run
gpedit.msc
Under the selection "User Configuration" -> "Administrative Templates" -> "System" -> "User Profiles" -> "Exclude directories in roaming profile", you can enter a semicolon-separated list of directories to exclude from the profile. The directories are internationalised and must be written in your own language the way they are in the profile. Examples of directories to exclude are:
log
Locale settings
Temporary Internet Files
My Documents
Application Data
Temporary Internet Files
Save your changes, and exit the editor.
Copy c:\windows\system32\GroupPolicy
to all
other Windows machines.
It's a good idea to copy it to your Windows OS deployment system to have it included at install time.
By using the legacy Windows policy editor
(poledit.exe
), you can create a Policy file
(NTConfig.pol) and put it in your netlogon share on the main server. This
has the advantage of working almost instantly on all Windows machines.
For some time, the policy editor standalone download has been removed from the Microsoft web site, but it's still available as part of the ORK Tools.
With poledit.exe
you can create .pol
files. If you put such a file on the main server as
/etc/samba/netlogon/NTLOGON.POL
it will
automatically be read by Windows machines and temporarily overwrite the
registry, thus applying the changes.
To make sensible use of poledit.exe
you
also need to download appropriate .adm files for your operating system and
applications; otherwise you cannot define many settings in
poledit.exe
.
Be aware that the new group policy tools,
gpedit.msc
and
gpmc.msc
, cannot create .pol files; they
either only work for the local machine or need an Active Directory server.
If you understand German, http://gruppenrichtlinien.de is a very good web site on this topic.
You can edit the registry of the local computer, and copy this registry key to other computers
Iniciar el editor del registro.
Navigate to HKEY_CURRENT_USER\Software\Microsoft\Windows
NT\CurrentVersion\Winlogon
Use the menu "Edit menu" -> "New" -> "String Value".
Call it ExcludeProfileDirs
Enter a semicolon-separated list of paths to exclude (in the same way as for a machine policy)
Now you can choose to export this registry key as a .reg file. Mark a selection, right-click, and select "Export".
Save the file and you can double click it, or add it to a script to spread it to other machines.
Fuentes:
Sometimes just removing directories from the profile is not enough. You may find that users lose files because they mistakenly save things into "My Documents" when this is not saved in the profiles. You may also want to redirect the directories used by some badly programmed applications to normal network shares.
All the instructions given above about machine policies apply here too. You
can use gpedit.msc
to edit the policy and
copy it to all machines. The redirection should be available under "User
Configuration" -> "Windows Settings" -> "Folder
Redirection". Directories that it can be useful to redirect include
"Desktop" and "My Documents".
One thing to remember is that if you enable folder redirection, those folders are automatically added to the synchronised folders list. If you do not want this, you should disable it via one of the following routes:
"User Configuration" -> "Administrative Templates" -> "Network" -> "Offline Files"
"Computer Configuration" -> "Administrative Templates" -> "Network" -> "Offline Files"
Using local policies, you can disable the roaming profile on individual machines. This is often wanted on special machines - for instance on dedicated machines, or machines that have lower than usual bandwith.
You can use the machine policy method describe above; the key is in "Administrative Templates" -> "System" -> "User Profiles" -> "Only allow local profiles".
FIXME: describe roaming profile key for the global policy editor here
If, perhaps, everyone has their own dedicated machine, and nobody else is
allowed to touch it, editing the Samba configuration will let you disable
roaming profiles for the entire network. You can alter the
smb.conf
file on the main server, unsetting
the "logon path" and "logon home" variables, then restart samba.
logon path = "" logon home = ""
Choosing the LTSP server profile or the combined server profile also installs xrdp, a package which uses the Remote Desktop Protocol to present a graphical login to a remote client. Microsoft Windows users can connect to the LTSP server running xrdp without installing additional software - they simply start a Remote Desktop Connection on their Windows machine and connect.
Additionally, xrdp can connect to a VNC server or another RDP server.
Some municipalities provide a remote desktop solution so that students and teachers can access Skolelinux from their home computer running Windows, Mac or Linux.
Xrdp comes without sound support; to compile the required modules this script could be used.
#!/bin/bash # Script to compile / recompile xrdp PulseAudio modules. # The caller needs to be root or a member of the sudo group. # Also, /etc/apt/sources.list must contain a valid deb-src line. set -e if [[ $UID -ne 0 ]] ; then if ! groups | egrep -q sudo ; then echo "ERROR: You need to be root or a sudo group member." exit 1 fi fi if ! egrep -q ^deb-src /etc/apt/sources.list ; then echo "ERROR: Make sure /etc/apt/sources.list contains a deb-src line." exit 1 fi TMP=$(mktemp -d) PULSE_UPSTREAM_VERSION="$(dpkg-query -W -f='${source:Upstream-Version}' pulseaudio)" XRDP_UPSTREAM_VERSION="$(dpkg-query -W -f='${source:Upstream-Version}' xrdp)" sudo apt -q update # Get sources and build dependencies: sudo apt -q install dpkg-dev cd $TMP apt -q source pulseaudio xrdp sudo apt -q build-dep pulseaudio xrdp # For pulseaudio 'configure' is all what is needed: cd pulseaudio-$PULSE_UPSTREAM_VERSION/ ./configure # Adjust pulseaudio modules Makefile (needs absolute path) # and build the pulseaudio modules. cd $TMP/xrdp-$XRDP_UPSTREAM_VERSION/sesman/chansrv/pulse/ sed -i 's/^PULSE/#PULSE/' Makefile sed -i "/#PULSE_DIR/a \ PULSE_DIR = $TMP/pulseaudio-$PULSE_UPSTREAM_VERSION" Makefile make # Copy modules to Pulseaudio modules directory, adjust rights. sudo cp *.so /usr/lib/pulse-$PULSE_UPSTREAM_VERSION/modules/ sudo chmod 644 /usr/lib/pulse-$PULSE_UPSTREAM_VERSION/modules/module-xrdp* # Restart xrdp, now with sound enabled. sudo service xrdp restart
freerdp-x11
is installed by default and is
capable of RDP and VNC.
RDP - the easiest way to access Windows terminal server. An alternative
client package is rdesktop
.
VNC client (Virtual Network Computer) gives access to Skolelinux remotely.
An alternative client package is
xvncviewer
.
NX graphical client gives students and teachers access to Skolelinux remotely on Windows, Mac or Linux PC. One municipality in Norway has provided NX support to all students since 2005. They report that the solution is stable.
Citrix ICA client HowTo to access Windows terminal server from Skolelinux.
The information in this chapter is outdated. Please read the information
provided on the Samba wiki about supported Windows versions, needed registry
patches and other procedures. Probably a line containing
server max protocol = NT1
needs to be added
to the [global]
section of
/etc/samba/smb-debian-edu.conf
on the main
server. Please consider updating this chapter if you know how to configure
Samba for Debian Edu.
https://wiki.samba.org/index.php/Joining_a_Windows_Client_or_Server_to_a_Domain
https://wiki.samba.org/index.php/Required_Settings_for_Samba_NT4_Domains
Samba has been fully prepared for use as an NT4-style domain controller with Windows XP, Windows Vista and Windows 7 as clients. After a machine has joined the domain, this machine can be fully managed with GOsa².
This documentation presumes that you have installed the Debian Edu main server and maybe also a Debian Edu workstation to verify that working under Debian Edu/Skolelinux works for you. We presume that you have already created some users that can flawlessly use the Debian Edu workstation. We also presume that you have a Windows XP/Vista/7 workstation at hand, so you can test access to the Debian Edu main server from a Windows machine.
Después de la instalación del servidor principal de Debian Edu, \\TJENER debería ser visible desde computadoras con Windows. El dominio de Debian Edu en Windows es SKOLELINUX. Utilice una computadora con Windows (o Linux con smbclient) para explorar su entorno de red de Windows/Samba.
INICIO -> comando ejecutar.
Esriba \\TJENER y presione enter.
-> a Windows Explorer window should open and show the netlogon share on \\TJENER, and maybe printers you already have configured for printing under Unix/Linux (CUPS queues).
Cuentas de usuarios de estudiantes y profesores que han sido configuradas mediante GOsa² pueden ingresar a \\TJENER\HOMES o \\TJENER\<username> y acceder a sus directorios personales con computadoras Windows que no se han unido al dominio SKOLELINUX.
INICIO -> comando ejecutar.
Escriba \\TJENER\HOMES o \\TJENER\<username> y presione enter.
Escriba su datos de usuario y contraseña en la ventana de autenticación que aparece.
-> una ventana de explorador de Windows se abrirá y le mostrará los archivos y directorios en su directorio personal de Debian Edu.
Por defecto, solamente [home] y [netlogon] son exportadas; más ejemplos para
estudiantes y profesores sobre como compartir pueden encontrarse en
/etc/samba/smb-debian-edu.conf
en el
servidor principal de Debian Edu.
To use Samba on TJENER as a domain controller, your network's Windows workstations have to join the SKOLELINUX domain provided by the Debian Edu main server.
The first thing you have to do is to enable the SKOLELINUX\Administrator account. This account is not intended for day-to-day usage; its current main purpose is to add Windows machines to the SKOLELINUX domain. To enable this account log on to TJENER as the first user (created during main server installation) and run this command:
$ sudo smbpasswd -e Administrator
The password of SKOLELINUX\Administrator has been preconfigured during the main server's installation. Please use the system's root account when authenticating as SKOLELINUX\Administrator.
Once you are done with your administrative work make sure to disable the SKOLELINUX\Administrator account again:
$ sudo smbpasswd -d Administrator
Make sure your Windows machine has the name that you want to use in the SKOLELINUX domain. If not, rename it first (and then reboot). The NetBIOS host name of the Windows machine will later on be used in GOsa² and cannot be changed there (without breaking the domain membership for this machine).
Joining Windows XP machines (tested with Service Pack 3) works out of the box.
Nota: Windows XP Home no soporta membresía por dominio, Windows XP Profesional es requerido.
Ingrese a la computadora Windows XP como adminsitrador (o cualquier cuenta con privilegios de administración).
Haga clic en "inicio", luego presione clic-derecho en "Computadora" y luego haga clic en "Propiedades".
Seleccione la pestaña "Nombre de computadora" y haga clic en "Cambiar…"
Debajo de "Miembro de", seleccione el botón junto a "Dominio:", escriba SKOLELINUX y luego haga clic en "OK"
Una ventana emergente le solicitará ingresar las credenciales de una cuenta con derechos de unirse al dominio. Escriba SKOLELINUX\Administrator en el campo nombre de usuario y la contraseña de usuario root del servidor principal, luego haga clic en "OK".
Una ventana emergente de confirmación le dará la bienvenida al dominio SKOLELINUX. Al hacer clic en "OK", tendrá otro mensaje informándole que necesita reiniciar la computadora para que los cambios puedan aplicarse. Haga clic en "OK".
After the reboot, when you login the first time, click on the "Options >>" button and select the domain SKOLELINUX instead of the local domain ("this computer").
Si el ingreso al dominio ha sido exitoso, usted podrá ver los detalles del equipo en GOsa² (en el menú "Sistemas").
Unir computadoras Windows Vista/7 al dominio SKOLELINUX, requiere la instalación de un parche en el registro del cliente Windows Vista/7. Este parche se encuentra en:
\\tjener\netlogon\win7+samba_domain-membership\Win7_Samba3DomainMember.reg
Para más información, consulte el archivo README_Win7-Domain-Membership.txt en el mismo directorio. Asegúrese de aplicar este parche como administrador local en el sistema Windows.
Después de aplicar el parche anterior y reiniciar el cliente, podrá unirse al dominio SKOLELINUX:
Haga clic en "inicio", luego presione clic-derecho en "Computadora" y luego haga clic en "Propiedades".
the basic system information page will open. Under "Computer name, domain, and workgroup settings", click on "Change Settings"
on the System Properties page, click on "Change..."
Debajo de "Miembro de", seleccione el botón junto a "Dominio:", escriba SKOLELINUX y luego haga clic en "OK"
Una ventana emergente le solicitará ingresar las credenciales de una cuenta con derechos de unirse al dominio. Escriba SKOLELINUX\Administrator en el campo nombre de usuario y la contraseña de usuario root del servidor principal, luego haga clic en "OK".
Una ventana emergente de confirmación le dará la bienvenida al dominio SKOLELINUX. Al hacer clic en "OK", tendrá otro mensaje informándole que necesita reiniciar la computadora para que los cambios puedan aplicarse. Haga clic en "OK".
After the reboot, when you login the first time, click on the "Options >>" button and select the domain SKOLELINUX instead of the local domain ("this computer").
Si el ingreso al dominio ha sido exitoso, usted podrá ver los detalles del equipo en GOsa² (en el menú "Sistemas").
Debian Edu ships some logon scripts that pre-configure the Windows user profile on first logon. When logging on to a Windows workstation that has joined the SKOLELINUX domain for the first time the following tasks are run:
copy the user's Firefox profile to a separate location and register that with Mozilla Firefox on Windows
set up Web-Proxy and start page in Firefox
set up Web-Proxy and start page in IE
add a MyHome icon to the Desktop that points to drive H: and opens Windows Explorer on double-click
Other tasks are run on every logon. For further information on this, please
refer to the /etc/samba/netlogon
folder on
your Debian Edu main server.
All Debian packages mentioned in this section can be installed by running
apt install <package>
(as root).
SWI-Prolog is an open source implementation of the programming language Prolog, commonly used for teaching and semantic web applications.
Warning: make sure you know the status of
the laws about monitoring and restricting computer users' activities in your
jurisdiction.
Some schools use control tools like Epoptes or iTALC to supervise their students. See also: Epoptes Homepage and iTALC Homepage.
To get full Epoptes support, these steps are required.
# Run on a combi server (and on each additional ltsp server): apt update apt install epoptes ltsp-chroot -m --arch i386 apt update ltsp-chroot -m --arch i386 apt install epoptes-client ltsp-chroot -m --arch i386 apt install ssvnc ltsp-chroot -m --arch i386 sed -i 's/test -f/#test -f/' /etc/init.d/epoptes-client ltsp-chroot -m --arch i386 sed -i 's/grep -qs/#grep -qs/' /etc/init.d/epoptes-client # If diskspace matters, use 'ltsp-update-image -n' instead. ltsp-update-image
Some schools use Squidguard or Dansguardian to restrict Internet access.
The HowTos from http://wiki.debian.org/DebianEdu/HowTo/ are either user- or developer-specific. Let's move the user-specific HowTos over here (and delete them over there)! (But first ask the authors if they are happy with moving them and putting them under the GPL - see the page histories to find them.)
http://wiki.debian.org/DebianEdu/HowTo/TeacherFirstStep - incomplete but interesting
Casa usuario debería cambiar su contraseña usando GOsa². Para hacerlo, solo
use un navegador web y vaya a
https://www/gosa/
.
Using GOsa² to change the password ensures that passwords for Kerberos (krbPrincipalKey), LDAP (userPassword) and Samba (sambaNTPassword and sambaLMPassword) are the same.
Changing passwords using PAM is working also at the GDM login prompt, but this will only update the Kerberos password, and not the Samba and GOsa² (LDAP) password. So after you changed your password at the login prompt, you really should also change it using GOsa².
Standalone Java applications are supported out of the box by the OpenJDK Java runtime.
All users can send and receive mails within the internal network;
self-signed certificates are provided to allow TLS secured connections. To
allow mail outside the internal network, the administrator needs to
configure the mailserver exim4
to suit the
local situation, starting with dpkg-reconfigure
exim4-config
.
Every user who wants to use Thunderbird needs to configure it as follows. For a user with username jdoe the internal email address is jdoe@postoffice.intern.
Start Thunderbird
Click 'Skip this and use my existing email'
Enter your email address
Uncheck 'Remember password'
Don't enter your password as Kerberos single sign on will be used
Click 'Continue'
For both IMAP and SMTP the settings should be 'STARTTLS' and 'Kerberos/GSSAPI'; adjust if not detected automatically
Click 'Done'
First time accessing the inbox click 'Confirm Security Exception' to accept the certificate; same applies if sending mail for the first time.
Existen usuarios de Debian Edu alrededor del mundo. Una forma fácil de
contribuir es dejarnos saber que existes y usas Debian Edu, esto nos motiva
y, por lo tanto, ya es una contribución valiosa.
El proyecto Debian Edu provee una base de datos de escuelas y usuarios del sistema para ayudar a encontrarse entre ellos mismos y también para dar una idea sobre la ubicación de los usuarios. Háganos saber sobre su instalación de Debian Edu, registrándose en esta base de datos. Para registrar su escuela, useeste formulario web.
Actualmente hay equipos locales en Noruega, Alemania, la región de Extremadura en España, Taiwan y Francia. Contruibdores y usuarias "aislados" existen en Grecia, Holanda, Japan y otros lugares.
El capítulo de soporte contiene explicaciones y enlaces a recursos localizados, ya que contruibuir y apoyar son dos lados de la misma moneda.
A nivel internacional estamos organizados en varios equipos que trabajan en distintas áreas.
Most of the time, the developer mailing list is our main medium for communication, though we have monthly IRC meetings on #debian-edu on irc.debian.org and even, less frequently, real gatherings, where we meet each other in person. New contributors should read our http://wiki.debian.org/DebianEdu/ArchivePolicy.
A good way to learn what is happening in the development of Debian Edu is to subscribe to the commit mailinglist.
¡Este documento necesita de su ayuda! No está finalizado todavía: si lo lee, notará varias lineas que dicen POR CORREGIR. Si usted saber lo que se necesita corregir, considere compartir su conocimiento con nosotros.
The source of the text is a wiki and can be edited with a simple webbrowser. Just go to http://wiki.debian.org/DebianEdu/Documentation/Stretch/ and you can contribute easily. Note: a user account is needed to edit the pages; you need to create a wiki user first.
Another very good way to contribute and to help users is by translating software and documentation. Information on how to translate this document can be found in the translations chapter of this book. Please consider helping the translation effort of this book!
https://lists.skolelinux.org/listinfo/admin-discuss - support mailing list
#debian-edu on irc.debian.org - IRC channel, mostly development related; do
not expect real time support even though it frequently happens
https://lists.skolelinux.org/listinfo/bruker - support mailing list
https://lists.skolelinux.org/listinfo/linuxiskolen - mailing list for the development member organisation in Norway (FRISK)
#skolelinux en irc.debian.org - canal IRC para soporte en Noruego
http://lists.debian.org/debian-edu-german - support mailing list
http://wiki.skolelinux.de - wiki with lots of HowTos etc.
#skolelinux.de en irc.debian.org - canal IRC para soporte en Alemán
http://lists.debian.org/debian-edu-french - support mailing list
Lists of companies providing professional support are available from http://wiki.debian.org/DebianEdu/Help/ProfessionalHelp.
New version of debian-installer from Debian Stretch, see its installation manual for more details.
The "Thin-Client-Server" profile has been renamed to "LTSP-Server" profile.
New artwork based on the "soft Waves" theme, the default artwork for Debian 9 Stretch.
Everything which is new in Debian 9 Stretch, eg:
Linux kernel 4.9
Desktop environments KDE Plasma Workspace 5.8, GNOME 3.22, Xfce 4.12, LXDE 0.99.2, MATE 1.16
KDE Plasma Workspace is installed by default; to choose one of the others see this manual.
Firefox 45.9 ESR and Chromium 59
Iceweasel has been re-renamed to Firefox!
Icedove has been re-renamed to Thunderbird and is now installed by default.
LibreOffice 5.2.6
Educational toolbox GCompris 15.10
Music creator Rosegarden 16.06
GOsa 2.7.4
LTSP 5.5.9
Debian Stretch includes more than 50000 packages available for installation.
More information about Debian 9 Stretch is provided in the release notes and the installation manual.
Translation updates for the templates used in the installer. These templates are now available in 29 languages.
The Debian Edu Stretch Manual is fully translated to German, French, Italian, Danish, Dutch, Norwegian Bokmål and Japanese. The Japanese translation was newly added for Stretch.
Partly translated versions exist for Spanish, Polish and Simplified Chinese.
Icinga replaces Nagios as monitoring tool.
kde-spectacle replaces ksnapshot as screenshot tool.
The free flash player gnash is back again.
Plymouth is installed and activated by default, except for the 'Main Server' and 'Minimal' profiles; pressing ESC allows to view boot and shutdown messages.
Upon upgrade from Jessie the LDAP data base has to be adjusted. The sudoHost value 'tjener' has to be replaced with 'tjener.intern' using GOsa² or an LDAP editor.
The 32-bit PC support (known as the Debian architecture i386) now no longer covers a plain i586 processor. The new baseline is the i686, although some i586 processors (e.g. the "AMD Geode") will remain supported.
Debian 9 enables unattended upgrades (for security updates) by default for new installations. This might cause a delay of about 15 minutes if a system with a low uptime value is powered off.
LTSP now uses NBD instead of NFS for the root filesystem. After each single
change to an LTSP chroot, the related NBD image must be regenerated
(ltsp-update-image
) for the changes to take
effect.
Concurrent logins of the same user on LTSP server and LTSP thin client are no longer allowed.
This document is written and copyrighted by Holger Levsen (2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017), Petter Reinholdtsen (2001, 2002, 2003, 2004, 2007, 2008, 2009, 2010, 2012, 2014), Daniel Heß (2007), Patrick Winnertz (2007), Knut Yrvin (2007), Ralf Gesellensetter (2007), Ronny Aasen (2007), Morten Werner Forsbring (2007), Bjarne Nielsen (2007, 2008), Nigel Barker (2007), José L. Redrejo Rodríguez (2007), John Bildoy (2007), Joakim Seeberg (2008), Jürgen Leibner (2009, 2010, 2011, 2012, 2014), Oded Naveh (2009), Philipp Hübner (2009, 2010), Andreas Mundt (2010), Olivier Vitrat (2010, 2012), Vagrant Cascadian (2010), Mike Gabriel (2011), Justin B Rye (2012), David Prévot (2012), Wolfgang Schweer (2012, 2013, 2014, 2015, 2016, 2017), Bernhard Hammes (2012) and Joe Hansen (2015) and is released under the GPL2 or any later version. Enjoy!
If you add content to it, please only do so if you are the author. You need to release it under the same conditions! Then add your name here and release it under the "GPL v2 or any later version" licence.
The Spanish translation is copyrighted by José L. Redrejo Rodríguez (2007), Rafael Rivas (2009, 2010, 2011, 2012, 2015) and Norman Garcia (2010, 2012, 2013) and is released under the GPL v2 or any later version.
The Bokmål translation is copyrighted by Petter Reinholdtsen (2007, 2012, 2014, 2015, 2016, 2017), Håvard Korsvoll (2007-2009), Tore Skogly (2008), Ole-Anders Andreassen (2010), Jan Roar Rød (2010), Ole-Erik Yrvin (2014, 2016, 2017), Ingrid Yrvin (2014, 2015, 2016, 2017), Hans Arthur Kielland Aanesen (2014), Knut Yrvin (2014), FourFire Le'bard (2014), Stefan Mitchell-Lauridsen (2014) and Ragnar Wisløff (2014) and is released under the GPL v2 or any later version.
The German translation is copyrighted by Holger Levsen (2007), Patrick Winnertz (2007), Ralf Gesellensetter (2007, 2009), Roland F. Teichert (2007, 2008, 2009), Jürgen Leibner (2007, 2009, 2011, 2014), Ludger Sicking (2008, 2010), Kai Hatje (2008), Kurt Gramlich (2009), Franziska Teichert (2009), Philipp Hübner (2009), Andreas Mundt (2009, 2010) and Wolfgang Schweer (2012, 2013, 2014, 2015, 2016, 2017) and is released under the GPL v2 or any later version.
The Italian translation is copyrighted by Claudio Carboncini (2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017) and Beatrice Torracca (2013, 2014) and is released under the GPL v2 or any later version.
The French translation is copyrighted by Christophe Masson (2008), Olivier Vitrat (2010), Cédric Boutillier (2012, 2013, 2014, 2015), Jean-Paul Guilloneau (2012), David Prévot (2012), Thomas Vincent (2012) and the French l10n team (2009, 2010, 2012) and is released under the GPL v2 or any later version.
The Danish translation is copyrighted by Joe Hansen (2012, 2013, 2014, 2015, 2016) and is released under the GPL v2 or any later version.
The Dutch translation is copyrighted by Frans Spiesschaert (2014, 2015, 2016, 2017) and is released under the GPL v2 or any later version.
The Japanese translation is copyrighted by victory (2016, 2017) and is released under the GPL v2 or any later version.
The Polish translation is copyrighted by Stanisław Krukowski (2016, 2017) and is released under the GPL v2 or any later version.
The Simplified Chinese translation is copyrighted by Ma Yong (2016, 2017), Boyuan Yang (2017) and Roy Zhang (2017) and is released under the GPL v2 or any later version.
Versions of this document translated into German, Italian, French, Danish, Dutch, Norwegian Bokmål and Japanese are available. Incomplete translations exist for Spanish, Polish and Simplified Chinese. There is an online overview of shipped translations.
As in many free software projects, translations of this document are kept in
PO files. More information about the process can be found in
/usr/share/doc/debian-edu-doc/README.debian-edu-stretch-manual-translations
.
The Git repository (see below) contains this file too. Take a look there and
at the language
specific conventions if you want to help translating this document.
To commit your translations you need to be a member of the Alioth project
debian-edu
. If your Alioth username differs
from your local one, create or edit
~/.ssh/config
. Add a config block like
this:
Host git.debian.org User <your-alioth-username>
Then check out the debian-edu-doc
source
using ssh access: git clone
git+ssh://git.debian.org/git/debian-edu/debian-edu-doc.git
If you only want to translate, you need to check out only a few files from Git (which can be done anonymously). Please file a bug against the debian-edu-doc package and attach the PO file to the bugreport. See instructions on how to submit bugs for more information.
You can check out the debian-edu-doc
source
anonymously with the following command (you need to have the
git
package installed for this to work):
git clone
git://anonscm.debian.org/debian-edu/debian-edu-doc.git
Then edit the file
documentation/debian-edu-stretch/debian-edu-stretch-manual.$CC.po
(replacing $CC with your language code). There are many tools for
translating available; we suggest using
lokalize
.
Then you either commit the file directly to Git (if you have the rights to do so) or send the file to the bugreport.
To update your local copy of the repository use the following command inside
the debian-edu-doc
directory:
git pull
Read /usr/share/doc/debian-edu-doc/README.debian-edu-stretch-manual-translations to find information how to create a new PO file for your language if there isn't one yet, and how to update translations.
Please keep in mind that this manual is still under development, so don't translate any string which contains " FIXME".
Basic information about Alioth (the host where our Git repository is located) and Git is available at http://wiki.debian.org/Alioth/Git.
If you are new to Git, look at the Pro
Git book; it has a chapter on the recording
changes to the repository. Also you might want to look at the
gitk
package that provides a GUI for Git.
Some language teams have decided to translate via Weblate. See https://hosted.weblate.org/projects/debian-edu-documentation/debian-edu-stretch/ for more information.
Please report any problems.
Note to translators: there is no need to translate the GPL license text. Translations are available at https://www.gnu.org/licenses/old-licenses/gpl-2.0-translations.html.
Copyright (C) 2007-2017 Holger Levsen < holger@layer-acht.org > and others, see the Copyright chapter for the full list of copyright owners.
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc. 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program.
You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.
c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program.
In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.
3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.
If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.
7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.
It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.
This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.
10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
Debian Edu Live CD/DVDs for Stretch are not available at the moment, but are
being worked on...
XFCE desktop
All packages from the Standalone profile
Todos los paquetes de la tarea «laptop»
XFCE desktop
All packages from the Workstation profile
Todos los paquetes de la tarea «laptop»
To activate a specific translation, boot using
locale=ll_CC.UTF-8
as a boot option, where
ll_CC.UTF-8 is the locale name you want. To activate a given keyboard
layout, use the keyb=KB
option where KB is
the desired keyboard layout. Here is a list of commonly used locale codes:
Lenguaje (Región) |
Valores local |
Distribución del teclado |
Noruego (Bokmål) |
nb_NO.UTF-8 |
no |
Noruego (Nynorsk) |
nn_NO.UTF-8 |
no |
Alemán |
de_DE.UTF-8 |
de |
Francés (Francia) |
fr_FR.UTF-8 |
fr |
Griego (Grecia) |
el_GR.UTF-8 |
el |
Japonés |
ja_JP.UTF-8 |
jp |
Sami del Norte (Noruega) |
se_NO |
no(smi) |
La lista completa de los códigos locales esta disponible en
/usr/share/i18n/SUPPORTED
, pero únicamente
los locales con UTF-8 son soportados por la imagen «live». No todas las
traducciones locales tienen instalación. Las distribuciones de teclados
pueden ser encontradas en /usr/share/keymaps/i386/.
read the release announcement on www.debian.org: Debian Edu / Skolelinux Jessie — a complete Linux solution for your school.
Nueva versión de debian-installer de Debian Jessie, vea el manual de instalación para más detalles.
Everything which is new in Debian 8 Jessie, eg:
Linux kernel 3.16.x
Desktop environments KDE Plasma Workspace 4.11.13, GNOME 3.14, Xfce 4.10, LXDE 0.5.6
new optional desktop environment: MATE 1.8
KDE Plasma Workspace is installed by default; to choose one of the others see this manual.
the browsers Iceweasel 31 ESR and Chromium 41
LibreOffice 4.3.3
Educational toolbox GCompris 14.12
Music creator Rosegarden 14.02
GOsa 2.7.4
LTSP 5.5.4
new boot framework: systemd. More information is available in the Debian systemd wiki page and in thesystemd manual.
Debian Jessie includes about 42000 packages available for installation.
More information about Debian 8 Jessie is provided in the release notes and the installation manual.
Translation updates for the templates used in the installer. These templates are now available in 29 languages.
Two manual translations have been completed: Dutch and Norwegian Bokmål.
The Debian Edu Jessie Manual is fully translated to German, French, Italian, Danish, Dutch and Norwegian Bokmål. A partly translated version exists for Spanish.
squid: Shutdown and reboot of the main server takes
longer than before due to a new default setting
shutdown_lifetime 30 seconds
. As an example
the delay could be set to 10 seconds by appending the line
shutdown_lifetime 10 seconds
to
/etc/squid3/squid.conf
.
ssh: The root user is no longer allowed to login via
SSH with password. The old default PermitRootLogin
yes
has been replaced with PermitRootLogin
without-password
, so ssh-keys will still work.
slbackup-php: To be able to use the slbackup-php site
(which uses root logins via ssh), PermitRootLogin
yes
has to be set temporarily in
/etc/ssh/sshd_config
.
sugar: As the Sugar desktop was removed from Debian Jessie, it is also not available in Debian Edu jessie.
Updated artwork and new Debian Edu / Skolelinux logo, visible during installation, in the login screen and as desktop wallpaper.
New version of debian-installer from Debian Wheezy, see installation manual for more details.
The DVD image was dropped, instead we added a USB flash drive / Blu-ray disc image, which behaves like the DVD image, but is too big to fit on a DVD.
Todo lo nuevo en Debian Wheezy 7.1, por ejemplo:
Linux kernel 3.2.x
Desktop environments KDE "Plasma" 4.8.4, GNOME 3.4, Xfce 4.8.6, and LXDE 0.5.5 (KDE "Plasma" is installed by default; to choose GNOME, Xfce or LXDE: see manual.)
Web browser Iceweasel 17 ESR
LibreOffice 3.5.4
LTSP 5.4.2
GOsa 2.7.4
CUPS print system 1.5.3
Educational toolbox GCompris 12.01
Music creator Rosegarden 12.04
Image editor Gimp 2.8.2
Virtual universe Celestia 1.6.1
Virtual stargazer Stellarium 0.11.3
Scratch visual programming environment 1.4.0.6
New version of debian-installer from Debian Wheezy, see installation manual for more details.
Debian Wheezy includes about 37000 packages available for installation.
More information about Debian Wheezy 7.1 is provided in the release notes and the installation manual.
Translation updates for the templates used in the installer. These templates are now available in 29 languages.
The Debian Edu Wheezy Manual is fully translated to German, French, Italian and Danish. Partly translated versions exist for Norwegian Bokmål and Spanish.
Slight changes to some objects and acls to have more types to choose from when adding systems in GOsa. Now systems can be of type server, workstation, printer, terminal or netdevice.
New Xfce desktop task.
LTSP diskless workstations run without any configuration.
On the dedicated client network of LTSP servers (default 192.168.0.0/24), machines run by default as diskless workstations if they are powerful enough.
GOsa gui: Now some options that seemed to be available, but are non functional, are greyed out (or are not clickable). Some tabs are completely hidden to the end user, others even to the GOsa admin.
Using KDE "Plasma" on standalone and roaming workstations, at least Konqueror, Chromium and Step sometimes fail to work out-of-the box when the machines are used outside the backbone network, proxy use is required to use the other network but no wpad.dat information is found. Workaround: Use Iceweasel or configure the proxy manually.
The following Debian Edu releases were made further in the past:
Debian Edu 6.0.7+r1 Codename "Squeeze", released 2013-03-03.
Debian Edu 6.0.4+r0 Codename "Squeeze", released 2012-03-11.
Debian Edu 5.0.6+edu1 Codename "Lenny", released 2010-10-05.
Debian Edu 5.0.4+edu0 Codename "Lenny", released 2010-02-08.
Debian Edu "3.0r1 Terra", released 2007-12-05.
Debian Edu "3.0r0 Terra" released 2007-07-22. Based on Debian 4.0 Etch released 2007-04-08.
Debian Edu 2.0, released 2006-03-14. Based on Debian 3.1 Sarge released 2005-06-06.
Debian Edu "1.0 Venus" release 2004-06-20. Based on Debian 3.0 Woody released 2002-07-19.
A complete and detailed overview about older releases is contained in Appendix C of the Jessie manual; or see the related release manuals on the release manuals page.
Más información sobre versiones más anteriores puede encontrarse en http://developer.skolelinux.no/info/cdbygging/news.html.