Yet another $HOME problem

	Free Downloads, Community Forum, FAQs and Developer Resources

Make /Tools Your Home | Link to us

Today's posts | Posts since last visit | Most Active Topics

All Forums	Register	Login	Search	Subscriptions	My Profile	Inbox
Tool Warehouse	FAQs	Resources	Help	Member List	Address Book	Logout

Yet another $HOME problem

Logged in as: Guest

Users viewing this topic: none

Printable Version

All Forums >> [SFU / Interix / SUA Technology] >> SFU / Interix - Getting Started >> Yet another $HOME problem

Page: [1]

Message

<< Older Topic Newer Topic >>

Yet another $HOME problem - Mar. 3, '04, 10:16:37 AM

Cthulhu

Posts: 17
Joined: Mar. 3, '04,
Status: offline

Hi, I' m novice SFU user;

I try to use \Documents and settings\%username% as my SFU $HOME directory...

after installation I found:

bash-2.05b$ set
ALLUSERSPROFILE=' H:\Documents and Settings\All Users' 
[...]
HOME=' /dev/fs/H/Documents and Settings/bartosza'

so command cd $HOME produce an error:

bash-2.05b$ cd $HOME
bash: cd: /dev/fs/H/Documents: No such file or directory

I try to map \Documents and settings to \SFU\home:

H:\Documents and Settings\bartosza>linkd f:\SFU\home " h:\Documents and Settings" 

Link created at: f:\SFU\home

but:

bash-2.05b$ cd /home
bash-2.05b$ ls -la
ls: fts_read: No such file or directory

Is there any way to solve this problem?...

best regards
Cth.

Post #: 1

RE: Yet another $HOME problem - Mar. 3, '04, 10:35:40 AM

Rodney

Posts: 3728
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline

It' s best to not use directory names with spaces in it.

You' ll get the best level of portability this way with settings and with scripts.

If you do the command as:

cd " $HOME"

The quotes (" ) will keep the whole path together.

The ' linkd' command is for setting junction points. Whether it' s working correctly or not I don' t know.

I' d suggest trying symbolic links before junction points if you don' t want to quote everything. If you look in the startup scripts for ksh and csh you' ll see that paths are usually in quotes to guard for the possibility of spaces in a pathname.

(in reply to Cthulhu)

Post #: 2

RE: Yet another $HOME problem - Mar. 3, '04, 10:39:58 AM

Cthulhu

Posts: 17
Joined: Mar. 3, '04,
Status: offline

ooops...

my IE crash while posting previous msg. so I guess that this messg. hasn' t come...

thanks Rodney!

Cth.

(in reply to Cthulhu)

Post #: 3

RE: Yet another $HOME problem - Mar. 3, '04, 11:51:05 AM

markfunk

Posts: 673
Joined: Mar. 31, '03,
Status: offline

Interix in SFU3.0 and 3.5 cannot deal with junction points that refer to absolute directory pathnames.
If the junction point is a relative directory pathname, then it works fine.

(in reply to Cthulhu)

Post #: 4

RE: Yet another $HOME problem - Mar. 4, '04, 6:18:37 AM

Cthulhu

Posts: 17
Joined: Mar. 3, '04,
Status: offline

Source and target are placed on different partitions.
I try this:

F:\SFU>linkd home " h:\Documents and Settings" 
Link created at: home

and this:

H:\>linkd f:\SFU\home " Documents and Settings" 
Link created at: f:\SFU\home

but it is still not working...

(in reply to markfunk)

Post #: 5

RE: Yet another $HOME problem - Mar. 4, '04, 6:35:14 AM

Cthulhu

Posts: 17
Joined: Mar. 3, '04,
Status: offline

quote:

I' d suggest trying symbolic links before junction points if you don' t want to quote everything. If you look in the startup scripts for ksh and csh you' ll see that paths are usually in quotes to guard for the possibility of spaces in a pathname

It works! Thanks!

Cth.

(in reply to Rodney)