http://www.murga.org/%7Epuppy/viewtopic ... 0958#30958
Several topic concerning the Gujin bootloader moved here.
http://gujin.org
That is the first parameter passed on the command line which is thekethd wrote:I think that 1.2 truncates a CONFIG.SYS line shorter than 0.9 does, under FreeDOS under the same conditions. So this would have to be the fault of Gujin? I suggest that Gujin always by default echo the actual commandline it is going to fully process.
name of the kernel file with its path (to know where is the file and so
deduce the root filesystem). You should still have 232 chars including
this filename with version 1.2 - IMHO it should be enough.
Gujin cannot know if something else is truncating the line (like SHELL=)
and so cannot display a warning.
There is a compilation switch to echo the command line, it is:
PRINT_COMMAND_LINE - but you have to regenerate tiny.exe
from source.
It is not enabled because some Linux version were already displaying
it - and usually still do it if you add the "debug" parameter to the
command line (and maybe remove "quiet"), I can send you a
modified version of tiny.exe tomorrow if you just want that, but
just try "debug" first.
OK, I'll have a look at it for v1.3, along with all the other stuff.kethd wrote:linld can accept up to about 256 characters (or eight parameters) to pass to the kernel/init, in a file. This is extremely useful and helpful in Puppy, for potentially troubleshooting rc.sysinit. (Because rc.sysinit is extremely difficult to edit, it is desireable to make it highly flexible based on parameters passed by the bootloader.) Please add this feature, in a way compatible with linld.
Something like "tiny.exe vmlinux initrd.img.gz @cmdfile" ?
I can have a look at a switch to not decompress the initrd in the setupkethd wrote:I only partially understand the issues with decompressed image.gz, but I am quite sure other DOS bootloaders are over-all more efficient, regardless of who is doing the job when. More to the point, I know for sure that this computer is capable of decompressing image.gz about five times faster than Gujin is actually doing it; I'd be happy to try to work with you to speed it up. (Esp since so far in my experiments only Gujin can bootload a standard Puppy in 32MB.) It seems like maybe the simplest quick fix would be to allow a switch to Gujin to bypass the uncompression that you do and have Gujin just pass the uncompressed file like other bootloaders do? (To test this, be sure to use a computer that is only a Pentium-I.)
screen, but I do not like it because people will complain that I do not
load correctly their initrd (for instance from their CompactFlash), and
that has to be my fault because they have formated their CompactFlash
using Windows and Windows did not find any erroneous sector, and
their CompactFlash is completely new and was extremely expensive.
Those still contain erroneous sectors.
The time Gujin spend is the time to read the file and then decompress
it - it has to be compared to a kernel doing the two steps and should
not be that different - but maybe to calculate the CRC32 (optimised
for size and not for speed).
Done.kethd wrote:Thank you for writing so much detail; I will try to study further.
(We should move this all onto a Gujin thread in Puppy forum, but I am not sure how to do that -- you could start one, and just link to it from here?)