This has appeared in the archives in the past and a Google search
for "osi_InitDebug 1719" returns
http://www-1.ibm.com/support/docview.wss?uid=swg1IY29990
This Windows error translates to "There are no protocol sequences"
which indicates that there are no RPC Client Protocols installed
On Friday, December 09, 2005 10:13:45 AM + David Howells
<[EMAIL PROTECTED]> wrote:
Derek Atkins <[EMAIL PROTECTED]> wrote:
Neither. That message is relatively normal and is perfectly safe to
ignore. The tainting is due to the fact that the Linux Developers don't
consider the IPL a "
On Saturday, December 03, 2005 05:51:57 PM -0800 Adam Megacz
<[EMAIL PROTECTED]> wrote:
Please forgive me if I misunderstand this; I come at the AFS thing
more from the protocol/programming angle than the IT professional /
storage administrator angle. Specifically, I know much less about t
That's what's in use here with the volume size less than 18GB to allow
saving to a DVD.
One server is in a remote location.
OpenVPN is used to store files directly from a laptop to /afs when
travelling - and the main laptop just died on return from the Arctic.
The vpn gets around all the fire
On Wed, 14 Dec 2005, Frank Burkhardt wrote:
What about this solution:
[...snip...]
Yeah, that was my option #1.
Unless I hear otherwise I think I'm going to go down that road and see how
far I get...
I'm thinking that a combined 3-pronged approach of 'vos backup' for a
snapshot, 'vos add
Unfortunately I won't have time to work out a patch in the near-term (next
month!), however I wondering if a documentation note would tide people
over until then?
On Wed, 14 Dec 2005, Jim Rees wrote:
I thought the "new way" was more recent than that. But I could be wrong.
Like I said, if you
I thought the "new way" was more recent than that. But I could be wrong.
Like I said, if you want to send a patch I'll look at it.
There is already some code in the libafs Makefile to generate the vnode_if.h
file. Maybe this could be extended to also generate the files it depends on.
___
That has been the "correct" procedure according to the documentation
dating back to FreeBSD 4.6 (that's the furthest back I have the handbook.)
:)
Need to ease up the tone, not starting conflict, I really really really
want this to work and work well on FreeBSD, perhaps overly enthusiastic is
We still support OpenAFS on previous versions of FreeBSD and I don't feel
like making the default depend on the OS version. But if you want to send
me a patch I'll be happy to look at it.
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lis
I got the instructions on how to do the build from:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-building.html
Procedure 2. Building a Kernel the "New" Way
cd /usr/src
make buildkernel KERNCONF=GENERIC
make installkernel KERNCONF=GENERIC
That places the files in /usr/
Again, I'm not sure at what stage the kernel build generates those files.
I'll bet you can make them without doing a full kernel compile. Did you try
that?
I build my kernels the old-fashioned way, so that's what the default is for
--with-bsd-kernel-build. I'm open to suggestions.
__
Russ has provided a good answer to you email; I only have a few things
to add:
I only can test on systems I have easy access to; for various political
reasons here, I only have easy access to Solaris and MacOS X, and I only
use MIT Kerberos (I installed Heimdal on a Solaris box here just so I coul
Hi,
I got the following error then I try to create an AFS volume on sunx86_510.
bash-3.00# /usr/afs/bin/vos create afs01 aa testvol -localauth
Could not change quota (error 134511920), continuing...
: No such file or directory
Failed to end the transaction on the volume testvol 536871442
: N
Okay, I did finally get OpenAFS to compile on the fresh FreeBSD 6.0
server, with full sources installed. Simply running a configure for the
kernel didn't do it, I did a full GENERIC compile using the "new world"
ways of compiling.
In order to get OpenAFS to build and install however, I had to
Please don't cc openafs-bugs when you post to openafs-info. Then every
clever person who just replies to all opens a new bug.
Post twice, or bcc openafs-bugs or something.
I'll take care of this.
On Wed, 14 Dec 2005, Rainer Toebbicke wrote:
Some xdr_ routines in src/rx use osi_alloc() whi
Some xdr_ routines in src/rx use osi_alloc() which is defined as
returning a char * in rx_misc.c, but do not declare it.
Consequently, the function call is considered to return an int which
truncates the pointer on systems (e.g. ia64) where an intis shorter
than a char *. Affected are xdr_ar
On Dec 14, 2005, at 11:26 AM, Thomas Mueller wrote:
On Tue, 13 Dec 2005, Russ Allbery wrote:
However, we're running into some problems with file server crashes on
Solaris 8 with 1.4.0 as well. We're currently working on figuring
out
what's going on.
This Morning I upgraded to OpenAFS-1.4.
Hi,
On Tue, Dec 13, 2005 at 05:21:03PM -0800, [EMAIL PROTECTED] wrote:
>
> Does it work to:
>
> 1. Have homedirs be forced-r/w mountpoints, use vos addsite / vos release
> for backups
> and do 'vos convertROtoRW' as recovery? I can't see why this one wouldn't
> work.
>
> 2. Do a 'vos copy
On Tue, 13 Dec 2005, Russ Allbery wrote:
> However, we're running into some problems with file server crashes on
> Solaris 8 with 1.4.0 as well. We're currently working on figuring out
> what's going on.
>
This Morning I upgraded to OpenAFS-1.4.1-rc2 on Scientific Linux 3.0.5,
Kernel 2.4.21-32.
On Dec 14, 2005, at 8:40 AM, lal anil wrote:
Hi
...
When I try to run .configure with
--with-afs-sysname=s390_linux26 and then run make I get the
following error
#make
make build
make[1]: Entering directory `/openafs-1.4.0'
make finale DEST=/openafs-1.4.0/s390_linux26/dest
COMPILE_PART
20 matches
Mail list logo
