I am one step further. I installed dosfstools via zypper and ran the RBE
install script again. It showed the following output:
required lower permissions for creating DOS filessystems.
'/usr/sbin/mkfs.msdos' -> '/home/rbe/bin/make-dosfs'
required lower permissions for labeling DOS filessystems.
'/usr/sbin/fatlabel' -> '/home/rbe/bin/fatlabel'
So, I finally know where this make-dosfs comes from :-) Perhaps you can
add *dosfstools *and *unzip *to the package dependencies in the install
script? These are the two I had to install manually after setting up the
container.
Sadly QEMU times out. Probably because it is running without KVM. I have
not found yet a solution to enable it for the container. This takes
longer than I wanted to, so I will dump the container and set up a
proper VM...
BTW your scripts look pretty good, and apart from the trouble caused by
myself this all seems to run very smooth...
Bernd
On 12.02.2024 16:03, Jerome Shidel via Freedos-devel wrote:
Hi Bernd,
So…
I booted the (Windows 10) machine that I use for creating FreeDOS
builds. (Host OS should not be relevant.)
There was an update to VirtualBox. So, I installed that and the
related new extension pack.
/( Following the instructions in the RBE’s Wiki. Except for CPU’s, I
went with 2 cores for a reduced build time. )/
I created a new VM for the RBE.
I download a fresh copy of openSUSE 15.5 Leap DVD install for x86.
/(newest version)/
/( I had a little trouble downloading openSUSE. My home internet was
recently upgraded to a 1Gb connection. With the standard mirror, I
would download for a few seconds at very fast rate. Then just stop at
some point. After switching to a different mirror, it downloaded
without problem. It makes me wonder if the first server was having
issues with the much faster rate. Possibly, it considered it a DDOS.
But, it could just be Windows. After all, I was having issues pulling
up GitLab on that machine and no issues on the Mac sitting next to it.
Then again, maybe since the new router fully supports IPv6, IDK. Only
a couple days since the upgrade and this was the only time I’ve had an
issue. Time will tell. )/
I installed openSUSE.
/(Note: I need to update wiki. Earlier versions of the openSUSE
defaulted to activating/*online repositories*/. Now you have to
choose. They need to be enabled for the install script to fetch
additional required packages. Otherwise, I used my normal location
settings and such. Finally (per wiki instructions), I selected the
system role as server.)/
After the install of openSUSE, I continued to the /Install Builder
Tools/ page in the wiki.
Used zypper to install git: *git sudo zypper install git*
Cloned RBE project: *git clone https://gitlab.com/FreeDOS/OS/builder.git*
Moved to the Builder directory: *cd builder*
Ran the install script for the RBE: *sudo ./install*
Rebooted. (End of wiki)
Logged in as normal user and changed dir to the *builder* dir.
Ran: *make*
/(waited a while watching build process)/
Result, Successful Build of a “Standard Release”
Ran: *make clean*
Edited custom.cfg to:
*unstable=yes*
*verbose=yes*
Ran: *make*
/(waited a while watching build process)/
/
/
Result, Build failed from unknown issue while creating bootable
floppy. However, I never use verbose mode in the normal VM’s that I
use to build the FreeDOS release media. It is possible I broke
something there a while back and didn’t notice. Or, changes to
openSUSE broke something there. Or, possible there is some issue with
one of the packages “unstable” branch”. So, I simply disabled verbose
output and tried again.
Ran: *make clean*
Edited custom.cfg and re-disabled verbose output.
Ran: *make*
/(waited a while watching build process)/
/
/
Result, Successful Build of a “Interim Build”
In conclusion, there is an unrelated issue regarding “verbose mode”
during release building process. This is not related to the error you
encountered. The error you received would most likely have been cause
by the RBE not getting installed correctly. This could be the result
of a bad download of the openSUSE operating system. Or possibly,
something failed during the RBE installation script and the error was
not caught by that script.
You can try to run the install script for the RBE again. Generally, it
checks the state of the system and only changes things when needed.
Primarily, that is because when I make major changes to the RBE, the
install script can just be run again to “patch up” any new changes
that are required.
If that does not remedy the problem, I would trash the VM and start
from the beginning. It could have been a corrupt download of openSUSE.
Left me know if this helped and fixes the build issue you had.
Thanks,
Jerome
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
