Misplaced Pages

#243756

18-578: LTSP may refer to: Linux Terminal Server Project Lutheran Theological Seminary at Philadelphia Topics referred to by the same term [REDACTED] This disambiguation page lists articles associated with the title LTSP . If an internal link led you here, you may wish to change the link to point directly to the intended article. Retrieved from " https://en.wikipedia.org/w/index.php?title=LTSP&oldid=540904851 " Category : Disambiguation pages Hidden categories: Short description

36-459: A central location. In LTSP-cluster high-availability and high-performance thin-clients are specified through the optional use of redundant components. Services that can be load-balanced and made highly available are: LTSP-Cluster can support Linux application servers as well as Windows application servers and provides a similar level of support, centralized management, high-availability, and load-balancing features for both platforms. Also included

54-496: A full desktop OS. Even a relatively slow CPU with as little as 128 MB of RAM can deliver excellent performance as a thin client. In addition, the use of centralized computing resources means that more performance can be gained for less money through upgrades to a single server rather than across a fleet of computers. By converting existing computers into thin clients, an educational institution can also gain more control over how their students are using computing resources as all of

72-433: A portal (based on uportal), an open-source middleware stack, a CD with free software for Windows/Mac and, finally, MILLE-Xterm itself. The MILLE-Xterm project's goal was to provide a scalable infrastructure for massive X-Terminal deployment. MILLE means Modèle d'Infrastructure Logiciel Libre en Éducation (Free Software Infrastructure Model for Education) and is targeted at educational institutions. As of 2009, MILLE-Xterm

90-404: A system without a "FUSE" facility. To implement a new file system, a handler program linked to the supplied libfuse library needs to be written. The main purpose of this program is to specify how the file system is to respond to read/write/stat requests. The program is also used to mount the new file system. At the time the file system is mounted, the handler is registered with the kernel. If

108-404: A user now issues read/write/stat requests for this newly mounted file system, the kernel forwards these IO-requests to the handler and then sends the handler's response back to the user. FUSE is particularly useful for writing virtual file systems . Unlike traditional file systems that essentially work with data on mass storage, virtual filesystems don't actually store data themselves. They act as

126-423: A view or translation of an existing file system or storage device. In principle, any resource available to a FUSE implementation can be exported as a file system. Conventional on-disk file systems can be implemented in user space with FUSE, e.g. for compatibility or licensing reasons. FUSE filesystems can create a view of an underlying file system, transforming the files in some way. FUSE filesystems can expose

144-613: Is free software originally released under the terms of the GNU General Public License and the GNU Lesser General Public License . The FUSE system was originally part of AVFS ( A Virtual Filesystem ), a filesystem implementation heavily influenced by the translator concept of the GNU Hurd . It superseded Linux Userland Filesystem , and provided a translational interface using lufis in libfuse1. FUSE

162-498: Is a software interface for Unix and Unix-like computer operating systems that lets non-privileged users create their own file systems without editing kernel code. This is achieved by running file system code in user space while the FUSE module provides only a bridge to the actual kernel interfaces. FUSE is available for Linux , FreeBSD , OpenBSD , NetBSD (as puffs ), OpenSolaris , Minix 3 , macOS , and Windows . FUSE

180-436: Is different from Wikidata All article disambiguation pages All disambiguation pages Linux Terminal Server Project This technology is useful in schools as it allows the school to provide pupils access to computers without purchasing or upgrading expensive desktop machines. Improving access to computers becomes less costly as thin client machines can be older computers that are no longer suitable for running

198-424: Is support for virtual desktops for remote users using NX technology . The NX protocol can allow remote Windows and Linux sessions to be accessed from a web browser with very low bandwidth (40 kbit/s) requirements and tolerance for high-latency connections. The NX client runs on various operating systems including Linux, Mac, and Windows. LTSP v5.x added support for a thin client type known as "fat clients". With

SECTION 10

#1732891486244

216-604: Is used on the fat clients, which provides a few benefits. LTSP is unique in offering the ability for a computer to mount its root filesystem over a network and run applications locally. On the Windows platform, the closest equivalent solution is to use a technology like Intel vPro to run a client-side hypervisor and mount the root filesystem image using iSCSI . Filesystem in Userspace Filesystem in Userspace ( FUSE )

234-430: The libfuse library, generally followed the pace of Linux kernel development while maintaining "best effort" compatibility with BSD descendants. This is possible because the kernel FUSE reports its own "feature levels", or versions. The exception is the FUSE fork for macOS, OSXFUSE, which has too many differences for sharing a library. A break in libfuse history is libfuse3, which includes some incompatible improvements in

252-506: The advent of inexpensive, relatively powerful computer hardware, the idea to run applications locally on the thin client while offering the manageability of a thin client solution became a reality. In the case of a LTSP fat client, the root filesystem is not a rudimentary chroot but a full Linux installation as a chroot. The fat client uses LDM to authenticate to the LTSP server and mounts user home directories using SSH and FUSE . The local CPU and RAM

270-413: The interface and performance, compared to the older libfuse2 now under maintenance mode. As the kernel-userspace protocol of FUSE is versioned and public, a programmer can choose to use a different piece of code in place of libfuse and still communicate with the kernel's FUSE facilities. On the other hand, libfuse and its many ports provide a portable high-level interface that may be implemented on

288-458: The user sessions can be monitored on the server. See Epoptes (A Lab Management Tool) . The founder and project leader of LTSP is Jim McQuillan , and LTSP is distributed under the terms of the GNU General Public License . Initially, the MILLE-Xterm project, funded by Canadian public agencies and school districts in the province of Quebec, created a version of LTSP integrating four subprojects:

306-492: Was integrated back into the LTSP as LTSP-cluster, a project specializing in the large scale deployment of LTSP. One of the main differences between LTSP and LTSP-cluster is the integration of a web-based central control center that replaces the traditional "one configuration file per thin client" as is the method of client customization through LTSP's lts.conf file in the main LTSP. LTSP-cluster allows organizations to centrally manage thousands of thin clients and their parameters from

324-632: Was originally released under the terms of the GNU General Public License and the GNU Lesser General Public License , later also reimplemented as part of the FreeBSD base system and released under the terms of Simplified BSD license. An ISC -licensed re-implementation by Sylvestre Gallon was released in March 2013, and incorporated into OpenBSD in June 2013. FUSE was merged into the mainstream Linux kernel tree in kernel version 2.6.14. The userspace side of FUSE,

#243756