Official NuTyX forums
Documentation => ISOs, initrd, initramfs => Topic started by: oyim on Mon Nov 26 06:22:09 2018
-
Hi thierry!
I finally got around to trying the "build your own customized .iso". Everything went great except for one issue. Before I generated the squashfs files, I looked at the containing folder. I noticed there was no Home folder that had been generated. I started to copy mine to it, but decided to go ahead without it. Of course, I got an error that no Home folder was present. It still produced the .iso, so I'm excited about that...will be a while before I can try it live.
My question is...
Is the lack of a Home folder intentional so that the user can add their own customization before generating the squashfs files and .iso?
Thanks again for such a great system! :D
-
Is the lack of a Home folder intentional so that the user can add their own customization before generating the squashfs files and .iso?
If you create a user while you are in the chroot building your own customized NuTyX and you choose then to create a new user with the command:
setup-nutyx -cu
A /home/<yournewuser> folder will be created. At the generation of the squashfs files, it will be included, and onces you launch the live (for example) no new user will be created. Same if you install it, it will have your <yournewuser> configured and valid.
And this feature works for other configuration parts:
network: setup-nutyx -cn
language(locale): setup-nutyx -cl
clock: setup-nutyx -cc
keyboard: setup-nutyx -ck
So yes the lack of a Home folder is intentional in a normal ISO generation. That's actually how setup-nutyx knows if they is a user or not already configured
Do not hesitate to ask me if not clear
Thanks again for such a great system!
Thanks a lot for your nices videos and feedbacks
-
HOORAY!
Despite not including a Home folder during the build, when I tried the "Live" option, it asked me to create a user before booting into the live system, and...it had a Home folder! Amazing! :D
Thank you for the tips! I will play around with it some more and see what happens.
Is it possible to use the same build to customize it more, or do I need to start a new build? Either way is fine with me...yesterday was mainly just a learning experience. ;)
Thank you!
-
Is it possible to use the same build to customize it more?
Absolutly, that's what I'm doing all the time when I update my custom ISO.
Go directy to: http://nutyx.org/en/generate-iso#9 and go on, you can skip http://nutyx.org/en/generate-iso#10 if you didn't update the kernel. Yes even update your custome ISO with newer version will works
-
Worked like a charm! :)
Thank you for allowing others to do this so easily.
-
Hi Thierry!
The .iso is coming along nicely! ;)
I have a couple of questions...please know that this was done in Virtualbox; I haven't tried installing it on actual hardware yet.
1. When using the "Install NuTyX on your machine" option (from my menu) in the live environment, I receive the following error...
Failed to execute child process "evte" (No such file or directory)
However, if I run the executable from the terminal (in the live session)...
sudo /root/bin/setup-nutyx
...the installer works great! I'm also able to install it from the Install option in the Grub screen.
Just wondering if I've done something wrong or left something out that may be causing that error. It's not a problem to me...just curious. ;)
2. The installer didn't allow me to create a new user during installation. Again, this is something that isn't a big deal...just wondering if I did something wrong or left out something during the build process?
3. Is it possible to build a 32bit version on my 64bit computer by specifying the architecture, or do I need to be on a 32bit computer?
Thank you Thierry...your work is amazing!
-
1. When using the "Install NuTyX on your machine" option (from my menu) in the live environment, I receive the following error...
Failed to execute child process "evte" (No such file or directory)
However, if I run the executable from the terminal (in the live session)...
sudo /root/bin/setup-nutyx
...the installer works great! I'm also able to install it from the Install option in the Grub screen.
Just wondering if I've done something wrong or left something out that may be causing that error. It's not a problem to me...just curious. ;)
Okay...I was given some advice, and I'm adding the packages vte and vte3 to see if that will help. :)
-
When using the "Install NuTyX on your machine" option (from my menu) in the live environment, I receive the following error...
I believe evte is the default terminal configured in your DE. This configuration is If I'm right done by the xdg-utils package.
So you have 3 possibilities:
- you have to build the request terminal
- modify your config
- make a link to let run xterm instead of evte
ln -sv xterm /usr/bin/evte
The installer didn't allow me to create a new user during installation.
Normal behavior, the installer found out that alreaydy one user exist so will not ask automaticaly for a new one.
To create a new one after install, runs:
sudo setup-nutyx -cu
Is it possible to build a 32bit version on my 64bit computer by specifying the architecture?
Yes, as explain here (https://nutyx.org/en/downloads#5l):
run the script install-nutyx by specifying the "ARCH" variable:
ARCH=i686 install-nutyx
-
Thank you Thierry. My apologies for not being more studious.
I believe evte is the default terminal configured in your DE. This configuration is If I'm right done by the xdg-utils package.
So you have 3 possibilities:
- you have to build the request terminal
- modify your config
- make a link to let run xterm instead of evte
Ahhh...thank you. To be honest, I've never even heard of the evte terminal. ;D
Normal behavior, the installer found out that alreaydy one user exist so will not ask automaticaly for a new one.
I thought that was probably the situation. No problem and easily taken care of! Thank you. :)
Yes, as explain here:
run the script install-nutyx by specifying the "ARCH" variable:
Thank you. As I said at the beginning of this post...my apologies for not being more studious.
Your help has been much appreciated, and thank you for taking the time to answer.
-
You're absolutly welcome, I appreciate so much such a feedbacks.
-
Thierry,
I've tried linking both xterm and lxterminal to evte, but I still get errors when trying to open the installer in the live session...the error says Failed to execute child process "x-terminal-emulator" (No such file or directory).
I'm trying to keep from having to build evte if possible. :P
Also...I have looked through all of the folders and files in the build environment, but I can't seem to find which configuration to change in order to have the installer open in the live session with another terminal other than evte. Can you possibly tell me where to look?
However...I am able to run the installer in the live environment by opening either lxterminal or xterm and issuing the command...
sudo /root/bin/setup-nutyx
Sorry...I have tried to figure this out on my own...but I've had no luck. ;D
-
I will figure out and come back to you as soon I have a solution.
Thanks again for your nices videos you post on YT
Regards,
Thierry
-
Found it:
Check your /usr/bin/obamenu file, line 13
terminal_string = "evte -e" # your favourites terminal exec string
I guess you know what you need to put there :D
-
Found it:
Check your /usr/bin/obamenu file, line 13
terminal_string = "evte -e" # your favourites terminal exec string
I guess you know what you need to put there :D
Well that's embarrassing! ::) What an idiot I must be! :o
All this time, I thought it was a configuration file somewhere in one of the folders produced by the build itself. I looked at every file...EVERY FILE...even the ones that were obviously not going to have what I was looking for! ;D
...and it was in my menu configuration! ::) What's bad is, I know to change the default terminal in obmenu-generator, it never occurred to me to change it in my current menu. I'm no longer using obamenu, so I'll look over the python script for pmenu.
Thank you Thierry...and I'm so sorry that I caused you extra work. Like I said in several of my videos...I'm such an idiot...and this just proved it! ;D :o ??? :-[ ;D
...gonna have to make a video about my idiocy on this for sure... ;D
-
Don't be sorry, It's a pleasure to help you really. I learn a lot by looking at your videos
-
One last issue that I haven't been able to solve...
When testing the .iso that I've made on actual hardware, I'm able to connect to my network on the computer (that I used to build the .iso on) using networkmanager and nm-applet.
However, I'm unable to connect on any other computers using either ethernet or wireless. This happens in both the live environment and an actual installation.
I've tried building the .iso with networkmanager, wicd, and I've also tried building the .iso without a network manager. If I try to set up the network connection manually, I'm still unable to connect with either ethernet or wireless.
I didn't copy any of my personal network configurations to the .iso.
I'm so sorry to ask about this, but I have looked over the handbook and any other NuTYX information that I've been able to think of, but I can't seem to find a solution.
What have I done wrong this time? ;D
-
Normaly this problem occurs when you did copy your /etc folder from your host NuTyX to your chroot NuTyX. If that the case, make shure to NOT copy the udev post-configurations files as they get modify (by udev) after a boot
-
Normaly this problem occurs when you did copy your /etc folder from your host NuTyX to your chroot NuTyX. If that the case, make shure to NOT copy the udev post-configurations files as they get modify (by udev) after a boot
Thanks Thierry. I haven't copied my /etc folder.
I have made some progress...
Before posting about the network issue, I had built a new .iso again without including NetworkManager or Wicd. I finally was able to test it on other computers today. This latest .iso will connect during setup in the live session using Ethernet but not wireless. Still...that made my day. :)
-
Thierry,
Would any other locales need to be added to the following to ensure that all are available?
for i in da de en es fi fr it nl ru sv tr
do
for j in dialog util-linux sudo
do
cards install $j.$i
done
done
Thank you.
-
In my solution, I assume the host machine (the machine you install the chroot on it) is a NuTyX of course:
First we check what's are the available locale todays for thoses 3 packages by looking what's in group:
cards info -b dialog|grep ^Group
Group : tr sv ru pt pl nl it fr fi es de da ar man dialog devel
cards info -b sudo|grep ^Group
Group : zh_CN es nn sv ru nl devel fr pl man ja fi tr it de doc da sudo
cards info -b util-linux|grep ^Group
Group : fi nl fr it pl ja sv ru da de doc zh_CN tr man es devel util-linux
Ok now we will take the one which have the most I guess it's sudo (whithout man devel and doc unless you want them) package:
for i in zh_CN es nn sv ru nl fr pl ja fi tr it de da
do
for j in dialog util-linux sudo
do
cards install $j.$i
done
done
Ok Now BEFORE you install all your customised packages, you exit and add all thoses locale in the cards.conf file of your ISO so that when you do the custom installation, all those locales are going to be installed
exit
for i in zh_CN es nn sv ru nl fr pl ja fi tr it de da
do
echo "locale $i" >> $LFS/etc/cards.conf
done
And by the way if you want any of the other groups (devel doc man) add them as well but don't be surprise by the size of your ISO.
If you did add the devel group, make shure to install cards.devel package so that peoples can directly compile they own packages.
So let's go back into our customised NuTyX:
install-nutyx -ec
get cards.devel
Now you can go on with all your customisations
-
Thank you Thierry. I appreciate your time more than I can express. I hope that you had a Merry Christmas!
-
Merry Chrismas to you and happy new year. Wish you a lot of more fun with your NuTyX installations