For one or even a small number of ROACH2s, there probably isn't much advantage to netboot. As the number of boards in the system increases, netboot helps because everything runs the same version always. Also, with the kernel and root filesystem on an SSD, netboot is less prone to failure/corruption. Maybe things are better now, but it used to be that if the ROACH2 linux crashed then the soloboot root filesystem could get corrupted.
HTH, Dave > On Jun 9, 2022, at 03:11, Michael D'Cruze > <[email protected]> wrote: > > Hello, > > I think nfs/netboot made sense when filesystem updates were being released > for R2, but I don't really understand why anyone would use it anymore. Roach2 > should soloboot by default, and unless you've compiled and are running a > custom filesystem for some reason I'm not sure why any other boot method > would be advantageous... Perhaps I'm missing something > > Best, > Michael > From: [email protected] <[email protected]> on behalf of 王钊 > <[email protected]> > Sent: 09 June 2022 09:45 > To: [email protected] <[email protected]> > Subject: Re: [casper] An error occurs when 'exportfs -a' is entered > > Hi Michael， > > I'm using ROACH2.I don't know much about other boot methods of ROACH2. My > tutor suggests that I use Netboot. > > I spent a lot of time on netboot, the first time I used Ubuntu16, and this > error occurred at netboot： > <154620_8cc3a188_10952828.webp> > > I am currently trying to use Ubuntu14 for netboot and also getting an error > about exportfs -a. > > I have also considered trying other boot methods, are there any related > tutorials？All I can find is netboot. > > Thank you very much for your reply！ > Wang > Michael D'Cruze <[email protected] > <mailto:[email protected]>> 于2022年6月8日周三 23:12写道： > Hi Wang, > > 😬 > I did use netboot for a while on my roach2 way back in the day, but it was > easier especially following various updates to the board to just use soloboot. > I hate to ask but is there a reason you need to use netboot? > I assume you're using a roach2, and not a roach1? > > BW > Michael > From: [email protected] <mailto:[email protected]> > <[email protected] <mailto:[email protected]>> on behalf of > Wang <[email protected] <mailto:[email protected]>> > Sent: 08 June 2022 15:52 > To: [email protected] <mailto:[email protected]> > <[email protected] <mailto:[email protected]>> > Subject: [casper] An error occurs when 'exportfs -a' is entered > > Hi CASPER, > How's it going? I'm using ubuntu14.04. > I had some problems setting up the ROACH netboot. > First, sudo apt-get install nfs-kernel-server nfs-common. > Second, sudo gedit /etc/exports,and add the lines: > # Share 'roach_boot' directory/srv/roach_boot > 192.168.100.0/24(rw,subtree_check,no_root_squash,insecure) > <http://192.168.100.0/24(rw,subtree_check,no_root_squash,insecure)> > The last, exportfs -a > At this time, the terminal displays: > sandang@wz-sandang:/etc$ sudo exportfs -a > exportfs: No options for to NFS: suggest NFS(sync) to avoid warning > exportfs: /etc/exports [1]: Neither 'subtree_check' or 'no_subtree_check' > specified for > export "NFS:to". > Assuming default behaviour ('no_subtree_check'). > NOTE: this default has changed since nfs-utils version 1.0.x > > May I ask what are the reasons for these? > I would be really appreciated if you reply! > Wang > -- > You received this message because you are subscribed to the Google Groups > "[email protected] <mailto:[email protected]>" group. > To unsubscribe from this group and stop receiving emails from it, send an > email [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/dbe7c801-e9a4-4967-b1aa-678bdf71aa83n%40lists.berkeley.edu > > <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/dbe7c801-e9a4-4967-b1aa-678bdf71aa83n%40lists.berkeley.edu?utm_medium=email&utm_source=footer>. > -- > You received this message because you are subscribed to the Google Groups > "[email protected] <mailto:[email protected]>" group. > To unsubscribe from this group and stop receiving emails from it, send an > email [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/LO4P265MB6154CAC9895302EA186451848AA49%40LO4P265MB6154.GBRP265.PROD.OUTLOOK.COM > > <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/LO4P265MB6154CAC9895302EA186451848AA49%40LO4P265MB6154.GBRP265.PROD.OUTLOOK.COM?utm_medium=email&utm_source=footer>. > -- > You received this message because you are subscribed to the Google Groups > "[email protected]" group. > To unsubscribe from this group and stop receiving emails from it, send an > email [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAEq%3DE3EAJsMBvh6tHeD6fbAwYhao5_cAm7Lpgu%3Dc%2B_tv5ciX9Q%40mail.gmail.com > > <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAEq%3DE3EAJsMBvh6tHeD6fbAwYhao5_cAm7Lpgu%3Dc%2B_tv5ciX9Q%40mail.gmail.com?utm_medium=email&utm_source=footer>. > -- > You received this message because you are subscribed to the Google Groups > "[email protected] <mailto:[email protected]>" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/LO4P265MB615457C0EB7B717B00142C888AA79%40LO4P265MB6154.GBRP265.PROD.OUTLOOK.COM > > <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/LO4P265MB615457C0EB7B717B00142C888AA79%40LO4P265MB6154.GBRP265.PROD.OUTLOOK.COM?utm_medium=email&utm_source=footer>. -- You received this message because you are subscribed to the Google Groups "[email protected]" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/1108B229-E537-45D8-8C16-C3C9C4AC5773%40berkeley.edu.
