On Friday 18 November 2005 08:33, John Coldrick wrote:
On Thursday 17 November 2005 21:39, Yogich wrote:
On Thursday 17 November 2005 11:40, Steve Graegert wrote: <SNIP>
This could indeed be true. Since I am used to the "old way" of editing modprobe.conf (f.k.a modules.conf), I prefer editing modprobe.conf directly. (I am quite sure, this will change when something goes wrong with some package action :-)
I edited it directly, and also commented out the 'alias sit0 ipv6' --and so far nothing br0ke.
<SNIP> -- ...Yogich
The problem with doing this isn't that it breaks anything, it's just that there's a solid chance that Yast will overwrite your changes. The notion is to keep certain files that are generated by the Yast setup whenever there are changes to the config, and keep your local changes confined to separate, safe files, which are always included by default.
This may not be apparent now, but probably will be in the future.
Cheers,
J.C.
Top-posting. Ouch. At any rate, I am well aware of the ramifications of changing the 'wrong file' and living to regret it. Fact is, I am uncertain as to how one would disable ipv6 any other way --like in the local file. Once enabled in the modprobe.conf file, how would one undo that? I'm afraid I know not, but would very much like to know ...if there indeed is a way. -- ...Yogich