No idea, I got rid of Angstrom the first week after receiving my Beaglebone blacks. Angstrom was too much of a pain in my backside to even want to bother with it.
On Mon, Dec 15, 2014 at 12:23 AM, Anubhav Goel <[email protected]> wrote: > > that sounds good!.. i shall try it and report back. > One point , how do I disable the default mechanism of loading the > thumbdrive ? i.e. , there must be some place/sh where these commands are > getting executed ? can you point me to them ? > > On Mon, Dec 15, 2014 at 12:49 PM, William Hermans <[email protected]> > wrote: >> >> Ok, so I do not know where the module "g_multi" is loaded from on >> angstrom, but g_multi is a USB to Serial, ethernet, and mass storage >> device. You should search the web on g_mass_storage to understand how the >> parameters work with g_multi . . >> >> So anyway, g_multi is caled similar to this: >> >> modprobe g_multi file=/dev/mmsclk01p1 >> >> >> This is how the device is shared out over USB. So, you *may* be able >> point the file location to /dev/null ( never tried it ), or create an empty >> directory *somewhere*. And point it to that. If Neithe fo those work for >> you, then get rid of g_multi, and use g_ether instead ( assuming you do not >> need Serial too ). >> >> On Mon, Dec 15, 2014 at 12:03 AM, Anubhav Goel <[email protected] >> > wrote: >>> >>> Hi ! >>> >>> On Mon, Dec 15, 2014 at 12:27 PM, <[email protected]> wrote: >>>> >>>> Hi Anubhav, >>>> >>>> do not move uEnv.txt, the U-Boot image and the kernel images >>>> around. Due to the limited technical possibilities of the very early >>>> boot stages, these files are exspected to be at certain physical >>>> place on the flash memory. >>>> >>>> Instead edit /etc/fstab and remove the mount command of /boot. >>>> Do a backup first. >>>> >>> m fstab shows: >>> rootfs / auto >>> defaults 1 1 >>> proc /proc proc >>> defaults 0 0 >>> devpts /dev/pts devpts >>> mode=0620,gid=5 0 0 >>> tmpfs /tmp tmpfs >>> defaults 0 0 >>> >>> It doesnt have the mount command of boot. >>> Even if I were able to stop the boot, would that mean disabling access >>> to the partition on windows desktop? I do require the parition to appear >>> on desktop when connected, but I dont want the user to access these >>> critical files. >>> >>> >>>> >>>> Best regards, >>>> Meino >>>> >>>> >>>> >>>> Anubhav Goel <[email protected]> [14-12-15 07:52]: >>>> > Hi William, >>>> > >>>> > Thanks for your quick response. >>>> > >>>> > I cannot really move to the debian, as it has taken me a lot of >>>> effort :) , >>>> > to understand my way around angstrom.. it will be very steep curve >>>> for me >>>> > as of now. >>>> > >>>> > I was thinking, is there no way to create a new vfat partition on >>>> bbb, and >>>> > expose that on the thumbdrive, and let this default one just remain >>>> > unmounted ? >>>> > >>>> > I will readup on the read-only part. >>>> > >>>> > Can you point me to some info on how/when does this partition get >>>> loaded ? >>>> > do we have some sort of hook that can be utilized ? >>>> > >>>> > Can I not place the mlo/ig& env files at a place where its picked by >>>> bbb , >>>> > but not exposed over thumbdrive ? >>>> > >>>> > Regards >>>> > Anubhav >>>> > >>>> > On Mon, Dec 15, 2014 at 11:57 AM, William Hermans <[email protected]> >>>> wrote: >>>> > > >>>> > > *My users may accidentally delete the mlo/uboot/uenv files, if >>>> presented >>>> > >> over their desktop.* >>>> > >> >>>> > > >>>> > > There are a few ways to deal with this*. *Just do not mount the boot >>>> > > loader partition. Would probably be the easiest for you. If you >>>> want to do >>>> > > what I would consider "the right way", then put a modern Debian >>>> build from >>>> > > Robert on it, and that whole partition will not exist, and the >>>> bootloader >>>> > > files will be in a hole in the first 1M of the block device. >>>> > > >>>> > > Aside from that, I do not think FAT/FAT32 partitions can be used >>>> with >>>> > > Linux permissions. However, you may be able to make the partition >>>> read >>>> > > only. Not sure on this, but if you're teaching students about he >>>> hardware / >>>> > > software. This may be preferable. >>>> > > >>>> > > Personally, I think "hiding" the files in the first 1M of disk >>>> space is >>>> > > the best way. Heck I've been using Linux for years, and I honestly >>>> have no >>>> > > idea how to reverse / mess that up. Eventually I'll have to read up >>>> on it >>>> > > myself, as it's pretty neat . . . >>>> > > >>>> > > On Sun, Dec 14, 2014 at 10:58 PM, Anubhav Goel < >>>> [email protected]> >>>> > > wrote: >>>> > >> >>>> > >> Hi Kenny, >>>> > >> >>>> > >> I have the same requirement, were you able to get any workaround >>>> to this ? >>>> > >> >>>> > >> I looked into bbb to find any default locations , like >>>> /boot/uEnv.txt .. >>>> > >> but it doesnt work , if I delete the file from media , but the >>>> > >> /boot/uenv.txt file is not picked up. >>>> > >> I was unable to find any other place to store the mlo & img files >>>> either. >>>> > >> >>>> > >> My users may accidentally delete the mlo/uboot/uenv files, if >>>> presented >>>> > >> over their desktop. >>>> > >> >>>> > >> Regards, >>>> > >> Anubhav >>>> > >> >>>> > >> On Wednesday, 24 July 2013 14:23:10 UTC+5:30, [email protected] >>>> wrote: >>>> > >>> >>>> > >>> Hi all, >>>> > >>> >>>> > >>> I am building a few prototype with Beaglebone Black. I want to >>>> let the >>>> > >>> user to plug into the mini-USB port from a PC and copy a output >>>> file I >>>> > >>> stored in /media/BEAGLEBONE. However, I don't want user to see >>>> all the >>>> > >>> documentation and tutorial of the BBB. It seems like BBB will >>>> copy all >>>> > >>> these files during reboot. >>>> > >>> >>>> > >>> I wonder if I can configure it without copying these files during >>>> > >>> reboot? or I can configure a different directory to show up while >>>> user plug >>>> > >>> in the mini-USB cable? I can control where the output file go in >>>> my >>>> > >>> program. Many thanks for any guidance. >>>> > >>> >>>> > >>> Kenny Lau >>>> > >>> >>>> > >> -- >>>> > >> For more options, visit http://beagleboard.org/discuss >>>> > >> --- >>>> > >> You received this message because you are subscribed to the Google >>>> Groups >>>> > >> "BeagleBoard" group. >>>> > >> To unsubscribe from this group and stop receiving emails from it, >>>> send an >>>> > >> email to [email protected]. >>>> > >> For more options, visit https://groups.google.com/d/optout. >>>> > >> >>>> > > -- >>>> > > For more options, visit http://beagleboard.org/discuss >>>> > > --- >>>> > > You received this message because you are subscribed to a topic in >>>> the >>>> > > Google Groups "BeagleBoard" group. >>>> > > To unsubscribe from this topic, visit >>>> > > >>>> https://groups.google.com/d/topic/beagleboard/lqPrGitRgCk/unsubscribe. >>>> > > To unsubscribe from this group and all its topics, send an email to >>>> > > [email protected]. >>>> > > For more options, visit https://groups.google.com/d/optout. >>>> > > >>>> > >>>> > -- >>>> > For more options, visit http://beagleboard.org/discuss >>>> > --- >>>> > You received this message because you are subscribed to the Google >>>> Groups "BeagleBoard" group. >>>> > To unsubscribe from this group and stop receiving emails from it, >>>> send an email to [email protected]. >>>> > For more options, visit https://groups.google.com/d/optout. >>>> >>>> -- >>>> For more options, visit http://beagleboard.org/discuss >>>> --- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "BeagleBoard" group. >>>> To unsubscribe from this topic, visit >>>> https://groups.google.com/d/topic/beagleboard/lqPrGitRgCk/unsubscribe. >>>> To unsubscribe from this group and all its topics, send an email to >>>> [email protected]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> -- >>> For more options, visit http://beagleboard.org/discuss >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "BeagleBoard" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to a topic in the >> Google Groups "BeagleBoard" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/beagleboard/lqPrGitRgCk/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
