Re: jhalfs breaks with complaint when fstab supplied

"Pierre Labastie" ([email protected] via alfs-discuss Mailing List) <[email protected]>
Newsgroups gmane.linux.lfs.automated
Message-ID <[email protected]>
On Wed, 2022-09-21 at 13:16 +0200, Dragan wrote:
>  On 21/09/2022 12:04, Pierre Labastie ([email protected] via alfs-
> discuss Mailing List) wrote:
>  
> > I can't understand your setup: is fstab in /sources/sources/lfs or
> > /sources/script?
> Accidentally in both since I've mowed al files from /source of latest build.
> Both config and fstab are in both.
> In other e-mail you wrote:
> 
> Looks like you have entered "/sources/sources/lfs" for "Fstab file (optional)"
> instead of "/sources/sources/lfs/fstab"...
> 
> Answer is: Absolutely not. Since I have entered only one change to existing
> configuration of the previous build: 
> Was:
> [*] Retrieve source files
> (/sources/sources
> 
> Changed to:
> [*] Retrieve source files
> (/sources/sources/lfs
> 
> followed by Q....

So you moved the fstab file (as far as I understand) without changing the
location of the fstab file in the configuration!
> 
> Current configuration file, in which fstab is not set is attached. Path to
> fstab was same as for config file.
> There is check for both config and fstab. Probably that it's file and not the
> name as I use file config and not .config because of ls.
> 
> Dragan
> 
> PS: On friday or saturday I will start new build after moving ../lfs /to
> ../dev and post result.

Don't use ../dev !! (see my preceding post)

The configuration file you attached is truncated. The problematic part is not
there. I understand you may want to hide some configuration details, but please
send the beginning of "# System configuration" in the "configuration" file (The
four variables HAVE_FSTAB, FSTAB, CONFIG_BUILD_KERNEL, CONFIG)

-- 
http://lists.linuxfromscratch.org/sympa/info/alfs-discuss
Unsubscribe: See the above information page
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.