freebsd-questions Digest, Vol 418, Issue 7
kwel kwel
kwel_mihai at yahoo.com
Wed Jun 6 11:36:27 UTC 2012
Please remove my email from your database i don't want to receive any other mail from you plzz thanks !
________________________________
From: "freebsd-questions-request at freebsd.org" <freebsd-questions-request at freebsd.org>
To: freebsd-questions at freebsd.org
Sent: Wednesday, June 6, 2012 1:39 PM
Subject: freebsd-questions Digest, Vol 418, Issue 7
Send freebsd-questions mailing list submissions to
freebsd-questions at freebsd.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
or, via email, send a message with subject or body 'help' to
freebsd-questions-request at freebsd.org
You can reach the person managing the list at
freebsd-questions-owner at freebsd.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-questions digest..."
Today's Topics:
1. Re: Is this something we (as consumers of FreeBSD) need to be
aware of? (Daniel Feenberg)
2. Re: Is this something we (as consumers of FreeBSD) need to be
aware of?] (Jerry)
3. Re: Is this something we (as consumers of FreeBSD) need to be
aware of? (Jerry)
4. implementing ipv6 into my ipfw ruleset... (Jason Usher)
5. Re: how do I fix this? (Gary Kline)
6. Curiousity ? (Geir Svalland)
7. Re: Is this something we (as consumers of FreeBSD) need to be
aware of? (Daniel Feenberg)
8. Re: /usr/bin/find - binary operands howto (grarpamp)
9. FreeBSD9 - I can't get my mouse to work (Walter Hurry)
10. Re: FreeBSD9 - I can't get my mouse to work (Bernt Hansson)
11. Re: FreeBSD9 - I can't get my mouse to work (Walter Hurry)
12. Re: FreeBSD9 - I can't get my mouse to work (Warren Block)
13. Re: Is this something we (as consumers of FreeBSD) need to be
aware of? (Chris Hill)
14. Re: Is this something we (as consumers of FreeBSD) need to be
aware of? (Mike Jeays)
15. Re: Is this something we (as consumers of FreeBSD) need to be
aware of? (Waitman Gobble)
16. Re: FreeBSD9 - I can't get my mouse to work (Walter Hurry)
17. Re: FreeBSD9 - I can't get my mouse to work (Scott Ballantyne)
18. Re: FreeBSD9 - I can't get my mouse to work (Erich)
19. Re: FreeBSD9 - I can't get my mouse to work (Waitman Gobble)
20. Re: FreeBSD9 - I can't get my mouse to work (Erich Dollansky)
21. Re: Is this something we (as consumers of FreeBSD) need to be
aware of? (Matthew Seaman)
22. Re: Is this something we (as consumers of FreeBSD) need to be
aware of? (Bruce Cran)
23. isc-dhcpd - logging client transactions (Ewald Jenisch)
24. Re: Is this something we (as consumers of FreeBSD) need to be
aware of? (Matthew Seaman)
25. Re: Is this something we (as consumers of FreeBSD) need to be
aware of? (Mehmet Erol Sanliturk)
26. Re: Is this something we (as consumers of FreeBSD) need to be
aware of? (Julian H. Stacey)
27. Re: Is this something we (as consumers of FreeBSD) need to be
aware of? (Jerry)
28. Re: Is this something we (as consumers of FreeBSD) need to be
aware of? (Bruce Cran)
----------------------------------------------------------------------
Message: 1
Date: Tue, 5 Jun 2012 17:00:14 -0400 (EDT)
From: Daniel Feenberg <feenberg at nber.org>
Subject: Re: Is this something we (as consumers of FreeBSD) need to be
aware of?
To: Polytropon <freebsd at edvax.de>
Cc: Kurt Buff <kurt.buff at gmail.com>, FreeBSD Questions
<questions at freebsd.org>
Message-ID: <Pine.GSO.4.64.1206051653120.5642 at nber6>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
On Tue, 5 Jun 2012, Polytropon wrote:
> On Tue, 5 Jun 2012 11:19:26 -0700, Kurt Buff wrote:
>> UEFI considerations drive Fedora to pay MSFT to sign their kernel binaries
>> http://cwonline.computerworld.com/t/8035515/1292406/565573/0/
>
> I may reply with another link:
> http://mjg59.dreamwidth.org/12368.html
>
I have a pretty basic question that probably displays some ignorance...
Does the loader need to be signed? Once signed, can it load anything, or
just things MS has approved? If MS signs the kernel, can the kernel run
anything, or just things MS has approved? If RH has a signed kernel, do
they have to sign all the userland programs that run under that kernel?
Can users sign programs compiled from source?
If MS only has to sign the first link in the chain, then the $99
certificate is not really a problem except for the pure of heart. If MS or
someone else has to sign all the way down to the userland binaries, then
users of FreeBSD will have to turn off secure boot in CMOS, and it will
lose a few users. But I can't tell from the discussions mentioned above.
Either way, I don't think it will destroy FreeBSD, or Linux, but I would
be interested anyway.
Daniel Feenberg
------------------------------
Message: 2
Date: Tue, 5 Jun 2012 17:20:46 -0400
From: Jerry <jerry at seibercom.net>
Subject: Re: Is this something we (as consumers of FreeBSD) need to be
aware of?]
To: FreeBSD <freebsd-questions at freebsd.org>
Message-ID: <20120605172046.2571e964 at scorpio>
Content-Type: text/plain; charset=UTF-8
On Tue, 5 Jun 2012 13:19:00 -0700
Colin Barnabas articulated:
>History show us that _everything_ will eventually run *nix.
Perhaps, but *nix will not run everything.
>Take a look at the Sony PS3 debacle. After Sony yanked support for
>installing other OS's, the community ripped apart their
>hypervisor in a matter of months. If these boot keys do gain any
>momentum, sooner than later the community with poke holes in the
>system.
Which, depending on how the end user or his flunky "poke holes" in the
system, may allow vendors to disallow warranty claims.
The question that I have not seen answered in this thread is what
FreeBSD intents to do. From what I have seen, most FreeBSD users do not
use the latest versions of most hardware, so it may be a while before
its user base is even effected.
--
Jerry ♔
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__________________________________________________________________
------------------------------
Message: 3
Date: Tue, 5 Jun 2012 18:10:55 -0400
From: Jerry <jerry at seibercom.net>
Subject: Re: Is this something we (as consumers of FreeBSD) need to be
aware of?
To: FreeBSD <freebsd-questions at freebsd.org>
Message-ID: <20120605181055.4af65fdb at scorpio>
Content-Type: text/plain; charset=UTF-8
On Tue, 5 Jun 2012 17:00:14 -0400 (EDT)
Daniel Feenberg articulated:
>On Tue, 5 Jun 2012, Polytropon wrote:
>
>> On Tue, 5 Jun 2012 11:19:26 -0700, Kurt Buff wrote:
>>> UEFI considerations drive Fedora to pay MSFT to sign their kernel
>>> binaries
>>> http://cwonline.computerworld.com/t/8035515/1292406/565573/0/
>>
>> I may reply with another link:
>> http://mjg59.dreamwidth.org/12368.html
>
>I have a pretty basic question that probably displays some ignorance...
>
>Does the loader need to be signed? Once signed, can it load anything,
>or just things MS has approved? If MS signs the kernel, can the kernel
>run anything, or just things MS has approved? If RH has a signed
>kernel, do they have to sign all the userland programs that run under
>that kernel? Can users sign programs compiled from source?
>
>If MS only has to sign the first link in the chain, then the $99
>certificate is not really a problem except for the pure of heart. If
>MS or someone else has to sign all the way down to the userland
>binaries, then users of FreeBSD will have to turn off secure boot in
>CMOS, and it will lose a few users. But I can't tell from the
>discussions mentioned above. Either way, I don't think it will destroy
>FreeBSD, or Linux, but I would be interested anyway.
I thought this URL <http://mjg59.dreamwidth.org/12368.html> also shown
above, answered that question.
--
Jerry ♔
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__________________________________________________________________
------------------------------
Message: 4
Date: Tue, 5 Jun 2012 15:12:06 -0700 (PDT)
From: Jason Usher <jusher71 at yahoo.com>
Subject: implementing ipv6 into my ipfw ruleset...
To: freebsd-questions at freebsd.org
Message-ID:
<1338934326.88519.YahooMailClassic at web122502.mail.ne1.yahoo.com>
Content-Type: text/plain; charset=us-ascii
I have a fairly simple ipfw ruleset, which looks like:
100 allow tcp from any to any established
110 allow icmp from any to any icmptypes 0,3,8,11
120 deny icmp from any to any
130 allow ip from any to any via lo0
200 allow udp from me to any 53
210 allow udp from any 53 to me
220 allow udp from any to me 33433-33499
230 allow tcp from any to 82.197.184.219 22,80,443 setup
65000 deny log ip from any to me
65001 deny log ip from any to me6
What I am wondering is, am I blocking all ipv6 traffic by not explicitly allowing ipv6 in (for the established rule 100, icmp rule 110, and the entire block of 200-230) ?
Or, since that is all tcp/udp/icmp, it doesn't matter, and I am properly allowing in ipv6 traffic, but ONLY for the tcp/udp ports I specify, and then blocking the rest ?
Basically: how is my ruleset treating ipv6 traffic (other than the fact that, at the end of the set, I deny all ipv6 that has gotten to that point)
thank you.
------------------------------
Message: 5
Date: Tue, 5 Jun 2012 15:34:27 -0700
From: Gary Kline <kline at thought.org>
Subject: Re: how do I fix this?
To: Roland Smith <rsmith at xs4all.nl>
Cc: FreeBSD <freebsd-questions at freebsd.org>
Message-ID: <20120605223427.GC23645 at thought.org>
Content-Type: text/plain; charset=us-ascii
On Tue, Jun 05, 2012 at 08:04:35AM +0200, Roland Smith wrote:
> Date: Tue, 5 Jun 2012 08:04:35 +0200
> From: Roland Smith <rsmith at xs4all.nl>
> Subject: Re: how do I fix this?
> To: Gary Kline <kline at thought.org>
> Cc: FreeBSD <freebsd-questions at freebsd.org>
>
> On Mon, Jun 04, 2012 at 09:53:11PM -0700, Gary Kline wrote:
> > no joy. I did another full upgrade. first time in many
> > months. then spent a couple hours with portmaster (thank
> > you, Roland:). this as a first upgrade.
>
> Make sure you update portmaster first. The latest versions have significant
> improvements. Also there has recently been a upgrade of libPNG, requiring a
> rebuild of everything that needs it.
pretty sure that I did exactly that.
>
> > what I want to do is get as current as possible and then
> > install 7.5. and stay there.
>
> 7.5 what? Do you mean Xorg? Please try and be specific.
FreeBSD-7.5. pretty sure I saw something about 7.4 being
upgraded to 7.5. I've been at FBSD-7.3 for a long ti me. I
dont remember how many times I have upgraded this release,
but it has been solid.
>
> > another question involves
> > accepting the "3-D" windows with whatever options they might
> > present.
>
> You mean the options dialogs as run by 'make config'?
exactly.
> Portmaster will first
> recurse through the port and all of its dependencies (if any) to handle any
> port OPTIONS via the 'make config' interface, before going off on the big
> build.
one thing ive been doing is de-selection most of the
options.. the box is my server. we [freebsders] have lost
the desktop 'market' ....
>
> > is there any upgrade utility or flag that will
> > accept and upgrade things without me having to be here?
>
> Yes and no. With the latest portmaster you can use the -y flag to
> automatically answer "yes" to all questions. But some ports are marked as
> "interactive", in the sense that they need you to give some input. Or they are
> marked as "restricted" in that you might have to go and download the tarball
> yourself somewhere. These are properties of the ports system and the
> individual ports. No port build tool can override that.
>
> BTW, use the -R flag with portmaster. If a long build fails, it skips already
> updated stuff on the second try.
super; I'll add -yR to the argv list. tx again,
gary
>
> Roland
> --
> R.F.Smith http://rsmith.home.xs4all.nl/
> [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
> pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)
--
Gary Kline kline at thought.org http://www.thought.org Public Service Unix
Voice By Computer (for Universal Access): http:/www.thought.org/vbc
The 8.57a release of Jottings: http://jottings.thought.org
Twenty-five years of service to the Unix community.
------------------------------
Message: 6
Date: Wed, 6 Jun 2012 00:20:11 +0200
From: "Geir Svalland" <g.svalland at bredband.net>
Subject: Curiousity ?
To: <freebsd-questions at freebsd.org>
Message-ID: <001d01cd4369$5ff8f270$1fead750$@svalland at bredband.net>
Content-Type: text/plain; charset="us-ascii"
Hello friends ( old )
I've moved over ( tried other, but not so further paths )
No, not all , but my butter and bread : my gateway
Also servers as my mail and DNS among others
>From FreeBSD to OpenBSD
Fckg gays, you want so much, but do we want it ?
All this going from bsd to clang and what ever ?
Get a clear step by step howto, and don't't fck belive all others are
whizzards ?
Hasse Hansson
------------------------------
Message: 7
Date: Tue, 5 Jun 2012 18:49:14 -0400 (EDT)
From: Daniel Feenberg <feenberg at nber.org>
Subject: Re: Is this something we (as consumers of FreeBSD) need to be
aware of?
To: FreeBSD <freebsd-questions at freebsd.org>
Message-ID: <Pine.GSO.4.64.1206051839020.19845 at nber6>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
On Tue, 5 Jun 2012, Jerry wrote:
> On Tue, 5 Jun 2012 17:00:14 -0400 (EDT)
> Daniel Feenberg articulated:
>
>> On Tue, 5 Jun 2012, Polytropon wrote:
>>
>>> On Tue, 5 Jun 2012 11:19:26 -0700, Kurt Buff wrote:
>>>> UEFI considerations drive Fedora to pay MSFT to sign their kernel
>>>> binaries
>>>> http://cwonline.computerworld.com/t/8035515/1292406/565573/0/
>>>
>>> I may reply with another link:
>>> http://mjg59.dreamwidth.org/12368.html
>>
>> I have a pretty basic question that probably displays some ignorance...
>>
>> Does the loader need to be signed? Once signed, can it load anything,
>> or just things MS has approved? If MS signs the kernel, can the kernel
>> run anything, or just things MS has approved? If RH has a signed
>> kernel, do they have to sign all the userland programs that run under
>> that kernel? Can users sign programs compiled from source?
>>
>> If MS only has to sign the first link in the chain, then the $99
>> certificate is not really a problem except for the pure of heart. If
>> MS or someone else has to sign all the way down to the userland
>> binaries, then users of FreeBSD will have to turn off secure boot in
>> CMOS, and it will lose a few users. But I can't tell from the
>> discussions mentioned above. Either way, I don't think it will destroy
>> FreeBSD, or Linux, but I would be interested anyway.
>
> I thought this URL <http://mjg59.dreamwidth.org/12368.html> also shown
> above, answered that question.
It says "once paid you can sign as many binaries as you want" but I don't
know if that means "as many different binaries" or "as many copies of the
same binary".
Later it says they will write a new bootloader that MS will sign and
"adding support for verifying that the kernel it's about to boot is signed
with a trusted key" but I don't know if that kernel is signed by MS or RH,
or if MS gets to approve it.
Finally it says "we'll be sanitising the kernel command line to avoid
certain bits of functionality that would permit an attacker to cause even
a signed kernel to launch arbitrary code" but does "arbitrary code" refer
to something I would want to do as a sys-admin?
dan feenberg
------------------------------
Message: 8
Date: Tue, 5 Jun 2012 19:02:18 -0400
From: grarpamp <grarpamp at gmail.com>
Subject: Re: /usr/bin/find - binary operands howto
To: freebsd-questions at freebsd.org
Message-ID:
<CAD2Ti2_H5D2keqj9UOF5GJrK2oukS7JPWspF3x8RMf8MJYbuhA at mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
A single find already had the needed selection and execution ops.
So I was trying it first, before writing an external parser, etc.
It's still not clear to me how find is compiling the arguments
internally, but using -vv on the utils helped a lot. After adding
-false after all the -exec's, it now works as desired up against
my array of inodes. I also worked in a pre-change, select, ls.
The arbitrary format of gfind is interesting. It can maybe be
approximated in find with -exec ls someargs {} \+.
------------------------------
Message: 9
Date: Tue, 5 Jun 2012 23:14:35 +0000 (UTC)
From: Walter Hurry <walterhurry at gmail.com>
Subject: FreeBSD9 - I can't get my mouse to work
To: freebsd-questions at freebsd.org
Message-ID: <jqm3sr$1l5$1 at dough.gmane.org>
Content-Type: text/plain; charset=UTF-8
Firstly, sorry if this is a bit of a newbie question. I am quite new to
FreeBSD (though fairly experienced at Linux). Almost everything in FreeBSD
is fine, except that no matter what I try I cannot get the (USB) mouse to
work.
I have scoured the handbook, and Googled, but to no avail.
This is 9.0-RELEASE on amd64 - fully updated.
I don't need the mouse in consoles, but I do want it in X.
Here is my xorg.conf in its entirety:
##################################
Section "ServerLayout"
Identifier "XFree86 Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
Option "Clone" "off"
EndSection
Section "ServerFlags"
Option "AutoAddDevices" "On"
EndSection
Section "Files"
ModulePath "/usr/local/lib/xorg/modules"
FontPath "/usr/local/lib/X11/fonts/Liberation/"
FontPath "/usr/local/lib/X11/fonts/LinLibertineG/"
FontPath "/usr/local/lib/X11/fonts/OTF/"
FontPath "/usr/local/lib/X11/fonts/TTF/"
FontPath "/usr/local/lib/X11/fonts/bitstream-vera/"
FontPath "/usr/local/lib/X11/fonts/dejavu/"
FontPath "/usr/local/lib/X11/fonts/URW/"
EndSection
Section "Module"
Load "ddc"
Load "dbe"
Load "extmod"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "XkbModel" "pc105"
Option "XkbLayout" "gb"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/sysmouse"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "ServerLayout"
Identifier "XFree86 Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
Option "Clone" "off"
EndSection
Section "ServerFlags"
Option "AutoAddDevices" "On"
EndSection
Section "Files"
ModulePath "/usr/local/lib/xorg/modules"
FontPath "/usr/local/lib/X11/fonts/Liberation/"
FontPath "/usr/local/lib/X11/fonts/LinLibertineG/"
FontPath "/usr/local/lib/X11/fonts/OTF/"
FontPath "/usr/local/lib/X11/fonts/TTF/"
FontPath "/usr/local/lib/X11/fonts/bitstream-vera/"
FontPath "/usr/local/lib/X11/fonts/dejavu/"
FontPath "/usr/local/lib/X11/fonts/URW/"
EndSection
Section "Module"
Load "ddc"
Load "dbe"
Load "extmod"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "XkbModel" "pc105"
Option "XkbLayout" "gb"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/sysmouse"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Device"
Identifier "Card0"
Screen 0
Driver "radeonhd"
VendorName "Radeon Video Driver"
Option "XAANoOffscreenPixmaps" "true"
Option "AccelMethod" "EXA"
Option "DRI" "true"
BusID "PCI:1:5:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1366x768"
EndSubSection
EndSection
##################################
and here are the relevant Xorg.0.log messages:
##################################
(EE) config/hal: couldn't initialise context: unknown error (null)
(EE) xf86OpenSerial: Cannot open device /dev/psm0
(EE) PS/2 Mouse: cannot open input device
(EE) PreInit returned NULL for "PS/2 Mouse"
(EE) config/hal: NewInputDeviceRequest failed (8)
((WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or
'vmmouse' will be disabled.
(WW) Disabling Mouse0
(WW) Disabling Keyboard0
(WW) Usb Mouse: No Device specified, looking for one...
(WW) PS/2 Mouse: No Device specified, looking for one...
(WW) Usb Mouse: No Device specified, looking for one...
(WW) Usb Mouse: No Device specified, looking for one...
(WW) Usb Mouse: No Device specified, looking for one...
(WW) Usb Mouse: No Device specified, looking for one...
(WW) Usb Mouse: No Device specified, looking for one...
(WW) Usb Mouse: No Device specified, looking for one...
(WW) Usb Mouse: No Device specified, looking for one...
##################################
Can anyone assist with this?
------------------------------
Message: 10
Date: Wed, 06 Jun 2012 01:22:51 +0200
From: Bernt Hansson <bah at bananmonarki.se>
Subject: Re: FreeBSD9 - I can't get my mouse to work
To: Walter Hurry <walterhurry at gmail.com>
Cc: freebsd-questions at freebsd.org
Message-ID: <4FCE94CB.4060309 at bananmonarki.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
2012-06-06 01:14, Walter Hurry skrev:
> Firstly, sorry if this is a bit of a newbie question. I am quite new to
> FreeBSD (though fairly experienced at Linux). Almost everything in FreeBSD
> is fine, except that no matter what I try I cannot get the (USB) mouse to
> work.
>
> I have scoured the handbook, and Googled, but to no avail.
>
> This is 9.0-RELEASE on amd64 - fully updated.
>
> I don't need the mouse in consoles, but I do want it in X.
>
> Here is my xorg.conf in its entirety:
>
> ##################################
> Section "ServerLayout"
> Identifier "XFree86 Configured"
> Screen 0 "Screen0" 0 0
> InputDevice "Mouse0" "CorePointer"
> InputDevice "Keyboard0" "CoreKeyboard"
> Option "Clone" "off"
> EndSection
>
> Section "ServerFlags"
> Option "AutoAddDevices" "On"
Set this to off.
> EndSection
>
> Section "Files"
> ModulePath "/usr/local/lib/xorg/modules"
> FontPath "/usr/local/lib/X11/fonts/Liberation/"
> FontPath "/usr/local/lib/X11/fonts/LinLibertineG/"
> FontPath "/usr/local/lib/X11/fonts/OTF/"
> FontPath "/usr/local/lib/X11/fonts/TTF/"
> FontPath "/usr/local/lib/X11/fonts/bitstream-vera/"
> FontPath "/usr/local/lib/X11/fonts/dejavu/"
> FontPath "/usr/local/lib/X11/fonts/URW/"
> EndSection
>
> Section "Module"
> Load "ddc"
> Load "dbe"
> Load "extmod"
> EndSection
>
> Section "InputDevice"
> Identifier "Keyboard0"
> Driver "keyboard"
> Option "XkbModel" "pc105"
> Option "XkbLayout" "gb"
> EndSection
>
> Section "InputDevice"
> Identifier "Mouse0"
> Driver "mouse"
> Option "Protocol" "auto"
> Option "Device" "/dev/sysmouse"
> EndSection
>
> Section "Monitor"
> Identifier "Monitor0"
> VendorName "Monitor Vendor"
> ModelName "Monitor Model"
> EndSection
>
>
> Section "ServerLayout"
> Identifier "XFree86 Configured"
> Screen 0 "Screen0" 0 0
> InputDevice "Mouse0" "CorePointer"
> InputDevice "Keyboard0" "CoreKeyboard"
> Option "Clone" "off"
> EndSection
>
> Section "ServerFlags"
> Option "AutoAddDevices" "On"
> EndSection
>
> Section "Files"
> ModulePath "/usr/local/lib/xorg/modules"
> FontPath "/usr/local/lib/X11/fonts/Liberation/"
> FontPath "/usr/local/lib/X11/fonts/LinLibertineG/"
> FontPath "/usr/local/lib/X11/fonts/OTF/"
> FontPath "/usr/local/lib/X11/fonts/TTF/"
> FontPath "/usr/local/lib/X11/fonts/bitstream-vera/"
> FontPath "/usr/local/lib/X11/fonts/dejavu/"
> FontPath "/usr/local/lib/X11/fonts/URW/"
> EndSection
>
> Section "Module"
> Load "ddc"
> Load "dbe"
> Load "extmod"
> EndSection
>
> Section "InputDevice"
> Identifier "Keyboard0"
> Driver "keyboard"
> Option "XkbModel" "pc105"
> Option "XkbLayout" "gb"
> EndSection
>
> Section "InputDevice"
> Identifier "Mouse0"
> Driver "mouse"
> Option "Protocol" "auto"
> Option "Device" "/dev/sysmouse"
> EndSection
>
> Section "Monitor"
> Identifier "Monitor0"
> VendorName "Monitor Vendor"
> ModelName "Monitor Model"
> EndSection
>
>
> Section "Device"
> Identifier "Card0"
> Screen 0
> Driver "radeonhd"
> VendorName "Radeon Video Driver"
> Option "XAANoOffscreenPixmaps" "true"
> Option "AccelMethod" "EXA"
> Option "DRI" "true"
> BusID "PCI:1:5:0"
> EndSection
>
>
> Section "Screen"
> Identifier "Screen0"
> Device "Card0"
> Monitor "Monitor0"
> DefaultDepth 24
> SubSection "Display"
> Depth 24
> Modes "1366x768"
> EndSubSection
> EndSection
> ##################################
>
> and here are the relevant Xorg.0.log messages:
>
> ##################################
> (EE) config/hal: couldn't initialise context: unknown error (null)
> (EE) xf86OpenSerial: Cannot open device /dev/psm0
> (EE) PS/2 Mouse: cannot open input device
> (EE) PreInit returned NULL for "PS/2 Mouse"
> (EE) config/hal: NewInputDeviceRequest failed (8)
> ((WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or
> 'vmmouse' will be disabled.
> (WW) Disabling Mouse0
> (WW) Disabling Keyboard0
> (WW) Usb Mouse: No Device specified, looking for one...
> (WW) PS/2 Mouse: No Device specified, looking for one...
> (WW) Usb Mouse: No Device specified, looking for one...
> (WW) Usb Mouse: No Device specified, looking for one...
> (WW) Usb Mouse: No Device specified, looking for one...
> (WW) Usb Mouse: No Device specified, looking for one...
> (WW) Usb Mouse: No Device specified, looking for one...
> (WW) Usb Mouse: No Device specified, looking for one...
> (WW) Usb Mouse: No Device specified, looking for one...
> ##################################
>
> Can anyone assist with this?
>
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
>
>
------------------------------
Message: 11
Date: Tue, 5 Jun 2012 23:26:24 +0000 (UTC)
From: Walter Hurry <walterhurry at gmail.com>
Subject: Re: FreeBSD9 - I can't get my mouse to work
To: freebsd-questions at freebsd.org
Message-ID: <jqm4j0$hce$1 at dough.gmane.org>
Content-Type: text/plain; charset=UTF-8
On Tue, 05 Jun 2012 23:14:35 +0000, Walter Hurry wrote:
> Firstly, sorry if this is a bit of a newbie question. I am quite new to
> FreeBSD (though fairly experienced at Linux). Almost everything in
> FreeBSD is fine, except that no matter what I try I cannot get the (USB)
> mouse to work.
>
> Can anyone assist with this?
>
One bit of information which might be relevant:
This is a laptop with a built-in touchpad. The touchpad works, even
though I have made no configuration changes for it. Unfortunately, as I
said, the mouse doesn't.
------------------------------
Message: 12
Date: Tue, 5 Jun 2012 17:40:06 -0600 (MDT)
From: Warren Block <wblock at wonkity.com>
Subject: Re: FreeBSD9 - I can't get my mouse to work
To: Walter Hurry <walterhurry at gmail.com>
Cc: freebsd-questions at freebsd.org
Message-ID: <alpine.BSF.2.00.1206051734550.7974 at wonkity.com>
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
On Tue, 5 Jun 2012, Walter Hurry wrote:
> Firstly, sorry if this is a bit of a newbie question. I am quite new to
> FreeBSD (though fairly experienced at Linux). Almost everything in FreeBSD
> is fine, except that no matter what I try I cannot get the (USB) mouse to
> work.
>
> I have scoured the handbook, and Googled, but to no avail.
>
> This is 9.0-RELEASE on amd64 - fully updated.
>
> I don't need the mouse in consoles, but I do want it in X.
>
> Here is my xorg.conf in its entirety:
There are duplicated sections in the output provided.
> ##################################
> Section "ServerLayout"
> Identifier "XFree86 Configured"
> Screen 0 "Screen0" 0 0
> InputDevice "Mouse0" "CorePointer"
> InputDevice "Keyboard0" "CoreKeyboard"
> Option "Clone" "off"
> EndSection
>
> Section "ServerFlags"
> Option "AutoAddDevices" "On"
> EndSection
Setting AutoAddDevices on means to use HAL for mouse detection. Is HAL
running?
On one notebook, I had to set moused_enable="YES" in /etc/rc.conf before
both the touchpad and an external mouse would work.
------------------------------
Message: 13
Date: Tue, 5 Jun 2012 19:57:30 -0400 (EDT)
From: Chris Hill <chris at monochrome.org>
Subject: Re: Is this something we (as consumers of FreeBSD) need to be
aware of?
To: G?k?in Akdeniz <goksin.akdeniz at gmail.com>
Cc: Bruce Cran <bruce at cran.org.uk>, Kurt Buff <kurt.buff at gmail.com>,
FreeBSD Questions <questions at freebsd.org>
Message-ID:
<alpine.BSF.2.00.1206051952510.59814 at tripel.monochrome.org>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
On Tue, 5 Jun 2012, G?k?in Akdeniz wrote:
> For the time being only ARM platform is restricted.
True, but I would be astonished if this restriction were not expanded by
MS in the future. Just my opinion, but I believe their ultimate goal is
to add platforms until the "secure boot" restriction encompasses most or
all desktop and server hardware. This would be over a period of years.
--
Chris Hill chris at monochrome.org
** [ Busy Expunging </> ]
------------------------------
Message: 14
Date: Tue, 5 Jun 2012 21:33:58 -0400
From: Mike Jeays <mike.jeays at rogers.com>
Subject: Re: Is this something we (as consumers of FreeBSD) need to be
aware of?
To: freebsd-questions at freebsd.org
Message-ID: <20120605213358.5047d683 at europa>
Content-Type: text/plain; charset=US-ASCII
On Tue, 5 Jun 2012 19:57:30 -0400 (EDT)
Chris Hill <chris at monochrome.org> wrote:
> On Tue, 5 Jun 2012, G?k?in Akdeniz wrote:
>
> > For the time being only ARM platform is restricted.
>
> True, but I would be astonished if this restriction were not expanded by
> MS in the future. Just my opinion, but I believe their ultimate goal is
> to add platforms until the "secure boot" restriction encompasses most or
> all desktop and server hardware. This would be over a period of years.
>
> --
> Chris Hill chris at monochrome.org
> ** [ Busy Expunging </> ]
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
This seems all too likely to me. I expect it will become very hard to find a consumer laptop that will run other operating systems in a few years. There won't be any in Best Buy or Staples, one can be pretty sure. It will be a Windows or Mac world. Not an attractive future.
------------------------------
Message: 15
Date: Tue, 5 Jun 2012 18:56:36 -0700
From: Waitman Gobble <gobble.wa at gmail.com>
Subject: Re: Is this something we (as consumers of FreeBSD) need to be
aware of?
To: Mike Jeays <mike.jeays at rogers.com>
Cc: freebsd-questions at freebsd.org
Message-ID:
<CAFuo_fwtui8D0U3bAAeh1xyfVk9YFJ4g5=y2JC-h==peH2FDtw at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On Jun 5, 2012 6:35 PM, "Mike Jeays" <mike.jeays at rogers.com> wrote:
>
> On Tue, 5 Jun 2012 19:57:30 -0400 (EDT)
> Chris Hill <chris at monochrome.org> wrote:
>
> > On Tue, 5 Jun 2012, G?k?in Akdeniz wrote:
> >
> > > For the time being only ARM platform is restricted.
> >
> > True, but I would be astonished if this restriction were not expanded by
> > MS in the future. Just my opinion, but I believe their ultimate goal is
> > to add platforms until the "secure boot" restriction encompasses most or
> > all desktop and server hardware. This would be over a period of years.
> >
> > --
> > Chris Hill chris at monochrome.org
> > ** [ Busy Expunging </> ]
> > _______________________________________________
> > freebsd-questions at freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > To unsubscribe, send any mail to "
freebsd-questions-unsubscribe at freebsd.org"
>
> This seems all too likely to me. I expect it will become very hard to
find a consumer laptop that will run other operating systems in a few
years. There won't be any in Best Buy or Staples, one can be pretty sure.
It will be a Windows or Mac world. Not an attractive future.
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "
freebsd-questions-unsubscribe at freebsd.org"
I understand there are only a few (like two) monster-sized computer
manufacturers, which are based in China, who manufacture the massive bulk
of "consumer" laptops. the name brand models in the local retail store are
almost always these ODM computers with a preloaded hard drive and a fancy
label w/ insignia slapped on the shell. One may purchase a "Generic" laptop
to spec (without any MS stuff installed, if you so desire), for a
single-unit competitive price.
for example search "compal" ...
i'm curious how the restricted boot scheme will come into play in these "no
flashy labels" portable machines.
Waitman Gobble
San Jose California USA
------------------------------
Message: 16
Date: Wed, 6 Jun 2012 02:21:53 +0000 (UTC)
From: Walter Hurry <walterhurry at gmail.com>
Subject: Re: FreeBSD9 - I can't get my mouse to work
To: freebsd-questions at freebsd.org
Message-ID: <jqmes1$dcf$1 at dough.gmane.org>
Content-Type: text/plain; charset=UTF-8
On Wed, 06 Jun 2012 01:22:51 +0200, Bernt Hansson wrote:
>> Option "AutoAddDevices" "On"
>
> Set this to off.
>
Thanks for the reply. Yes, I've tried setting it to "Off", but there is
no apparent difference; only a new set of messages in Xorg.0.log:
(EE) config/hal: couldn't initialise context: unknown error (null)
(EE) config/hal: NewInputDeviceRequest failed (8)
(EE) config/hal: NewInputDeviceRequest failed (8)
(EE) config/hal: NewInputDeviceRequest failed (8)
(EE) config/hal: NewInputDeviceRequest failed (8)
(EE) config/hal: NewInputDeviceRequest failed (8)
(EE) config/hal: NewInputDeviceRequest failed (8)
(WW) Mouse0: No Device specified, looking for one...
------------------------------
Message: 17
Date: 6 Jun 2012 02:05:14 -0000
From: Scott Ballantyne <sdb at ssr.com>
Subject: Re: FreeBSD9 - I can't get my mouse to work
To: Walter Hurry <walterhurry at gmail.com>
Cc: freebsd-questions at freebsd.org
Message-ID: <20120606020514.8485.qmail at irelay.ssr.com>
Walter Hurry <walterhurry at gmail.com> writes:
>
> Firstly, sorry if this is a bit of a newbie question. I am quite new to
> FreeBSD (though fairly experienced at Linux). Almost everything in FreeBSD
> is fine, except that no matter what I try I cannot get the (USB) mouse to
> work.
>
> I have scoured the handbook, and Googled, but to no avail.
>
> This is 9.0-RELEASE on amd64 - fully updated.
>
> I don't need the mouse in consoles, but I do want it in X.
>
The clue here is 'fully updated'. The latest hald has a bug that keeps
the mouse from working. If you look in your X.org.0.log you may find
a section which says that /dev/ums, configured by hal, is busy, and
unloads the mouse. If you don't find that, then ignore the rest of
this email :)
There are various "solutions" to this, one is to disable the auto
configure, and add the configuration for both keyboard and mouse to
the .conf file. Another is to restart dbus and hald. You can switch
to a console window from X and run this command:
/usr/local/etc/rc.d/dbus restart && /usr/local/etc/rc.d/hald restart
If that fixes it, then you can automate it by putting something like
this in /usr/local/etc/rc.d , call it haldfixbug or something like
that:
----------
#!/bin/sh
#
# PROVIDE: HALD_FIX_BUG
# REQUIRE: hald dbus
#
[ "$1" = start ] && /usr/local/etc/rc.d/dbus restart && /usr/local/etc/rc.d/hald restart && echo "DBUS HALD BUG FIX ATTEMPTED"
[ "$1" = faststart ] && /usr/local/etc/rc.d/dbus restart && /usr/local/etc/rc.d/hald restart && echo "DBUS HALD BUG FIX ATTEMPTED"
sleep 5
exit 0
-------------
This might not work if you use startx, but should be ok with xdm or
gdm. It works for me, maybe not for you.
Best,
Scott
--
sdb at ssr.com
------------------------------
Message: 18
Date: Wed, 06 Jun 2012 09:55:08 +0700
From: Erich <erichfreebsdlist at ovitrap.com>
Subject: Re: FreeBSD9 - I can't get my mouse to work
To: freebsd-questions at freebsd.org
Cc: Walter Hurry <walterhurry at gmail.com>
Message-ID: <1923831.l0mLy8oBIz at x220.ovitrap.com>
Content-Type: text/plain; charset="us-ascii"
Hi
I have had success on my hardware with this setting:
# The working configuration. The mouse daemon in /etc/rc.conf
# was dsabled.
#
# Section "ServerLayout"
# Identifier "X.org Configured"
# Screen 0 "Screen0" 0 0
# InputDevice "Mouse0" "CorePointer"
# InputDevice "Keyboard0" "CoreKeyboard"
# EndSection
#
# Section "ServerFlags"
# Option "AllowEmptyInput" "false"
# Option "AutoAddDevices" "false"
# EndSection
Turning off the mouse daemon was the key on that hardware.
The same xorg settings needed the mouse daemon turned on on other hardware.
Good luck!
Erich
On 06 June 2012 2:21:53 Walter Hurry wrote:
> On Wed, 06 Jun 2012 01:22:51 +0200, Bernt Hansson wrote:
> >> Option "AutoAddDevices" "On"
> >
> > Set this to off.
> >
> Thanks for the reply. Yes, I've tried setting it to "Off", but there is
> no apparent difference; only a new set of messages in Xorg.0.log:
>
> (EE) config/hal: couldn't initialise context: unknown error (null)
> (EE) config/hal: NewInputDeviceRequest failed (8)
> (EE) config/hal: NewInputDeviceRequest failed (8)
> (EE) config/hal: NewInputDeviceRequest failed (8)
> (EE) config/hal: NewInputDeviceRequest failed (8)
> (EE) config/hal: NewInputDeviceRequest failed (8)
> (EE) config/hal: NewInputDeviceRequest failed (8)
> (WW) Mouse0: No Device specified, looking for one...
>
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
>
>
------------------------------
Message: 19
Date: Tue, 5 Jun 2012 19:59:48 -0700
From: Waitman Gobble <gobble.wa at gmail.com>
Subject: Re: FreeBSD9 - I can't get my mouse to work
To: freebsd-questions at freebsd.org
Message-ID:
<CAFuo_fwiz25Fgv8P4Z+3nemX+wiTvt1ZO=+PkR-4cU_+ts4Fkg at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On Tue, Jun 5, 2012 at 7:05 PM, Scott Ballantyne <sdb at ssr.com> wrote:
> Walter Hurry <walterhurry at gmail.com> writes:
>
> >
> > Firstly, sorry if this is a bit of a newbie question. I am quite new to
> > FreeBSD (though fairly experienced at Linux). Almost everything in
> FreeBSD
> > is fine, except that no matter what I try I cannot get the (USB) mouse to
> > work.
> >
> > I have scoured the handbook, and Googled, but to no avail.
> >
> > This is 9.0-RELEASE on amd64 - fully updated.
> >
> > I don't need the mouse in consoles, but I do want it in X.
> >
>
> The clue here is 'fully updated'. The latest hald has a bug that keeps
> the mouse from working. If you look in your X.org.0.log you may find
> a section which says that /dev/ums, configured by hal, is busy, and
> unloads the mouse. If you don't find that, then ignore the rest of
> this email :)
>
> There are various "solutions" to this, one is to disable the auto
> configure, and add the configuration for both keyboard and mouse to
> the .conf file. Another is to restart dbus and hald. You can switch
> to a console window from X and run this command:
>
> /usr/local/etc/rc.d/dbus restart && /usr/local/etc/rc.d/hald restart
>
> If that fixes it, then you can automate it by putting something like
> this in /usr/local/etc/rc.d , call it haldfixbug or something like
> that:
>
> ----------
> #!/bin/sh
> #
> # PROVIDE: HALD_FIX_BUG
> # REQUIRE: hald dbus
> #
>
> [ "$1" = start ] && /usr/local/etc/rc.d/dbus restart &&
> /usr/local/etc/rc.d/hald restart && echo "DBUS HALD BUG FIX ATTEMPTED"
> [ "$1" = faststart ] && /usr/local/etc/rc.d/dbus restart &&
> /usr/local/etc/rc.d/hald restart && echo "DBUS HALD BUG FIX ATTEMPTED"
> sleep 5
> exit 0
> -------------
>
> This might not work if you use startx, but should be ok with xdm or
> gdm. It works for me, maybe not for you.
>
> Best,
> Scott
> --
> sdb at ssr.com
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "
> freebsd-questions-unsubscribe at freebsd.org"
>
i'll give that a try. After updating a couple of days ago the mouse is
glued to the center of the screen after starting X. I noticed if i first
kill moused before startx it works fine. (moused apparently restarts). But
maybe this solution will end the work-around.
Waitman Gobble
San Jose California USA
------------------------------
Message: 20
Date: Wed, 06 Jun 2012 10:35:14 +0700
From: Erich Dollansky <erich at alogreentechnologies.com>
Subject: Re: FreeBSD9 - I can't get my mouse to work
To: freebsd-questions at freebsd.org
Cc: Waitman Gobble <gobble.wa at gmail.com>
Message-ID: <1529132.jI8PiRModA at x220.ovitrap.com>
Content-Type: text/plain; charset="us-ascii"
Hi,
On 05 June 2012 19:59:48 Waitman Gobble wrote:
> On Tue, Jun 5, 2012 at 7:05 PM, Scott Ballantyne <sdb at ssr.com> wrote:
>
> i'll give that a try. After updating a couple of days ago the mouse is
> glued to the center of the screen after starting X. I noticed if i first
> kill moused before startx it works fine. (moused apparently restarts). But
> maybe this solution will end the work-around.
>
I came to this the same way. X stopped working with the mouse after an upgrade many, many years ago.
If it happens again, I play with the parameters in there.
I have read that other people also played with HAL but I never needed so.
Erich
------------------------------
Message: 21
Date: Wed, 06 Jun 2012 08:32:02 +0100
From: Matthew Seaman <matthew at FreeBSD.org>
Subject: Re: Is this something we (as consumers of FreeBSD) need to be
aware of?
To: FreeBSD <freebsd-questions at FreeBSD.org>
Cc: Jerry <jerry at seibercom.net>
Message-ID: <4FCF0772.8000609 at FreeBSD.org>
Content-Type: text/plain; charset="utf-8"
On 05/06/2012 23:10, Jerry wrote:
> I thought this URL <http://mjg59.dreamwidth.org/12368.html> also shown
> above, answered that question.
Signing bootloaders and kernels etc. seems superficially like a good
idea to me. However, instant reaction is that this is definitely *not*
something that Microsoft should be in charge of. Some neutral[*] body
without any commercial interests should do that job, and
bootloader/kernel signing should be freely available.
On deeper thought though, the whole idea appears completely unworkable.
It means that you will not be able to compile your own kernel or
drivers unless you have access to a signing key. As building your own
is pretty fundamental to the FreeBSD project, the logical consequence is
that FreeBSD source should come with a signing key for anyone to use.
Which completely abrogates the whole point of signing
bootloaders/kernels in the first place: anyone wishing to create malware
would be able to sign whatever they want using such a key. It's
DRM-level stupidity all over again.
My conclusion: boycott products, manufacturers and/or OSes that
participate in this scheme. FreeBSD alone won't make any real
difference to manufacturers, but I hope there is still enough of the
original spirit of freedom within the Linux camp, and perhaps from
Google/android to make an impact.
I'm pretty sure there can be a way of whitelisting bootloaders and so
forth to help prevent low-level malware, but this isn't it.
Cheers,
Matthew
[*] I suggest ICANN might be the right sort of organization to fulfil
this role.
--
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 267 bytes
Desc: OpenPGP digital signature
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20120606/9d4665e5/signature-0001.pgp
------------------------------
Message: 22
Date: Wed, 06 Jun 2012 09:45:05 +0100
From: Bruce Cran <bruce at cran.org.uk>
Subject: Re: Is this something we (as consumers of FreeBSD) need to be
aware of?
To: Matthew Seaman <matthew at FreeBSD.org>
Cc: Jerry <jerry at seibercom.net>, FreeBSD
<freebsd-questions at FreeBSD.org>
Message-ID: <4FCF1891.9020006 at cran.org.uk>
Content-Type: text/plain; charset=UTF-8; format=flowed
On 06/06/2012 08:32, Matthew Seaman wrote:
> On deeper thought though, the whole idea appears completely unworkable.
> It means that you will not be able to compile your own kernel or
> drivers unless you have access to a signing key. As building your own
> is pretty fundamental to the FreeBSD project, the logical consequence is
> that FreeBSD source should come with a signing key for anyone to use.
It just means that anyone wishing to run their own kernels would either
need to disable secure boot, or purchase/create their own certificate
and install it.
--
Bruce Cran
------------------------------
Message: 23
Date: Wed, 6 Jun 2012 11:02:33 +0200
From: Ewald Jenisch <a at jenisch.at>
Subject: isc-dhcpd - logging client transactions
To: <freebsd-questions at freebsd.org>
Message-ID: <20120606090233.GA3748 at aurora.oekb.co.at>
Content-Type: text/plain; charset="us-ascii"
Hi,
I've set up isc-dhcpd (/usr/ports/net/isc-dhcp42-server). The daemon
runs, hands out IP-addresses however logging doesn't seem to work.
Here's what I've got in the respective config-files:
/etc/rc.conf:
# dhcpd
dhcpd_enable="YES"
dhcpd_conf="/usr/local/etc/dhcpd.conf"
dhcpd_ifaces="em0"
dhcpd_withumask="022"
dhcpd_chuser_enable="YES"
dhcpd_withuser="dhcpd"
dhcpd_withgroup="dhcpd"
dhcpd_chroot_enable="YES"
dhcpd_devfs_enable="YES"
dhcpd_rootdir="/var/db/dhcpd"
/usr/local/etc/dhcpd.conf:
...
log-facility local7;
/etc/syslog.conf:
local7.* /var/log/dhcpd.log
/var/log/dhcpd.log is "touch"ed, so it exists.
Also restarted syslogd and isc-dhcpd.
Result: dhcpd works (i.e. I see entries in the leases-file
(/var/db/dhcpd/var/db/dhcpd/dhcpd.leases) however nothing is logged to
/var/log/dhcpd.log.
I can rule out any error with syslogd.conf since when I start isc-dhcp
"by hand" (/usr/local/sbin/dhcpd -d) I get an error message - and this
one is definitely logged to /var/log/dhcpd.log.
What I really need though is a log of all the DHCP-transactions,
i.e. DHCP-requests, address assignments etc.
Thanks much in advance for your help,
-ewald
------------------------------
Message: 24
Date: Wed, 06 Jun 2012 10:38:41 +0100
From: Matthew Seaman <matthew at FreeBSD.org>
Subject: Re: Is this something we (as consumers of FreeBSD) need to be
aware of?
To: Bruce Cran <bruce at cran.org.uk>
Cc: Jerry <jerry at seibercom.net>, FreeBSD
<freebsd-questions at FreeBSD.org>
Message-ID: <4FCF2521.6090006 at FreeBSD.org>
Content-Type: text/plain; charset="utf-8"
On 06/06/2012 09:45, Bruce Cran wrote:
> On 06/06/2012 08:32, Matthew Seaman wrote:
>> On deeper thought though, the whole idea appears completely unworkable.
>> It means that you will not be able to compile your own kernel or
>> drivers unless you have access to a signing key. As building your own
>> is pretty fundamental to the FreeBSD project, the logical consequence is
>> that FreeBSD source should come with a signing key for anyone to use.
> It just means that anyone wishing to run their own kernels would either
> need to disable secure boot, or purchase/create their own certificate
> and install it.
Indeed. However disabling secure boot is apparently:
* too difficult for users of Fedora
* not possible on all platforms (arm based tablets especially)
and purchasing your own certificate currently means paying $99 to
Microsoft, or else getting a key from the hardware manufacturer (which I
very much suspect will not be free either).
While I would expect the typical FreeBSD user to be quite capable of
disabling secure boot, I know that this is something that will result in
realms of questions by new users, alarmist claims that "FreeBSD is not
secure" and general glee amongst the "FreeBSD is dying" crowd.
This is just another misconceived DRM scheme and suffers from all the
same old flaws.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 267 bytes
Desc: OpenPGP digital signature
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20120606/7544b4d4/signature-0001.pgp
------------------------------
Message: 25
Date: Wed, 6 Jun 2012 02:46:38 -0700
From: Mehmet Erol Sanliturk <m.e.sanliturk at gmail.com>
Subject: Re: Is this something we (as consumers of FreeBSD) need to be
aware of?
To: Matthew Seaman <matthew at freebsd.org>
Cc: Bruce Cran <bruce at cran.org.uk>, Jerry <jerry at seibercom.net>,
FreeBSD <freebsd-questions at freebsd.org>
Message-ID:
<CAOgwaMv9uRguo9j70_jYG3-FXCT4e0+J3X05DD39E58YOmWLLQ at mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
On Wed, Jun 6, 2012 at 2:38 AM, Matthew Seaman <matthew at freebsd.org> wrote:
> On 06/06/2012 09:45, Bruce Cran wrote:
> > On 06/06/2012 08:32, Matthew Seaman wrote:
> >> On deeper thought though, the whole idea appears completely unworkable.
> >> It means that you will not be able to compile your own kernel or
> >> drivers unless you have access to a signing key. As building your own
> >> is pretty fundamental to the FreeBSD project, the logical consequence is
> >> that FreeBSD source should come with a signing key for anyone to use.
>
> > It just means that anyone wishing to run their own kernels would either
> > need to disable secure boot, or purchase/create their own certificate
> > and install it.
>
> Indeed. However disabling secure boot is apparently:
>
> * too difficult for users of Fedora
>
> * not possible on all platforms (arm based tablets especially)
>
> and purchasing your own certificate currently means paying $99 to
> Microsoft, or else getting a key from the hardware manufacturer (which I
> very much suspect will not be free either).
>
> While I would expect the typical FreeBSD user to be quite capable of
> disabling secure boot, I know that this is something that will result in
> realms of questions by new users, alarmist claims that "FreeBSD is not
> secure" and general glee amongst the "FreeBSD is dying" crowd.
>
> This is just another misconceived DRM scheme and suffers from all the
> same old flaws.
>
> Cheers,
>
> Matthew
>
> --
> Dr Matthew J Seaman MA, D.Phil.
> PGP: http://www.infracaninophile.co.uk/pgpkey
>
>
>
http://www.infoworld.com/t/hacking/tech-behind-flame-attack-could-compromise-microsoft-update-194867
Thank you very much .
Mehmet Erol Sanliturk
------------------------------
Message: 26
Date: Wed, 06 Jun 2012 01:37:18 +0200
From: "Julian H. Stacey" <jhs at berklix.com>
Subject: Re: Is this something we (as consumers of FreeBSD) need to be
aware of?
To: FreeBSD Questions <questions at freebsd.org>
Message-ID: <201206052338.q55NbIWr062787 at fire.js.berklix.net>
jerrymc at msu.edu wrote:
> Quoting Kurt Buff <kurt.buff at gmail.com>:
>
> > UEFI considerations drive Fedora to pay MSFT to sign their kernel binaries
> > http://cwonline.computerworld.com/t/8035515/1292406/565573/0/
> >
> > This would seem to make compiling from source difficult.
> >
>
> I don't see how this MS scam is even at all legal.
> It is clearly restraint of trade and probably violates some other
> related laws too.
A shame Bush blocked dismembering monopolist Microsoft.
The last enormous fines Microsoft paid the EU for monopoly abuse,
presumably failed to discipline Microsoft.
Time for increased fines, till Microsoft stops abusing its monooly.
Would be nice if the fines were so high it forced a free recall by
hardware vendors to fix, if it can't be fixed with a UEFI net upgrade.
Cheers,
Julian
--
Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com
Reply below not above, cumulative like a play script, & indent with "> ".
Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable.
Mail from @yahoo dumped @berklix. http://berklix.org/yahoo/
------------------------------
Message: 27
Date: Wed, 6 Jun 2012 06:24:37 -0400
From: Jerry <jerry at seibercom.net>
Subject: Re: Is this something we (as consumers of FreeBSD) need to be
aware of?
To: FreeBSD <freebsd-questions at freebsd.org>
Message-ID: <20120606062437.41f48a9e at scorpio>
Content-Type: text/plain; charset="utf-8"
On Wed, 06 Jun 2012 10:38:41 +0100
Matthew Seaman articulated:
>On 06/06/2012 09:45, Bruce Cran wrote:
>> On 06/06/2012 08:32, Matthew Seaman wrote:
>>> On deeper thought though, the whole idea appears completely
>>> unworkable. It means that you will not be able to compile your own
>>> kernel or drivers unless you have access to a signing key. As
>>> building your own is pretty fundamental to the FreeBSD project, the
>>> logical consequence is that FreeBSD source should come with a
>>> signing key for anyone to use.
>
>> It just means that anyone wishing to run their own kernels would
>> either need to disable secure boot, or purchase/create their own
>> certificate and install it.
>
>Indeed. However disabling secure boot is apparently:
>
> * too difficult for users of Fedora
>
> * not possible on all platforms (arm based tablets especially)
>
>and purchasing your own certificate currently means paying $99 to
>Microsoft, or else getting a key from the hardware manufacturer (which
>I very much suspect will not be free either).
I think you are in error there Matthew. From what I have read The $99
goes to Verisign, not Microsoft - further once paid you can sign as
many binaries as you want.
>While I would expect the typical FreeBSD user to be quite capable of
>disabling secure boot, I know that this is something that will result
>in realms of questions by new users, alarmist claims that "FreeBSD is
>not secure" and general glee amongst the "FreeBSD is dying" crowd.
>
>This is just another misconceived DRM scheme and suffers from all the
>same old flaws.
I don't feel this is misconceived at all. Again, from what I have read,
most non-Microsoft operating systems have been able to use UEFI Secure
Boot for nearly eight years; however, they have actively refused to do
so. However, now Microsoft has stepped up to the plate and is
actively taking advantage of the scheme. Actually, Microsoft has been
issuing warnings for ten years when a user would attempt to install
unsigned drivers. Now the FOSS community is getting its knickers in a
knot. They should have taken this into account a long time ago. In any
case, we are talking $99 dollars total, not per user here for the
certificate. If that is going to cause a problem, I'll donate the $99.
In any case, the real problem appears to be how FreeBSD is going to
handle drivers which apparently will need to be signed since they work
at the kernel level. Apparently Fedora has a working solution for that
all ready.
--
Jerry ♔
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__________________________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20120606/4bf1d8b5/signature-0001.pgp
------------------------------
Message: 28
Date: Wed, 06 Jun 2012 11:38:51 +0100
From: Bruce Cran <bruce at cran.org.uk>
Subject: Re: Is this something we (as consumers of FreeBSD) need to be
aware of?
To: FreeBSD <freebsd-questions at freebsd.org>
Cc: Jerry <jerry at seibercom.net>
Message-ID: <4FCF333B.9030402 at cran.org.uk>
Content-Type: text/plain; charset=UTF-8; format=flowed
On 06/06/2012 11:24, Jerry wrote:
>
> They should have taken this into account a long time ago. In any
> case, we are talking $99 dollars total, not per user here for the
> certificate. If that is going to cause a problem, I'll donate the $99.
It's not the $99 that'll be the problem, but the fact that it's Verisign
(actually Symantec, since they bought Verisign) that you deal with.
Whereas Globalsign accept applications from individuals, Verisign
require company documents before they'll generate a certificate.
--
Bruce Cran
------------------------------
_______________________________________________
freebsd-questions at freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
End of freebsd-questions Digest, Vol 418, Issue 7
*************************************************
More information about the freebsd-questions
mailing list