Hello,
I realize the difficulties in trying to use quotas on the _host_ system to
limit the size of jails on the host system - userid mapping, etc. This is
not what I am asking.
I wonder, is it possible for the root user of a jail to set quotas
_inside_ her jail for users _inside_ her jail ?
On Fri, 30 Aug 2002, Patrick Thomas wrote:
I wonder, is it possible for the root user of a jail to set quotas
_inside_ her jail for users _inside_ her jail ? Can anyone simply confirm
or deny that this is possible ?
You can't. You have to set quota from the host machine over something like
You might get it to run under Linux emulation... I've never tried it
though.
The VMWare documentation for even version 3.1 indicates FreeBSD support
as a client OS only.
I assume you knew that, but I wanted to save you the trouble of a
possible wild-goose-chase id you didn't.
Good luck!
On Wed, Aug 28, 2002 at 11:09:57AM -0400, Richard Stanaford wrote:
The VMWare documentation for even version 3.1 indicates FreeBSD support
as a client OS only.
If you check the small print, that's what it says.
Having said that though, I have had 3.0 running as well as 2.0, under
-STABLE,
Of course we run Vmware 2 under emulation. So vmware 3 MUST be run under
emulation.
As has been said before, it probably runs but the setup
program looks for too many linux specifics and doesn't generate a good
config file.
It just takes someone to figure out what it needs.
On Wed, 28 Aug 2002,
Terry Lambert writes:
Wilko Bulte wrote:
I knew not to recommend the Alpha because it is limited to 2G
of physical memory.
?
FreeBSD is limited to using 2G of whatever you have in the Alpha.
Which is a deficiency that has been debated a number of times,
IIRC it
In message [EMAIL PROTECTED],
Patrick
Thomas writes:
And more important;y, does anyone know _why_ it is happening and what it
means for a system affected ?
I had this occur once. As it turned out, one of the clocks in the clock
chip was hooped. Replacing the motherboard fixed the problem.
Another interesting processor family is the AMD x86-64 ClawHammer.
I do not know the progress the FreeBSD/x86-64 project. I would imagine
the major difficulty will be getting a running compiler.
I just wish AMD added an 8K page size so the Page Table Maps did not
eat so much memory.
--mark
Ut-oh. Time for a rant...
mark tinguely wrote:
Another interesting processor family is the AMD x86-64 ClawHammer.
I do not know the progress the FreeBSD/x86-64 project. I would imagine
the major difficulty will be getting a running compiler.
Actually, the major difficulty is getting a box,
Has anyone got this to work yet? Is it something that will get fixed with
fbsd, or will it tack a bios upgrade from intel?
I was wondering if there is a way to just hardcode this value for the time
being, I know that my box has two Intel SE7500CW2 CPUs in it. Could this
whole problem be
Has anyone got this to work yet? Is it something that will get fixed with
fbsd, or will it tack a bios upgrade from intel?
I was wondering if there is a way to just hardcode this value for the time
being, I know that my box has two Intel SE7500CW2 CPUs in it. Could this
whole problem be
On Fri, Aug 30, 2002 at 12:41:54AM -0700, Patrick Thomas wrote:
I wonder, is it possible for the root user of a jail to set quotas
_inside_ her jail for users _inside_ her jail ? Can anyone simply confirm
or deny that this is possible ?
Yes, it is possible. The following procedure
Peter Wemm wrote:
Lars Eggert wrote:
We just got a bunch of Dell machines that have this controller as well.
Any news about support in sym?
No, you want the 'mpt' driver that Matt Jacob recently committed. The 1030
has nothing in common with sym.
I backported the mpt driver from -STABLE
On Fri, Aug 30, 2002 at 12:11:12 -0700, Lars Eggert wrote:
Peter Wemm wrote:
Lars Eggert wrote:
We just got a bunch of Dell machines that have this controller as well.
Any news about support in sym?
No, you want the 'mpt' driver that Matt Jacob recently committed. The 1030
has
Hi,
Is there some function using which I can copy data from the Kernel Virtual
Space to a pinned Physical Address Page.
Thanx,
Pavan Balaji,
Intel Corporation
Email: [EMAIL PROTECTED]
Only the Paranoid Survive -- Andy Grove
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
On Fri, 30 Aug 2002, Balaji, Pavan wrote:
Hi,
Is there some function using which I can copy data from the Kernel Virtual
Space to a pinned Physical Address Page.
Not as such, though there are plenty of places that do such a thing. The
answer is always to map the physical page somewhere
On Fri, Aug 30, 2002 at 12:50:14 -0700, Lars Eggert wrote:
Kenneth D. Merry wrote:
Did you also backport rev 1.35 and 1.36 of scsi_all.c?
You may need that as well.
Good catch, I missed that file. After applying that patch, they now seem
to be detected correctly:
da0 at mpt1 bus 0
I'm a little bit confused about this vmapbuf() thing. This is what I think,
correct me if I'm wrong.
I have this User Virtual address, userbuf -- associated to physadd
Now, I do vmapbuf(physadd), and I get a Kernel Virtual Address associated to
this physadd. Now, I write to this Kernel Virtual
On Fri, 30 Aug 2002, Balaji, Pavan wrote:
I'm a little bit confused about this vmapbuf() thing. This is what I think,
correct me if I'm wrong.
I have this User Virtual address, userbuf -- associated to physadd
Now, I do vmapbuf(physadd), and I get a Kernel Virtual Address associated
On Fri, 30 Aug 2002, Balaji, Pavan wrote:
I'm a little bit confused about this vmapbuf() thing. This is what I think,
correct me if I'm wrong.
I have this User Virtual address, userbuf -- associated to physadd
Now, I do vmapbuf(physadd), and I get a Kernel Virtual Address associated
Thanx. It's nearly done. I just need to know two more small things.
physio() requires a dev_t as a parameter. What do I give in over here? I
can't give NULL, cause it does use it for some stuff in the function
definition.
Also, the only other parameters to physio() are the uio and the ioflag
On Fri, 30 Aug 2002, Balaji, Pavan wrote:
Thanx. It's nearly done. I just need to know two more small things.
physio() requires a dev_t as a parameter. What do I give in over here? I
can't give NULL, cause it does use it for some stuff in the function
definition.
I wasn't suggesting
While we're on the topic of vmapbuf:
I have a kernel module that maps two 64k chunks of user memory into the kernel
using the same set of steps that cam_periph_mapmem uses. However, I inevitably
get the following panic after running the code for a bit:
Aug 30 14:55:26 testhost /kernel: panic:
[ cc list trimmed ]
[ I guess I got unsubscribed from hackers, so I missed the front end of
this. Every time I try and sort out majordomo at FreeBSD, it fails for
me (like trying ask what am I subscribed to) and all requests to
postmaster seem to bitbucket. Oh well. ]
This isn't good. Part of
Oh, yes- let me know if you've upgraded to the latest LSI 53c1030 f/w
(that'd 1.0.12).
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Matthew,
Matthew Jacob wrote:
This isn't good. Part of it just the chip later presenting the
completion for a command that I had already timed out. But basically,
we never got a response to a command, so we timed it out. Later, the
chip presented us with the comamnd as being done- and being
Hello hackers...
Syscall number (when catching syscall) in -STABLE in placed in:
p-p_md.md_regs-tf_eax (for i386)
p-p_md.md_tf[FRAME_V0] (for alpha)
But as I see, in -CURRENT even p_md has diffrent type.
Could someone can give me equivalent place (where syscall number is
mark tinguely wrote:
Another interesting processor family is the AMD x86-64 ClawHammer.
I do not know the progress the FreeBSD/x86-64 project. I would imagine
the major difficulty will be getting a running compiler.
Nope, the compiler is already pretty robust.
I just wish AMD added an 8K
On Fri, 30 Aug 2002, Lars Eggert wrote:
Matthew,
Matthew Jacob wrote:
This isn't good. Part of it just the chip later presenting the
completion for a command that I had already timed out. But basically,
we never got a response to a command, so we timed it out. Later, the
chip
Matthew Jacob wrote:
In some sense this sounds like an interrupt issue. The timeout is 30
seconds, and it looks like we give up on the command but it's done
instantaneously afterwards.
Hm. I don't know much about the PCI code, so maybe what follows won't
make any sense and may not be
30 matches
Mail list logo
