You are not logged in.

#1 2022-05-10 18:04:35

PatoJAD
Member
From: Argentina
Registered: 2022-05-10
Posts: 6
Website

[SOLVED] Archiso does not generate home folders

First of all I apologize for my low level of English. I hope that even so I can explain myself well using web tools. hmm

I find myself generating an ISO with Archiso. Although I had several inconveniences, I was able to solve the vast majority. Except for the fact that users' home folders are not created. If I can log in with the user created by the tty. However it tells me that it doesn't have access to the folder /home/lynx in this particular case.


I clearly read the documentation smile Therefore, I leave below the configuration of the necessary files to create the user according to the wiki

  • /airootfs/etc/passwd SOLUTION: This file must end with a blank line

    root:x:0:0:root:/root:/usr/bin/zsh
    lynx:x:1000:1000::/home/lynx:/usr/bin/zsh
  • /airootfs/etc/shadow

    root::14871::::::
    lynx:$6$.nNsPougJ2VHtnii$hmAJBCv/aXIcqEl6bI3TBjkQKE4CSyLuW2b2H4EsXP7/4.mWBbc6zfENNo7gIAXY.8X.o.m/xR5PEyKZ7yPpJ/:14871::::::
  • /airootfs/etc/group

    root:x:0:root
    adm:x:4:lynx
    wheel:x:10:lynx
    uucp:x:14:lynx
    sys:x:3:bin,lynx
    users:x:984:lynx
    rfkill:x:982:lynx
    autologin:x:1001:lynx
    lynx:x:1000:
  • /airootfs/etc/gshadow

    root:!*::root
    autologin:!::lynx
    wheel:!*::lynx
    users:!*::lynx
    rfkill:!*::lynx
    lynx:!*::
  • profiledef.sh

    ...
    file_permissions=(
      ["/etc/lightdm"]="0:0:755"
      ["/home/lynx"]="1000:1000:755" // This was used for a test where if that folder is created but the skel file is not copied
      ["/etc/lightdm/lightdm.conf"]="0:0:400"
      ["/etc/sudoers.d"]="0:0:755"
      ["//etc/sudoers.d/g_wheel"]="0:0:400"
      ["/etc/shadow"]="0:0:400"
      ["/etc/gshadow"]="0:0:400"
      ["/root"]="0:0:750"
      ["/root/.automated_script.sh"]="0:0:755"
      ["/usr/bin/lynx-desktop"]="0:0:755"
      ["/usr/bin/lynx-desktop-service"]="0:0:755"
      ["/usr/bin/lynx-menu"]="0:0:755"
      ["/usr/bin/lynx-dock"]="0:0:755"
      ["/usr/local/bin/choose-mirror"]="0:0:755"
      ["/usr/local/bin/Installation_guide"]="0:0:755"
      ["/usr/local/bin/livecd-sound"]="0:0:755"
    )

But here it says that only that should be enough but it is not. Does anyone have an idea how I could do it? I tried to create the folder by hand in airootfs and give it permission but it doesn't copy everything that has /etc/skel.

Last edited by PatoJAD (2022-05-12 16:42:45)

Offline

#2 2022-05-10 19:25:46

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 10,069

Re: [SOLVED] Archiso does not generate home folders

 ["/home/lynx"]="1000:1000:755" // This was used for a test where if that folder is created but the skel file is not copied

remove that, prepend LC_ALL=C   to the mkarchiso command and run it again
Post the output it generates.

Welcome to archlinux forums

Last edited by Lone_Wolf (2022-05-10 19:26:05)


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
Did you use the guided installer ? If yes, I can't help you.

(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#3 2022-05-10 20:14:25

PatoJAD
Member
From: Argentina
Registered: 2022-05-10
Posts: 6
Website

Re: [SOLVED] Archiso does not generate home folders

First of all thanks for the welcome. I have spent time in Arch and generating content in Spanish on GNU/Linux. And registering in the forum is to be able to collaborate with the base distro that finished my distrohooping and that is the base of my "distro"

Without further ado, I leave you the output based on what you told me:

:: Running post-transaction hooks...
( 1/32) Creating system user accounts...
Creating group 'locate' with GID 21.
Creating group 'ntp' with GID 87.
Creating group 'vboxsf' with GID 109.
Creating group 'avahi' with GID 977.
Creating user 'avahi' (Avahi mDNS/DNS-SD daemon) with UID 977 and GID 977.
Creating group 'named' with GID 40.
Creating user 'named' (BIND DNS Server) with UID 40 and GID 40.
Creating group 'dhcpcd' with GID 976.
Creating user 'dhcpcd' (dhcpcd privilege separation) with UID 976 and GID 976.
Creating group 'dnsmasq' with GID 975.
Creating user 'dnsmasq' (dnsmasq daemon) with UID 975 and GID 975.
Creating group 'git' with GID 974.
Creating user 'git' (git daemon user) with UID 974 and GID 974.
Creating group 'lightdm' with GID 973.
Creating user 'lightdm' (Light Display Manager) with UID 973 and GID 973.
Creating group 'nbd' with GID 972.
Creating user 'nbd' (Network Block Device) with UID 972 and GID 972.
Creating group 'nm-openvpn' with GID 971.
Creating user 'nm-openvpn' (NetworkManager OpenVPN) with UID 971 and GID 971.
Creating user 'ntp' (Network Time Protocol) with UID 87 and GID 87.
Creating group 'nvidia-persistenced' with GID 143.
Creating user 'nvidia-persistenced' (NVIDIA Persistence Daemon) with UID 143 and GID 143.
Creating group 'openvpn' with GID 970.
Creating user 'openvpn' (OpenVPN) with UID 970 and GID 970.
Creating group 'partimag' with GID 110.
Creating user 'partimag' (Partimage user) with UID 110 and GID 110.
Creating group 'polkitd' with GID 102.
Creating user 'polkitd' (PolicyKit daemon) with UID 102 and GID 102.
Creating group 'rpc' with GID 32.
Creating user 'rpc' (Rpcbind Daemon) with UID 32 and GID 32.
Creating group 'usbmux' with GID 140.
Creating user 'usbmux' (usbmux user) with UID 140 and GID 140.
( 2/32) Updating journal message catalog...
( 3/32) Reloading system manager configuration...
  Skipped: Running in chroot.
( 4/32) Updating udev hardware database...
( 5/32) Applying kernel sysctl settings...
  Skipped: Running in chroot.
( 6/32) Creating temporary files...
Failed to open file "/sys/devices/system/cpu/microcode/reload": Read-only file system
error: command failed to execute correctly
( 7/32) Reloading device manager configuration...
  Skipped: Running in chroot.
( 8/32) Arming ConditionNeedsUpdate...
( 9/32) Updating the MIME type database...
(10/32) Updating fontconfig configuration...
(11/32) Uncommenting en_US.UTF-8 locale and running locale-gen...
Generating locales...
  en_US.UTF-8... done
Generation complete.
(12/32) Rebuilding certificate stores...
(13/32) Updating module dependencies...
(14/32) Install DKMS modules
==> dkms install --no-depmod nvidia/510.68.02 -k 5.17.5-256-tkg-bmq
==> dkms install --no-depmod broadcom-wl/6.30.223.271 -k 5.17.5-256-tkg-bmq
==> depmod 5.17.5-256-tkg-bmq
(15/32) Cleaning up...
(16/32) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux-tkg-bmq.preset: 'default'
  -> -k /boot/vmlinuz-linux-tkg-bmq -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-tkg-bmq.img
==> Starting build: 5.17.5-256-tkg-bmq
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [memdisk]
  -> Running build hook: [archiso]
  -> Running build hook: [archiso_loop_mnt]
  -> Running build hook: [archiso_pxe_common]
==> WARNING: Possibly missing firmware for module: softing_cs
==> WARNING: Possibly missing firmware for module: bnx2x
==> WARNING: Possibly missing firmware for module: bna
==> WARNING: Possibly missing firmware for module: liquidio
==> WARNING: Possibly missing firmware for module: mlxsw_spectrum
==> WARNING: Possibly missing firmware for module: nfp
==> WARNING: Possibly missing firmware for module: qed
  -> Running build hook: [archiso_pxe_nbd]
  -> Running build hook: [archiso_pxe_http]
  -> Running build hook: [archiso_pxe_nfs]
  -> Running build hook: [archiso_kms]
==> WARNING: Possibly missing firmware for module: ast
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: qla1280
==> WARNING: Possibly missing firmware for module: qla2xxx
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: xhci_pci
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-tkg-bmq.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-tkg-bmq.preset: 'fallback'
  -> -k /boot/vmlinuz-linux-tkg-bmq -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-tkg-bmq-fallback.img -S autodetect
==> Starting build: 5.17.5-256-tkg-bmq
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [memdisk]
  -> Running build hook: [archiso]
  -> Running build hook: [archiso_loop_mnt]
  -> Running build hook: [archiso_pxe_common]
==> WARNING: Possibly missing firmware for module: softing_cs
==> WARNING: Possibly missing firmware for module: bnx2x
==> WARNING: Possibly missing firmware for module: bna
==> WARNING: Possibly missing firmware for module: liquidio
==> WARNING: Possibly missing firmware for module: mlxsw_spectrum
==> WARNING: Possibly missing firmware for module: nfp
==> WARNING: Possibly missing firmware for module: qed
  -> Running build hook: [archiso_pxe_nbd]
  -> Running build hook: [archiso_pxe_http]
  -> Running build hook: [archiso_pxe_nfs]
  -> Running build hook: [archiso_kms]
==> WARNING: Possibly missing firmware for module: ast
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: qla1280
==> WARNING: Possibly missing firmware for module: qla2xxx
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: xhci_pci
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-tkg-bmq-fallback.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'LynxOS'
==> WARNING: No image file specified. Skipping image `LynxOS'
(17/32) Updating the appstream cache...
? Metadata cache was updated successfully.
(18/32) Reloading system bus configuration...
  Skipped: Running in chroot.
(19/32) Warn about old perl modules
(20/32) Updating fontconfig cache...
(21/32) Probing GDK-Pixbuf loader modules...
(22/32) Updating GIO module cache...
(23/32) Compiling GSettings XML schema files...
(24/32) Probing GTK2 input method modules...
(25/32) Probing GTK3 input method modules...
(26/32) Updating icon theme caches...
(27/32) Reloading GVFS config...
killall: /proc lacks process entries (not mounted ?)
(28/32) Updating the info directory file...
(29/32) Uncommenting all mirrors in /etc/pacman.d/mirrorlist...
(30/32) Updating the desktop file MIME type cache...
(31/32) Updating the vlc plugin cache...
(32/32) Work around FS#49347 by removing custom pacman hooks that are only required during ISO build...
[mkarchiso] INFO: Done! Packages installed successfully.
[mkarchiso] INFO: Creating version files...
[mkarchiso] INFO: Done!
[mkarchiso] INFO: Copying /etc/skel/* to user homes...
[mkarchiso] INFO: Done!
[mkarchiso] INFO: Creating a list of installed packages on live-enviroment...
[mkarchiso] INFO: Done!
[mkarchiso] INFO: Setting up SYSLINUX for BIOS booting from a disk...
[mkarchiso] INFO: Preparing kernel and initramfs for the ISO 9660 file system...
[mkarchiso] INFO: Done!
[mkarchiso] INFO: Done! SYSLINUX set up for BIOS booting from a disk successfully.
[mkarchiso] INFO: Setting up SYSLINUX for BIOS booting from an optical disc...
[mkarchiso] INFO: Done! SYSLINUX set up for BIOS booting from an optical disc successfully.
[mkarchiso] INFO: Setting up systemd-boot for UEFI booting...
[mkarchiso] INFO: Creating FAT image of size: 186368 KiB...
mkfs.fat 4.2 (2021-01-31)
[mkarchiso] INFO: Preparing kernel and initramfs for the FAT file system...
[mkarchiso] INFO: Done!
[mkarchiso] INFO: Done! systemd-boot set up for UEFI booting successfully.
[mkarchiso] INFO: Preparing an /EFI directory for the ISO 9660 file system...
[mkarchiso] INFO: Done!
[mkarchiso] INFO: Cleaning up in pacstrap location...
[mkarchiso] INFO: Done!
[mkarchiso] INFO: Creating SquashFS image, this may take some time...
Parallel mksquashfs: Using 8 processors
Creating 4.0 filesystem on /home/pato/Lynx/OS/lynx-iso/work/iso/arch/x86_64/airootfs.sfs, block size 1048576.
[========================================================- ] 126306/126788  99%
Unrecognised xattr prefix system.posix_acl_default
Unrecognised xattr prefix system.posix_acl_default
Unrecognised xattr prefix system.posix_acl_access
Unrecognised xattr prefix system.posix_acl_default
Unrecognised xattr prefix system.posix_acl_access
[=========================================================-] 126788/126788 100%

Exportable Squashfs 4.0 filesystem, xz compressed, data block size 1048576
	compressed data, compressed metadata, compressed fragments,
	compressed xattrs, compressed ids
	duplicates are removed
Filesystem size 1715976.08 Kbytes (1675.76 Mbytes)
	34.28% of uncompressed filesystem size (5006250.82 Kbytes)
Inode table size 1070976 bytes (1045.88 Kbytes)
	20.90% of uncompressed inode table size (5124151 bytes)
Directory table size 1419586 bytes (1386.31 Kbytes)
	36.48% of uncompressed directory table size (3891704 bytes)
Xattr table size 106 bytes (0.10 Kbytes)
	66.25% of uncompressed xattr table size (160 bytes)
Number of duplicate files found 19129
Number of inodes 154194
Number of files 132714
Number of fragments 2361
Number of symbolic links 9835
Number of device nodes 0
Number of fifo nodes 0
Number of socket nodes 0
Number of directories 11645
Number of hard-links 2553
Number of ids (unique uids + gids) 20
Number of uids 9
	root (0)
	lightdm (970)
	unknown (110)
	pato (1000)
	colord (973)
	nobody (65534)
	ntp (87)
	rpc (32)
	systemd-journal-remote (978)
Number of gids 16
	root (0)
	named (40)
	network (90)
	unknown (110)
	polkitd (102)
	ftp (11)
	locate (21)
	tty (5)
	dbus (81)
	pato (1001)
	colord (973)
	games (50)
	rpc (32)
	systemd-journal-remote (978)
	systemd-coredump (981)
	storage (987)
[mkarchiso] INFO: Creating checksum file for self-test...
[mkarchiso] INFO: Done!
[mkarchiso] INFO: Creating ISO image...
xorriso 1.5.4 : RockRidge filesystem manipulator, libburnia project.

xorriso : NOTE : Environment variable SOURCE_DATE_EPOCH encountered with value 1652212474
Drive current: -outdev 'stdio:/home/pato/lynxos-2022.05.10-x86_64.iso'
Media current: stdio file, overwriteable
Media status : is blank
Media summary: 0 sessions, 0 data blocks, 0 data, 76.6g free
xorriso : WARNING : -volid text does not comply to ISO 9660 / ECMA 119 rules
Added to ISO image: directory '/'='/home/pato/Lynx/OS/lynx-iso/work/iso'
xorriso : UPDATE :     108 files added in 1 seconds
xorriso : UPDATE :     108 files added in 1 seconds
xorriso : NOTE : Copying to System Area: 432 bytes from file '/home/pato/Lynx/OS/lynx-iso/work/iso/syslinux/isohdpfx.bin'
libisofs: NOTE : Automatically adjusted MBR geometry to 1017/117/32
libisofs: NOTE : Aligned image size to cylinder size by 268 blocks
xorriso : UPDATE :  4.38% done
xorriso : UPDATE :  37.98% done
ISO image produced: 1045262 sectors
Written to medium : 1045262 sectors at LBA 0
Writing to 'stdio:/home/pato/lynxos-2022.05.10-x86_64.iso' completed successfully.

[mkarchiso] INFO: Done!
2.0G	/home/pato/lynxos-2022.05.10-x86_64.iso

I omit all the installation content of the packages. This is the error when starting the iso:

https://i.postimg.cc/d3KwwWpf/Captura-d … -16-26.png


Mod Edit - Replaced oversized image with link.
CoC - Pasting pictures and code

Last edited by Slithery (2022-05-10 20:39:07)

Offline

#4 2022-05-12 09:47:19

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 10,069

Re: [SOLVED] Archiso does not generate home folders

Don't see anything wrong, but there's an easy way to verify if the home folder is created :

look at x86_64/airootfs/home under the work directory you gave archiso .
If that doesn't have a folder lynx with the files from skel, something went wrong before running mkarchiso command.

I did notice you made lots of changes to the profile / packages ..
You may want to start with a simple profile like releng or even baseline and just add the user stuff to verify that works as intended.

Last edited by Lone_Wolf (2022-05-12 09:47:45)


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
Did you use the guided installer ? If yes, I can't help you.

(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#5 2022-05-12 12:51:24

PatoJAD
Member
From: Argentina
Registered: 2022-05-10
Posts: 6
Website

Re: [SOLVED] Archiso does not generate home folders

Check the work folder and I could notice that nothing is created inside home, which is why the error is being generated before.

I could try, but I don't really understand why adding packages can cause problems in this regard.

Offline

#6 2022-05-12 15:48:57

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 10,069

Re: [SOLVED] Archiso does not generate home folders

<Added>
NOTE :
My remarks are just meant to show you where things could have gone wrong.
From what I see this will be an awesome installer / live distro once you get everything working.
<end-of-addition>


Your liveiso appears to be booting to a graphical environment and probably autologins to a sddm session .
Among the packages you added are polkit and sudo .

The summary of creating the iso wrt users & groups :

Number of ids (unique uids + gids) 20
Number of uids 9
	root (0)
	lightdm (970)
	unknown (110)
	pato (1000)
	colord (973)
	nobody (65534)
	ntp (87)
	rpc (32)
	systemd-journal-remote (978)
Number of gids 16
	root (0)
	named (40)
	network (90)
	unknown (110)
	polkitd (102)
	ftp (11)
	locate (21)
	tty (5)
	dbus (81)
	pato (1001)
	colord (973)
	games (50)
	rpc (32)
	systemd-journal-remote (978)
	systemd-coredump (981)
	storage (987)

The unknown 110 user and group show  a potential problem.
There's  user 1000 pato and group 1001 pato
The files you added user/group info to don't mention pato at all.
The summary shows no sign of the user lynx which should have id 1000 .

Also

Although I had several inconveniences, I was able to solve the vast majority

All combined that indicates you have made many changes. Even if you documented all of them very precise it will be hard to determine which single one or mix of several caused the problem.

I advise you to start fresh and make limited changes then test them before adding others.

Last edited by Lone_Wolf (2022-05-12 15:54:47)


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
Did you use the guided installer ? If yes, I can't help you.

(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#7 2022-05-12 16:39:43

PatoJAD
Member
From: Argentina
Registered: 2022-05-10
Posts: 6
Website

Re: [SOLVED] Archiso does not generate home folders

First of all I want to thank you very much. Sorry if my comment sounded aggressive, it really wasn't the idea. I was particularly disoriented.

If I start again, even creating the ISO as it comes by default, the user 1000 pato and the group 1001 pato appear, which become my user of the machine that I am creating the ISO.

The problem with the rest of the users and some packages (which were unnecessary) ended up cleaning them. However, when creating the user, the error prevailed. I ended up forking the makearchiso script to modify the user creation part (I started getting screen prints to know what the error was)

In short, the problem is basically that the passwd file must end in an empty line, that way everything is created accordingly.

Thanks again and I learned a lot thanks to you! A big hug and we'll see you again here.

Offline

#8 2022-05-12 22:06:08

qinohe
Member
From: Netherlands
Registered: 2012-06-20
Posts: 1,429

Re: [SOLVED] Archiso does not generate home folders

PatoJAD wrote:

In short, the problem is basically that the passwd file must end in an empty line, that way everything is created accordingly.

No, that is not true, etc/passwd don't need to end in a blank line.
There is no documentation describing that you need to add a blank line(man5 passwd), nor do any of my own passwd files need it!
The passwd file don't leave room for interpretation, you can't add a blank line or add 'anything' for that matter for it will be read!
If you have 'solved' your issue you should now be able to remove that blank line and all should be fine.
If not you still have an issue which I don't understand you are able to solve with a blank line but it ain't normal and indicates a problem.
I don't have time to really dive into this right now I don't know about your level of Linux expertise but I tend to agree with Lone_Wolf you may start with releng and slowly extend;)

Offline

#9 2022-05-13 11:54:18

PatoJAD
Member
From: Argentina
Registered: 2022-05-10
Posts: 6
Website

Re: [SOLVED] Archiso does not generate home folders

As I mentioned, I started it from 0, even before closing, review without adding anything, just add the user. And indeed leaving a blank line at the end (\n) works correctly.

This may be due to the way this file is being parsed. If we look at the makeiso script, we can see at line 357 (I think) that it is looping through the file and for some strange reason it doesn't take the last line (we can see it emitting a message in the while)

  • If we don't add anything, it doesn't even take root

  • when we add a line (with our user) it takes root and ignores it

  • when we add the 3rd line (in this case blank) Just there it takes the user's line.

I can "believe" that this behavior is due to the way the while is done. Could this be a bug? I don't know but that's how it is working today even with a blank releng

Offline

#10 2022-05-13 17:23:59

qinohe
Member
From: Netherlands
Registered: 2012-06-20
Posts: 1,429

Re: [SOLVED] Archiso does not generate home folders

I don't see any of the behavior you describe just tried and the ISO with user without blank line builds and result ISO is completely usable...
Did notice a double F-slash in your profiledef :'["//etc/sudoers.d/g_wheel"]="0:0:400"' should be single OC

Are you using scripts or are you using a custom PKGBUILD?
BTW. I don't believe there is a bug in that while loop it's performing alright here!

edit: we could ask @nl6720 to keep an eye on this thread if he spots anything out of the order, thanks @nl6720;)

Last edited by qinohe (2022-05-13 17:27:36)

Offline

#11 2022-05-13 17:36:16

PatoJAD
Member
From: Argentina
Registered: 2022-05-10
Posts: 6
Website

Re: [SOLVED] Archiso does not generate home folders

I think that due to my level of English I am not explaining myself well. And I apologize for this

Do you understand the tests you perform on the script? I never said that "it works badly" and I did not say that "the ISO was not functional".

I explain better the error:

The ISO was created correctly, it could even be used. The only thing is that it did not create the space (home) of the added user as the documentation informs.

An interesting test would be to add a user (in your case) without leaving the blank line in the file and see if it takes it. If so, you should check again because of the error.

After a lot of testing, I noticed that the script when iterating for some reason didn't take the last line (saying this is a bug is wrong) Just take this as an understanding, add a blank line to the file (like most advanced editors they do nowadays) And I could verify by iterating and modifying the scipt that this case took it.

Taking that into account, I compiled it again with the official script and everything worked 10

I had corrected the 2 lines (//) before, and it is not related to the user creation part.

Offline

#12 2022-05-13 20:02:56

qinohe
Member
From: Netherlands
Registered: 2012-06-20
Posts: 1,429

Re: [SOLVED] Archiso does not generate home folders

Do you understand the tests you perform on the script? I never said that "it works badly" and I did not say that "the ISO was not functional".

That wasn't quite clear to me, it is now.

An interesting test would be to add a user (in your case) without leaving the blank line in the file and see if it takes it. If so, you should check again because of the error.

?Not clear what you mean but I'll explain what I did!
Used a fresh releng, added root and 2 users (no blank line in 'passwd') also created 'etc/{group,gshadow,shadow}'
Added a 'etc/skel' with files and added some packages and a customrepo to the mix.
Tweaked profiledef a little and that's it.
Started building and a usable ISO with 2 home dirs. + root is created.
There were no errors .. well one but meaningless.

edit: I use archiso-git 63.r0.g66d4c7f-1

Last edited by qinohe (2022-05-13 20:04:17)

Offline

Board footer

Powered by FluxBB