+ Post New Thread
Results 1 to 9 of 9
*nix Thread, Locking the filesystem? in Technical; So, I've created an install of Debian which runs a python script after auto-login which wraps around FreeRDP to allow ...
  1. #1

    localzuk's Avatar
    Join Date
    Dec 2006
    Location
    Minehead
    Posts
    18,381
    Thank Post
    525
    Thanked 2,615 Times in 2,021 Posts
    Blog Entries
    24
    Rep Power
    891

    Locking the filesystem?

    So, I've created an install of Debian which runs a python script after auto-login which wraps around FreeRDP to allow kids to log in with it using NLA (allowing our load balancer to work right).

    Now, I've got everything working as I want except a single feature - I want the disk to basically be locked. I know I could get it to mount everything read-only, but I suspect this will just cause everything to spew nonsense at the user when they turn on the machine.

    How do I go about making it 'locked' so that var doesn't fill up with logs etc...? HP managed it with their ThinPro system somehow.

    I don't really care about logs etc... because if there is an issue, it'll just get reimaged back to the base image.

    Any ideas?

  2. #2

    Join Date
    Nov 2010
    Posts
    473
    Thank Post
    64
    Thanked 72 Times in 59 Posts
    Rep Power
    35
    I wouldn't worry about the logs - Linux is designed to be on forever and rotates them peridically, throwing away the oldest ones. If you're really worried, put /var on a different partition.

  3. #3

    dhicks's Avatar
    Join Date
    Aug 2005
    Location
    Knightsbridge
    Posts
    5,738
    Thank Post
    1,299
    Thanked 797 Times in 693 Posts
    Rep Power
    239
    Quote Originally Posted by localzuk View Post
    Any ideas?
    Could you replace the log files in var with symbolic links to /dev/null?

  4. #4

    dhicks's Avatar
    Join Date
    Aug 2005
    Location
    Knightsbridge
    Posts
    5,738
    Thank Post
    1,299
    Thanked 797 Times in 693 Posts
    Rep Power
    239
    Quote Originally Posted by mats View Post
    I wouldn't worry about the logs - Linux is designed to be on forever and rotates them peridically, throwing away the oldest ones.
    It does cause disk access though, which might wear down a (cheaper / older) SSD or similar.

  5. #5

    Join Date
    Jan 2007
    Location
    Nottinghamshire
    Posts
    530
    Thank Post
    1
    Thanked 84 Times in 58 Posts
    Rep Power
    38
    If you don't want the user to alter files, just don't give them write access to their home dir. If you want it to restore to a known state on logout/reboot, perhaps the way live CDs work, loopback a ram FS

  6. #6
    morganw's Avatar
    Join Date
    Apr 2009
    Location
    Cambridge
    Posts
    818
    Thank Post
    46
    Thanked 132 Times in 126 Posts
    Rep Power
    40
    You could base the solution on Debian Live instead. This gives you hooks at various stages to configure the system and user for a live session. Locally installed or network boot it...

  7. #7


    Join Date
    Jan 2006
    Posts
    8,202
    Thank Post
    442
    Thanked 1,032 Times in 812 Posts
    Rep Power
    340
    Quote Originally Posted by localzuk View Post
    So, I've created an install of Debian which runs a python script after auto-login which wraps around FreeRDP to allow kids to log in with it using NLA (allowing our load balancer to work right).

    Now, I've got everything working as I want except a single feature - I want the disk to basically be locked. I know I could get it to mount everything read-only, but I suspect this will just cause everything to spew nonsense at the user when they turn on the machine.

    How do I go about making it 'locked' so that var doesn't fill up with logs etc...? HP managed it with their ThinPro system somehow.

    I don't really care about logs etc... because if there is an issue, it'll just get reimaged back to the base image.

    Any ideas?
    I've read and re-read your post - could you explain a bit further because I don't understand why you want the disk read-only.
    Have you thought about deleting profiles on login and just recreating them them from /etc/skel or am I on a different line from your thinking?

  8. #8

    localzuk's Avatar
    Join Date
    Dec 2006
    Location
    Minehead
    Posts
    18,381
    Thank Post
    525
    Thanked 2,615 Times in 2,021 Posts
    Blog Entries
    24
    Rep Power
    891
    Basically, the disk is 1GB in size. After full setup, it has 45MB of space left. I don't want to hit issues where the log files grow and fill the disk. So, I want the disk locked so on reboot, there is still 45MB space left - meaning that even if the disk fills up in a session for whatever reason, a reboot will resolve it.

  9. #9


    Join Date
    Jan 2006
    Posts
    8,202
    Thank Post
    442
    Thanked 1,032 Times in 812 Posts
    Rep Power
    340
    understood. I think @dhicks is on the right lines with redirecting to /dev/null in your /etc/rsyslog.conf



SHARE:
+ Post New Thread

Similar Threads

  1. Any way to freeze/lock the screen when register not taken in SIMS?
    By El_Nombre in forum How do you do....it?
    Replies: 9
    Last Post: 3rd May 2011, 05:17 PM
  2. [Website] Lock the taskbar?
    By theeldergeek in forum Jokes/Interweb Things
    Replies: 0
    Last Post: 18th May 2010, 09:09 PM
  3. Mute On Lock: The Auto Muter Utility
    By DaveP in forum Downloads
    Replies: 0
    Last Post: 23rd February 2010, 08:59 AM
  4. Replies: 6
    Last Post: 17th January 2006, 06:13 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •