Matthew Dillon scribbled this message on Aug 1:
> :Yeah, I know about -alldirs... The problem was that we had customers who
> :wanted us to export their home directories, and unless I gave them their own
> :filesystem, I couldn't restrict it in the manner i wanted. :)
> :
> :Just checking to see t
In message <[EMAIL PROTECTED]>, Mike Smith writes:
>> My semantics may be wrong on these two: what I'm talking about is
>> what is in handbook chapter 8 "Using command line utilities " gives
>> you a disk which doesn't boot.
>
>Ok; of those two examples, the first should give you a truly dedicate
> In message <[EMAIL PROTECTED]>, Mike Smith writes:
> >> In message <[EMAIL PROTECTED]>, Bruce Evans writes:
> >>
> >> >All of the above only work for the easy case where the whole disk is
> >> >being labelled. In general, the disk size must be reduced to the slice
> >> >size before applying a
In message <[EMAIL PROTECTED]>, Mike Smith writes:
>> In message <[EMAIL PROTECTED]>, Bruce Evans writes:
>>
>> >All of the above only work for the easy case where the whole disk is
>> >being labelled. In general, the disk size must be reduced to the slice
>> >size before applying a label to a s
> In message <[EMAIL PROTECTED]>, Bruce Evans writes:
>
> >All of the above only work for the easy case where the whole disk is
> >being labelled. In general, the disk size must be reduced to the slice
> >size before applying a label to a slice.
>
> And that is the problem, it seems that "dange
In message <[EMAIL PROTECTED]>, Warner Losh writes:
>In message <[EMAIL PROTECTED]> "Daniel C. Sobral" writes:
>: > Jordan exists.
>:
>: Don't go there. This whole existance-of-perl-scripts thingy is
>: dangerous territory.
>
>I've met jordan's cats, does that count :-)
Only if you can prove tha
In message <[EMAIL PROTECTED]>, Bruce Evans writes:
>All of the above only work for the easy case where the whole disk is
>being labelled. In general, the disk size must be reduced to the slice
>size before applying a label to a slice.
And that is the problem, it seems that "dangerously dedicat
I just started hacking the zp driver to support the 3Com 3C562
dual-function ether/modem card, and I wanted to make sure I'm not
duplicating effort. While I'm at it, there are two significant design
issues that I could use input on:
First, the current zp driver cannot be configured if the pccard
On Sun, 1 Aug 1999, Matthew Dillon wrote:
> Well, theoretically there is nothing wrong going on since you can mount
> things on top of an NFS directory. Mount only complains about
> duplicate normal partition mounts because it can't open the buffered
> block device the second t
Jonathan; just some context, this is with your old 16-bit-protmode
patches, spiffed up for -current, which I committed late last week.
> Finally I back from my work, suped, builded kernel with APM_DEBUG and
> managed to get my computer booted using serial console, however due to
> unknown for
> What makes this all the more puzzling is that it happens only on one
> machine. Hint: it's a laptop (Dell Latitude CPi). panic is a normal
> Pentium machine of no particular lineage. Does this ring a bell with
> anybody?
Do you have APM enabled? Do you have the "broken statclock" option
en
>
> :Yeah, I know about -alldirs... The problem was that we had customers who
> :wanted us to export their home directories, and unless I gave them their own
> :filesystem, I couldn't restrict it in the manner i wanted. :)
> :
> :Just checking to see that I wasn't missing a way to do this. :)
> :
> IIRC, mount permissions (i.e., what IP addresses, root UID mangling, etc)
> are set per filesystem. Given a filesystem structure like this:
>
> > df
> Filesystem 1K-blocks UsedAvail Capacity Mounted on
> /dev/da0s1a127023271518971123%/
> /dev/ccd0c8321099 23
:Yeah, I know about -alldirs... The problem was that we had customers who
:wanted us to export their home directories, and unless I gave them their own
:filesystem, I couldn't restrict it in the manner i wanted. :)
:
:Just checking to see that I wasn't missing a way to do this. :)
:
:Kevin
I'
>
> You misunderstood me. The problem you have is the fact that NFS exports
> are usually limited to the physical mount point of the filesystem being
> exported. Thus it thinks that /var above is the same as /, or that
> /var/tmp is the same as /var if both happen to be in the
IIRC, mount permissions (i.e., what IP addresses, root UID mangling, etc)
are set per filesystem. Given a filesystem structure like this:
> df
Filesystem 1K-blocks UsedAvail Capacity Mounted on
/dev/da0s1a127023271518971123%/
/dev/ccd0c8321099 2391764 526364
:You sure about you can export a directory multiple times? I can't even
:export two directories under the same filesystem.
:
:su-2.03# mount
:/dev/wd0s1a on / (NFS exported, local, noatime, soft-updates, writes: sync 3945 async
:1317317)
:procfs on /proc (local)
:su-2.03# cat /etc/exports
:
:/var
>
> To export a single filesystem multiple times, *all* of the attributes must
> be the same. If they aren't the only person you are fooling is yourself,
> since once a filesystem is NFS exported, it is open to the world.
>
> anyway the syntax for what you want is:
>
> /var /var/mails
To export a single filesystem multiple times, *all* of the attributes must
be the same. If they aren't the only person you are fooling is yourself,
since once a filesystem is NFS exported, it is open to the world.
anyway the syntax for what you want is:
/var /var/mail some.machine
--
David C
> Well, theoretically there is nothing wrong going on since you can mount
> things on top of an NFS directory. Mount only complains about
> duplicate normal partition mounts because it can't open the buffered
> block device the second time. NFS doesn't care how many times a
>
Fine , take it up with the kerberos group over at MIT -- it is hard
to believe that they would not have patches for X11R6 and
proper protocol.
> Amancio Hasty <[EMAIL PROTECTED]> writes:
> > I would starrt by looking at the api and making the mods to X11R6
>
> No, the protocol used in the
:I'm a little bit astonished that's now possible to mount via nfs
:several times at the same mountpoint with freebsd nfs clients:
:
:normal behaviour (Linux 2.2, Solaris):
:--
:
:magma:/ # mount magma:/cdrom /mnt
:magma:/ # mount magma:/cdrom /mnt
:mount: magma:
In message <[EMAIL PROTECTED]> "Daniel C. Sobral" writes:
: > Jordan exists.
:
: Don't go there. This whole existance-of-perl-scripts thingy is
: dangerous territory.
I've met jordan's cats, does that count :-)
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-cu
Amancio Hasty <[EMAIL PROTECTED]> writes:
> I would starrt by looking at the api and making the mods to X11R6
No, the protocol used in the X11R6 code is wrong. You would need to
design and implement a new one.
> and if you can do a net search on xdm and kerberos -- there is an
> X11R6 xdm for
I would starrt by looking at the api and making the mods to X11R6
and if you can do a net search on xdm and kerberos -- there is an
X11R6 xdm for kerberos 5 floating around.
--
Amancio Hasty
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-cu
>It seems that our new boot blocks doesn't like the taste of disks
>prepared according to the meagre information we have in the handbook.
>
>The following script seems to DTRT for me, and should really be
>either integrated into a "fdisk -A" flag or maybe as a stand alone
>script. Either way: man
Mark Murray <[EMAIL PROTECTED]> writes:
> far as I know, X11R6.n K5 is broken, as it is based on a very
> early beta of MIT K5.
To many knowledge, the code that's in X11R6 is still based on a really
old beta of MIT k5 and it would take some work to get it to work with
some modern code. And besid
On Sat, 31 Jul 1999, Jeroen Ruigrok/Asmodai wrote:
>
> No, just options DDB.
> This bt was obtained after doing gdb -k kernel.0 vmcore.0
> I still have the DDB trace on paper which I can type in if needed/wanted.
>
> > What you do with the results depends a lot on what you find. On the
> > who
On Sun, Aug 01, 1999 at 09:55:56PM +0200, Mark Murray wrote:
> I have kerberos5 waiting in the wings for a compatible version
> (Heimdal will be coming out Real Soon Now).
>
> In the meanwhile - Kerberos 5 is available as a port, and as
> far as I know, X11R6.n K5 is broken, as it is based on a v
In message <[EMAIL PROTECTED]>, Nik Clayton writes:
>On Sun, Aug 01, 1999 at 04:19:52PM +0200, Poul-Henning Kamp wrote:
>> The following script seems to DTRT for me, and should really be
>> either integrated into a "fdisk -A" flag or maybe as a stand alone
>> script. Either way: manpage & handboo
On Sun, Aug 01, 1999 at 04:19:52PM +0200, Poul-Henning Kamp wrote:
> The following script seems to DTRT for me, and should really be
> either integrated into a "fdisk -A" flag or maybe as a stand alone
> script. Either way: manpage & handbook needs updated too.
What, specifically, is wrong with
I have kerberos5 waiting in the wings for a compatible version
(Heimdal will be coming out Real Soon Now).
In the meanwhile - Kerberos 5 is available as a port, and as
far as I know, X11R6.n K5 is broken, as it is based on a very
early beta of MIT K5.
M
> Hi !
>
> Have a Cisco Router and want
Hi !
Have a Cisco Router and want to play a bit with Kerberos support.
As far as I know Cisco router support Kerberos 5 and I'm not sure,
if it works with Kerberos 4 as well.
So I though that it might perhaps be a good idea to re-build my
FreeBSD 4.0 system and X11 with Kerberos5 support.
Is i
I'm a little bit astonished that's now possible to mount via nfs
several times at the same mountpoint with freebsd nfs clients:
normal behaviour (Linux 2.2, Solaris):
--
magma:/ # mount magma:/cdrom /mnt
magma:/ # mount magma:/cdrom /mnt
mount: magma:/cdrom a
On Sun, 1 Aug 1999, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote:
> I'm messing around with the latest mesa and have discovered (suprise)that our
> assembler doesn't support 3dnow instructions. Are there any plans to update to
> a version of binutils that does? Linux's stuff appears
It seems that our new boot blocks doesn't like the taste of disks
prepared according to the meagre information we have in the handbook.
The following script seems to DTRT for me, and should really be
either integrated into a "fdisk -A" flag or maybe as a stand alone
script. Either way: manpage
Hi,
before the newbus changes I used to get a ton of:
Sorry, read DMA channel unavailable.
Now playing mp3's under CURRENT from yesterday I only get about three of
those messages per 10 minutes.
That's better ;)
cheers!
--
Jeroen Ruigrok van der Werven asmodai(at)wx
37 matches
Mail list logo
