[syslinux] gpxelinux and cramfs

[Michael L Martin]

You are, of course, correct. My limited knowledge of PHP is showing.

I made two changes to my php.ini file based on what I found in the
one running in our data center, one of which is upload_max_filesize.
The other, which turns out to be the real culprit, was memory_limit.
This value was set to 8M. Changing it to 128M is what really solved
the problem.

Thanks, Jeff, for pointing out this mistake on my part. I hope that this
thread can be of help to others in the future, and it's important to
have all the facts actually factual.

-Michael


Jeff Sadowski wrote:
> On Wed, Apr 22, 2009 at 10:37 AM, Michael L Martin <mmartin at fuzzcat.net> wrote:
>   
>> Mystery solved.
>>
>> PHP was the culprit. upload_max_filesize was still set to the default
>> of 2M. This was chopping my fsimage off during the transfer. All is
>> well now.
>>
>>     
>
> I thought upload_max_filesize was for uploading files? IE: sending
> files to the apache server not downloading. I remember setting this
> for a person to upload files to my server. That should not effect
> people pulling the image from the server. If that did anything for
> downloads it would be highly suspicious. Download file sizes are by
> default much bigger.
>
>   
>> Thanks, Peter - you gave me the hints I needed as to where and how
>> to look for this erro.
>>
>> -Michael
>>
>>
>>
>> Michael L Martin wrote:
>>     
>>> H. Peter Anvin wrote:
>>>       
>>>> Michael L Martin wrote:
>>>>
>>>>         
>>>>> I assume that you mean that fsimage looks corrupt, which was my
>>>>> first assumption. However, it boots fine from the USB stick, and the
>>>>> two images are identical (at least diff thinks so).
>>>>>
>>>>>           
>>>> I mean it doesn't show up correctly in memory.
>>>>
>>>>         
>>> Yes, no doubt. If a load it across tftp (using atftpd) it seems fine. When
>>> I load it across http (using apache) it fails. My current theory, subject
>>> to change without notice, is that something's not right in my Apache
>>> configuration.
>>>
>>>       
>>>>> For what it's worth, we want to use HTTP to serve this stuff up, and
>>>>> it's my understanding that plain pxelinux.0 doesn't grok http. Just
>>>>> for grins, though, I'll give it a try.
>>>>>
>>>>>           
>>>> This is a debugging exercise.
>>>>
>>>>    -hpa
>>>>
>>>>
>>>>         
>>> _______________________________________________
>>> Syslinux mailing list
>>> Submissions to Syslinux at zytor.com
>>> Unsubscribe or set options at:
>>> http://www.zytor.com/mailman/listinfo/syslinux
>>> Please do not send private replies to mailing list traffic.
>>>
>>>       
>> _______________________________________________
>> Syslinux mailing list
>> Submissions to Syslinux at zytor.com
>> Unsubscribe or set options at:
>> http://www.zytor.com/mailman/listinfo/syslinux
>> Please do not send private replies to mailing list traffic.
>>
>>
>>     
>
> _______________________________________________
> Syslinux mailing list
> Submissions to Syslinux at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
> Please do not send private replies to mailing list traffic.
>
>