OpenAFS on FreeBSD Progress (Works)

[Matt W. Benjamin]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Jason (and the rest of this apparently small list),

I apologize for not piping up before, I didn't join freebsd-afs when I
was copied on an initial flurry of emails, but just did.

I have the following progress:

1. I finished initial work fixing open issues with the stalled FreeBSD
client cache manager in OpenAFs, and made it run on i386 FreeBSD 7.0 and
8-Current [as of around Sept. 15 or so].

2. The i386 FreeBSD 7.0 target is now an "officially supported platform"
in OpenAFS 1.4.8--though the client has only recently been finished, and
probably has undiscovered issues--the only issues I'm actually aware of
for certain are a cosmetic, and I use the port myself

3. This week I posted a patch to OpenAFS RT (our bug tracker) adding
x86_64 FreeBSD 7.0 support, with some help from Tony Jago.  I'm
expecting to see the x86_64 platform officially supported in the next
stable OpenAFS release

Just as extra information, I've also worked on the i386 OpenBSD port,
updating it for OpenBSD 4.4, and am most of the way through a new port
to NetBSD 4.0, based on the existing OpenBSD port (which was itself
based on an ancient NetBSD port, in fact).

I would appreciate any help and guidance getting OpenAFS more fully
usable in FreeBSD.

Matt

OpenAFS on FreeBSD Progress
Jason C. Wells jcw at highperformance.net
Mon Sep 22 03:57:56 UTC 2008

    * Previous message: AFS Hackathon - October 27-28 at Google HQ,
Mountain View, CA, USA
    * Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

At the beginning of the year, there was a discussion on a port of
OpenAFS, especially the client/cache manager for FreeBSD.  Did this
discussion bear any fruit?

I'm considering switching to Debian on my desktop to get OpenAFS.  I'd
wait if I knew an OpenAFS port was forthcoming.

Regards,
Jason



- --

Matt Benjamin

The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI  48104

http://linuxbox.com

tel. [phone]
fax. [phone]
cel. 734-216-5309

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJOsrEJiSUUSaRdSURCI9UAJ455pRtBv79aVN6FzNZuHiIStJ1mwCfV18i
4OFN+p5UmRmcYuIGoDiaiBs=
=f62N
-----END PGP SIGNATURE-----
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-afs
To unsubscribe, send any mail to "[hidden email]"

[Jason C. Wells]

Great news Matt!  I can't wait to try it.  I have a big upgrade planned
in the near future and will work in AFS client support at the same time.

Later,
Jason
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-afs
To unsubscribe, send any mail to "[hidden email]"

[Boris Samorodov]

Hello List,

Matt Benjamin <[hidden email]> writes:
> Hi Jason (and the rest of this apparently small list),
>
> I apologize for not piping up before, I didn't join freebsd-afs when I
> was copied on an initial flurry of emails, but just did.
>
> I have the following progress:

Good work, thank you and all involved very much!

> 1. I finished initial work fixing open issues with the stalled FreeBSD
> client cache manager in OpenAFs, and made it run on i386 FreeBSD 7.0 and
> 8-Current [as of around Sept. 15 or so].
>
> 2. The i386 FreeBSD 7.0 target is now an "officially supported platform"
> in OpenAFS 1.4.8--though the client has only recently been finished, and
> probably has undiscovered issues--the only issues I'm actually aware of
> for certain are a cosmetic, and I use the port myself
>
> 3. This week I posted a patch to OpenAFS RT (our bug tracker) adding
> x86_64 FreeBSD 7.0 support, with some help from Tony Jago.  I'm
> expecting to see the x86_64 platform officially supported in the next
> stable OpenAFS release

Well, I've just finish a FreeBSD port. It is based on port by Alec Kloss
(CCed0 which was sent to me by Tony Jago (CCed) by email. Actually I
wrote some comments about the port I've got but haven't received
a reply so far.

Let me introduce the port: ftp://ftp.ipt.ru/pub/tmp/openafs.shar
or one can browse it here: ftp://ftp.ipt.ru/pub/tmp/openafs .

The port was tested at tinderbox for 7.0-i386, 7-STABLE-i386,
8-CURRENT-i386, 7-STABLE-amd64, 8-CURRENT-amd64.

The port uses sources from 1.4.8 with integrated patches for amd64.
Actually, there are two extra patches. the first one is needed for
building at amd64. It should be committed along with those from
OpenAFS RT (ftp://ftp.ipt.ru/pub/tmp/openafs/files/patch-configure).
While the second one is a real hack to make openafs to compile at
8-CURRENT (ftp://ftp.ipt.ru/pub/tmp/openafs/files/patch-curseswindows.c).

I'd like to create two separate ports: openafs-server and
openafs-client. But I don't know right now how to do it.

Any comments are appreciated.


WBR
--
Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone & Internet SP
FreeBSD committer, http://www.FreeBSD.org The Power To Serve
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-afs
To unsubscribe, send any mail to "[hidden email]"

[Matt W. Benjamin]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Boris (CC others),

Thanks for your work, in turn!

As you can imagine, since I'm from the OpenAFS side, I have the
following agenda:

1. get official FreeBSD port of openafs server and client
established--it sounds like you're on track to do this (more below)

2. absorb all relevant patches into OpenAFS upstream repo--we have
Tony's 64bit fixes, as you saw, and have built these into what I
submitted to RT for AMD64 target;  thanks for the pointer to the other
two patches, and for putting them into RT already (!);  I'll look at
those shortly

Note that I have submitted additional patches for FreeBSD openafs server
and client that will probably appear in the next stable
release--including masking SIGSYS triggered by ktc_GetToken as used by
vos and other programs, when the lkm is not loaded [ugh], sorry didn't
fix that earlier.

Now, returning to the port topic...

- From what I understand, Alec's port uses Arla as the client, so I think
that port isn't the _client_ port I personally and OpenAFS are trying
for, but presumably they can coexist?  Alec's is ideal for sites wishing
to blend OpenAFS with Arla as the client, &c, and we certainly want to
assist in any way we can with that effort, as well.

I would like to open discussion on how OpenAFS specifically should best
interface with the FreeBSD ports system--and people who would like to
help us keep that port up to date :)

Regards,

Matt

Boris Samorodov wrote:
>
> I'd like to create two separate ports: openafs-server and
> openafs-client. But I don't know right now how to do it.
>
> Any comments are appreciated.
>
>
> WBR




- --

Matt Benjamin

The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI  48104

http://linuxbox.com

tel. [phone]
fax. [phone]
cel. 734-216-5309

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJPYmMJiSUUSaRdSURCAKrAJ0SZfZlY8UYIas7h5tshzUYn8iwLACeNPzK
CCbpepY7BVZb8SYKrF5nzlY=
=OY6z
-----END PGP SIGNATURE-----
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-afs
To unsubscribe, send any mail to "[hidden email]"

[Tony Jago]

> Note that I have submitted additional patches for FreeBSD openafs server
> and client that will probably appear in the next stable
> release--including masking SIGSYS triggered by ktc_GetToken as used by
> vos and other programs, when the lkm is not loaded [ugh], sorry didn't
> fix that earlier.

That would be excellent. Another option would be to have many of the
commands default to -localauth when the kernel module isn't loaded as this
is probably what the user was wanting anyway.

On this topic, it's impossible to setup an openafs server without a working
afs client as you need to setup the root.cell and set permissions. For this
reason I think afs will become a lot more used when the client is working.

>From my personal testing, the server 1.4.8 on freebsd (on AMD and i386) work
really well. We have being using it in light production mode for some time
in freebsd jails. The client I have had problems with. When testing I found
it corrupts files. It can't handle symlinks and is just a little rusty at
the moment. I haven't tried the 1.4.8 client but will give it a go shortly
to see how things go.

> - From what I understand, Alec's port uses Arla as the client, so I think
> that port isn't the _client_ port I personally and OpenAFS are trying
> for, but presumably they can coexist?  Alec's is ideal for sites wishing
> to blend OpenAFS with Arla as the client, &c, and we certainly want to
> assist in any way we can with that effort, as well.

Both ports can co-exist in the freebsd ports system. They probably should be
marked to exclude each other.

> I would like to open discussion on how OpenAFS specifically should best
> interface with the FreeBSD ports system--and people who would like to
> help us keep that port up to date :)

>> I'd like to create two separate ports: openafs-server and
>> openafs-client. But I don't know right now how to do it.

I would also recommend a openafs metaport that combines the client and the
server. Have a look at the mysql-client, mysql-server and mysql ports to see
an example of how to do this sort of thing.

I am really looking forward to a stable afs on freebsd. It's been a long
wait. This combined with a ZFS filesystem in the backend is a very very
powerful system.

Tony

_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-afs
To unsubscribe, send any mail to "[hidden email]"

[Derrick Brashear]

On Mon, Dec 8, 2008 at 6:55 PM, Tony Jago <[hidden email]> wrote:

> Note that I have submitted additional patches for FreeBSD openafs server
>> and client that will probably appear in the next stable
>> release--including masking SIGSYS triggered by ktc_GetToken as used by
>> vos and other programs, when the lkm is not loaded [ugh], sorry didn't
>> fix that earlier.
>>
>
> That would be excellent. Another option would be to have many of the
> commands default to -localauth when the kernel module isn't loaded as this
> is probably what the user was wanting anyway.

Unless they're horribly broken they will be there.

>
> On this topic, it's impossible to setup an openafs server without a working
> afs client as you need to setup the root.cell and set permissions. For this
> reason I think afs will become a lot more used when the client is working.
>

Annoying, maybe. Hardly impossible.




--
Derrick
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-afs
To unsubscribe, send any mail to "[hidden email]"

[Matt W. Benjamin]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Tony,

1. I can't reproduce any problem with symlinks, and I've tested the
obvious things--can you put a bug in openafs RT with details?

2. File data consistency.  That is noted, please put it in RT as well,
if you could--the simpler the steps to reproduce (less complex i/o,
iozone, and other dependencies, the easier to fix, likely)--there
haven't been many testers yet, but we're committed to supporting the client.

Thanks!

Matt

Tony Jago wrote:
> The client I have had problems with. When
> testing I found it corrupts files. It can't handle symlinks and is just
> a little rusty at the moment. I haven't tried the 1.4.8 client but will
> give it a go shortly to see how things go.

- --

Matt Benjamin

The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI  48104

http://linuxbox.com

tel. [phone]
fax. [phone]
cel. 734-216-5309

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJPb9lJiSUUSaRdSURCKMlAJ4xybGtTSmL1yyjAJatb4DCaDi9bACfaH2x
0vSCDZ1OPQrq21jfJUKhwc0=
=Vj3u
-----END PGP SIGNATURE-----
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-afs
To unsubscribe, send any mail to "[hidden email]"

[Boris Samorodov]

Hi Matt and others,


Matt Benjamin <[hidden email]> writes:

> As you can imagine, since I'm from the OpenAFS side, I have the
> following agenda:
>
> 1. get official FreeBSD port of openafs server and client
> established--it sounds like you're on track to do this (more below)

Yes.

> 2. absorb all relevant patches into OpenAFS upstream repo--we have
> Tony's 64bit fixes, as you saw, and have built these into what I
> submitted to RT for AMD64 target;  thanks for the pointer to the other
> two patches, and for putting them into RT already (!);  I'll look at
> those shortly

Seems I wasn't clear enough. I created a port using *your* diff from
RT. But added two extra patches. The first one to enable the port to
be compiled at amd64 and the second one to enable to compile the port
at FreeBSD-CURRENT.

Actually, I tried but didn't find a way to submit a followup to your
ticket at RT database.

> Note that I have submitted additional patches for FreeBSD openafs server
> and client that will probably appear in the next stable
> release--including masking SIGSYS triggered by ktc_GetToken as used by
> vos and other programs, when the lkm is not loaded [ugh], sorry didn't
> fix that earlier.
>
> Now, returning to the port topic...
>
> From what I understand, Alec's port uses Arla as the client, so I think
> that port isn't the _client_ port I personally and OpenAFS are trying

Yes, it's a server port.

> for, but presumably they can coexist?  Alec's is ideal for sites wishing
> to blend OpenAFS with Arla as the client, &c, and we certainly want to
> assist in any way we can with that effort, as well.
>
> I would like to open discussion on how OpenAFS specifically should best
> interface with the FreeBSD ports system--and people who would like to
> help us keep that port up to date :)

Seconded.


WBR
--
Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone & Internet SP
FreeBSD committer, http://www.FreeBSD.org The Power To Serve
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-afs
To unsubscribe, send any mail to "[hidden email]"

[Matt W. Benjamin]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Boris Samorodov wrote:

> Hi Matt and others,
>
>
> Matt Benjamin <[hidden email]> writes:
>
>> As you can imagine, since I'm from the OpenAFS side, I have the
>> following agenda:
>>
>> 1. get official FreeBSD port of openafs server and client
>> established--it sounds like you're on track to do this (more below)
>
> Yes.
>
>> 2. absorb all relevant patches into OpenAFS upstream repo--we have
>> Tony's 64bit fixes, as you saw, and have built these into what I
>> submitted to RT for AMD64 target;  thanks for the pointer to the other
>> two patches, and for putting them into RT already (!);  I'll look at
>> those shortly
>
> Seems I wasn't clear enough. I created a port using *your* diff from
> RT. But added two extra patches. The first one to enable the port to
> be compiled at amd64 and the second one to enable to compile the port
> at FreeBSD-CURRENT.

Sorry, I did mistake you.

Which patches from RT (#s) do you have?  For now, please attach any
patch that we don't have.  I have OpenAFS compiling at amd64, in
#123811, and I thought it compiled at CURRENT (but it maybe stopped at
some point), and will merge any reasonable change you have.

We need to fix RT access.  We really will.

Thanks,

Matt

- --

Matt Benjamin

The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI  48104

http://linuxbox.com

tel. [phone]
fax. [phone]
cel. 734-216-5309

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJPrPqJiSUUSaRdSURCJyzAJwPnsh+Emm01KhzfOsaMNxfP3OYqQCfZXJP
z9I4E4VJ/Z6aizTCRudtBVk=
=om2C
-----END PGP SIGNATURE-----
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-afs
To unsubscribe, send any mail to "[hidden email]"

[Boris Samorodov]

Hi Matt,

Matt Benjamin <[hidden email]> writes:

> Which patches from RT (#s) do you have?  For now, please attach any
> patch that we don't have.  I have OpenAFS compiling at amd64, in
> #123811,

I took the diff from this ticket and create patches based on it.

> and I thought it compiled at CURRENT (but it maybe stopped at
> some point),

I test ports with ports-mgmt/tinderbox. This program creates a vanilla
environment for building/packaging. The environment of the main system
don't influence testing.

> and will merge any reasonable change you have.

The first one is just like a diff for src/cf/osconf.m4:
ftp://ftp.ipt.ru/pub/tmp/openafs/files/patch-configure
Without this patch I got an error at amd64 build:
-----
...
cd picobj && cc -I. -I.  -I/work/a/ports/net/openafs/work/openafs-1.4.8/src/config -I/work/a/ports/net/openafs/work/openafs-1.4.8/include  -O2 -pipe   -c glue.c
+ cc -shared -o libafssetpag.so.1.0 picobj/setpag.o picobj/glue.o syscall.o
/usr/bin/ld: picobj/setpag.o: relocation R_X86_64_32 can not be used when making a shared object; recompile with -fPIC
picobj/setpag.o: could not read symbols: Bad value
*** Error code 1
-----

The second patch (I called it a hack) deals with the absence of sgtty.h
since __FreeBSD_version=800039:
ftp://ftp.ipt.ru/pub/tmp/openafs/files/patch-curseswindows.c
A better way may be to use ifdefs here.
Without this patch I get an error at 8-CURRENT build:
-----
...
cd src && cd gtx && make all
...
cc  -O -I/work/a/ports/net/openafs/work/openafs-1.4.8/src/config -I. -I. -I/work/a/ports/net/openafs/work/openafs-1.4.8/include -I/work/a/ports/net/openafs/work/openafs-1.4.8/include/afs -I/work/a/ports/net/openafs/work/openafs-1.4.8/include/rx -I/work/a/ports/net/openafs/work/openafs-1.4.8 -I/work/a/ports/net/openafs/work/openafs-1.4.8/src -I/work/a/ports/net/openafs/work/openafs-1.4.8/src -O2 -pipe -fPIC  -c curseswindows.c
curseswindows.c:35:19: error: sgtty.h: No such file or directory
*** Error code 1
-----


WBR & HTH
--
Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone & Internet SP
FreeBSD committer, http://www.FreeBSD.org The Power To Serve
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-afs
To unsubscribe, send any mail to "[hidden email]"

[Boris Samorodov]

"Tony Jago" <[hidden email]> writes:

>>> I'd like to create two separate ports: openafs-server and
>>> openafs-client. But I don't know right now how to do it.
>
> I would also recommend a openafs metaport that combines the client and
> the server.

What's the purpose of this port? I understand when a big collection
of ports (like xorg, gnome, etc.) are combined together.

> Have a look at the mysql-client, mysql-server and mysql
> ports to see an example of how to do this sort of thing.

I didn't manage to find a metaport for mysql...


WBR
--
Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone & Internet SP
FreeBSD committer, http://www.FreeBSD.org The Power To Serve
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-afs
To unsubscribe, send any mail to "[hidden email]"

[Palle Girgensohn]

--On fredag, fr 12 dec 2008 17.52.26 +0300 Boris Samorodov <[hidden email]>
wrote:

> "Tony Jago" <[hidden email]> writes:
>
>>>> I'd like to create two separate ports: openafs-server and
>>>> openafs-client. But I don't know right now how to do it.
>>
>> I would also recommend a openafs metaport that combines the client and
>> the server.
>
> What's the purpose of this port? I understand when a big collection
> of ports (like xorg, gnome, etc.) are combined together.

I two ports share the same code base, but install different files, then a
metaport or similar could be clever. See for example
databases/postgresql83-(server|client). The postgresql83-server depends on
the client. The client can installed without the server. Similar to
OpenAFS, hence. Now, they have the same source tarball, so the -client port
just sets a few parameters and then uses the postgresql83-server port as a
master Makefile.

>> Have a look at the mysql-client, mysql-server and mysql
>> ports to see an example of how to do this sort of thing.
>
> I didn't manage to find a metaport for mysql...

Works almost exactly the same as described for postgresql. :-)

Regards,
Palle

>
>
> WBR
> --
> Boris Samorodov (bsam)
> Research Engineer, http://www.ipt.ru Telephone & Internet SP
> FreeBSD committer, http://www.FreeBSD.org The Power To Serve
> _______________________________________________
> [hidden email] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-afs
> To unsubscribe, send any mail to "[hidden email]"

_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-afs
To unsubscribe, send any mail to "[hidden email]"

[Palle Girgensohn-2]

--On fredag, fr 12 dec 2008 17.52.26 +0300 Boris Samorodov <[hidden email]>
wrote:

> "Tony Jago" <[hidden email]> writes:
>
>>>> I'd like to create two separate ports: openafs-server and
>>>> openafs-client. But I don't know right now how to do it.
>>
>> I would also recommend a openafs metaport that combines the client and
>> the server.
>
> What's the purpose of this port? I understand when a big collection
> of ports (like xorg, gnome, etc.) are combined together.

I two ports share the same code base, but install different files, then a
metaport or similar could be clever. See for example
databases/postgresql83-(server|client). The postgresql83-server depends on
the client. The client can installed without the server. Similar to
OpenAFS, hence. Now, they have the same source tarball, so the -client port
just sets a few parameters and then uses the postgresql83-server port as a
master Makefile.

>> Have a look at the mysql-client, mysql-server and mysql
>> ports to see an example of how to do this sort of thing.
>
> I didn't manage to find a metaport for mysql...

Works almost exactly the same as described for postgresql. :-)

Regards,
Palle <[hidden email]>

>
>
> WBR
> --
> Boris Samorodov (bsam)
> Research Engineer, http://www.ipt.ru Telephone & Internet SP
> FreeBSD committer, http://www.FreeBSD.org The Power To Serve
> _______________________________________________
> [hidden email] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-afs
> To unsubscribe, send any mail to "[hidden email]"

_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-afs
To unsubscribe, send any mail to "[hidden email]"

[Boris Samorodov]

Palle Girgensohn <[hidden email]> writes:

> --On fredag, fr 12 dec 2008 17.52.26 +0300 Boris Samorodov
> <[hidden email]> wrote:
>
>> "Tony Jago" <[hidden email]> writes:
>>
>>>>> I'd like to create two separate ports: openafs-server and
>>>>> openafs-client. But I don't know right now how to do it.
>>>
>>> I would also recommend a openafs metaport that combines the client and
>>> the server.
>>
>> What's the purpose of this port? I understand when a big collection
>> of ports (like xorg, gnome, etc.) are combined together.
>
> I two ports share the same code base, but install different files,
> then a metaport or similar could be clever.

How? I don't undrestand what for we need a *third* port. I agree and
was going to create two ports: server and client.

> See for example
> databases/postgresql83-(server|client).

There is no third metaport for server and client with combines them. [1]

> The postgresql83-server
> depends on the client. The client can installed without the
> server. Similar to OpenAFS, hence. Now, they have the same source
> tarball, so the -client port just sets a few parameters and then uses
> the postgresql83-server port as a master Makefile.

You have just desribed what I was going to do (actually, has already
done): create an openafs-sever (master) and openafs-client (a
meta-port).

>>> Have a look at the mysql-client, mysql-server and mysql
>>> ports to see an example of how to do this sort of thing.
>>
>> I didn't manage to find a metaport for mysql...
>
> Works almost exactly the same as described for postgresql. :-)

[1] ;-)


WBR
--
Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone & Internet SP
FreeBSD committer, http://www.FreeBSD.org The Power To Serve
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-afs
To unsubscribe, send any mail to "[hidden email]"

[Palle Girgensohn-2]

--On fredag, fr 12 dec 2008 19.03.07 +0300 Boris Samorodov <[hidden email]>
wrote:

> You have just desribed what I was going to do (actually, has already
> done): create an openafs-sever (master) and openafs-client (a
> meta-port).

Sounds perfect. ;-)
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-afs
To unsubscribe, send any mail to "[hidden email]"

[Boris Samorodov]

Boris Samorodov <[hidden email]> writes:

> "Tony Jago" <[hidden email]> writes:
>
>>>> I'd like to create two separate ports: openafs-server and
>>>> openafs-client. But I don't know right now how to do it.
>>
>> I would also recommend a openafs metaport that combines the client and
>> the server.
>
> What's the purpose of this port? I understand when a big collection
> of ports (like xorg, gnome, etc.) are combined together.

Replying to myself. Seems I found out why this port may be needed:
Both server and client have common files (i.e. should be marked
as have CONFLICTS and can't be installed with each other).


WBR
--
Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone & Internet SP
FreeBSD committer, http://www.FreeBSD.org The Power To Serve
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-afs
To unsubscribe, send any mail to "[hidden email]"

[Palle Girgensohn-2]

--On fredag, fr 12 dec 2008 21.28.19 +0300 Boris Samorodov <[hidden email]>
wrote:

> Boris Samorodov <[hidden email]> writes:
>> "Tony Jago" <[hidden email]> writes:
>>
>>>>> I'd like to create two separate ports: openafs-server and
>>>>> openafs-client. But I don't know right now how to do it.
>>>
>>> I would also recommend a openafs metaport that combines the client and
>>> the server.
>>
>> What's the purpose of this port? I understand when a big collection
>> of ports (like xorg, gnome, etc.) are combined together.
>
> Replying to myself. Seems I found out why this port may be needed:
> Both server and client have common files (i.e. should be marked
> as have CONFLICTS and can't be installed with each other).

You don't need a meta port, you a client and a server port, and let the
client install all common files, and let the server depend on the client,
which is reasonable anyway.

/Palle

>
>
> WBR
> --
> Boris Samorodov (bsam)
> Research Engineer, http://www.ipt.ru Telephone & Internet SP
> FreeBSD committer, http://www.FreeBSD.org The Power To Serve
> _______________________________________________
> [hidden email] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-afs
> To unsubscribe, send any mail to "[hidden email]"

_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-afs
To unsubscribe, send any mail to "[hidden email]"

[Ben Kaduk]

On Fri, Dec 12, 2008 at 6:34 PM, Palle Girgensohn <[hidden email]> wrote:

>
>
> --On fredag, fr 12 dec 2008 21.28.19 +0300 Boris Samorodov <[hidden email]>
> wrote:
>
>> Boris Samorodov <[hidden email]> writes:
>>>
>>> "Tony Jago" <[hidden email]> writes:
>>>
>>>>>> I'd like to create two separate ports: openafs-server and
>>>>>> openafs-client. But I don't know right now how to do it.
>>>>
>>>> I would also recommend a openafs metaport that combines the client and
>>>> the server.
>>>
>>> What's the purpose of this port? I understand when a big collection
>>> of ports (like xorg, gnome, etc.) are combined together.
>>
>> Replying to myself. Seems I found out why this port may be needed:
>> Both server and client have common files (i.e. should be marked
>> as have CONFLICTS and can't be installed with each other).
>
> You don't need a meta port, you a client and a server port, and let the
> client install all common files, and let the server depend on the client,
> which is reasonable anyway.

We have a couple of servers here (MIT SIPB) that aren't running clients.
As the guy who installed them reasoned, it's just another thing that might
go wrong.

I think that separate client, server, and meta packages is perfectly reasonable.

-Ben Kaduk
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-afs
To unsubscribe, send any mail to "[hidden email]"

[Rick C. Petty-5]

On Sat, Dec 13, 2008 at 12:34:49AM +0100, Palle Girgensohn wrote:
>
> >Replying to myself. Seems I found out why this port may be needed:
> >Both server and client have common files (i.e. should be marked
> >as have CONFLICTS and can't be installed with each other).
>
> You don't need a meta port, you a client and a server port, and let the
> client install all common files, and let the server depend on the client,
> which is reasonable anyway.

I think you have that backwards.  The client contains a kernel module.  The
server is all run in userland.  I think in this case, have the client depend
upon the server and have the server install all common files.  I agree that
there should not be a metaport.

-- Rick C. Petty
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-afs
To unsubscribe, send any mail to "[hidden email]"

[Derrick Brashear]

On Fri, Dec 12, 2008 at 6:34 PM, Palle Girgensohn <[hidden email]>wrote:

>
>
> --On fredag, fr 12 dec 2008 21.28.19 +0300 Boris Samorodov <[hidden email]>
> wrote:
>
>  Boris Samorodov <[hidden email]> writes:
>>
>>> "Tony Jago" <[hidden email]> writes:
>>>
>>>  I'd like to create two separate ports: openafs-server and
>>>>>> openafs-client. But I don't know right now how to do it.
>>>>>>
>>>>>
>>>> I would also recommend a openafs metaport that combines the client and
>>>> the server.
>>>>
>>>
>>> What's the purpose of this port? I understand when a big collection
>>> of ports (like xorg, gnome, etc.) are combined together.
>>>
>>
>> Replying to myself. Seems I found out why this port may be needed:
>> Both server and client have common files (i.e. should be marked
>> as have CONFLICTS and can't be installed with each other).
>>
>
> You don't need a meta port, you a client and a server port, and let the
> client install all common files, and let the server depend on the client,
> which is reasonable anyway.
>

Given that an OpenAFS server can be run clientless I don't agree.
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-afs
To unsubscribe, send any mail to "[hidden email]"