Mailinglist Archive: opensuse-bugs (16634 mails)

[bugzilla_noreply@xxxxxxxxxx]

https://bugzilla.novell.com/show_bug.cgi?id=416108

User pgajdos@xxxxxxxxxx added comment
https://bugzilla.novell.com/show_bug.cgi?id=416108#c12





--- Comment #12 from Petr Gajdos <pgajdos@xxxxxxxxxx>  2008-11-20 02:30:32 MST 
---
Q1 was meaned another way: I wonder why chunk

#
# commented block without any FOO1=value1 directly after #
#
#FOO=value

get special "CommentedVariableBlock" type. I guess^2 that it could be the
"example" as you said. I have some scrappy informations that in the past was
only one variable per one chunk allowed (not true now, see
/etc/sysconfig/joystick). If yes, then table above begins to have little sense
(above all, I don't understand the third line while -m is used -- this is
actually our problem). 

There is much of code to handle commented variable blocks, therefore I don't
believe it hasn't or hadn't some purpose. Unfortunatelly, I haven't find any
document that describes intended fillup behaviour by now. Thus, I cannot say
how long it can take to fix it, because I don't actually know what to fix :-).
But for 11.1 is too late anyway (I am new for fillup, you know), I agree.

There is an easy wrokaround to fix this:

# Examples: "tr0", "eth0 eth1"

or

# Example:
# * FW_ZONES="wlan"
# * FW_DEV_wlan="wlan0"
# * FW_SERVICES_wlan_TCP="80"
# * FW_ALLOW_FW_BROADCAST_wlan="yes"
#

By the way, wasn't somewhere usage or recommendation to not use #FOO=value in
the real comment?


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.