Re: [sword-devel] location of configuration information

2002-02-13 Thread David White
I think that's a very reasonable way to do it; my suggestion was made because I thought someone said something that implied path names were currently hard-coded or something...but the system you've already got looks fine.. -David. On Wed, 2002-02-13 at 05:18, Troy A. Griffitts wrote: > I don't t

Re: [sword-devel] location of configuration information

2002-02-12 Thread Brook Humphrey
On Tuesday 12 February 2002 16:01, you wrote: > it looks like either the the SWORD_PATH or the /etc/sword.conf changes > should help you out. i don't have a multi-os environment to play much > with that. Yes you can just point the sword.conf to your files on your windows drive. > > Dan Blake wro

Re: [sword-devel] location of configuration information

2002-02-12 Thread mark
it looks like either the the SWORD_PATH or the /etc/sword.conf changes should help you out. i don't have a multi-os environment to play much with that. Dan Blake wrote: > With these 4 methods of specifying the location of data wouldn't it be > possible to share modules in a multi-booting syste

Re: [sword-devel] location of configuration information

2002-02-12 Thread Dan Blake
With these 4 methods of specifying the location of data wouldn't it be possible to share modules in a multi-booting system, as long as at least one of those systems could read the others file system? That way you could install whatever frontend you wanted on each of your operating systems and inst

[sword-devel] location of configuration information

2002-02-12 Thread Troy A. Griffitts
I don't think many people commenting on this subject know how sword data is located. We allow 4 different ways to specify WHERE the data is saved. 1) current working directory 2) $SWORD_PATH environment variable 3) /etc/sword.conf: DataPath= 4) $HOME/.sword/ Sword data can be place anywhere on