|
|
|
|
|
|
| Author |
Message |
Dr. R. E. Hawkins
*nix forums addict
Joined: 23 Jun 2006
Posts: 55
|
 Posted: Mon Jul 17, 2006 9:49 pm Post subject:
getting write permission over nfs exported ports directory
|
|
|
I have, at last, managed to export my ports directory over nfs,
and have some of the ports installing on the other machines from
packages that I built.
I have an exports file with
/usr64/ports /usr64/src /usr64/local/etc -mapall=remote_builds
-network 192.168.0.0 -mask 255.255.0.0
and I've created the remote_builds user, done "chgrp -R remote_builds"
on the exported directories, as well as "chmod -R g+w" on them.
I'm successfully installing the *built* packages, and can write to the
foreign directories, but when it tries to build itself, the work directory
is created as 755 or root:wheel. Is there a umask-ish solution to
control the user and mask in this situation? I assume that I could
manually build as remote_user, but this will be a lot o switching back
and forth.
I've also toyed with unionfs, but it doesn't seem that it builds the
heirarchy for a file in the upper layer (e.g., if I have /usr/ports in the
upper layer on the local machine, and /usr/ports/net/getit in the lower
layer by nfs, It won't create /usr/ports/net/getit/work on the local
machine)
hawk |
|
| Back to top |
|
 |
Chronos
*nix forums Guru Wannabe
Joined: 30 Sep 2005
Posts: 174
|
| Posted: Mon Jul 17, 2006 9:59 pm Post subject:
Re: getting write permission over nfs exported ports directory
|
|
|
After replacing Dr. R. E. Hawkins with a small shell script on Monday 17
Jul 2006 22:49, the following appeared on stdout:
| Quote: | I'm successfully installing the built packages, and can write to the
foreign directories, but when it tries to build itself, the work
directory is created as 755 or root:wheel. Is there a umask-ish
solution to control the user and mask in this situation? I assume
that I could manually build as remote_user, but this will be a lot o
switching back and forth.
|
It's not a good idea to use NFS mounts as source build locations. Make
yourself a locally writable directory somewhere (like /usr/local/work)
and stick that path in /etc/make.conf
as "WRKDIRPREFIX=/usr/local/work". Not only will it solve your problem,
but your builds will be much faster as well.
You may want to make a separate user (such as build) and map root to it
on the ports export (-maproot=build) so you can give ownership of
${PORTSDIR}/distfiles and packages to that user. That will allow any
machine in your build set to download distfiles and write packages to
your repository.
--
Chronos |
|
| Back to top |
|
|
Dr. R. E. Hawkins
*nix forums addict
Joined: 23 Jun 2006
Posts: 55
|
| Posted: Tue Jul 18, 2006 12:19 am Post subject:
Re: getting write permission over nfs exported ports directory
|
|
|
On Mon, 17 Jul 2006 23:59:22 +0100, Chronos wrote:
| Quote: | After replacing Dr. R. E. Hawkins with a small shell script on Monday 17
Jul 2006 22:49, the following appeared on stdout:
I'm successfully installing the built packages, and can write to the
foreign directories, but when it tries to build itself, the work
directory is created as 755 or root:wheel. Is there a umask-ish
solution to control the user and mask in this situation? I assume
that I could manually build as remote_user, but this will be a lot o
switching back and forth.
It's not a good idea to use NFS mounts as source build locations. Make
yourself a locally writable directory somewhere (like /usr/local/work)
and stick that path in /etc/make.conf
as "WRKDIRPREFIX=/usr/local/work". Not only will it solve your problem,
but your builds will be much faster as well.
|
That sounds a lot better, but it seems to be ignoring it, whether I set it
in make.conf or as an environmental variable. It's already in make.conf,
and then:
slytherin# ls -ld /usr/local/work
drwxrwxr-x 2 root remote_builds 512 Jul 17 16:55 /usr/local/work
slytherin# setenv WRKDIRPREFIX /usr/local/work^
slytherin# setenv WRKDIRPREFIX /usr/local/workESC[28DPKG_PATH /usr/ports/package
s/All
slytherin# cd /usr/ports/devel/libthai
slytherin# make
make: cannot open current directory: Permission denied
The lines in /etc/make.conf are
# to be able to work on ports from nfs mount
WRKDIRPREFIX=/usr/local/work
PKG_PATH=/usr/ports/Packages/All
| Quote: | You may want to make a separate user (such as build) and map root to it
on the ports export (-maproot=build) so you can give ownership of
${PORTSDIR}/distfiles and packages to that user. That will allow any
machine in your build set to download distfiles and write packages to
your repository.
|
I've done this with a remote_builds user, and used -mapalll=remote_builds.
I made sure it has the same uid on all three machines. The other machines
writing to the repository hadn't really occurred to me--I build on the
laptop since all three machines have similar speeds, but the laptop has 1G
of memory, while the others have 256M
hawk, still amazed that memory measured in megabytes can be "small" |
|
| Back to top |
|
|
Chronos
*nix forums Guru Wannabe
Joined: 30 Sep 2005
Posts: 174
|
| Posted: Tue Jul 18, 2006 1:07 pm Post subject:
Re: getting write permission over nfs exported ports directory
|
|
|
After replacing Dr. R. E. Hawkins with a small shell script on Tuesday
18 Jul 2006 01:19, the following appeared on stdout:
| Quote: | PKG_PATH=/usr/ports/Packages/All
|
No.
PACKAGES=/usr/ports/packages
"All" is the directory that holds the actual binary packages, which then
get symlinked into their relevant categories. For example, on my amd64
machines, the make.conf has the following three lines:
WRKDIRPREFIX=/usr/local/work
PACKAGES=/usr/ports/packages-amd64
DISTDIR=/usr/ports/distfiles
which gives me a repository that looks like this:
/usr/ports/packages-amd64 $ ls
All deskutils java net-p2p tcl84
Latest devel kde news textproc
accessibility dns lang palm tk84
archivers editors linux perl5 www
astro emulators mail print x11
audio ftp math python x11-clocks
benchmarks games misc ruby x11-fonts
cad gnome multimedia scheme x11-servers
comms graphics net security x11-themes
converters hamradio net-im shells x11-toolkits
databases ipv6 net-mgmt sysutils x11-wm
The only difference on the i386 boxen is the PACKAGES line, which reads
packages-i386. They use the same ports tree and distfiles.
| Quote: | I made sure it has the same uid on all three machines.
|
No again. Only the build/repository/machine holding the ports tree needs
that user. The -maproot=remote_builds line in /etc/exports maps root on
the remote machine (which you'll need to be to install ports) to
remote_builds on the server. That way, *root* on the remote has the
privileges required to install and build ports and also has write
privilege on the directories it needs on the server without
compromising security too much.
The whole point of this is never to have root on the remote mapped as
root on the server, which would mean that any old munchkin supplying
root as its local user would have full root access to anything
exported.
In summary: Remote machine you are building or installing ports on you
need to be either logged in as root or su'd. The server machine with
the ports tree and package repository is mapping that root user to
remote_builds, a unique UID for its own purposes that limits the write
access of the remote machine to two directories, /usr/ports/distfiles
and /usr/ports/packages, the work directory being local to the remote
machine.
--
Chronos |
|
| Back to top |
|
|
Chronos
*nix forums Guru Wannabe
Joined: 30 Sep 2005
Posts: 174
|
| Posted: Wed Jul 19, 2006 9:22 am Post subject:
Re: getting write permission over nfs exported ports directory
|
|
|
After replacing Chronos with a small shell script on Tuesday 18 Jul 2006
14:07, the following appeared on stdout:
| Quote: | PACKAGES=/usr/ports/packages
|
And damn me if I didn't miss out another vital bit o' information...
You may also want to set the PACKAGES environment variable in (I
assume) /usr/local/etc/pkgtools.conf as well as make.conf if you're
using portinstall and/or portupgrade to build your packages. The
PKG_PATH variable should be fine as it is.
--
Chronos |
|
| Back to top |
|
|
Dr. R. E. Hawkins
*nix forums addict
Joined: 23 Jun 2006
Posts: 55
|
| Posted: Wed Jul 19, 2006 6:02 pm Post subject:
Re: getting write permission over nfs exported ports directory
|
|
|
On Tue, 18 Jul 2006 15:07:33 +0100, Chronos wrote:
| Quote: | After replacing Dr. R. E. Hawkins with a small shell script on Tuesday
18 Jul 2006 01:19, the following appeared on stdout:
PKG_PATH=/usr/ports/Packages/All
No.
PACKAGES=/usr/ports/packages
|
Ahh. Thanks. I was also using quotes in make.conf for the path.
| Quote: | "All" is the directory that holds the actual binary packages, which then
get symlinked into their relevant categories. For example, on my amd64
machines, the make.conf has the following three lines:
WRKDIRPREFIX=/usr/local/work
PACKAGES=/usr/ports/packages-amd64
DISTDIR=/usr/ports/distfiles
|
I've done this now, and it all works except for one minor matter:
If I type, say, "portinstall -OP webfonts", it first checks the nfs
directory, finds no package (that port never builds a package due
to license issues), and then tries to fetch a prebuilt package from
freebsd.org. Is there a way to stop this beavior? (I only want it to use
a package if I built it).
the same ports tree and distfiles.
| Quote: | I made sure it has the same uid on all three machines.
No again. Only the build/repository/machine holding the ports tree needs
that user. The -maproot=remote_builds line in /etc/exports maps root on
the remote machine (which you'll need to be to install ports) to
remote_builds on the server. That way, *root* on the remote has the
privileges required to install and build ports and also has write
privilege on the directories it needs onhe server without
compromising security too much.
|
I added the user to the other machines in a fit of prissiness to get rid
of the numeric group owners  [hmm, never would have expected a spell
checker that doesn't recognize "hmm" to recognize "prissiness" ]
I'm still functioning on root as the local and getting mapped to
emote_builds. The more I think about it, the more convinced I am that
I should put distfiles and packages onto the desktop with tons of
disk space, rather than the laptop (though it does have a 100g drive).
thanks greatly
hawk |
|
| Back to top |
|
|
Chronos
*nix forums Guru Wannabe
Joined: 30 Sep 2005
Posts: 174
|
| Posted: Wed Jul 19, 2006 6:31 pm Post subject:
Re: getting write permission over nfs exported ports directory
|
|
|
After replacing Dr. R. E. Hawkins with a small shell script on Wednesday
19 Jul 2006 19:02, the following appeared on stdout:
| Quote: | Is there a way to stop this beavior? (I only want it to use
a package if I built it).
|
Most certainly. In /usr/local/etc/pkgtools.conf, uncomment the line that
reads "ENV['PKG_FETCH'] = 'false'"
This has the effect of using false as the package download application,
which then returns a non-zero result, forcing the port build instead
(providing you only use -P and not -PP). Note that you will still see
port(install|upgrade) checking for local packages and then trying to
fetch them when one is not found, but it will fail to download the
binary package every time and revert back to port build unless the
package exists in your local repository.
--
Chronos |
|
| Back to top |
|
|
Dr. R. E. Hawkins
*nix forums addict
Joined: 23 Jun 2006
Posts: 55
|
| Posted: Wed Jul 19, 2006 11:38 pm Post subject:
Re: getting write permission over nfs exported ports directory
|
|
|
On Wed, 19 Jul 2006 11:22:00 +0100, Chronos wrote:
| Quote: | After replacing Chronos with a small shell script on Tuesday 18 Jul 2006
14:07, the following appeared on stdout:
PACKAGES=/usr/ports/packages
And damn me if I didn't miss out another vital bit o' information...
You may also want to set the PACKAGES environment variable in (I
assume) /usr/local/etc/pkgtools.conf as well as make.conf if you're
using portinstall and/or portupgrade to build your packages. The
PKG_PATH variable should be fine as it is.
|
That also seems to default to /usr/ports/packages,
which is fine.
I did discover that I also need to set
ENV['PORTS_DBDIR']] ||= '/usr/local/work'
so that the portsdb can be written on the client machine.
It seems that I need one more, so that portinstall/portupgrade will use
/usr/local/work. If I cd to the directory, make works fine.
If I use
portupgrade -OPf webfonts
however, I get
make: cannot open current directory: Permission denied
which I assume is because it's not using WRKDIRPREFIX from make.conf.
Reading through /usr/local/etc/pkgtools.conf, however, I don't see any.
I suspect something with PORTUPGRADE_ARGS would do it (maybe set
WRKDIRPREFIX here?
Oh, and for those reading this in archives, the reason I'm debugging with
webfonts is that it is a package that *must* build, as the license
prevents the building of a package, and it builds almost instantly.
hawk, eternally gratefull |
|
| Back to top |
|
|
Chronos
*nix forums Guru Wannabe
Joined: 30 Sep 2005
Posts: 174
|
| Posted: Thu Jul 20, 2006 12:32 am Post subject:
Re: getting write permission over nfs exported ports directory
|
|
|
After replacing Dr. R. E. Hawkins with a small shell script on Thursday
20 Jul 2006 00:38, the following appeared on stdout:
| Quote: | make: cannot open current directory: Permission denied
|
Hmm...
# portupgrade -OPf webfonts
---> Checking for the latest package of 'x11-fonts/webfonts'
---> Found a package
of 'x11-fonts/webfonts': /usr/ports/packages-amd64/All/webfonts-0.30.tbz
(webfonts-0.30)
---> Reinstalling 'webfonts-0.30' (x11-fonts/webfonts) using a package
---> Backing up the old version
---> Uninstalling the old version
---> Deinstalling 'webfonts-0.30'
[Updating the pkgdb <format:bdb_btree> in /var/db/pkg ... - 448 packages
found (-1 +0) (...) done]
---> Installing the new version via the package
/usr/X11R6/bin/fc-cache: "lib/X11/fonts/webfonts": caching, 30 fonts, 0
dirs
/usr/X11R6/bin/fc-cache: succeeded
---> Cleaning out obsolete shared libraries
[Updating the pkgdb <format:bdb_btree> in /var/db/pkg ... - 449 packages
found (-0 +1) . done]
I remove the package from my repository and I get:
# portupgrade -OPf webfonts
---> Checking for the latest package of 'x11-fonts/webfonts'
---> Fetching the package(s) for 'webfonts-0.30' (x11-fonts/webfonts)
---> Fetching webfonts-0.30
** The command returned a non-zero exit status: 1
** Failed to fetch
ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/amd64/packages-6.1-release \
/All/webfonts-0.30.tbz
** The command returned a non-zero exit status: 1
** Failed to fetch
ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/amd64/packages-6.1-release \
/All/webfonts-0.30.tgz
** Failed to fetch webfonts-0.30
** Listing the failed packages (*:skipped / !:failed)
! webfonts-0.30 (fetch error)
[NOTE: This is what I was saying before and is a direct result of the
PKG_FETCH environment variable. It looks like an error, but due to
international copyright laws, it's not. We want this behaviour]
---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed
** Could not find the latest version (0.30)
---> Using the port instead of a package
---> Reinstalling 'webfonts-0.30' (x11-fonts/webfonts)
---> Building '/usr/ports/x11-fonts/webfonts'
<snippety, as this is long and tedious enough already without EULAs>
===> Registering installation for webfonts-0.30
<Lots of cleaning, nothing to see here>
---> Cleaning out obsolete shared libraries
[Updating the pkgdb <format:bdb_btree> in /var/db/pkg ... - 449 packages
found (-0 +1) . done]
I think you may have a permission problem left over from before you
mapped root to remote_builds. Before we start looking at other things,
can you please chown -R remote_builds:wheel both /usr/ports/distfiles
and /usr/ports/packages on the server (laptop?) as root and try the
webfonts upgrade again [1]? Also issue a portsclean -C to remove the
entire /usr/local/work/* cruft.
All ports should honour the WRKDIRPREFIX variable, just as they should
all honour LOCALBASE/X11BASE (don't mention X11BASE. I did, but I think
I got away with it). Bad Things [TM] happen to ports (and maintainers)
that don't, as it's used by bsd.port.mk, the master Makefile of the
entire ports system. In fact, it's pretty damn difficult to avoid it
and still have your port get past the big, nasty, hairy-armed, clue
stick and cattle prod wielding committers.
[1] Did I not mention that these two need to be owned by remote_builds?
--
Chronos |
|
| Back to top |
|
|
Dr. R. E. Hawkins
*nix forums addict
Joined: 23 Jun 2006
Posts: 55
|
| Posted: Thu Jul 20, 2006 10:41 pm Post subject:
Re: getting write permission over nfs exported ports directory
|
|
|
On Thu, 20 Jul 2006 02:32:58 +0100, Chronos wrote:
| Quote: | After replacing Dr. R. E. Hawkins with a small shell script on Thursday
20 Jul 2006 00:38, the following appeared on stdout:
make: cannot open current directory: Permission denied
Hmm...
# portupgrade -OPf webfonts
---> Checking for the latest package of 'x11-fonts/webfonts'
---> Found a package
of 'x11-fonts/webfonts': /usr/ports/packages-amd64/All/webfonts-0.30.tbz
(webfonts-0.30)
---> Reinstalling 'webfonts-0.30' (x11-fonts/webfonts) using a package
---> Backing up the old version
---> Uninstalling the old version
---> Deinstalling 'webfonts-0.30'
[Updating the pkgdb <format:bdb_btree> in /var/db/pkg ... - 448 packages
found (-1 +0) (...) done]
---> Installing the new version via the package
/usr/X11R6/bin/fc-cache: "lib/X11/fonts/webfonts": caching, 30 fonts, 0
dirs
/usr/X11R6/bin/fc-cache: succeeded
---> Cleaning out obsolete shared libraries
[Updating the pkgdb <format:bdb_btree> in /var/db/pkg ... - 449 packages
found (-0 +1) . done]
|
I get
eyry ttyp3%portupgrade -OPf webfonts
---> Checking for the latest package of 'x11-fonts/webfonts'
---> Fetching the package(s) for 'webfonts-0.30' (x11-fonts/webfonts)
---> Fetching webfonts-0.30
** The command returned a non-zero exit status: 1
** Failed to fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-6.1-release/All/webfonts-0.30.tbz
** The command returned a non-zero exit status: 1
** Failed to fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-6.1-release/All/webfonts-0.30.tgz
** Failed to fetch webfonts-0.30
** Listing the failed packages (*:skipped / !:failed)
! webfonts-0.30 (fetch error)
---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed
** Could not find the latest version (0.30)
---> Using the port instead of a package
---> Reinstalling 'webfonts-0.30' (x11-fonts/webfonts)
---> Building '/usr/ports/x11-fonts/webfonts'
make: cannot open current directory: Permission denied
webfonts-0.30: "/usr/ports/devel/pkg-config" erroneous -- dependency list incomplete
===> Cleaning for cabextract-1.1
===> Cleaning for fontconfig-2.3.2_5,1
===> Cleaning for xorg-libraries-6.9.0
===> Cleaning for gmake-3.81_1
make: cannot open current directory: Permission denied
*** Error code 1
Stop in /nfs/redtail/usr.ports/x11-fonts/webfonts.
*** Error code 1
Stop in /nfs/redtail/usr.ports/x11-fonts/webfonts.
** Listing the failed packages (*:skipped / !:failed)
! x11-fonts/webfonts (webfonts-0.30) (clean error)
---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed
eyry ttyp3%^Dexit
(a cd into the nfs mounted dir and "make" still works)
On the laptop/server:
redtail# ls -ld /usr/ports /usr/ports/distfiles /usr/ports/packages
drwxr-xr-x 68 root wheel 1536 Jul 20 15:32 /usr/ports
drwxrwxr-x 27 remote_builds wheel 10752 Jul 17 16:51 /usr/ports/distfiles
drwxrwxr-x 48 remote_builds wheel 1024 Jul 20 10:30 /usr/ports/packages
redtail# cat /etc/exports
/etc -mapall=remote_builds -network 192.168.0.0 -mask 255.255.0.0
/usr64/ports /usr64/src /usr64/local/etc -mapall=remote_builds -network 192.168.0.0 -mask 255.255.0.0
and back on the client,
eyry ttyp3%grep nfs /etc/fstab
redtail:/usr64/src /nfs/redtail/usr.src nfs rw 3 0
redtail:/usr64/ports /nfs/redtail/usr.ports nfs rw 3 0
#/nfs/redtail/usr.src /usr/src unionfs b 4 4
#/nfs/redtail/usr.ports /usr/ports unionfs b 4 4
eyry ttyp3%mount
/dev/ad1s1a on / (ufs, local, soft-updates)
devfs on /dev (devfs, local)
/dev/ad1s2a on /home (ufs, local)
/dev/ad1s1e on /usr (ufs, local, soft-updates)
/dev/ad1s1d on /var (ufs, local, soft-updates)
/dev/ad0s4 on /xfr (msdosfs, local)
linprocfs on /usr/compat/linux/proc (linprocfs, local)
redtail:/usr64/src on /nfs/redtail/usr.src (nfs)
redtail:/usr64/ports on /nfs/redtail/usr.ports (nfs)
eyry ttyp3%^Dexit
| Quote: | I think you may have a permission problem left over from before you
mapped root to remote_builds. Before we start looking at other things,
can you please chown -R remote_builds:wheel both /usr/ports/distfiles
and /usr/ports/packages on the server (laptop?)
|
I had them as root:remote_builds, 775
I've made this change, but there doesn't seem to be any difference.
as root and try the
| Quote: | webfonts upgrade again [1]? Also issue a portsclean -C to remove the
entire /usr/local/work/* cruft.
|
done.
thanks
hawk |
|
| Back to top |
|
|
Chronos
*nix forums Guru Wannabe
Joined: 30 Sep 2005
Posts: 174
|
| Posted: Fri Jul 21, 2006 12:06 am Post subject:
Re: getting write permission over nfs exported ports directory
|
|
|
After replacing Dr. R. E. Hawkins with a small shell script on Thursday
20 Jul 2006 23:41, the following appeared on stdout:
| Quote: | eyry ttyp3%portupgrade -OPf webfonts
|
Is that a root prompt? /usr/local/work should be owned root:wheel and
ports should be built and installed with root privileges *on the local
machine*. This is why I said -maproot not -mapall for exports on
redtail.
On redtail:
/etc/exports
/etc -mapall=remote_builds -network 192.168.0.0 -mask 255.255.0.0
/usr64/ports /usr64/src /usr64/local/etc -maproot=remote_builds -network
192.168.0.0 -mask 255.255.0.0
On eyry, you need to be root and your /usr/local/work should look like
this:
drwxr-xr-x 3 root wheel 512 Jul 20 02:44 work
Your mountpoints on eyry are strange, too. Personally, I would have
redtail:/usr64/ports mounted on /usr/ports (it'll override whatever is
in there but leave it intact. I see what you were trying to do in your
fstab, but unionfs is a little more complex, where it takes whatever
you're mounting and overrides anything that exists whilst still leaving
anything that doesn't exist on the new mount visible to the OS. An
example of how this works can be found by looking at how profile.sh
works), and similarly redtail:/usr64/src on /usr/src.
Here's how I'm set up (I've replaced the username I have set up on the
server with the one you have used for clarity):
/etc/exports:
/usr/ports -maproot=remote_builds -network <my network> -mask <my
netmask>
(Note: My /usr/ports on the server is a separate partition so it gets a
line of its own, which is why /usr/src doesn't appear here too. Not
important for this discussion)
/usr/ports/distfiles and package repositories on the server:
drwxr-xr-x 47 remote_builds wheel 32256 Jul 20 15:52 distfiles
drwxr-xr-x 57 remote_builds wheel 1024 Apr 29 22:10
packages-amd64
drwxr-xr-x 56 remote_builds wheel 1024 Jun 30 22:03
packages-i386
/usr/ports permissions:
drwxr-xr-x 71 root wheel 2048 Jul 20 15:41 ports (note, this
*must* be readable by remote_builds. You need to (c|cv)sup, make
fetchindex and portsdb -u on redtail only. Never try to update the tree
from eyry because it doesn't have permission to write the portsdb to
the ports directory which, now that I think about it, could be the
problem here. Is the INDEX-? and INDEX-?.db up to date on redtail?
/etc/fstab on one of my clients:
server:/usr/ports /usr/ports nfs rw 0 0
and mount on the same machine:
server:/usr/ports on /usr/ports (nfs)
Given this little lot and the configuration we have set up in make.conf
and pkgtools.conf, things just work.
--
Chronos |
|
| Back to top |
|
|
Google
|
|
| Back to top |
|
|
|
|
The time now is Mon Dec 01, 2008 6:49 pm | All times are GMT
|
|
Loan | Premade MySpace Layouts | Personal Loans | Electrical Shops | Credit Cards
|
|
Copyright © 2004-2005 DeniX Solutions SRL
|
|
|
|
Other DeniX Solutions sites:
Unix/Linux blog |
electronics forum |
medicine forum |
science forum |
|
|
Privacy Policy
|
Powered by phpBB © 2001, 2005 phpBB Group
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
Forum index
»
*nix
»
BSD
»
FreeBSD
