Bug 42555

Summary: FreeBSD 4.6.2 + XFree 4.2 + DHCP + Firewall extrem rules = problems!!!! (startx doesn't work)
Product: Base System Reporter: Daniel Tourde <daniel.tourde>
Component: miscAssignee: Giorgos Keramidas <keramida>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description Daniel Tourde 2002-09-08 19:10:01 UTC
Freshly installed machine (Normal system + XFree)
I have a DHCP connection and I want to have strong firewall rules, therefore I chose "extrem" rules.
Once XFree 86 configured and the machine rebooted (directly at the first trial, without ANY customisation of my own), when I type startx as root, I obtain a strange message from a module of Xfree 86 (I am under windows and I don't remember the name, sorry. Something like xfree86io) telling me that it cannot access /dev/io....

If I switch back to normal firewall rules, then startx starts Xfree as root but if I try it as a normal user, it says "Cannot open /var/log/XFree86.log.0"

It seems also that the system does not really recognize the name I get from the DHCP server (myname.myprovider.com) and it complains about that when I quit X11.

How-To-Repeat:  See the full description:

Install FreeBSD 4.6.2 (basic system + XFree 86)
Configure XFree 86 (mouse = Auto)
Network: DHCP
Firewall : extrem

reboot. Log as root and type "startx". X never starts.
Comment 1 Giorgos Keramidas freebsd_committer freebsd_triage 2002-09-08 20:10:47 UTC
State Changed
From-To: open->closed


Not a bug report.  Please ask general questions by sending email 
to freebsd-questions@freebsd.org.  Your problems seem to be related 
to an increased kern.securelevel, but the description of the problems 
doesn't include enough details to be sure. 

Try asking in freebsd-questions. 
Thank you for using FreeBSD and reporting what you thought was a bug, though. 


Comment 2 Giorgos Keramidas freebsd_committer freebsd_triage 2002-09-08 20:10:47 UTC
Responsible Changed
From-To: freebsd-bugs->keramida