dougb | 1 Jan 2009 09:58
Picon
Favicon

Re: conf/40548: list of /etc/defaults/make.conf undocummented variables (no fix yet)

Synopsis: list of /etc/defaults/make.conf undocummented variables (no fix yet)

State-Changed-From-To: open->closed
State-Changed-By: dougb
State-Changed-When: Thu Jan 1 08:57:24 UTC 2009
State-Changed-Why: 

This report has long since been superseded by new releases and
deprecation of this file.

Responsible-Changed-From-To: freebsd-bugs-≥dougb
Responsible-Changed-By: dougb
Responsible-Changed-When: Thu Jan 1 08:57:24 UTC 2009
Responsible-Changed-Why: 

I'm closing this one.

http://www.freebsd.org/cgi/query-pr.cgi?pr=40548
_______________________________________________
freebsd-bugs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscribe <at> freebsd.org"

dougb | 1 Jan 2009 10:28
Picon
Favicon

Re: conf/118047: Move /etc/printcap to /usr/share/examples/

Old Synopsis: SUGGESTION: /etc/printcap vs mergemaster
New Synopsis: Move /etc/printcap to /usr/share/examples/

Class-Changed-From-To: sw-bug-≥change-request
Class-Changed-By: dougb
Class-Changed-When: Thu Jan 1 09:24:27 UTC 2009
Class-Changed-Why: 

This isn't really a standards issue, so throw it back into the pool.

FWIW, I don't have this problem since I have a mergemaster pre-compare
script that deletes /etc/printcap from the temproot. This will be even
easier going forward with the new IGNORE_FILES option so I'm not convinced
that this move is necessary.

Responsible-Changed-From-To: freebsd-standards-≥freebsd-bugs
Responsible-Changed-By: dougb
Responsible-Changed-When: Thu Jan 1 09:24:27 UTC 2009
Responsible-Changed-Why: 

Throw it back into the pool.

http://www.freebsd.org/cgi/query-pr.cgi?pr=118047
_______________________________________________
freebsd-bugs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscribe <at> freebsd.org"

zawwintun | 1 Jan 2009 10:23
Picon

misc/130089: I can't find Myanmar BSD user group


>Number:         130089
>Category:       misc
>Synopsis:       I can't find Myanmar BSD user group
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jan 01 09:30:01 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     zawwintun
>Release:        6.0 or higher
>Organization:
none
>Environment:
>Description:
I request to add for Myanmar BSD user group,if possible.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
(Continue reading)

remko | 1 Jan 2009 17:02
Picon
Favicon

Re: misc/130089: I can't find Myanmar BSD user group

Synopsis: I can't find Myanmar BSD user group

Responsible-Changed-From-To: freebsd-bugs-≥remko
Responsible-Changed-By: remko
Responsible-Changed-When: Thu Jan 1 16:02:28 UTC 2009
Responsible-Changed-Why: 
I'll take it.

http://www.freebsd.org/cgi/query-pr.cgi?pr=130089
_______________________________________________
freebsd-bugs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscribe <at> freebsd.org"

Stefan Hegnauer | 1 Jan 2009 22:17
Picon
Picon

kern/130102: 'pfctl -d' from inside a jail disables pf on the jail host


>Number:         130102
>Category:       kern
>Synopsis:       'pfctl -d' from inside a jail disables pf on the jail host
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jan 01 21:20:01 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Stefan Hegnauer
>Release:        7.1-PRERELEASE #9
>Organization:
>Environment:
FreeBSD jailhost.x.y.z 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #9: Wed Dec 31 09:05:43 CET 2008    
root <at> jailhost.x.y.z:/usr/obj/usr/src/sys/IBMT20  i386
>Description:
I have a jail host (192.168.1.10) with two jails running, webjail (192.168.1.80) and mailjail
(192.168.1.25). The host uses pf for some additional protection on the single network interface facing
my DMZ router, with rules for the two jailed hosts. So far everything seems to work as intended.
The setup of the jails is according to the descriptions in the jail(8) manual page with no deviations.

If I use pfctl(8) as root in one of the jails it is possible to control pf(4) that runs on the host. For example I
(Continue reading)

Remko Lodder | 1 Jan 2009 22:50

Re: kern/130102: 'pfctl -d' from inside a jail disables pf on the jail host

The following reply was made to PR kern/130102; it has been noted by GNATS.

From: Remko Lodder <remko <at> elvandar.org>
To: Stefan Hegnauer <stefan.hegnauer <at> gmx.ch>
Cc: freebsd-gnats-submit <at> FreeBSD.org
Subject: Re: kern/130102: 'pfctl -d' from inside a jail disables pf on the jail host
Date: Thu, 1 Jan 2009 22:49:11 +0100

 >>
 > FreeBSD jailhost.x.y.z 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #9: Wed  
 > Dec 31 09:05:43 CET 2008     root <at> jailhost.x.y.z:/usr/obj/usr/src/ 
 > sys/IBMT20  i386
 >> Description:
 > I have a jail host (192.168.1.10) with two jails running, webjail  
 > (192.168.1.80) and mailjail (192.168.1.25). The host uses pf for  
 > some additional protection on the single network interface facing my  
 > DMZ router, with rules for the two jailed hosts. So far everything  
 > seems to work as intended.
 > The setup of the jails is according to the descriptions in the  
 > jail(8) manual page with no deviations.
 >
 > If I use pfctl(8) as root in one of the jails it is possible to  
 > control pf(4) that runs on the host. For example I can disable pf on  
 > the host altogether using 'pfctl -d', or re-enable it again with  
 > 'pfctl -e', or load a different ruleset with 'pfctl -f <rulefile>'  
 > etc.
 > It seems that pfctl easily gets out of the jail which I did not  
 > expect, and I did also not find any reference of this behaviour in  
 > the handbook, the FAQ, the PR database or anywhere else on the net
 >> How-To-Repeat:
(Continue reading)

bz | 1 Jan 2009 22:55
Picon
Favicon

Re: kern/130102: 'pfctl -d' from inside a jail disables pf on the jail host

Synopsis: 'pfctl -d' from inside a jail disables pf on the jail host

Responsible-Changed-From-To: freebsd-bugs-≥bz
Responsible-Changed-By: bz
Responsible-Changed-When: Thu Jan 1 21:54:54 UTC 2009
Responsible-Changed-Why: 
Take; most likely a documentation problem.

http://www.freebsd.org/cgi/query-pr.cgi?pr=130102
_______________________________________________
freebsd-bugs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscribe <at> freebsd.org"

Benjamin Stuppin | 2 Jan 2009 00:29
Picon
Favicon

misc/130103: 7.1-RC X -> systemcrash


>Number:         130103
>Category:       misc
>Synopsis:       7.1-RC X -> systemcrash
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jan 01 23:30:01 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Benjamin Stuppin
>Release:        7.1-RC2 amd64
>Organization:
>Environment:
FreeBSD rechner.local.net 7.1-RC2 FreeBSD 7.1-RC2 #0: Tue Dec 23 11:42:13 UTC 2008     root <at> driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64

>Description:
Hi,
when i install FreeBSD 7.1-RC1/2 and install X11 my system hangs up when i 
startx -> logout -> startx 
it also hung up after installing drm for radeonhd -> startx -> mplayer <movie> -> fullscreen -> normal mode 

The System freezes so i can't do anything (lack another pc to test if only x runs but sometime i also saw a kernel panic message when i was on terminal 1 during a crash).
(Continue reading)

Garrett Cooper | 2 Jan 2009 00:50
Picon

Re: misc/130103: 7.1-RC X -> systemcrash

The following reply was made to PR misc/130103; it has been noted by GNATS.

From: "Garrett Cooper" <yanefbsd <at> gmail.com>
To: "Benjamin Stuppin" <benjamin_stuppin <at> yahoo.de>
Cc: freebsd-gnats-submit <at> freebsd.org
Subject: Re: misc/130103: 7.1-RC X -> systemcrash
Date: Thu, 1 Jan 2009 15:46:08 -0800

 Benjamin,
     I have a 2 similar motherboards (P5K-e Wifi), and used to use
 another similar model (P5B Deluxe), but purposely use nVidia cards so
 I haven't run into this issue, and used to have a cousin of your
 processor (Q6600). I also run CURRENT.
     Some diagnostics to try:
     1. Have you checked for BIOS updates for your board? If it's not
 fully up to date I highly suggest investing in a thumbdrive and put
 the BIOS image on the drive, then flash from the in-BIOS flashing
 utility. The Windows utility is trash and will brick your motherboard
 50%+ of the time.
     2. Does 8-CURRENT boot, install, and work?
 Cheers,
 -Garrett
_______________________________________________
freebsd-bugs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscribe <at> freebsd.org"

Garrett Cooper | 2 Jan 2009 00:50
Picon

Re: misc/130103: 7.1-RC X -> systemcrash

The following reply was made to PR misc/130103; it has been noted by GNATS.

From: "Garrett Cooper" <yanefbsd <at> gmail.com>
To: "Benjamin Stuppin" <benjamin_stuppin <at> yahoo.de>
Cc: freebsd-gnats-submit <at> freebsd.org
Subject: Re: misc/130103: 7.1-RC X -> systemcrash
Date: Thu, 1 Jan 2009 15:47:11 -0800

     Also, try disabling ACPI and then see if you can reproduce the
 issue without it on.
 -Garrett
_______________________________________________
freebsd-bugs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscribe <at> freebsd.org"


Gmane