Re: Unable to set up transient service directory

"Bruce Dubbs" ([email protected] via blfs-support Mailing List) <[email protected]>
Newsgroups gmane.linux.lfs.beyond.support
Message-ID <[email protected]>
On 6/13/25 3:49 PM, "Cliff mcDiarmid" ([email protected] via blfs-support 
Mailing List) wrote:
> On Fri, 2025-06-13 at 07:29 +0000, Cliff mcDiarmid wrote:
>>> On 6/12/25 2:15 AM, tjoen ([email protected] via blfs-support Mailing
>>> List) wrote:
>>> On 6/11/25 9:18 PM, "Cliff mcDiarmid" ([email protected] via
>>> blfs-
>> support Mailing List) wrote:
>>
>>> Jun 06 23:23:12 cliffhanger systemd[3337]: Failed to copy os-
>>> release for
>>> propagation, ignoring: No such file or directory
>>
>>
>>> www.linuxfromscratch.org/lfs/view/stable-systemd/chapter11/theend.html
>>> That's odd. Were you still in chroot? Did you customize the fields
>> 'DISTRIB_CODENAME' and 'VERSION_CODENAME'?
>>
>> No but it helps if one has the file at all!   Installation was
>> through jhalfs
>> and totally missed it.   Installed it now and all okay.
> 
>> Jhalfs has been creating os-release for systemd since 2017 (and for
>> sysv since 2020)... If this has not been done, I'd say you may have had
> .previous errors (so that the commands for creating it have not been
>> run). Note that of course bugs may happen, so you might want to open a
>> thread on alfs-discuss.
> 
> I know how this happened.   Every time I've built LFS with jhalfs I've let it
> build the kernel with everything in place.  But It's always failed and that's
> where I stop the build.  Hence no os-release file.

I'll note here that I never have jhalfs build the kernel.  My procedure is just too 
different.  My naming of the kernel, config, and System.map is different. I use a 
custom config. I need firmware that is not installed by jhalfs.

I'll also note that I always configure grub by hand.

IMO, some things just don't lend themselves to automation.

   -- Bruce

-- 
http://lists.linuxfromscratch.org/sympa/info/blfs-support
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.