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

[Zarro Boogs per Child]

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

Comment(by mtd):

 Replying to [comment:14 mstone]:
 > Regarding the question of shippability: I'm certainly interested in the
 patch though I'd like to see some more testing results first.

 If I can assist let me know.  As you can see from the patch I've included
 test cases, and I've been running it (without problems) since I came up
 with the patch.  Of course that's a very small amount of time.  I'm not an
 expert in testing these things to know what're the most fruitful areas to
 test, and I don't have enough time to become such an expert.

 > 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.).

 > (In my mind, a correct implementation would respond gracefully to the
 addition of new mingetty's ttys both before and after the X tty.)

 I agree that would be nicer.  I'm not clear on how to discover free ttys,
 though, especially as I'm not clear what assumptions our approach to
 configuring ttys via upstart allows us to make about the relative timings
 of tty allocations vs. prefdm/olpc-dm invocation.

 As a meta-comment I'd return to my "how important is improving olpc-dm?"
 question: it sounds like you guys have thought about this a lot (or are
 willing to), in which case random contributors without much *dm experience
 are just going to drag you down at the design phase, IMO.

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