I also install SAMBA on all the Linux systems so I can get at the folders.
Hopefully both images will be accepted in this email. In this case it's a
BeagleBone Black running an older version of Linux attached to a special card
that emulates an older 20MB MFM hard disk drive connected to an S100 computer
running OS9-68K.
John
> From: Thaddeus Waldner [mailto:[email protected]]
>
> Can you please detail how to reliably connect to a server?
>
> On a few of my systems I connect via wifi and mount the network path on a
> local folder. I have fstab set up to do this but it works only if I call
> 'mount -a' manually after logging in. This is presumably because the
> network link is not up at the time when drives are mounted by the OS.
>
> Is there a "wait for network" fstab switch?
> Or would I need to set up a script that waits for the network?
>
> My file server is a Samba system, if that makes a difference.
>
>
> On Fri, Jul 1, 2022 at 3:27 AM Chris Albertson <[email protected]>
> wrote:
>
> > I solved this problem (using Pi4 as a development system) by placing all my
> > files on a file server. Development systems see near constant re-compiles
> > and write to log files, source code edits and backups and so on. The
> > networking on the Pi4 is pretty fast, or "fast" compared to an SD card.
> > The File Server is connected to a backup system that does a
> > continuous real-time sync. This means that if the server explodes I
> > lose only a few minutes of work.
> >
> > On Thu, Jun 30, 2022 at 7:48 AM Thaddeus Waldner <[email protected]>
> > wrote:
> >
> > > Here are some recent experiences with flash storage on a Pi4 as a
> > > development environment running LinuxCNC 2.8.2.
> > >
> > > A while back I posted in this mailing list that using an SSD on the Pi4
> > is
> > > prohibitive because it causes latency issues. At the time, I tested this
> > on
> > > a heavily used, repurposed ssd. I later discovered that the SSD was
> > failing
> > > due to write wear. This is likely what caused the latency issues in the
> > > first place.
> > >
> > > In the meantime I ran the Pi4 (2GB memory) as a development platform,
> > > running up to 3 instances of VS Code (1.5GB memory each) along with
> > Glade,
> > > browser, etc. This type of usage made short work of the Samsung EVO
> > microSD
> > > card. The card wear issue first showed up as spurious latency
> > violations. A
> > > bit later the entire system became maddeningly slow and unusable.
> > >
> > > Cloning to a fresh sd card solved the problem.
> > >
> > > In the process of making backups I also cloned the system to an SSD
> > (intel
> > > 320 this time) and to my surprise, it ran with zero latency issues. I
> > will
> > > be using SSDs from now on, thank you.
> > >
> > > Some takeaways:
> > > 1) large page files are bad news for cheap flash storage
> > > 2) "worn out" storage will cause latency issue on low latency systems
> > > 3) latency tests on a low latency system might be a way to detect flash
> > > write wear issues.
> > >
> > > Thaddeus
> > >
> > > _______________________________________________
> > > Emc-users mailing list
> > > [email protected]
> > > https://lists.sourceforge.net/lists/listinfo/emc-users
> > >
> >
> >
> > --
> >
> > Chris Albertson
> > Redondo Beach, California
> >
> > _______________________________________________
> > Emc-users mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/emc-users
> >
>
> _______________________________________________
> Emc-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/emc-users
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users
