You can get many system-paths via the find_directory() function, which
kind of
lets the need for generic/static names disappear... (And allows for
customization
through third parties, if the app is well-written (which means that it
actually uses
this system calls).)
(http://www.beunited.org/bebook/The%20Storage%20Kit/misc.html#Directories)
cya, Daniel Furrer
John Tegen wrote:
$0.02:
If it's going to change, how about keeping it generic so if the name changes again or third party uses it for alternate reasons.
For example: /boot/os
John
-----Original Message----- From: openbeos-bounce@xxxxxxxxxxxxx [mailto:openbeos-bounce@xxxxxxxxxxxxx]On Behalf Of Peter Biocini Sent: Wednesday, July 07, 2004 6:38 PM To: openbeos@xxxxxxxxxxxxx Subject: [openbeos] /boot/haiku...?
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.
Good luck, Haiku team.