Unable to login into custom live image

[Sreyan Chakravarty]

Hi,

I have created a custom live image using livecd-creator, but when I
boot from it there is no way to login into KDE after that.

I have tried adding:

%post
cat <<FOE > /etc/sddm.conf.d/autologin.conf
[Autologin]
User=live-user
Session=plasma.desktop
FOE
%end

But I get the message:

ignoring %post failure (code 1)
/tmp/ks-script-xntc2id7: line 1: /etc/sddm.conf.d/autologin.conf: No
such file or directory

My kickstart file is very basic and I have not added any packages that
would cause problems.

Even building an image without any modifications causes a login problem.
-- 
Regards,
Sreyan Chakravarty

[Scott Dowdle]

Greetings,

----- Original Message -----
>  I have created a custom live image using livecd-creator, but when I
>  boot from it there is no way to login into KDE after that.
>  
>  I have tried adding:
>  
>  %post
>  cat <<FOE > /etc/sddm.conf.d/autologin.conf
>  [Autologin]
>  User=live-user
>  Session=plasma.desktop
>  FOE
>  %end 
Looking at the current kickstarts in F33, I see:

# set up autologin for user liveuser
if [ -f /etc/sddm.conf ]; then
sed -i 's/^#User=.*/User=liveuser/' /etc/sddm.conf
sed -i 's/^#Session=.*/Session=plasma.desktop/' /etc/sddm.conf
else
cat > /etc/sddm.conf << SDDM_EOF
[Autologin]
User=liveuser
Session=plasma.desktop
SDDM_EOF
fi

Looks like the file might have changed... and there is the difference between live-user
and liveuser.

Sort out those details and you can probably get a working solution.

TYL,
-- 
Scott Dowdle
704 Church Street
Belgrade, MT 59714
[phone] [home]
[phone] [work]

[Sreyan Chakravarty]

On Wed, Dec 23, 2020 at 12:17 AM Scott Dowdle <dowdle(a)montanalinux.org&gt; wrote:
>  Greetings,
>
>  ----- Original Message -----
>  > I have created a custom live image using livecd-creator, but when I
>  > boot from it there is no way to login into KDE after that.
>  >
>  > I have tried adding:
>  >
>  > %post
>  > cat <<FOE > /etc/sddm.conf.d/autologin.conf
>  > [Autologin]
>  > User=live-user
>  > Session=plasma.desktop
>  > FOE
>  > %end
>
>  Looking at the current kickstarts in F33, I see:
>
>  # set up autologin for user liveuser
>  if [ -f /etc/sddm.conf ]; then
>  sed -i 's/^#User=.*/User=liveuser/' /etc/sddm.conf
>  sed -i 's/^#Session=.*/Session=plasma.desktop/' /etc/sddm.conf
>  else
>  cat > /etc/sddm.conf << SDDM_EOF
>  [Autologin]
>  User=liveuser
>  Session=plasma.desktop
>  SDDM_EOF
>  fi
>
>  Looks like the file might have changed... and there is the difference between live-user
> and liveuser.
>
>  Sort out those details and you can probably get a working solution.
>  

Can you tell me which file you found that in ?


-- 
Regards,
Sreyan Chakravarty

[Scott Dowdle]

Greetings,

----- Original Message -----
>  Can you tell me which file you found that in ? 
This command will reveal the answer (assuming you have the package that provides the files
installed):

grep autologin /usr/share/spin-kickstarts/*kde*

TYL,
-- 
Scott Dowdle
704 Church Street
Belgrade, MT 59714
[phone] [home]
[phone] [work]

[Hony Chiang]

Hello Dowdle,

I use Fedora 33 live image to boot my SUT, but there is no spin-kickstarts folder in the
filesystem. 
One livesys script is found in /etc/init.d path. Is it possible to modify this script in
squashfs.img or to add some parameters in grub.cfg for disabled “Welcome to Fedora” screen
and enabled “Auto login” features?

Thanks,
Hony

-----Original Message-----
From: Scott Dowdle [mailto:[e-mail]] 
Sent: Wednesday, December 23, 2020 3:43 AM
To: livecd(a)lists.fedoraproject.org
Subject: [Fedora-livecd-list] Re: Unable to login into custom live image

[CAUTION: External Mail]

Greetings,

----- Original Message -----
>  Can you tell me which file you found that in ?
>  
This command will reveal the answer (assuming you have the package that provides the files
installed):

grep autologin /usr/share/spin-kickstarts/*kde*

TYL,
-- 
Scott Dowdle
704 Church Street
Belgrade, MT 59714
[phone] [home]
[phone] [work]
_______________________________________________
livecd mailing list -- livecd(a)lists.fedoraproject.org
To unsubscribe send an email to livecd-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://urldefense.com/v3/__https://docs.fedoraproject.org/en-US/project/...

List Guidelines:
https://urldefense.com/v3/__https://fedoraproject.org/wiki/Mailing_list_g...

List Archives:
https://urldefense.com/v3/__https://lists.fedoraproject.org/archives/list...

[Hony Chiang]

Hello Chakravarty,

I use Fedora 33 live image to boot my SUT, but don’t see any file below in the live
filesystem.

/etc/sddm.conf.d/autologin.conf
kickstarts
/etc/sddm.conf

Thanks,
Hony

-----Original Message-----
From: Sreyan Chakravarty [mailto:[e-mail]] 
Sent: Wednesday, December 23, 2020 3:14 AM
To: livecd(a)lists.fedoraproject.org
Subject: [Fedora-livecd-list] Re: Unable to login into custom live image

[CAUTION: External Mail]

On Wed, Dec 23, 2020 at 12:17 AM Scott Dowdle <dowdle(a)montanalinux.org&gt; wrote:
>  Greetings,
>
>  ----- Original Message -----
>  > I have created a custom live image using livecd-creator, but when I
>  > boot from it there is no way to login into KDE after that.
>  >
>  > I have tried adding:
>  >
>  > %post
>  > cat <<FOE > /etc/sddm.conf.d/autologin.conf
>  > [Autologin]
>  > User=live-user
>  > Session=plasma.desktop
>  > FOE
>  > %end
>
>  Looking at the current kickstarts in F33, I see:
>
>  # set up autologin for user liveuser
>  if [ -f /etc/sddm.conf ]; then
>  sed -i 's/^#User=.*/User=liveuser/' /etc/sddm.conf
>  sed -i 's/^#Session=.*/Session=plasma.desktop/' /etc/sddm.conf
>  else
>  cat > /etc/sddm.conf << SDDM_EOF
>  [Autologin]
>  User=liveuser
>  Session=plasma.desktop
>  SDDM_EOF
>  fi
>
>  Looks like the file might have changed... and there is the difference between live-user
> and liveuser.
>
>  Sort out those details and you can probably get a working solution.
>
>  

Can you tell me which file you found that in ?


-- 
Regards,
Sreyan Chakravarty
_______________________________________________
livecd mailing list -- livecd(a)lists.fedoraproject.org
To unsubscribe send an email to livecd-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://urldefense.com/v3/__https://docs.fedoraproject.org/en-US/project/...

List Guidelines:
https://urldefense.com/v3/__https://fedoraproject.org/wiki/Mailing_list_g...

List Archives:
https://urldefense.com/v3/__https://lists.fedoraproject.org/archives/list...

[Scott Dowdle]

Greetings,

----- Original Message -----
>  Hello Chakravarty,
>  
>  I use Fedora 33 live image to boot my SUT, but don’t see any file
>  below in the live filesystem.
>  
>  /etc/sddm.conf.d/autologin.conf
>  kickstarts
>  /etc/sddm.conf 
Those files are related to the KDE Plasma spin.  I assume you are using the Fedora
Workstation (aka GNOME) spin?  If so, GNOME uses GDM for a graphical login manager than
SDDM.  The "Welcome" program is part of the WORKSTATION spin.

TYL,
-- 
Scott Dowdle
704 Church Street
Belgrade, MT 59714
[phone] [home]
[phone] [work]

[Sreyan Chakravarty]

On Wed, 23 Dec 2020, 8:55 pm Scott Dowdle, <dowdle(a)montanalinux.org&gt; wrote:

>  Greetings,
>
>  ----- Original Message -----
>  > Hello Chakravarty,
> >  
>  > I use Fedora 33 live image to boot my SUT, but don’t see
> any file
>  > below in the live filesystem.
> >  
>  > /etc/sddm.conf.d/autologin.conf
>  > kickstarts
>  > /etc/sddm.conf
>
>  Those files are related to the KDE Plasma spin.  I assume you are using
>  the Fedora Workstation (aka GNOME) spin?  If so, GNOME uses GDM for a
>  graphical login manager than SDDM.  The "Welcome" program is part of the
>  WORKSTATION spin.
>  
I think it would make the most sense to unsquash the live image of the
Fedora 33 ISO and copy what they do for auto login.

>

[Scott Dowdle]

Greetings,

----- Original Message -----
>  I think it would make the most sense to unsquash the live image of
>  the Fedora 33 ISO and copy what they do for auto login. 
You don't have to unsquash anything, just look at the kickstart files published in the
stock Fedora repo... as what they do is shown there.

dnf install fedora-kickstarts
cd /usr/share/spin-kickstarts/
  (examine desired .ks files)

And those scripts can be modified and used to build your own media with livecd-creator or
livemedia-creator.

For more info, feel free to pop into #fedora-respins on the Freenode IRC network... but
remember IRC isn't always immediate and interactive... especially over the holidays
when some folks are unavailable.

TYL,
-- 
Scott Dowdle
704 Church Street
Belgrade, MT 59714
[phone] [home]
[phone] [work]

[Sreyan Chakravarty]

On Thu, Dec 24, 2020 at 9:01 PM Scott Dowdle <dowdle(a)montanalinux.org&gt; wrote:
>  Greetings,
>
>  ----- Original Message -----
>  > I think it would make the most sense to unsquash the live image of
>  > the Fedora 33 ISO and copy what they do for auto login.
>
>  You don't have to unsquash anything, just look at the kickstart files published in
> the stock Fedora repo... as what they do is shown there.
>
>  dnf install fedora-kickstarts
>  cd /usr/share/spin-kickstarts/
>    (examine desired .ks files)
>
>  And those scripts can be modified and used to build your own media with livecd-creator or
> livemedia-creator.
>
>  For more info, feel free to pop into #fedora-respins on the Freenode IRC network... but
> remember IRC isn't always immediate and interactive... especially over the holidays
> when some folks are unavailable.
>  
It did not work. I have added liveuser into the fedora live kickstart,
but it does not log me in.

A lot of strange behavior is exhibited.

When I open up a tty and type in liveuser, it does nothing and gives
me back to the login prompt. It gives no error or anything.

Errors pop up when I use other usernames.

The user is "liveuser" not "live-user".

I think the problem is with the authentication module.

-- 
Regards,
Sreyan Chakravarty

[Scott Dowdle]

Greetings,

----- Original Message -----
>  It did not work. I have added liveuser into the fedora live
>  kickstart, but it does not log me in.
>  
>  A lot of strange behavior is exhibited.
>  
>  When I open up a tty and type in liveuser, it does nothing and gives
>  me back to the login prompt. It gives no error or anything.
>  
>  Errors pop up when I use other usernames.
>  
>  The user is "liveuser" not "live-user".
>  
>  I think the problem is with the authentication module. 
Feel free to share your kickstart(s) and perhaps we can have a look at them.

TYL,
-- 
Scott Dowdle
704 Church Street
Belgrade, MT 59714
[phone] [home]
[phone] [work]

[Sreyan Chakravarty]

On Tue, Dec 29, 2020 at 12:22 AM Scott Dowdle <dowdle(a)montanalinux.org&gt; wrote:
>  Greetings,
>
>  ----- Original Message -----
>  > It did not work. I have added liveuser into the fedora live
>  > kickstart, but it does not log me in.
>  >
>  > A lot of strange behavior is exhibited.
>  >
>  > When I open up a tty and type in liveuser, it does nothing and gives
>  > me back to the login prompt. It gives no error or anything.
>  >
>  > Errors pop up when I use other usernames.
>  >
>  > The user is "liveuser" not "live-user".
>  >
>  > I think the problem is with the authentication module.
>
>  Feel free to share your kickstart(s) and perhaps we can have a look at them.
>  
I have modified fedora-live-kde.ks by adding live user in its post section:
https://pastebin.com/raw/CQVkPr8S

This is my flattened kickstart:
ksflatten -c fedora-live-kde.ks -o kde_flattened.ks -v F33
https://pastebin.com/raw/B5Ph4Rbw

I have also verified the Fedora 33 KDE image by unsquashing its live
image. Strangely, it does not have any live user added to sddm.conf,
but it can somehow "magically" log me in.

Let me know if you are not able to view the pastebins.

Do me a favor, rather than fiddling with my kickstarts, can you just
verify whether you can create a KDE Live image from the kickstarts
that you can log into.

-- 
Regards,
Sreyan Chakravarty

[Scott Dowdle]

Greetings,

----- Original Message -----
>  I have modified fedora-live-kde.ks by adding live user in its post
>  section:
>  https://pastebin.com/raw/CQVkPr8S
>  
>  This is my flattened kickstart:
>  ksflatten -c fedora-live-kde.ks -o kde_flattened.ks -v F33
>  https://pastebin.com/raw/B5Ph4Rbw 
I built an iso using livecd-creator with your kickstart file... and I believe I discovered
the root cause of your problem (no liveuser on the media)... and that is, with the package
set you have provided, for whatever reason, the shadow-utils packages (which provides
useradd/adduser) isn't part of the package transaction and as result the post section
where the user gets created can't find the command and can't make the user.  Just
added that package to the list and at least that part should be resolved.

TYL,
-- 
Scott Dowdle
704 Church Street
Belgrade, MT 59714
[phone] [home]
[phone] [work]

[Sreyan Chakravarty]

On Tue, Dec 29, 2020 at 1:39 AM Scott Dowdle <dowdle(a)montanalinux.org&gt; wrote:
>  Greetings,
>
>  ----- Original Message -----
>  > I have modified fedora-live-kde.ks by adding live user in its post
>  > section:
>  > https://pastebin.com/raw/CQVkPr8S
>  >
>  > This is my flattened kickstart:
>  > ksflatten -c fedora-live-kde.ks -o kde_flattened.ks -v F33
>  > https://pastebin.com/raw/B5Ph4Rbw
>
>  I built an iso using livecd-creator with your kickstart file... and I believe I
> discovered the root cause of your problem (no liveuser on the media)... and that is, with
> the package set you have provided, for whatever reason, the shadow-utils packages (which
> provides useradd/adduser) isn't part of the package transaction and as result the post
> section where the user gets created can't find the command and can't make the
> user.  Just added that package to the list and at least that part should be resolved.
>  
Ok, so what do I have to do ?

Isn't this a bug ?

-- 
Regards,
Sreyan Chakravarty

[Scott Dowdle]

Greetings,

----- Original Message -----
>  Ok, so what do I have to do ?
>  
>  Isn't this a bug ? 
My bad.  I was mistaken... as the shadow-utils is being added to the package transaction
and is there.  I built an iso from your kickstart but I did change one thing... the repo
definitions as I have a local mirror.  I used the Fedora 33 repos and I see your kickstart
is using the rawhide repos.  Are you really wanting the rawhide repos?  The media I
produced from your kickstart (with the F33 repos) worked fine.  The liveuser was there and
it automatically logged into KDE.  Why was I mistaken earlier?  I was looking in the
package cache directories to see what was downloaded and I only looked in the fedora
directory... and it wasn't there... but it was in the updates directory as the package
was coming from updates.

I've been doing rawhide builds myself (for cinnamon, kde plasma, lxde, lxqt, mate,
work, and xfce) and for the past week or so, they have been failing to build as a result
of missing package dependencies.  That will most likely be fixed in the not-too-distant
future, but for now, it is broken.  I don't recall exactly what package was missing or
if it affects all of my desktop spins or not.  As you'd expect, trying to do updates
on a rawhide VM is also not working as a result of missing deps.  It is not uncommon for
rawhide to be broken from time to time.

TYL,
-- 
Scott Dowdle
704 Church Street
Belgrade, MT 59714
[phone] [home]
[phone] [work]

[Sreyan Chakravarty]

On Tue, 29 Dec 2020, 2:12 am Scott Dowdle, <dowdle(a)montanalinux.org&gt; wrote:

>  Greetings,
>
>  ----- Original Message -----
>  > Ok, so what do I have to do ?
> >  
>  > Isn't this a bug ?
>
>  My bad.  I was mistaken... as the shadow-utils is being added to the
>  package transaction and is there.  I built an iso from your kickstart but I
>  did change one thing... the repo definitions as I have a local mirror.  I
>  used the Fedora 33 repos and I see your kickstart is using the rawhide
>  repos.  Are you really wanting the rawhide repos?  The media I produced
>  from your kickstart (with the F33 repos) worked fine.  The liveuser was
>  there and it automatically logged into KDE.  Why was I mistaken earlier?  I
>  was looking in the package cache directories to see what was downloaded and
>  I only looked in the fedora directory... and it wasn't there... but it was
>  in the updates directory as the package was coming from updates.
>
>  I've been doing rawhide builds myself (for cinnamon, kde plasma, lxde,
>  lxqt, mate, work, and xfce) and for the past week or so, they have been
>  failing to build as a result of missing package dependencies.  That will
>  most likely be fixed in the not-too-distant future, but for now, it is
>  broken.  I don't recall exactly what package was missing or if it affects
>  all of my desktop spins or not.  As you'd expect, trying to do updates on a
>  rawhide VM is also not working as a result of missing deps.  It is not
>  uncommon for rawhide to be broken from time to time.
>  

The rawhide repos are added by default. Even I thought that it was kind of
weird.

So you just changed the repos to the F33 repos, did you do anything else?

>

[Scott Dowdle]

Greetings,

----- Original Message -----
>  The rawhide repos are added by default. Even I thought that it was
> kind of weird.
>  
>  So you just changed the repos to the F33 repos, did you do anything else? 
Nope.  And it worked for me.

TYL,
-- 
Scott Dowdle
704 Church Street
Belgrade, MT 59714
[phone] [home]
[phone] [work]

[Sreyan Chakravarty]

On Tue, Dec 29, 2020 at 12:01 PM Scott Dowdle <dowdle(a)montanalinux.org&gt; wrote:
>  Nope.  And it worked for me. 
I am confused, you just said that getting rid of the rawhide repos
solved the problem.

So now you are saying it worked with rawhide ?

-- 
Regards,
Sreyan Chakravarty

[Sreyan Chakravarty]

On Tue, Dec 29, 2020 at 1:16 PM Sreyan Chakravarty <sreyan32(a)gmail.com&gt; wrote:
>  On Tue, Dec 29, 2020 at 12:01 PM Scott Dowdle <dowdle(a)montanalinux.org&gt; wrote:
>  >
>  > Nope.  And it worked for me.
>
>  I am confused, you just said that getting rid of the rawhide repos
>  solved the problem.
>
>  So now you are saying it worked with rawhide ?
>  
I used the Fedora 33 repos and it did not work. I am having the same problem.
-- 
Regards,
Sreyan Chakravarty

[Sreyan Chakravarty]

On Tue, Dec 29, 2020 at 2:35 PM Sreyan Chakravarty <sreyan32(a)gmail.com&gt; wrote:
>  On Tue, Dec 29, 2020 at 1:16 PM Sreyan Chakravarty <sreyan32(a)gmail.com&gt; wrote:
>  >
>  > On Tue, Dec 29, 2020 at 12:01 PM Scott Dowdle <dowdle(a)montanalinux.org&gt;
> wrote:
>  > >
>  > > Nope.  And it worked for me.
>  >
>  > I am confused, you just said that getting rid of the rawhide repos
>  > solved the problem.
>  >
>  > So now you are saying it worked with rawhide ?
>  >
>
>  I used the Fedora 33 repos and it did not work. I am having the same problem. 
I am however getting:

                     Failed to Remount Kernel and Root Filesystems

in the boot log.

-- 
Regards,
Sreyan Chakravarty

[Sreyan Chakravarty]

On Tue, Dec 29, 2020 at 2:36 PM Sreyan Chakravarty <sreyan32(a)gmail.com&gt; wrote:
>  On Tue, Dec 29, 2020 at 2:35 PM Sreyan Chakravarty <sreyan32(a)gmail.com&gt; wrote:
>  >
>  > On Tue, Dec 29, 2020 at 1:16 PM Sreyan Chakravarty <sreyan32(a)gmail.com&gt;
> wrote:
>  > >
>  > > On Tue, Dec 29, 2020 at 12:01 PM Scott Dowdle <dowdle(a)montanalinux.org&gt;
> wrote:
>  > > >
>  > > > Nope.  And it worked for me.
>  > >
>  > > I am confused, you just said that getting rid of the rawhide repos
>  > > solved the problem.
>  > >
>  > > So now you are saying it worked with rawhide ?
>  > >
>  >
>  > I used the Fedora 33 repos and it did not work. I am having the same problem.
>
>  I am however getting:
>
>                       Failed to Remount Kernel and Root Filesystems
>
>  in the boot log.
>  
Can you share the kickstart which worked for you ?

-- 
Regards,
Sreyan Chakravarty

[Scott Dowdle]

Greetings,

----- Original Message -----
>  Can you share the kickstart which worked for you ? 
I used the kickstart you provided the URL for for your flattened one. I made two
modifications to it:

1) Replaced your two repo lines with local mirror references for Fedora 33 Base OS and
Updates
2) Added the shadow-utils package to the end of your package list (before the - removals)

I made a recording showing the whole process including doing an install with the created
media:
https://www.montanalinux.org/files/livecd-creator-20201229.mp4

TYL,
-- 
Scott Dowdle
704 Church Street
Belgrade, MT 59714
[phone] [home]
[phone] [work]

[Sreyan Chakravarty]

On Tue, Dec 29, 2020 at 11:17 PM Scott Dowdle <dowdle(a)montanalinux.org&gt; wrote:
>  Greetings,
>
>  ----- Original Message -----
>  > Can you share the kickstart which worked for you ?
>
>  I used the kickstart you provided the URL for for your flattened one. I made two
> modifications to it:
>
>  1) Replaced your two repo lines with local mirror references for Fedora 33 Base OS and
> Updates
>  2) Added the shadow-utils package to the end of your package list (before the -
> removals)
>
>  I made a recording showing the whole process including doing an install with the created
> media:
>  https://www.montanalinux.org/files/livecd-creator-20201229.mp4
>  
First of all I really appreciate you taking time out from your
schedule to give such an in depth demonstration. I am saving your
video for future reference.

Next, I should tell you that I did not require the shadow-utils
package, I just had to use the "not-rawhide" repos.
Here is how I did it:

Opened up fedora-repos.ks
Commented all lines for rawhide, and uncommented all lines for
"not-rawhide" repos.
Downloaded the fedora-not-rawhide kickstart file.

I also found that livecd-creator does not need a flattened kickstart
you can just use a regular kickstart and it is smart enough to figure
out by itself what to do.

I do have a couple of questions though. You see, the main reason I am
creating my livecd is because I want to put all my home settings into
it like the config/ and local/ folder.

I have noticed some strange things with regards to the /home/liveuser
directory. If you unsquash the squashfs.img in the LiveOS directory
and mount rootfs.img you will see that under /home there is no
directory for liveuser.
Yet when I boot the live image I get a directory in the live system
called /home/liveuser.

Where does it spontaneously materialize from ?

Also the fedora-live-base.ks actually creates the liveuser directory,
yet it is not there when the liveimage is ready.

Very confusing.

Lastly, I would like to know the order in which the %post sections are
executed in a kickstart file. What is the ordering ? How is that
ordering determined ?

Thanks.

-- 
Regards,
Sreyan Chakravarty

[Scott Dowdle]

Greetings,

----- Original Message -----
>  On Tue, Dec 29, 2020 at 11:17 PM Scott Dowdle
>  Next, I should tell you that I did not require the shadow-utils
>  package, I just had to use the "not-rawhide" repos.
>  Here is how I did it: 
I believe you... as it should have been pulled in by dependencies  and not need to be
explicitly listed.  For my builds I favor complete (unversioned) package lists rather than
using package groups.  That takes more work... as before I start a new build, I create a
VM (for the spins I care about anyway), get it setup how I like it... and then export a
package list... which I %include in my kickstart.  That's probably going overboard but
works-for-me.

>  I also found that livecd-creator does not need a flattened kickstart
>  you can just use a regular kickstart and it is smart enough to figure
>  out by itself what to do. 
That is correct.  I make my package list a separate file and it is easy to include a
different list without having to edit the kickstart.  ANOTHER advantage of livecd-creator
over livemedia-creator.  Also the repo defs in lcc are normal looking whereas they are
different/weird in lmc.  So, for my kickstarts everything is all in one file except for
the package list and the repo list which I use %includes for.

>  I do have a couple of questions though. You see, the main reason I
> am
>  creating my livecd is because I want to put all my home settings into
>  it like the config/ and local/ folder.
>  
>  I have noticed some strange things with regards to the /home/liveuser
>  directory. If you unsquash the squashfs.img in the LiveOS directory
>  and mount rootfs.img you will see that under /home there is no
>  directory for liveuser.
>  Yet when I boot the live image I get a directory in the live system
>  called /home/liveuser.
>  
>  Where does it spontaneously materialize from ? 
The %post stuff really creates a script on the media that gets run at boot time... so the
liveuser is created every time the live media boots... and is NOT baked-in.   If you want
to dump liveuser account customizations in, you're going to have to find a way to make
it part of the script that creates the liveuser account on boot.  That shouldn't be
too hard.  You'll just have to copy everything you care about into your image (usually
doable in the "%post --nochroot" section so you have a stuff to copy from.  I
can provide an example of that from my own REMIX kickstarts although I'm not copying
anything into liveuser but into /root/ as my media includes the build scripts that they
were made with under /root/livecd-creator.  The root account IS baked-in a little easier.

>  Lastly, I would like to know the order in which the %post sections
>  are executed in a kickstart file. What is the ordering ? How is that
>  ordering determined ? 
I've always wondered that myself... which is why in my kickstarts I manually edit and
merge all of the %posts into a single %post... which removes the mystery.  I wish I had a
better answer for you on that.

TYL,
-- 
Scott Dowdle
704 Church Street
Belgrade, MT 59714
[phone] [home]
[phone] [work]

[Sreyan Chakravarty]

On Wed, Dec 30, 2020 at 11:34 PM Scott Dowdle <dowdle(a)montanalinux.org&gt; wrote:
>  The %post stuff really creates a script on the media that gets run at
> boot time... so the liveuser is created every time the live media boots... and is NOT
> baked-in.   If you want to dump liveuser account customizations in, you're > going
> to have to find a way to make it part of the script that creates the liveuser account on
> boot.  That shouldn't be too hard.  You'll just have to copy everything you care
> about into your image (usually doable in the "%post --> > nochroot"
> section so you have a stuff to copy from.  I can provide an example of that from my own
> REMIX kickstarts although I'm not copying anything into liveuser but into /root/ as my
> media includes the build scripts that they > were made with under /root/livecd-creator.
>  The root account IS baked-in a little easier. 
Yes. I saw its an init/rc.d script.

I am getting an error that seems to look real nasty:

Running scriptlet: kernel-core-5.9.16-200.fc33.x86_64
/etc/dracut.conf.d/99-liveos.conf:filesystems+="vfat msdos isofs ext4
xfs btrfs squashfs "
/etc/dracut.conf.d/99-liveos.conf:add_drivers+="sr_mod sd_mod ide-cd
cdrom =ata sym53c8xx aic7xxx ehci_hcd uhci_hcd ohci_hcd usb_storage
usbhid uas firewire-sbp2 firewire-ohci sbp2 ohci1394 ieee1394
mmc_block sdhci sdhci-pci pata_pcmcia mptsas virtio_blk virtio_pci
virtio_scsi virtio_net virtio_mmio virtio_balloon virtio-rng  "

dracut: WARNING: <key>+=" <values> ": <values> should have
surrounding
white spaces!
dracut: WARNING: This will lead to unwanted side effects! Please fix
the configuration file.

dracut: No '/dev/log' or 'logger' included for syslog logging
dracut-install: ERROR: installing 'sr_mod'
dracut-install: ERROR: installing 'ext4'
sort: fflush failed: 'standard output': Broken pipe
sort: write error

gzip: stdout: Broken pipe


I am not sure if this a bug or if this error is because I am doing
something wrong. I am not sure even if I have to worry about this
error.


-- 
Regards,
Sreyan Chakravarty

[Jasper Hartline]

It failed to install ext4 into the initramfs so I would worry about it

On Thu, Dec 31, 2020 at 7:50 AM Sreyan Chakravarty <sreyan32(a)gmail.com&gt;
wrote:

>  On Wed, Dec 30, 2020 at 11:34 PM Scott Dowdle
> <dowdle(a)montanalinux.org&gt;
>  wrote:
>  > The %post stuff really creates a script on the media that gets run at
>  boot time... so the liveuser is created every time the live media boots...
>  and is NOT baked-in.   If you want to dump liveuser account customizations
>  in, you're > going to have to find a way to make it part of the script that
>  creates the liveuser account on boot.  That shouldn't be too hard.  You'll
>  just have to copy everything you care about into your image (usually doable
>  in the "%post --> > nochroot" section so you have a stuff to copy from. 
> I
>  can provide an example of that from my own REMIX kickstarts although I'm
>  not copying anything into liveuser but into /root/ as my media includes the
>  build scripts that they > were made with under /root/livecd-creator.  The
>  root account IS baked-in a little easier.
>
>  Yes. I saw its an init/rc.d script.
>
>  I am getting an error that seems to look real nasty:
>
>  Running scriptlet: kernel-core-5.9.16-200.fc33.x86_64
>  /etc/dracut.conf.d/99-liveos.conf:filesystems+="vfat msdos isofs ext4
>  xfs btrfs squashfs "
>  /etc/dracut.conf.d/99-liveos.conf:add_drivers+="sr_mod sd_mod ide-cd
>  cdrom =ata sym53c8xx aic7xxx ehci_hcd uhci_hcd ohci_hcd usb_storage
>  usbhid uas firewire-sbp2 firewire-ohci sbp2 ohci1394 ieee1394
>  mmc_block sdhci sdhci-pci pata_pcmcia mptsas virtio_blk virtio_pci
>  virtio_scsi virtio_net virtio_mmio virtio_balloon virtio-rng  "
>
>  dracut: WARNING: <key>+=" <values> ": <values> should have
> surrounding
>  white spaces!
>  dracut: WARNING: This will lead to unwanted side effects! Please fix
>  the configuration file.
>
>  dracut: No '/dev/log' or 'logger' included for syslog logging
>  dracut-install: ERROR: installing 'sr_mod'
>  dracut-install: ERROR: installing 'ext4'
>  sort: fflush failed: 'standard output': Broken pipe
>  sort: write error
>
>  gzip: stdout: Broken pipe
>
>
>  I am not sure if this a bug or if this error is because I am doing
>  something wrong. I am not sure even if I have to worry about this
>  error.
>
>
>  --
>  Regards,
>  Sreyan Chakravarty
>  _______________________________________________
>  livecd mailing list -- livecd(a)lists.fedoraproject.org
>  To unsubscribe send an email to livecd-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>

[Sreyan Chakravarty]

On Fri, 1 Jan 2021, 4:08 am Jasper Hartline, <jasper.hartline(a)gmail.com
>  
wrote:

>  It failed to install ext4 into the initramfs so I would worry about it
>  
What can I do to rectify this problem?

I have made no changes to the Kickstart. Do you get the same problem on
your side ?

>