On Mon, Feb 02, 2009 at 02:23:04PM -0500, Jim McQuillan wrote:
>
>
> David Burgess wrote:
> > On Mon, Feb 2, 2009 at 10:38 AM, Joseph Bishay
> > wrote:
> >> Hello,
> >>
> >> On Mon, Feb 2, 2009 at 11:00 AM, Scott Balneaves
> >> wrote:
> >>> Are all your students in the same primary group? Usu
jam wrote:
> On Tuesday 03 February 2009 04:09:08 ltsp-discuss-
> requ...@lists.sourceforge.net wrote:
> [snip]
>> If you were using a very small set of plugins for Eclipse, you may be able
>> to drive down memory costs, but that goes back to the questions about what
>> types of development you'r
On Tuesday 03 February 2009 04:09:08 ltsp-discuss-
requ...@lists.sourceforge.net wrote:
[snip]
> If you were using a very small set of plugins for Eclipse, you may be able
> to drive down memory costs, but that goes back to the questions about what
> types of development you're doing.
You folk do
We are using LDAP as well, with the primary group for all students being
ldapusers, instead of creating individual groups for each user.
I recall running into this before when working with Jim Kronebusch, and after
talking to him, his recommendation was to run the following:
"Just do a cd /media
Another option is ACLs, which works nicely if you need fine grained,
multiple group permissions control:
https://help.ubuntu.com/community/UbuntuLTSP/ACLSupport
(shameless plug for the howto I wrote, and coincidentally referring to
right now before I read this list post ;) )
Cheers,
Jordan
On Mon, Feb 02, 2009 at 12:54:52PM -0700, David Burgess wrote:
> I'm sure there are other solutions, but mine has been to change the
> default umask to something like 007 and then if I want user tina to be
> able to edit files from joe, I just adduser tina joe, then tina can
> edit joe's files.
T
On Mon, Feb 2, 2009 at 12:23 PM, Jim McQuillan wrote:
>
>
> David Burgess wrote:
>> On Mon, Feb 2, 2009 at 10:38 AM, Joseph Bishay
>> wrote:
>>> Hello,
>>>
>>> On Mon, Feb 2, 2009 at 11:00 AM, Scott Balneaves
>>> wrote:
Are all your students in the same primary group? Usually this is what
David Burgess wrote:
> On Mon, Feb 2, 2009 at 10:38 AM, Joseph Bishay
> wrote:
>> Hello,
>>
>> On Mon, Feb 2, 2009 at 11:00 AM, Scott Balneaves
>> wrote:
>>> Are all your students in the same primary group? Usually this is what
>>> causes
>>> this. Typically, in modern Linuxes, each user sh
Bjorn,
Thanks - I noticed the typo - but, unfortunately, I don't have
permissions to rename a page. Need to figure out how to get more access. :)
/sbin/halt shuts down the power, but I'll investigate /sbin/poweroff to
see if it's a better solution. An idea to modify this behavior also
comes up
Got it. We have a /etc/security/group.conf in openSUSE as well, the same
as Ubuntu. Actually it is a part of pam, hence not dist specific.
This could be very useful for LTSP users.
SB
Shrenik Bhura wrote:
> Is there anyway that we may enforce the groups that are applicable to a
> user (or the gr
On Friday 23 January 2009 03:43:13 pm Jordan Erickson wrote:
> Automated thin-client shutdown via cron (go green!):
> https://help.ubuntu.com/community/UbuntuLTSP/AutomatedTCShutodwn
Hi Jordan,
s/Shutodwn/Shutdown/ :-)
I notice you use /sbin/halt, not /sbin/poweroff. Any particular
reason? Th
On Mon, Feb 2, 2009 at 10:38 AM, Joseph Bishay wrote:
> Hello,
>
> On Mon, Feb 2, 2009 at 11:00 AM, Scott Balneaves
> wrote:
>> Are all your students in the same primary group? Usually this is what causes
>> this. Typically, in modern Linuxes, each user should have their own primary
>> group th
Hello,
On Mon, Feb 2, 2009 at 11:00 AM, Scott Balneaves
wrote:
> Are all your students in the same primary group? Usually this is what causes
> this. Typically, in modern Linuxes, each user should have their own primary
> group the same as their userid.
>
> Scott
I was having this problem also
John Hansen wrote:
> We recently upgraded to Hardy, and after updating the chroot, USB drives are
> mounting successfully. However, now anyone logged onto a thin client can see
> other users USB sticks mounted on their desktops. Only the user of that USB
> stick can read the device, but it appears
On Mon, Feb 02, 2009 at 09:38:19AM -0600, John Hansen wrote:
> We recently upgraded to Hardy, and after updating the chroot, USB drives are
> mounting successfully. However, now anyone logged onto a thin client can see
> other users USB sticks mounted on their desktops. Only the user of that USB
>
We recently upgraded to Hardy, and after updating the chroot, USB drives are
mounting successfully. However, now anyone logged onto a thin client can see
other users USB sticks mounted on their desktops. Only the user of that USB
stick can read the device, but it appears on everyones desktop that i
Is there anyway that we may enforce the groups that are applicable to a
user (or the groups that a user is effectively member of) in opensuse?
AFAIK, the same can be done via /etc/groups.conf in Ubuntu and may be in
Debian too. Is there an equivalent in openSUSE?
Any helpful and quick responses s
17 matches
Mail list logo
