On Saturday, 19 November 2005 at 21:37:03 -0600, Stephen Montgomery-Smith wrote:
I recently upgraded from stable-6 of Nov 4 to stable-6 of today on
my Dell Latitude D800 Laptop, and suddenly the response of the
touchpad mouse and keyboard was bery bad.
Heh. I saw the subject line and thought
On Nov 19, 2005, at 19:43 , Joseph Koshy wrote:
AFAICT cross-compiling amd64 on a i386 machine isn't supported
yet. I ran into a similar problem when I upgraded an i386
machine to amd64. I thought I could just set CPUTYPE=athlon-64
and buildworld would do the right thing. Apparently not.
On Nov 20, 2005, at 09:50 , Eirik Øverby wrote:
On Nov 19, 2005, at 19:43 , Joseph Koshy wrote:
AFAICT cross-compiling amd64 on a i386 machine isn't supported
yet. I ran into a similar problem when I upgraded an i386
machine to amd64. I thought I could just set CPUTYPE=athlon-64
and
Hi,
I got this panic on freshly installed FreeBSD 6. I did this df -h and
noticed that /mnt/oldroot/home is somewhat mangled. The /mnt/oldroot is
root of FreeBSD 4.11 system. I successfully copied some settings and all
user accounts from that /mnt/oldroot/home earlier today. This is what I
did
Hello,
whilst copying files from SD-Card via usb card reader
with mcopy, I encountered the following error with
FreeBSD 6.0-STABLE from 15.11.2005. Even though the
device was reattached automatically (nice improvement, btw!),
this error is very annoying.
Is this behaviour already known, or
On Sun, 20 Nov 2005, Michael Voucko wrote:
Berkeley-derived kernels do not allow a broadcast datagram to be
fragmented. If the size of an IP datagram that is being sent to a
broadcast address exceeds the outgoing interface MTU, EMSGSIZE is
returned (pp. 233?234 of TCPv2). This is a policy
Hello,
I am slightly unsatisfied with user rights management,
especially with usb-devices, but also with access to
cd/dvd-burners for the following reason:
I'd like to be able to allow access to burners that
are accessed as scsi-devices (via atapicam) for some
users, but for that to work it is
thanks for replying.
No, I actually did not have gnome installed, as I'm running fluxbox but may be
I had some sub-gnome ports installed that I didn't notice and that are
responsible for the build failure.
May be I should uninstall all *gnome* ports and restart.
Best regards,
Didier
-
On Sun, Nov 20, 2005 at 02:16:24PM +0100, Holger Kipp wrote:
Is there an easy way to name the devices a user might
be allowed to access rw, without compromising the system?
I don't want to give operator group to these users,
and I don't want to blindly allow access to some
da- or
Dear Roland,
thank you very much for your answer.
On Sun, Nov 20, 2005 at 03:04:22PM +0100, Roland Smith wrote:
On Sun, Nov 20, 2005 at 02:16:24PM +0100, Holger Kipp wrote:
Is there an easy way to name the devices a user might
be allowed to access rw, without compromising the system?
I
On Sun, Nov 20, 2005 at 05:37:36PM +0100, Holger Kipp wrote:
Dear Roland,
thank you very much for your answer.
On Sun, Nov 20, 2005 at 03:04:22PM +0100, Roland Smith wrote:
On Sun, Nov 20, 2005 at 02:16:24PM +0100, Holger Kipp wrote:
Is there an easy way to name the devices a user
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I have a small machine setup to act as simple network gateway.
I have one wireless and one wired interfaces without IP configuration
on them, and they are added as if_bridge(4) members.
When i issue arp -na command on the machine i get this:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Niki Denev wrote:
Hello,
I have a small machine setup to act as simple network gateway.
I have one wireless and one wired interfaces without IP configuration
on them, and they are added as if_bridge(4) members.
When i issue arp -na command on
On Sun, Nov 20, 2005 at 06:47:54PM +0100, Roland Smith wrote:
On Sun, Nov 20, 2005 at 05:37:36PM +0100, Holger Kipp wrote:
Dear Roland,
Is there an easy way to name the devices a user might
be allowed to access rw, without compromising the system?
I don't want to give operator group
Strange indeed.
On a 1750 with bge's:
475 mbufs in use
501/25600 mbuf clusters in use (current/max)
0/3/6656 sfbufs in use (current/peak/max)
1120 KBytes allocated to network
0 requests for sfbufs denied
0 requests for sfbufs delayed
0 requests for I/O initiated by sendfile
100 calls to protocol
On Sun, Nov 20, 2005 at 07:50:44PM +0200, Niki Denev wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I have a small machine setup to act as simple network gateway.
I have one wireless and one wired interfaces without IP configuration
on them, and they are added as
On Sun, Nov 20, 2005 at 07:26:38PM +0100, Holger Kipp wrote:
Doesn't matter that you get UNKNOWN. It _will_ work with sane without
access to /dev/usb*. It does here.
This is an Epson Perfection 1260. Don't ask what the 'Perfection' stands
for. Anyway, this is in fact a Plustek, so I have
Hello,
I'm running 6.0-STABLE and see that the option removable_interfaces is not
used in any config script.
/etc# grep -r removable_interfaces *
defaults/rc.conf:removable_interfaces=# Removable network
interfaces for /etc/pccard_ether.
What is is the use of it now?
I can't
Hi,
Since I upgraded from 6.0-release to 6.0-stable on Nov 10th, my laptop
hangs for about 1-2 seconds everytime a battery monitoring tool asks for
the cmbat battery status. My laptop is a Dell Precision M70 and shares
its motherboard with many other Dell laptops. I can reproduce the
problem
On 11/20/05, Pierre-Luc Drouin [EMAIL PROTECTED] wrote:
Hi,
Since I upgraded from 6.0-release to 6.0-stable on Nov 10th, my laptop
hangs for about 1-2 seconds everytime a battery monitoring tool asks for
the cmbat battery status. My laptop is a Dell Precision M70 and shares
its motherboard
On Sun, Nov 20, 2005 at 10:14:37AM +0100, Eirik ?verby wrote:
On Nov 20, 2005, at 09:50 , Eirik ?verby wrote:
On Nov 19, 2005, at 19:43 , Joseph Koshy wrote:
AFAICT cross-compiling amd64 on a i386 machine isn't supported
yet. I ran into a similar problem when I upgraded an i386
On Wed, Nov 16, 2005 at 05:57:12PM +0100, Roland Smith wrote:
However, when I insert a CF card with normal partioning I need /dev/da0s1,
and this is not present in the /dev filesystem because the partition table
has not been read.
snip
The only way I can see to *force* the superblock to
Hi. I have an error after upgrade to FreeBSD 6.0-RELEASE in time of booting:
ad1: req=0xc2998000 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER
Will Robinson !!
swap_pager: indefinite bufobj: 0 blkno: 3 size: 4096
then it's just halt.
But not everytime, sometime it's booting
On Sun, 20 Nov 2005 21:04:59 +
Brian Candler [EMAIL PROTECTED] wrote:
On Wed, Nov 16, 2005 at 05:57:12PM +0100, Roland Smith wrote:
However, when I insert a CF card with normal partioning I
need /dev/da0s1, and this is not present in the /dev filesystem
because the partition table
Hi, we are having a number of issues with 6.0-Release.
Our setup: We have ~40 machines in a development test environment,
ranging from P5/150Mhz/32M ram/IDE, PII Celerons, P3, P4, single and
dual processor setups.
Issue 1: Can't install on a Pentium P5 class machine:
The install panics when
Hi all!
I've seen this error some 300 times
at the beginning of boot process.
System goes up and works with no issue.
It is nforce3 250 with amd64, 6.0 os.
Using sysctl, I've found the line:
dev.acpi_perf.0.%driver: acpi_perf
In bios acpi apic is turned off, due to
acpi errors from 5.4 era. Kernel
26 matches
Mail list logo
