<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffcc" text="#663300">
<br>
<blockquote cite="mid20070321144404.4BC8A73195@hormel.redhat.com"
type="cite">
<pre wrap="">
</pre>
<br>
<hr size="4" width="90%"><br>
<table class="header-part1" border="0" cellpadding="0" cellspacing="0"
width="100%">
<tbody>
<tr>
<td>
<div class="headerdisplayname" style="display: inline;">Subject:
</div>
Re: [K12OSN] Full system file access from terminals??</td>
</tr>
<tr>
<td>
<div class="headerdisplayname" style="display: inline;">From: </div>
Peter Scheie <a class="moz-txt-link-rfc2396E" href="mailto:peter@scheie.homedns.org"><peter@scheie.homedns.org></a></td>
</tr>
<tr>
<td>
<div class="headerdisplayname" style="display: inline;">Date: </div>
Tue, 20 Mar 2007 17:57:30 -0500</td>
</tr>
<tr>
<td>
<div class="headerdisplayname" style="display: inline;">To: </div>
"Support list for open source software in schools."
<a class="moz-txt-link-rfc2396E" href="mailto:k12osn@redhat.com"><k12osn@redhat.com></a></td>
</tr>
</tbody>
</table>
<table class="header-part2" border="0" cellpadding="0" cellspacing="0"
width="100%">
<tbody>
<tr>
<td>
<div class="headerdisplayname" style="display: inline;">To: </div>
"Support list for open source software in schools."
<a class="moz-txt-link-rfc2396E" href="mailto:k12osn@redhat.com"><k12osn@redhat.com></a></td>
</tr>
</tbody>
</table>
<br>
xmechanic wrote:
<br>
<blockquote type="cite"><snip!><br>
<br>
</blockquote>
Not sure why version 6 wouldn't work when version 5 does. Did you try
turning off selinux? That has caused problems in the past.
<br>
<br>
As for the users having access to the full file system on the server,
that is the way it's supposed to work; it is not a chrooted environment
that the users log into. A kernel and an X server are loaded on the
client, but then pointed at the display manager, gdm by default, on the
server via xdmcp. So, users are logging into the server similar to if
they were telnetting or ssh-ing in, except with a graphical interface.
Once logged in, users are 'on' the server.
<br>
<br>
Petre
<br>
<br>
<font face="Arial">Petre.. and the others,</font><br>
</blockquote>
<font face="Arial">Thank you for your replys. The way the file system
was laid out, I was under the impression that the users would be
chrooted into the /opt/ltsp/i386 directory. I'm still a little hazy on
the concept of why a terminal user would be able to move to directorys
above /opt/ltsp/i386, since that's the only directory that's
'exported', besides the r/o fonts directorys in /usr/** & the swap
files Also, in the issue with version 6.0 not working, I tried
disabling SElinux and when I did, it evidently broke something, because
the system then took like 15 minutes to boot after that. I know files
need to be relabeled on reboot, but this was every reboot thereafter,
so I finally sidelined it and eventually re-installed the system with
Ver. 5.0. I would still like to know if there is an easy way to chroot
a user to his/her directory, yet still be able to access all programs,
etc. Thanks again for your help!<br>
<br>
Dave Land<br>
Land Computer Service<br>
</font>
<blockquote cite="mid20070321144404.4BC8A73195@hormel.redhat.com"
type="cite"><br>
<hr size="4" width="90%"></blockquote>
<pre class="moz-signature" cols="72">
</pre>
</body>
</html>