#5705 BLOC 8.2.0 (: sudo gives "can't access tty" errors.

Zarro Boogs per Child bugtracker at laptop.org
Tue Aug 5 18:58:12 EDT 2008

#5705: sudo gives "can't access tty" errors.
   Reporter:  cjb      |       Owner:  mstone                       
       Type:  defect   |      Status:  new                          
   Priority:  blocker  |   Milestone:  8.2.0 (was Update.2)         
  Component:  distro   |     Version:                               
 Resolution:           |    Keywords:  rainbow-integration, security
Next_action:  package  |    Verified:  0                            
  Blockedby:           |    Blocking:  7797                         

Comment(by mikus):

 Replying to [comment:15 mtd]:
 > Replying to [comment:14 mstone]:
 > > Regarding the question of correctness: Why should we be hardcoding the
 tty number at all?
 > Slight nitpick - that might be more flexibility rather than correctness.
 But regardless, it just depends on what you're aiming for and how long you
 want to carry olpc-dm.  If not for too long, then who cares?  As as one of
 cscott's queries implied, if it was wrong for this long and nobody cared
 too much, this small (but clear) enhancement in maintainability might not
 justify the additional complexity (changing invocation
 scripts/documentation, etc.).

 A minor comment, for the sake of recording what I've seen -- I'm not
 asking for any code changes.

 I'm one of the people who have issued 'startx -- :1', and have (not very
 successfully) ended up in Sugar on ctl-alt-F4.  I think if the tty is
 hard-coded, that impacts people who want to simultaneously run more than
 one "user" on the OLPC.

Ticket URL: <http://dev.laptop.org/ticket/5705#comment:22>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system

More information about the Bugs mailing list