Displaying 4 results from an estimated 4 matches for "2nd_path".
2013 Jun 12
3
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
On Wed, 12 Jun, at 05:01:13PM, Ady wrote:
> Perhaps the following is just a crazy idea... How about no
> path-separator in the cfg file, and instead use multiple PATH
> directives for each path in the cfg file?
>
> Instead of the previous:
> PATH first_path:2nd_path
>
> now just use:
> PATH first_path
> PATH 2nd_path
You can actually do this already - multiple PATH directives are
concatenated. But I think there's still value in allowing users to
specify multiple entries with one PATH.
--
Matt Fleming, Intel Open Source Technology Center
2013 Jun 12
0
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
...; which was complete madness.
>
> Matt Fleming, Intel Open Source Technology Center
Perhaps the following is just a crazy idea... How about no
path-separator in the cfg file, and instead use multiple PATH
directives for each path in the cfg file?
Instead of the previous:
PATH first_path:2nd_path
now just use:
PATH first_path
PATH 2nd_path
If this syntax would be possible (while multiple paths in one line
would be "unsupported"), then each PATH directive would accept only
one path in the cfg file. Each PATH directive would add more paths,
in the same order they appear in the...
2013 Jun 12
0
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
...2 Jun, at 05:01:13PM, Ady wrote:
> > Perhaps the following is just a crazy idea... How about no
> > path-separator in the cfg file, and instead use multiple PATH
> > directives for each path in the cfg file?
> >
> > Instead of the previous:
> > PATH first_path:2nd_path
> >
> > now just use:
> > PATH first_path
> > PATH 2nd_path
>
> You can actually do this already - multiple PATH directives are
> concatenated. But I think there's still value in allowing users to
> specify multiple entries with one PATH.
Right, so assumin...
2013 Jun 12
5
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
On Tue, 11 Jun, at 03:54:21AM, H. Peter Anvin wrote:
> On 06/11/2013 01:03 AM, Matt Fleming wrote:
> > On Mon, 10 Jun, at 07:57:50AM, H. Peter Anvin wrote:
> >> Either that or make the path a list rather than a string, using the
> >> normal word separators when entered on the command line, a bit like the
> >> (t)csh does. That is a bigger change but is probably