Page 3 of 3
Re: IFL log file
Posted: Fri Dec 13, 2024 3:43 am
by tbifan39
I think it is working!
I booted it twice and the partition mounted both times; no problem. The IFL window no longer comes up automatically, but I can click the IFL icon at the top to start it...No big deal.
i created iflscript with runall in it. I put the file the folder with makedisk,exe, makedisk,cfg, etc.
I added the following line to makedisk.cfg
ADD3=iflscript,>/tbu/utility|initrmfs
I will test it several times and make an image this weekend and report back.
Thank you for spending so much time with me to find a solution. I learned a lot during this process.
You may want to consider adding this information to the manual and FAQ. This may help others who are using multiboot programs.
Re: IFL log file
Posted: Fri Dec 13, 2024 3:46 am
by tbifan39
P.S. What part of the registry is the stored information?
Re: IFL log file
Posted: Fri Dec 13, 2024 8:57 am
by TeraByte Support(PP)
IFL doesn't run automatically on startup when scripts are run. To make IFL run after mounting, edit the iflfind (or whatever you named it) script and insert the following two lines after the "mount" command (before the "break" command).
For example:
(Showing an entire example script here, but you would only be adding those two lines and not making any other changes to your script.)
Code: Select all
#! /bin/bash
for f in sd{a..z}
do
p=2
echo Checking /dev/$f$p...
blkid /dev/$f$p | grep "LABEL=\"IFL_4" > /dev/null
if [ "$?" = "0" ]; then
echo IFL partition found: /dev/$f$p
mkdir /tbu/iflmedia
mount /dev/$f$p /tbu/iflmedia
nohup /tbu/imagel &
disown $!
break
fi
done
The MakeDisk settings are normally located at "HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\TeraByte Unlimited\MakeDisk" but they're not editable.
Re: IFL log file
Posted: Fri Dec 13, 2024 2:06 pm
by tbifan39
Almost there...
nohup /tbu/imagel &
disown $!
This cause an error - No file of directory. I removed nohup
/tbu/imagel &
disown $!
This load the IFL window. Is this okay.? Do I need nohup?
Re: IFL log file
Posted: Fri Dec 13, 2024 10:49 pm
by TeraByte Support(PP)
That should still work okay.
Re: IFL log file
Posted: Sat Dec 14, 2024 12:41 am
by tbifan39
Why doesn't nohup work? What can I do to get it to work?
Re: IFL log file
Posted: Sat Dec 14, 2024 1:09 am
by TeraByte Support(PP)
Not sure. It worked for me. The main thing was to separate imagel from the terminal so it remains running after the terminal running the script closes, which both nohup and disown can do. So, if IFL is remaining running (which you said it is), you should be good.
Re: IFL log file
Posted: Sat Dec 14, 2024 2:11 am
by tbifan39
Where is nohup command located? The error message makes me think that nohup is not found
Re: IFL log file
Posted: Sat Dec 14, 2024 4:29 am
by TeraByte Support(PP)
It's a function in BusyBox. The link is at /usr/bin/nohup and runs /bin/busybox.
Re: IFL log file
Posted: Sat Dec 14, 2024 8:08 am
by tbifan39
Okay. I used midnight commander to search for nohup and it didn't find it. It must not be there for some reason.
No biggie... I can click on the IFL icon at the top.
I'm happy you figured out how to mount the partition automatically. That was what I was mainly needing.
I did a back up and it worked and saved the IFL.log also.
Thank you so much for your help!