> Regardless, the check I added should be there as it was an uncovered
> error condition.
... and I just realised I deleted your patch. D'oh!
> >BTW Jim, the stuff you're working on sounds really cool. Thanks for
> >taking it on!
>
> Apparently I am a glutton for punishment. Expect more bug
At 17:44 -0800 12/7/00, Mike Smith wrote:
>This is probably an OK workaround. I think that there's something
>fundamentally wrong with the 'net' filesystems getting called for an open
>against a disk device, but I've paged out all the libstand state and I
>can't get it back fast enough to comment
This is probably an OK workaround. I think that there's something
fundamentally wrong with the 'net' filesystems getting called for an open
against a disk device, but I've paged out all the libstand state and I
can't get it back fast enough to comment more usefully. 8(
BTW Jim, the stuff you
At 16:02 -0800 12/7/00, Jim Browne wrote:
>When TFTP tries to open a file, it is expecting struct open_file
>member f_devdata to be a pointer to a socket number. When currdev
>is "pxe", that assumption is correct. When currdev is "disk*", that
>assumption is incorrect. Specifically, tftp.c d
At 00:13 -0800 12/7/00, Mike Smith wrote:
> > The option works wonderfully for /boot/pxeboot. But it turns out
> > that the normal /boot/loader, when compiled with the above
> > option, will crash horribly whenever it tries to open() a file and
> > can't find it in the UFS filesys
:I've already looked at this, investigating a problem reported in
:connection with PR 21559. I'll probably sort it out in the next day
:or two, unless someone else gets there first.
:
:--
:Robert Nordier
:
:[EMAIL PROTECTED]
:[EMAIL PROTECTED]
That'd be great. When you have a patch, if you
Matt Dillon wrote:
> I sure would appreciate it if one of the bootstrap gurus could take
> a look at what happens when the tftp open routine is called from a
> normal disk-based /boot/loader!
I've already looked at this, investigating a problem reported in
connection with PR 2155
> Ah ha! I think I found the culprit, but I'm not sure exactly where
> in the tftp code the problem is occuring.
>
> I have been setting LOADER_TFTP_SUPPORT in /etc/make.conf so my pxeboot
> file uses tftp to get the kernel rather then NFS (since NFS appears to
> only be able
Ah ha! I think I found the culprit, but I'm not sure exactly where
in the tftp code the problem is occuring.
I have been setting LOADER_TFTP_SUPPORT in /etc/make.conf so my pxeboot
file uses tftp to get the kernel rather then NFS (since NFS appears to
only be able to get [roo
9 matches
Mail list logo
