View Single Post
  #21   Spotlight this post!  
Unread 25-05-2012, 16:21
connor.worley's Avatar
connor.worley connor.worley is offline
Registered User
FRC #0973 (Greybots)
Team Role: Mentor
 
Join Date: Mar 2011
Rookie Year: 2010
Location: Berkeley/San Diego
Posts: 601
connor.worley has a reputation beyond reputeconnor.worley has a reputation beyond reputeconnor.worley has a reputation beyond reputeconnor.worley has a reputation beyond reputeconnor.worley has a reputation beyond reputeconnor.worley has a reputation beyond reputeconnor.worley has a reputation beyond reputeconnor.worley has a reputation beyond reputeconnor.worley has a reputation beyond reputeconnor.worley has a reputation beyond reputeconnor.worley has a reputation beyond repute
Re: paper: 987 Kinect Implementation

Quote:
Originally Posted by JesseK View Post
As for using RAMDISK, that's not as straightforward as one might think. For one, most default Linux installs take 1Gb-2GB of total disk space, which would then be put into RAM (unsure of this Ubuntu image though). Then, any changes that are made to the O/S or program settings would have to be re-compressed and re-deployed as the O/S image for RAMDISK to open up at runtime. Usually the data directories (such as /home) and in this case FRC-related application directories (such as /opt) are NFS (network file system) mounted and are actually located on another computer -- yet I wouldn't recommend it for a live FRC field environment. Ergo, the data directories would then have to go somewhere -- presumably still on the SD card that's potentially causing the root issue anyways.
I will have to play with VxWork's nfsdLib. I've never seen the cRIO or switch brown out, but if they did, would the pandaboard be able to recover?
__________________
Team 973 (2016-???)
Team 5499 (2015-2016)
Team 254 (2014-2015)

Team 1538 (2011-2014)
2014 Driver (25W 17L 1T)
日本語でOK
Reply With Quote