1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
|
INSTALLATION INSTRUCTIONS for tkchooser2
Ethan Gold <etgold@cs.columbia.edu> 2/14/00
1. Alternative icon sets
If you'd like to use the alternative icon sets (not default in this
version) you can find all available ones in the alt_icons directory
of the distribution. You can copy them over the icons in the regular
"icons" directory in your install point, or in this local distribution
before proceeding to the steps below, or copy them into your own personal
~/.tkchooser/icons directory to use them for just yourself. You can choose
to use any subset of them - it doesn't matter.
2. IF YOU DO NOT want the options file to live in /etc/:
* Run "make config" to set up the executables library paths.
This will make a backup of the original tkchooser2.tcl script
and modify the original to use the INTALLROOT directory indicated
in the Makefile. (alpr.tcl is subjected to the same operation.)
CONTINUE HERE REGARDLESS:
* su to root if necessary to write to your chosen INSTALLROOT
* run "make install"
This will create a new installation of tkchooser OR overwrite
an existing installation. The Makefile will save a copy of your
current chooser.cfg as chooser.cfg.bak. You may want to take precautions
of your own.
* run "make installdoc" if you want the documentation (such as it is)
installed in the $(DOCDIR) specified in the Makefile
* IF YOU DO NOT want the options file in /etc, remove /etc/chooser.cfg
Sorry, the Makefile isn't that smart. The flexibility not to use
/etc/ is now an artifact.
3. Read the samba notes below if you want to use the SMB layer.
The link to the executable will be made as "tkchooser", not
"tkchooser2" or "tkchooser2.tcl".
The link to the pap wrapper will be named "alpr", not "alpt.tcl".
Additional plugins should be copied to the $(LIBDIR)/plugins/
directory for global installation and icons should be copied to
the $(LIBDIR/icons/ directory, also for global installation.
For personal installation, ${HOME}/.tkchooser may be substituted for
$(LIBDIR) for installing plugins and icons on a per-user basis.
SMB Notes and Caveats:
----------------------
One of the two following must be true:
1. Samba MUST be running for SMB browsing to work because there
is no other way to jumpstart the scanning process. Smbclient uses the
local machine to figure out some basics of the LAN. If you ever
intend to browse your own machine, samba must be running locally.
2. smbmaster must be set to a domain master in the chooser.cfg file.
* Your guest account in your /etc/smb.conf (or wherever) file MUST be
a proper unix username - I recommend "nobody" as this seems to work
for me. If you are not using local lookup (smbmaster instead) this
may be irrelevant. Just be aware that your samba config may not
work out-of-the-box.
* Your security type seems to need to be set to "SHARE" as well.
(again, for non smbmaster installations - read the samba docs)
* Also, the SMB server on your machine MUST return a workgroup and
master pair for your local workgroup or there's nowhere else to look
for network browsing. This means (I THINK) that your "hosts allow = "
line must be set to... something. On my setup it must be "hosts allow
= all", but if you can get it to work using restricted access methods,
more power to ya. You can check this by running:
smbclient -L `hostname`
and seeing if it returns a workgroup list.
If you prefer to use a static master lookup server, uncomment
the indicated line in the chooser.cfg file. This can be done
in your personal
~/.tkchooser/chooser.cfg too, of course.
* If your server thinks that it is the workgroup master even though it
is not, it might return an incomplete workgroup list. I don't know
what to do about this. You'll just have to wait until it figures
things out or force the smb module to use a domain master with the
smbmaster option.
* IMPORTANT CHANGE: only smbmount version 2.0+ is now supported by
tkchooser. No more 2.0 kernels - sorry. If you're desperate, email
me for an old copy of the smbmount plugin which will talk to older
versions of smbmount. Smbmount versions 2.0.5 and 2.0.6 are both
supported now. Set the indicated config line in chooser.cfg
appropriately.
* Additionally, if you want to mount volumes as a normal (non-root)
user, smbmount (or smbmnt) and smbumount MUST be setuid AND you must
have write permissions on the target directory. I keep a directory in
my home directory for mounting remote volumes. PLEASE PLEASE PLEASE
don't install tkchooser as suid root to get around this, because
tkchooser will execute any arbitrary tcl code in any user's
~/.tkchooser/chooser.cfg file.
Appletalk Notes and Caveats:
----------------------------
The default configuration assumes you have netatalk
installed. If you don't, be sure to disable it and/or
choose a different default protocol.
Broadcast for netatalk doesn't exist.
update - it does! hopefully someone will turn it into
something that can be easily used with tkchooser.
Enscript Notes and Caveats:
---------------------------
(note - you may want to use the separately downloadable version of
Enscriptconfig at this point - the two may not be in sync yet, but
I think they are... - nice project managment, eh?)
In order to make GUI configuration of enscriptrc file as
useful as possible, the enscript plugin relies on a set of
structured comments inside the .enscriptrc (or enscript.cfg)
files which give it additional information. This approach was
used because enscript also has to parse these files. I MAY
move the enscript plugin's configuration into a seperate file
at some point and just write out straight enscriptrc's, but
didn't want to maintain both files/mappings at the time of this
writing. One advantage of this is that the plugin SHOULD be able
to read normal enscript files lacking the comment structure - the
downside is that help strings won't be defined, option lists
won't be built, and options won't be categorized.
IF you want to use the enhanced options for the enscript plugin
or standalone Enscript configurator you should apply the supplied
patch to the file util.c in the enscript-1.6.1 distribution. This
will allow enscript to read a slew of it's normally commandline-only
options from a config file as well. This means that the enscript
configurator can set them in the GUI. Once the patched enscript
is installed, open the newopts.cfg file from the tkchooser2
distribution and copy the lines into the etc/enscript.cfg file
provided with tkchooser2. Then installed tkchooser2. Or you can
just copy the newopts.cfg line directly into your already installed
/usr/local/tkchooser/etc/enscript.cfg (or wherever). Placement in
the file is not critical, but if you don't put the config lines in the
recommended sections they might show up in unintuitive places.
Your call. If you add the newopts.cfg lines without installing
the patched enscript then enscript will die when reading Enscriptconfig
or enscript plugin generated .enscriptrc files because it won't
recognize the config directives.
That is all.
|
