Selon François Revol <revol@xxxxxxx>: > Selon Axel Dörfler <axeld@xxxxxxxxxxxxxxxx>: > > > François Revol <revol@xxxxxxx> wrote: > > > Selon Peter Biocini <blueslogic@xxxxxxxxx>: > > > > What are you guys going to do about the /boot/beos folder in R1? > > > > Are > > > > you going to just keep it flat out as /boot/beos, or are you going > > > > to > > > > make /boot/haiku and make some kind of link? I just thought it > > > > would > > > > be interesting to bring up this question. > > > As far as I'm concerned this is not to be changed in the near future. > > > Many installation scripts use that, just like uname should return > > > beos > > > as well. > > > It's not like it's anintentional use of any TM anyway :) > > > It's required for compatibility. > > > > Oh, don't do that: > When I say many I don't speak only for mine :p > > > > > $ finddir > > usage: /bin/finddir [ -v volume ] directory_which > > -v <file> use the specified volume for directory > > constants that are volume-specific. > > <file> can be any file on that volume. > > defaults to the boot volume. > > For a description of recognized directory_which constants, > > see the find_directory(...) documentation in the Be Book. > > > Gosh, I wrote that command myself (find_directory, with a -l > switch to list them), and never noticed about this one =) > Still things to learn it seems. > > Seems we don't even have it in our cvs... I'll modify mine and upload it when I've the occasion. François.