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
|
$NetBSD: README.Interix,v 1.7 2004/04/21 20:34:16 tv Exp $
Please read the general README file as well.
NOTE: Currently, Interix support in pkgsrc is unstable, so errors and
problems are expected. Known caveats are listed at the bottom of this
document.
Interix is a POSIX compatible subsystem for the Windows NT kernel, providing
a Unix-like environment with a tighter kernel integration than available
with Cygwin. It is part of the Windows Services for Unix package, available
for Windows 2000, XP, and 2003. SFU can be downloaded from:
http://www.microsoft.com/windows/sfu/
Services for Unix 3.5 (current as of this writing) has been tested. 3.0 may
work, but is not officially supported.
At an absolute minimum, the following packages must be installed from the
Windows Services for Unix 3.5 distribution in order to use bootstrap-pkgsrc:
Utilities -> Base Utilities
Interix GNU Components -> (all)
Remote Connectivity
Interix SDK
The Remote Connectivity subcomponent, Windows Remote Shell Service, does not
need to be installed, but Remote Connectivity itself should be installed in
order to have a working inetd.
Last but not least, if the installer prompts whether to change the default
POSIX behavior to case-sensitive, answer Yes. If the filename handling
remains as case-insensitive, then "bootstrap" will require the
"--ignore-case-check" option.
=====
KNOWN CAVEATS
* The package imanager (either the pkgsrc "su" user, or the user
running "pkg_add") must be a member of the local Administrators
group. Such a user must also be used to run the bootstrap. This is
slightly relaxed from the normal pkgsrc requirement of "root".
* The package manager should use a umask of 002. "make install" will
automatically complain if this is not the case. This ensures that
directories written in /var/db/pkg are Administrators-group writeable.
* It is not necessary, in general, to have a "root" user on the Windows
system; any member of the local Administrators group will suffice.
However, some packages currently assume that the user named "root" is
the privileged user (these will eventually be fixed). To accommodate
these, you may create such a user; make sure it is in the local group
Administrators.
* The popular Interix binary packages from http://www.interopsystems.com/
use an older version of pkgsrc's pkg_* tools and occupy the /var/db/pkg
directory (though the packages install to /usr/local). If you want to
have both kinds of packages installed in the system, supply the option
"--pkgdbdir=DIRECTORY" to "bootstrap".
* On Windows under Interix, the "root" user is actually named
"Administrator". This may require some modification to pkgsrc to
introduce a parameterized root user for installation purposes.
(Likewise, the bootstrap script sets the root group to
"+Administrators".)
|
