Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
R remotebootserver
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 12
    • Issues 12
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • remote-boot
  • remotebootserver
  • Wiki
  • server packages

server packages · Changes

Page history
marceloonit created page: server packages authored Nov 09, 2017 by Marcelo Oliveira's avatar Marcelo Oliveira
Hide whitespace changes
Inline Side-by-side
Showing with 27 additions and 0 deletions
+27 -0
  • server-packages.md server-packages.md +27 -0
  • No files found.
server-packages.md 0 → 100644
View page @ 1467ae99
For this project we are going to use the ltsp-server package provided by the LTSP Project as the base of the Polilinux Remote Boot Server, while I am writing this document ltsp-server is on its 5.5.9 version as we are going to see through the apt-cat show command ahead.
That specific package will give to the server some interesting features such as the possibility of easily building chroot of different architectures, generating some services configuration files and the lts.conf file, which will allow us to set some configurations to our clients, moreover if we don’t want to use such features, we can just build our chroot manually and ignore ltsp-server commands.
First of all, let’s have a look what packages LTSP Project provides.
[remoteos][command]
root@remoteos:~# apt-cache search ltsp
[command output]
education-ltsp-server - Debian Edu networked LTSP server packages
education-thin-client-server - transitional package for education-ltsp-server
epoptes - Computer lab management tool
fts - Modular TFTP/Fuse supplicant
fts-ltsp-ldap - LDAP LTSP module for the TFTP/Fuse supplicant
fts-opsi - LDAP LTSP module for the TFTP/Fuse supplicant
ldm - LTSP display manager
ldm-server - server components for LTSP display manager
ldm-themes - Collection of themes for the LTSP login manager
ltsp-client - complete LTSP client environment
ltsp-client-core - basic LTSP client environment
ltsp-server - basic LTSP server environment
ltsp-server-standalone - complete LTSP server environment
ltsp-docs - LTSP Documentation
ltspfs - Fuse based remote filesystem for LTSP thin clients
ltspfsd - Fuse based remote filesystem hooks for LTSP thin clients
ltspfsd-core - Fuse based remote filesystem daemon for LTSP thin clients
You will get an output like the output above. As you can see LTSP project has many packages however the only package we need to deploy the Polilinux Remote Boot Server is the one on weight bold font, the other packages aren’t essential to the fat-client server environment.
\ No newline at end of file
Clone repository
  • conventions
  • Home
  • server and iso details
  • server packages
  • setting static ipv4 to our server