Re: [Sheflug] Minicom

["Chris J" <cej [at] xxxxxxxxxxxxxxxx>]

> 
> #minicom
> LANG/ja
> LANG/ko
> LANG/ru
> Cannot create lockfile. Sorry.
> 
> I've tried to do 'chmod +x /var/lock'  but I'm still getting the same 
> error message.  Anyone know how to fix this so that I can login to my 
> iPAQ and finish the upgrade ?
> 

Three possibilities: 
1. Have you tried making /var/lock world writable? This is the least
	secure option.
2. A more secure option: put minicom in a given group (e.g., uucp), 
	then make it setgid and have /var/lock group writable. Something
	like this:
		chgrp uucp /path/to/minicom
		chmod 2711 /path/to/minicom
		chgrp uucp /var/lock
		chmod 775 /var/lock
	Of course, if other things are depending on /var/lock to be in a
	given group, then this may not work. It all depends on your setup
	and config. Or see what group /var/lock currently belongs to and
	change minicom to that group then setgid()
3. See what group /var/lock belongs to and add yourself (or whichever
	user you're running minicom as) to that group, and ensure /var/lock
	is group writable.

Chris...

-- 
\ Chris Johnson           \
 \ cej [at] nightwolf.org.uk    ~-----,   
  \ http://cej.nightwolf.org.uk/  ~-----------------------------------, 
   \ Redclaw chat - http://redclaw.org.uk - telnet redclaw.org.uk 2000 \____
___________________________________________________________________

Sheffield Linux User's Group -
http://www.sheflug.co.uk/mailfaq.html

  GNU the choice of a complete generation.