Freebsd 8 stable amd64
It mounts different file systems by NFS (with locking) on a
data server directly connected (gigabit) to the server
Apache running in a several jails on those nfs folders.
Now and then I get huge slow-down. When I look in the logs
I get thousand of lines like these:
Mar
Nate Eldredge wrote:
On SysV, you can get BSD-type behavior by setting the sgid bit on the
directory in question, e.g. chmod g+s dir. Then new files will
inherit their group from the directory. I suspect this will work on
FreeBSD/ZFS too even though chmod g+s on a directory is undocumented.
Adrian Penisoara wrote:
Is the ownership of the new file decided by the open() syscall or by
the filesystem layer ?
On a superficial lookup through the sources it appears a filesystem
layer choice...
Which of the following would then be the best option (also taking POLA
into account):
* leave
I don't know if this is the correct list to discuss this matter, if not
I apologize in advance.
I've always understood group ownership as a way to allow members of
the same group to operate on files / folders which belong to that group,
while leaving out others.
Let's suppose to have a directory
I don't know if this is the correct list to discuss this matter, if not
I apologize in advance.
I've always understood group ownership as a way to allow members of
the same group to operate on files / folders which belong to that group,
while leaving out others.
Let's suppose to have a directory
I don't know if this is the correct list to discuss this matter, if not
I apologize in advance.
I've always understood group ownership as a way to allow members of
the same group to operate on files / folders which belong to that group,
while leaving out others.
Let's suppose to have a directory
I've installed a 3ware 9500 sata controller with 4 1TB disks
in raid 5.
Apart from the usual wrong geometry warning the starting configuration
is ok: I create a single partition with the default labels plus a /usr/home
label with takes most of the disk space (about 2.7TB).
When I reboot the
Bjoern A. Zeeb wrote:
Since the multi-ip jail feature isn't yet part of the base system
(why???)
I was searching the internet for a suitable patch to apply manually.
I couldn't find any. The one I found didn't apply cleanly to a 7 system.
Can any of you point me to a working multi-ip jail
Since the multi-ip jail feature isn't yet part of the base system (why???)
I was searching the internet for a suitable patch to apply manually.
I couldn't find any. The one I found didn't apply cleanly to a 7 system.
Can any of you point me to a working multi-ip jail patch?
Thanks in advance.
Eygene Ryabinkin wrote:
Hi Eygene, I could only now test the new port and it works. Now it's
just a matter
of fine-tuning it (i.e. I'd like to increase the acceleration of the
pointer)
Thanks for the great job!
___
freebsd-hackers@freebsd.org
Eygene Ryabinkin wrote:
Giulio, good day.
Long time ago, in December 2007, we discuissed the problem with
Synaptics touchpad driver for FreeBSD in the freebsd-hackers list.
I had corrected the problem and driver seems to work, but I need
more testing with real hardware. I had opened the
Eygene Ryabinkin wrote:
Please, try again if you have some spare time.
Ok. Now the server starts, but the mouse pointer isn't moving...
in the ServerLayout section I have this:
#InputDevice Mouse1 CorePointer
InputDevice Keyboard1 CoreKeyboard
InputDevice Synaptics_Touchpad
Eygene Ryabinkin wrote:
in the ServerLayout section I have this:
#InputDevice Mouse1 CorePointer
InputDevice Keyboard1 CoreKeyboard
InputDevice Synaptics_TouchpadCorePointer
And if you'll try
'InputDevice Synaptics_Touchpad CorePointer SendCoreEvents'?
Nothing
Eygene Ryabinkin wrote:
Aargh, this is the funny thing: you have no devices that are handled
by the 'mouse' driver. And Xorg automatically adds one.
Please, uncomment your 'Mouse1' device inside ServerLayout, start
moused and try again. The 'default pointer' should disappear.
And probably
Doesn't work. Both with linux-firefox and native firefox it either hangs or
crashes.
I tried this site: http://www.patek.com
os: 7.0 beta 4 amd64
Hope it helps...
___
freebsd-hackers@freebsd.org mailing list
Donnie wrote:
On Dec 12, 10:51 am, Giulio Ferro [EMAIL PROTECTED] wrote:
Unfortunately those settings are already specified in /e
tc/X11/xorg.conf in the
section InputDevice for thetouchpad.
If you look in the /usr/ports/x11-drivers/synaptics/pkg-message it's all
already there
I had
Eygene Ryabinkin wrote:
Giulio, good day.
Good day.
--
(II) Synaptics touchpad driver version 0.14.6 (1406)
Synaptics_Touchpad no synaptics event device found (checked 10 nodes)
Synaptics_Touchpad The /dev/input/event* device nodes seem to be missing
(EE) xf86OpenSerial: No
Hi,
I just wanted to report that the synaptics touchpad driver
(/usr/ports/x11-drivers/synaptics)
doesn't work in my configuration:
freebsd 7 beta4 - amd64 - synaptics-0.14.6_2
I set hw.psm.synaptics_support=1 in /boot/loader.conf,
disable moused, change /etc/X11/xorg.conf according to the
Bjoern A. Zeeb wrote:
On Mon, 26 Nov 2007, Baldur Gislason wrote:
Hi,
And since we're on this subject... is it possible to do IPSEC over UDP
tunnels in FreeBSD now? I have a couple of networks with dumb NAT and
need a way to tunnel out of them in a reliable manner.
only with the patch, not
I've noticed that in the kernel configuration IPSEC_ESP disappeared
from the options. It says that you just need device crypto and IPSEC.
Does this mean that with crypto and IPSEC I have all I need to treat
ESP like the old IPSEC_ESP option?
I'm having some problems right now setting up a vpn
VANHULLEBUS Yvan wrote:
I'm having some problems right now setting up a vpn to complete phase 2,
(the error is no proposal chosen).
Since ipsec-tools uses the facilities in the kernel, I want to make sure
that the
kernel provides everything racoon needs...
That really sounds
Sam Fourman Jr. wrote:
if there was a bounty system for FreeBSD I would pledge $100 USD for
work that would help amd64 nvidia... heck I would even settle for
someone that wants to take lead and setup a paypal collection.
Sam Fourman Jr.
I completely agree. Some guy here went as far as
Remko Lodder wrote:
Ok, let's see how we can fund this project. First of all the interested
developers
should assess the bulk of work to do and how long it will take them to
complete
it. Then we can think about how many people are interested in opening their
wallet to see it come into
What is the status of the work required by the vidia guys
so that they can code their driver for amd64 architecture?
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to
Alastair Hogge wrote:
On Thu, 27 Sep 2007 18:15:52 Giulio Ferro wrote:
What is the status of the work required by the vidia guys
so that they can code their driver for amd64 architecture?
Hey,
There is no driver.
I sort of surmised that already...
Status can be found here:
http
Sam Fourman Jr. wrote:
There is no driver.
I sort of surmised that already...
So, we are still years away from seeing a working nvidia driver,
by the look of it...
I guess what I am confused about, is there someone actively working on
the Nvidia requests, or does a capable
Remko Lodder wrote:
without that, do notice that people do this in their own free time, which
could either take some time before it's there, or might not be interesting
enough to work on currently (because of other things at work, private life
other code etc).
To say that there isn't enough
Dag-Erling Smørgrav wrote:
Giulio Ferro [EMAIL PROTECTED] writes:
To say that there isn't enough interest in the nvidia driver would be
outrageous.
No, it would be true.
From the slew of messages on the subject (on the nvidia forum, for example)
it wouldn't seem to be so true...
I
Hi,
I'm trying your driver in my sony AR41S notebook:
pciconf -lv
...
device = '3945ABG Intel 3945ABG Wireless LAN controller'
...
[EMAIL PROTECTED]:3:0: class=0x060700 card=0x9016104d chip=0x8039104c rev=0x00
hdr=0x02
uname -a
... 7.0-CURRENT FreeBSD 7.0-CURRENT #3 : Tue Aug 21 12:41:59 CEST
29 matches
Mail list logo
