I was thinking that, as a part of distinguishing Haiku from the original BeOS (and possibly for the same trademark reasons that necessitated the name change in the first place, but I’m not sure if it applies), we should consider changing the directory and filenames that specifically refer to BeOS. Most notably, /boot/beos. It could be moved to /boot/haiku, I’d think, with a symlink to /boot/beos remaining in place as a legacy feature for applications that depend on /boot/beos being where it is. Is there any technical problem preventing this from being an adequate solution?
Benjamin Mullins wrote:
I was thinking that, as a part of distinguishing Haiku from the original BeOS (and possibly for the same trademark reasons that necessitated the name change in the first place, but I'm not sure if it applies), we should consider changing the directory and filenames that specifically refer to BeOS. Most notably, /boot/beos. It could be moved to /boot/haiku, I'd think, with a symlink to /boot/beos remaining in place as a legacy feature for applications that depend on /boot/beos being where it is. Is there any technical problem preventing this from being an adequate solution?
I think something like that has already taken place (based on my limited booting of Haiku so far)
umccullough wrote:
I think something like that has already taken place (based on my limited booting of Haiku so far)
Not as far as I’m aware. In the latest VM images (from http://www.schmidp.com/index.php?option=com_files&path=/haiku/images/), it’s still /boot/beos. The closest thing is /Haiku, which is a symlink to /boot.
Benjamin Mullins wrote:
umccullough wrote:I think something like that has already taken place (based on my limited booting of Haiku so far)Not as far as I’m aware. In the latest VM images (from http://www.schmidp.com/index.php?option=com_files&path=/haiku/images/), it’s still /boot/beos. The closest thing is /Haiku, which is a symlink to /boot.
you are probably right - I do remember something like /Haiku - and that is probably what I was thinking of from the few times i’ve actually booted haiku successfully.
I think that currently the paths are being maintained so that applications that have those paths hardcoded will still work. I would think that for R1 we would probably have the old paths along with links for the new paths (or the other way around). After R1, we would drop the old paths. Anyway, it really isn’t up to me, but I vaguely remember hearing something about keeping the old paths for the reason I mentioned before.