On Wednesday 04 January 2006 02:36, Otto Moerbeek wrote:
On Tue, 3 Jan 2006, Dave Feustel wrote:
On Tuesday 03 January 2006 17:50, Otto Moerbeek wrote:
On Tue, 3 Jan 2006, Dave Feustel wrote:
On Tuesday 03 January 2006 17:11, J.C. Roberts wrote:
The rule of thumb
Feh, just have a read-only / with a read/write /home. Then just tell
Dad to pull the plug when he's finished.
FWIW he, and you, will probably go back to windows right quick with
that solution.
Hello!
On Tue, Jan 03, 2006 at 03:24:22AM -0800, J.C. Roberts wrote:
My dad (68 years old) has finally succeeded in destroying/infecteding
his MS-Windows NT4 box, in spite of my best efforts to secure the darn
thing (e.g. No MSIE, No Microsoft Networking, stripped of just about
everything MS-ish
On Tue, 3 Jan 2006, Joachim Schipper wrote:
Basically, all mail clients suck. And the one that sucks less is not
very newbie-friendly.
Joachim
Hehehe, I agree. However, I have used a few graphical clients that
weren't too bad. Evolution, Thunderbird, and Sylpheed-Claws. A few
On Tue, Jan 03, 2006 at 12:45:46PM -0500, Michael Erdely wrote:
On 1/3/06, Joachim Schipper [EMAIL PROTECTED] wrote:
Since /etc/X11/xdm/TakeConsole runs with root permission on every user
logout to prevent /dev/console sniffing I modified it to perform the
shutdown if the flag file is
On Tue, Jan 03, 2006 at 07:04:36PM +0100, Joachim Schipper wrote:
On Tue, Jan 03, 2006 at 12:45:46PM -0500, Michael Erdely wrote:
Add dad to the operator group which can run /sbin/shutdown without sudo.
That's not a very good idea.
$ ls -la /dev/wd*
brw-r- 1 root operator0,
The first thing I did was add a flag file to my dad's home directory
and made sure he cant modify or delete it.
# touch /home/dad/.xshutdown
# chown root:wheel /home/dad/.xshutdown
# chmod 400 /home/dad/.xshutdown
login: dad
password:
dadsbox $ ls -l .xshutdown
-r
On Tue, Jan 03, 2006 at 08:24:44PM +0200, Juha Erkkila wrote:
On Tue, Jan 03, 2006 at 07:04:36PM +0100, Joachim Schipper wrote:
On Tue, Jan 03, 2006 at 12:45:46PM -0500, Michael Erdely wrote:
Add dad to the operator group which can run /sbin/shutdown without sudo.
That's not a very
Hello!
On Tue, Jan 03, 2006 at 11:15:46AM -0800, patrick ~ wrote:
The first thing I did was add a flag file to my dad's home directory
and made sure he cant modify or delete it.
# touch /home/dad/.xshutdown
# chown root:wheel /home/dad/.xshutdown
# chmod 400 /home/dad/.xshutdown
On Tue, 3 Jan 2006 20:24:44 +0200, Juha Erkkila [EMAIL PROTECTED]
wrote:
On Tue, Jan 03, 2006 at 07:04:36PM +0100, Joachim Schipper wrote:
On Tue, Jan 03, 2006 at 12:45:46PM -0500, Michael Erdely wrote:
Add dad to the operator group which can run /sbin/shutdown without sudo.
That's not a
On Tuesday 03 January 2006 17:11, J.C. Roberts wrote:
The rule of thumb for granting privileges is simple; avoid granting
permissions whenever possible.
Check the ownership/privileges on /tmp/.X11-unix/X0 after you start kde or Xorg.
Also check the ownership/privileges on the /dev/[pt]typ*
On Tue, 3 Jan 2006 15:03:31 +0100, Hannah Schroeter [EMAIL PROTECTED]
wrote:
On Tue, Jan 03, 2006 at 03:24:22AM -0800, J.C. Roberts wrote:
My dad (68 years old) has finally succeeded in destroying/infecteding
his MS-Windows NT4 box, in spite of my best efforts to secure the darn
thing (e.g. No
On Tue, 3 Jan 2006, Dave Feustel wrote:
On Tuesday 03 January 2006 17:11, J.C. Roberts wrote:
The rule of thumb for granting privileges is simple; avoid granting
permissions whenever possible.
Check the ownership/privileges on /tmp/.X11-unix/X0 after you start kde or
Xorg.
Come on,
On Tue, 3 Jan 2006 22:46:50 +0100, Hannah Schroeter [EMAIL PROTECTED]
wrote:
Hello!
On Tue, Jan 03, 2006 at 11:15:46AM -0800, patrick ~ wrote:
The first thing I did was add a flag file to my dad's home directory
and made sure he cant modify or delete it.
# touch /home/dad/.xshutdown
#
On Tuesday 03 January 2006 17:50, Otto Moerbeek wrote:
On Tue, 3 Jan 2006, Dave Feustel wrote:
On Tuesday 03 January 2006 17:11, J.C. Roberts wrote:
The rule of thumb for granting privileges is simple; avoid granting
permissions whenever possible.
Check the
Dave Feustel wrote:
Check the ownership/privileges on /tmp/.X11-unix/X0 after you start kde or
Xorg.
You can stop repeating this now, you have already demonstrated your
ignorance.
On Tue, 03 Jan 2006 17:34:57 -0500, Dave Feustel
[EMAIL PROTECTED] wrote:
On Tuesday 03 January 2006 17:11, J.C. Roberts wrote:
The rule of thumb for granting privileges is simple; avoid granting
permissions whenever possible.
Check the ownership/privileges on /tmp/.X11-unix/X0 after you
On Tuesday 03 January 2006 18:20, J.C. Roberts wrote:
I'm not really a KDE user. Heck, I even resist installing X11 whenever
possible.
I am getting ever closer to adopting your point of view re X11 and KDE.
--
Lose, v., experience a loss, get rid of, lose the weight
Loose, adj., not tight, let
On Tue, 3 Jan 2006, Dave Feustel wrote:
On Tuesday 03 January 2006 17:50, Otto Moerbeek wrote:
On Tue, 3 Jan 2006, Dave Feustel wrote:
On Tuesday 03 January 2006 17:11, J.C. Roberts wrote:
The rule of thumb for granting privileges is simple; avoid granting
permissions
19 matches
Mail list logo
