I have run fbsd kernels that support Large File System on multiple PC platforms with cpus from Intel and AMD, without any problems with missing Hardware dependencies.
So, my response was to BRUCE who brought up missing driver issue to the OP. I have never run into any missing driver issues on any of the PC I installed the Large File System on them. So, Bruce has NOT come up with any answer about just exactly which driver he assumes is missing. On 11/29/18, Ken Moffat <zarniwh...@ntlworld.com> wrote: > On Thu, Nov 29, 2018 at 02:47:38PM -0700, JD wrote: >> >> On 11/29/2018 02:41 PM, Douglas R. Reno wrote: >> > >> > On 11/29/18 3:37 PM, JD wrote: >> > > >> > > On 11/29/2018 02:18 PM, Bruce Dubbs wrote: >> > > > >> > > > 1. LFS got on to the hard drive using the host's drivers. >> > > > >> > > > 2. The specific driver needed depends on the HW. Try rebuilding >> > > > the kernel with make defconfig; make >> > > > >> > > Hey Bruce, >> > > you are saying that LFS varies and depends on the hardware?? >> > > Exactly which hardware? >> > > The disk IO layer drivers are dependent on type of disk HW interface >> > > at the lowest level. >> > > Above that an abstraction layer is used, and it is possible (if >> > > necessary) to build yet >> > > another abstraction layer above that. >> > > The FS's LFS layer is built on top of the "block io" layer, as the >> > > file system works >> > > with BLOCKS. >> > > So, please explain what type of hardware is LFS dependent on? >> > > >> > >> > Would you happen to be here for inquiries on Large File Support (LFS), >> > not Linux From Scratch? The two things are entirely separate, and "Large >> > File Support" was coined many years after the Linux From Scratch >> > distribution was started. >> > >> NO > > So, maybe you are here to troll ? > > On the off-chance that you are not trolling: linuxfromscratch (LFS) > is installed in a chroot by building from a pre-existing linux > system running on the same machine. > > As part of that, some parts of the build may be specific to the > machine (or what a VM presents as, if building in a VM), e.g. gmp > goes out of its way to optimise for what is expected to be present > on that machine (see past issues where a low-end pentium of what was > then the latest intel family lacked an instruction which whoever had > updated gmp's configure script thought was present on all of that > family). > > And the kernel configuration, because we expect the builder to build > for the machine he or she is using, will vary from one machine to > the next. > > ĸen > -- > I'm saving up 22 shillings and 10 pence (almost a pound!) per week to > buy an ARM-13. > http://www.antipope.org/charlie/blog-static/2018/11/brexit-means-brexit.html > -- > http://lists.linuxfromscratch.org/listinfo/lfs-support > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page > > Do not top post on this list. > > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > A: Top-posting. > Q: What is the most annoying thing in e-mail? > > http://en.wikipedia.org/wiki/Posting_style > -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
