Annotation of pkgsrc/bootstrap/README.Interix, Revision 1.10
1.10 ! tv 1: $NetBSD: README.Interix,v 1.9 2004/04/27 14:03:24 tv Exp $
1.1 grant 2:
3: Please read the general README file as well.
4:
1.8 tv 5: Interix is a POSIX compatible subsystem for the Windows NT kernel,
6: providing a Unix-like environment with a tighter kernel integration than
7: available with Cygwin. It is part of the Windows Services for Unix
8: package, available for free for any licensed copy of Windows 2000, XP,
9: or 2003. SFU can be downloaded from:
1.1 grant 10:
11: http://www.microsoft.com/windows/sfu/
12:
1.8 tv 13: Services for Unix 3.5, current as of this writing, has been tested. 3.0
14: or 3.1 may work, but are not officially supported. (The main difference
15: in 3.0/3.1 is lack of pthreads.)
1.6 tv 16:
1.9 tv 17: A prebuilt bootstrap kit and prebuilt binary packages for Interix 3.5 are
18: available from the pkgsrc information page:
19:
20: http://www.netbsd.org/Documentation/software/packages.html
21:
22: =====
23:
1.8 tv 24: At an absolute minimum, the following packages must be installed from
25: the Windows Services for Unix 3.5 distribution in order to use pkgsrc:
1.1 grant 26:
27: Utilities -> Base Utilities
28: Interix GNU Components -> (all)
29: Remote Connectivity
30: Interix SDK
31:
1.8 tv 32: When using pkgsrc on Interix, it is best NOT to install the Utilities
33: subcomponent "UNIX Perl". That is Perl 5.6 without shared module
34: support, installed to /usr/local, and will only cause confusion.
35: Instead, install Perl 5.8 from pkgsrc (or from a binary package
36: available at the URL above).
37:
38: The Remote Connectivity subcomponent "Windows Remote Shell Service" does
39: not need to be installed, but Remote Connectivity itself should be
40: installed in order to have a working inetd.
41:
42: Finally, during installation you may be asked whether to enable setuid
43: behavior for Interix programs, and whether to make pathnames default to
44: case-sensitive. Both options should be enabled. (If you choose to
45: disable setuid, many system programs from pkgsrc may not work.)
1.3 tv 46:
1.1 grant 47: =====
48:
1.8 tv 49: IMPORTANT NOTES
1.1 grant 50:
1.6 tv 51: * The package imanager (either the pkgsrc "su" user, or the user
52: running "pkg_add") must be a member of the local Administrators
53: group. Such a user must also be used to run the bootstrap. This is
54: slightly relaxed from the normal pkgsrc requirement of "root".
55:
1.7 tv 56: * The package manager should use a umask of 002. "make install" will
1.6 tv 57: automatically complain if this is not the case. This ensures that
58: directories written in /var/db/pkg are Administrators-group writeable.
59:
1.8 tv 60: * The popular Interix binary packages from http://www.interopsystems.com/
61: use an older version of pkgsrc's pkg_* tools. Ideally, these should
62: NOT be used in conjunction with pkgsrc. If you choose to use them at
63: the same time as the pkgsrc packages, ensure that you use the proper
64: pkg_* tools for each type of binary package.
65:
66: =====
67:
68: KNOWN ISSUES
69:
1.4 tv 70: * It is not necessary, in general, to have a "root" user on the Windows
71: system; any member of the local Administrators group will suffice.
72: However, some packages currently assume that the user named "root" is
1.6 tv 73: the privileged user (these will eventually be fixed). To accommodate
1.4 tv 74: these, you may create such a user; make sure it is in the local group
75: Administrators.
76:
1.10 ! tv 77: And the following two issues mean that binary packages (pkg_add) should be
! 78: installed by Administrator for the time being:
! 79:
! 80: * "pkg_add" creates directories of mode 0755, not 0775, in $PKG_DBDIR.
! 81: This will be fixed.
! 82:
! 83: * set-gid files in Interix seem to require using Administrator to install
! 84: the setgid file. (I'm working to confirm this.)
! 85:
1.8 tv 86: =====
CVSweb <webmaster@jp.NetBSD.org>