[Bug 375834] New: ppp over vlan-tagged ethernet - occasional network startup order problems (rcnetwork script doesnt properly start ethernet, vlan and dsl0 in this order, but eth dsl0 (which then fails) then vlan)
https://bugzilla.novell.com/show_bug.cgi?id=375834 User abittner@stud.fh-heilbronn.de added comment https://bugzilla.novell.com/show_bug.cgi?id=375834#c7 Summary: ppp over vlan-tagged ethernet - occasional network startup order problems (rcnetwork script doesnt properly start ethernet, vlan and dsl0 in this order, but eth dsl0 (which then fails) then vlan) Product: openSUSE 10.3 Version: Final Platform: x86 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: abittner@stud.fh-heilbronn.de QAContact: qa@suse.de Found By: --- hello opensuse team, for a while now i have tried to find the reason of my networking problems on a vdsl2 line (germany, deutsche telekom vdsl2-based broadband consumer line). deutsche telekom provides a pppoe-based vdsl2 line. the only specialty and difference to other standard adsl/adsl2+ lines is the vlan-tag on the ethernet-interface of their line. the ethernet-device needs to set/use vlan-id #7 to communicate with their vdsl2 cpe (ethernet modem/bridge). everything else is standard pppoe. i used to have many older opensuse versions on normal adsl/adsl2+ lines with simple pppoe. everything worked fine. the dsl0 device was defined with yast2. fine so far. with the vdsl2 line of deutsche telekom i needed to create the textfile ifcfg-vlan7 in /etc/sysconfig/network/ eth2 is the pci ethernetcard which connects to the vdsl2 modem/bridge. # the content of ifcfg-vlan7 is: STARTMODE=hotplug ETHERDEVICE=eth2 IPADDR=10.168.2.2 NETMASK=255.255.255.0 #ifcfg-eth2 content is: BOOTPROTO='static' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='192.168.1.1/24' MTU='1500' NAME='Realtek RTL-8169 Gigabit Ethernet' NETMASK='255.255.255.0' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' UNIQUE='JNkJ.oxSyVMMObW1' USERCONTROL='no' _nm_name='bus-pci-0000:04:09.0' PREFIXLEN='' # the content of ifcfg-dsl0 is: BOOTPROTO='none' DEVICE='vlan7' MODEM_IP='10.0.0.138' NAME='DSL Connection' PPPD_OPTIONS='' PPPMODE='pppoe' PROVIDER='tonline-dsl' STARTMODE='hotplug' UDI='' USERCONTROL='yes' VPIVCI='' the problem is that during the bootup of this system many times the dsl0 device fails to start (rcnetwork status after login displays "unused") and somehow i figured it is because the system sometimes wants to start dsl0 too quickly or virtually at the same time as the vlan7 device, and sometimes the vlan7 device coming up after the dsl0. which fails ofcourse as dsl0 devices depends/uses the vlan7 device. can this be fixed in a simple and easy way? also: yast doesnt really offer to handle vlan devices at all properly, i needed to do manual editing/configuration of the ifcfg-vlanX file, and you cant select/create/handle vlan devices inside yast. generally: vlan devices can only be ontop of eth devices, and pppoe can only be ontop of eth devices as the name already suggests. as vlan only exists on top of ethernet devices (if im not mistaken), and no vlan can be on top of ppp or such devices, the order of device starting needs to be ethernet -> vlan -> xxx-over-ethernet to make any sense, as vlan is only some bits/bytes inside a slightly enhanced/modded ethernet-frame. as pppoe can be ontop of ethernet, and ethernet can be ethernet or vlan-tagged-ethernet so ppp should only brought up after all ethernet and vlan-tagged-ethernet devices have started themselves. i have slightly taken a look into the /sbin/rcnetwork script and found: ###################################################################### # Get interfaces to handle # # Seperate this interfaces into several sets, not all mutually exclisive; # none of them may contain lo, because it will always handled separately # # AVAILABLE_IFACES are all interfaces from /sys/class/net # these have to be shut down when stopping # # PHYSICAL_IFACES are interfaces to present physical devices, they will be # derived from AVAILABLE_IFACES # # DIALUP_IFACES are modemX, dslX, etc., they are derived from ifcfg-* files # # TUNNEL_IFACES are interfaces that do not fit into PHYSICAL and DIALUP and # are as well derived from ifcfg-* files # # PHYSICAL, DIALUP and TUNNEL are mutually exclusive. Their union contains # AVAILABLE and MANDATORY and all of them have to be set up when starting # # MANDATORY_IFACES these must be up and well configured for success # At first get DIALUP and TUNNEL while IFS=- read a b; do test -z "$b" && continue b=`type_filter $b` case "`get_iface_type_from_config $b`" in lo|eth|tr|wlan|irda|ip6tnl|mip6mnha) continue ;; *ppp|dsl|modem|isdn) DIALUP_IFACES="$DIALUP_IFACES $b" ;; vlan|bond|bridge|ipip|sit|gre) TUNNEL_IFACES="$TUNNEL_IFACES $b" ............................ im not a programmer or networking expert, but to my undersanding the vlan needs to be closer to ethernet and way before a ppp devices as ppp can be over/on ethernet...... maybe other scenarios should also be taken into account, i didnt think about bonding, bridging, gre and so forth...... thanks for a quick fix or hint how to make my vdsl2 startup to work more reliable and to properly bring up the interfaces that depend on each other. best regards. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=375834 User mzugec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=375834#c1 Michal Zugec <mzugec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mt@novell.com, mzugec@novell.com Status|NEW |NEEDINFO Info Provider| |abittner@stud.fh-heilbronn.de --- Comment #1 from Michal Zugec <mzugec@novell.com> 2008-04-01 05:55:39 MST --- Can you re-test it with last build of openSUSE-11.0? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=375834 User abittner@stud.fh-heilbronn.de added comment https://bugzilla.novell.com/show_bug.cgi?id=375834#c2 --- Comment #2 from andreas bittner <abittner@stud.fh-heilbronn.de> 2008-04-01 06:00:53 MST --- i will try if there is an easy way to get some latest build of 11.0 to download (daily isos or some other way somewhere?) or is it possible to simply reorder that while - case loop in the rcnetwork script? shouldnt the second group inside the case be the vlan|bond|bridge|.... and the third group inside the case the *ppp|dsl|modem|isdn.... ? maybe this would fix this behaviour already? or can i take a look at this/similar rcnetwork script of the current 11.0 ? cheers. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=375834 User mzugec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=375834#c3 --- Comment #3 from Michal Zugec <mzugec@novell.com> 2008-04-01 07:12:38 MST --- Yes, you can download from http://software.opensuse.org/developer (last development version) As I remember, there was some fixes regarding device orders, so it would be useful to confirm if we need just backport, or bugfix -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=375834 User abittner@stud.fh-heilbronn.de added comment https://bugzilla.novell.com/show_bug.cgi?id=375834#c4 --- Comment #4 from andreas bittner <abittner@stud.fh-heilbronn.de> 2008-04-01 07:18:49 MST --- okay, i am already downloading the alpha3 i386 dvd torrent and will test it then. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=375834 User abittner@stud.fh-heilbronn.de added comment https://bugzilla.novell.com/show_bug.cgi?id=375834#c5 --- Comment #5 from andreas bittner <abittner@stud.fh-heilbronn.de> 2008-04-01 10:15:23 MST --- right now i am typing this from inside 11.0 alpha3 i386 dvd, clean install. inside yast and networking config there is now an option "add vlan" type of device, but somehow i cant select any devices (eth0, eth1...) to which the vlan tag applies. that dropdown dialogbox simply wont drop down, and thus doesnt displays any of my eth devices on this testbox. i have two devices, eth0 configed with dhcp and eth1 for example without any config, or static ip, or no ip at all. i tried pretty much everything.... also yast generates me this ifcfg-vlan7 file but in there "ETHERDEVICE=" is simply empty. it doesn set any devices (as i could drop down them). somehow this is pretty much weird with yast. did these vlan and other device types also exist back in 10.3 in yast? i never came across this inside the ui/ncurses also, when being inside the vlan window, i can only select dhcp or static ip there, but not "no ip". since a pppoe device running on a vlan-tagged-eth wouldnt be needing ip on ethx nor on the vlanx device at all. only simple raw ethernet, without ip, and then ppp over that ethernet. this also seems a bug to me. yast seems instable in the networking part to me. regards. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=375834 User abittner@stud.fh-heilbronn.de added comment https://bugzilla.novell.com/show_bug.cgi?id=375834#c6 --- Comment #6 from andreas bittner <abittner@stud.fh-heilbronn.de> 2008-04-01 10:31:28 MST --- other than that, when manually editing the ifcfg-vlan7 and ifcfg-ethx files, and then removing dhcp there and manually adding ethx in the vlan7 file where its needed for ETHERDEVICE= then rcnetwork stop / start seems to work in the proper order. first the ethx devices start, then after that the vlan7 device comes up. also the /sbin/rcnetwork script of 11.0 alpha3 seems to be different in the case loop and like i suspected handles the vlan separate and before the pppx devices get handled: -------------- # At first sort into BONDING, DIALUP, TUNNEL and BRIDGE interface sets. while IFS=- read a b; do test -z "$b" && continue b=`type_filter $b` case "`get_iface_type_from_config $b`" in lo|eth|tr|wlan|irda|ip6tnl|mip6mnha) continue ;; bond) BONDING_IFACES="$BONDING_IFACES $b" ;; vlan) VLAN_IFACES="$VLAN_IFACES $b" ;; *ppp|dsl|modem|isdn) DIALUP_IFACES="$DIALUP_IFACES $b" ;; ipip|sit|gre) TUNNEL_IFACES="$TUNNEL_IFACES $b" ;; bridge) BRIDGE_IFACES="$BRIDGE_IFACES $b" ;; *) -------------------- and if i am not mistaken, further down in the sources it seem to handle vlan type devices always separately and BEFORE any dialup (pppx) type devices: ---------------- for b in $BONDING_IFACES $VLAN_IFACES $DIALUP_IFACES $TUNNEL_IFACES $BRIDGE_IFACES; do ---------------------- so i think 11.0 alpha3 handles vlan tagged ethernet with pppoe devices on them properly, while opensuse 10.3 was failing for me many times. but please do take a look into yast and the vlan device handling/creating/editing there. it seems pretty buggy to me. thanks. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=375834 User mzugec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=375834#c7 --- Comment #7 from Michal Zugec <mzugec@novell.com> 2008-04-01 10:39:51 MST --- 1 - alpha3 has an old rpm (yast2-network-2.16.26) - this is fixed later (in yast2-network-2.16.28): - possibility to use unconfigured device for vlan, bond and bridge (bnc#369195) 2 - empty ifcfg-vlan7 because of this (no selected device = no ETHERDEVICE) 3 - no, this is new feature (http://en.opensuse.org/YaST/Network/11.0-new_features) 4 - please report as a new bug that there is needed "no ip" option and attach there manually created configuration you need to have 5 - please copy your /etc/sysconfig/network/ifcfg-* files from 10.3 to 11.0 and test "network startup order problems" -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=375834 User mzugec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=375834#c8 --- Comment #8 from Michal Zugec <mzugec@novell.com> 2008-04-01 10:40:17 MST --- middle-air collision ;-) -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=375834 User mzugec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=375834#c9 --- Comment #9 from Michal Zugec <mzugec@novell.com> 2008-04-01 10:45:07 MST --- for last yast2-network package you can search in http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/suse/$(... architecture) be carefull and download just this one package manually -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=375834 User abittner@stud.fh-heilbronn.de added comment https://bugzilla.novell.com/show_bug.cgi?id=375834#c10 --- Comment #10 from andreas bittner <abittner@stud.fh-heilbronn.de> 2008-04-01 10:51:20 MST --- ok one more thing.... i have manually fixed the ifcfg-vlan7 file allright. then i went back into yast and wanted to create the dsl0 device (dsl settings). there yast (dsl module) scans if it can detect any pppoe (pppox?) devices, but this testmachine isnt conntected to any ppp-offering devices (xdsl modem/bridge) at the moment. so it offers to manually select the ethx cards where the dsl0 device should be running on. so here in this window, the properly (manually edited) ifcfg-vlan7 is missing as a device. this has been the case also back in opensuse 10.3, where i simply generated a dsl0 device on some of my ethx cards, and then changed the textfile manually to vlan7 (DEVICE='vlan7') so 11.0 alpha3 has also this bug, that pppox configuration doesnt offer all the possible eth-x type devices where a pppoe device could possibly be connected to. pppoe could even be possible over exotic ethernet stuff like wlan and all kinds of other ethernet-based stuff. please add this functionality to the dsl module of yast. there is also the bug that on this 11.0 alpha3 testmachine i selected a normal ethernetcard to create the dsl0 device on, but at the end it never got created (the first screen of the dsl device config) always stays empty. the ifcfg-dslx file never gets created on 11.0 alpha3. it creates the /etc/sysconfig/network/providers/myprovider file though properly with all the username/password, timeouts, dns/ips and so on..... so adding the dsl0 "device" itself seems to fail at the moment, or in general when yast cant really communicate with a true dsl counterpart (xdsl bridge/modem/pppox-server). this hasnt been the case with opensuse 10.3. dsl-configuration has always been possible even in "offline" mode, when no dsl devices were connected at all, you could create the dsl0 device and so on. bug? fix? regards. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=375834 User abittner@stud.fh-heilbronn.de added comment https://bugzilla.novell.com/show_bug.cgi?id=375834#c11 --- Comment #11 from andreas bittner <abittner@stud.fh-heilbronn.de> 2008-04-01 10:58:33 MST --- for the newer yast2-network package i only get: rpm -Uvh yast2-network-2.16.28-5.i586.rpm error: Failed dependencies: rpmlib(PayloadIsLzma) <= 4.4.2-1 is needed by yast2-network-2.16.28-5.i586 and i dont find any rpmlib stuff on the download.opensuse.org server in those folders..... wondering whats wrong.... rpm -aq | grep -i rpm rpm-4.4.2-175 deltarpm-3.4-60 uname -a Linux linux-t0ak 2.6.25-rc5-git3-6-pae #1 SMP 2008-03-14 16:14:49 +0100 i686 athlon i386 GNU/Linux cheers. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=375834 User mzugec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=375834#c12 --- Comment #12 from Michal Zugec <mzugec@novell.com> 2008-04-01 12:27:56 MST --- Ah I found that there is some problem with different compression in rpm (I don't know how to solve that now), so you can't use newer rpm unfortunately (or I can build manually one for you) Andreas, please create new bugreport and paste there comment from #10 and close this one as fixed in 11.0. (original bugreport is about sysconfig and you continue about yast-network) Thank you Michal -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=375834 User abittner@stud.fh-heilbronn.de added comment https://bugzilla.novell.com/show_bug.cgi?id=375834#c13 --- Comment #13 from andreas bittner <abittner@stud.fh-heilbronn.de> 2008-04-01 14:57:30 MST --- ok i have filed two reports, one for the "no-ip missing for vlan configuration" https://bugzilla.novell.com/show_bug.cgi?id=376063 and for the yast2 dsl module that it never creates the dslX device in the list nor the configfile on the harddrive. https://bugzilla.novell.com/show_bug.cgi?id=376059 you can close this bug now. thanks for the quick replies anyways. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=375834 User mzugec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=375834#c14 Michal Zugec <mzugec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|abittner@stud.fh-heilbronn.de | Resolution| |FIXED --- Comment #14 from Michal Zugec <mzugec@novell.com> 2008-04-01 15:27:42 MST --- thanks, reported bug fixed in sysconfig in openSUSE-11.0 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=375834 User abittner@stud.fh-heilbronn.de added comment https://bugzilla.novell.com/show_bug.cgi?id=375834#c15 --- Comment #15 from andreas bittner <abittner@stud.fh-heilbronn.de> 2008-04-02 03:06:44 MST --- ok i still have one more question regarding this original bugreport. i filed it against opensuse 10.3 because thats the latest official stable/final opensuse release. and i have this problem there. so we do need a backport or fix for opensuse 10.3 it doesnt help me at all if its gonna work fine in 11.0 there are current opensuse releases out there that need to work properly. will there be a backport/fix for 10.3 for the startup order of the network interfaces? thanks for any hints. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=375834 User mzugec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=375834#c16 Michal Zugec <mzugec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #16 from Michal Zugec <mzugec@novell.com> 2008-04-02 03:13:57 MST --- reopened, assigned to sysconfig maintainer -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=375834 User mzugec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=375834#c17 Michal Zugec <mzugec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |mt@novell.com Status|REOPENED |NEW --- Comment #17 from Michal Zugec <mzugec@novell.com> 2008-04-02 03:14:37 MST --- Marius, will you backport this for 10.3? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=375834 User mt@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=375834#c18 Marius Tomaschewski <mt@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #18 from Marius Tomaschewski <mt@novell.com> 2008-04-02 03:22:02 MST --- Yes, I think it makes sense. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=375834 User ast@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=375834#c21 --- Comment #21 from Anja Stock <ast@novell.com> 2008-04-11 04:09:31 MST --- released for 10.3 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=375834 User abittner@stud.fh-heilbronn.de added comment https://bugzilla.novell.com/show_bug.cgi?id=375834#c22 --- Comment #22 from andreas bittner <abittner@stud.fh-heilbronn.de> 2008-04-11 08:04:42 MST --- thanks for the update. is this gonna be backported to all the current open/suse platforms that are still out there being used? i still have several 10.2 and 10.1 boxes, and after all, they are still in the active productlifecycle regards. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=375834 User mzugec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=375834#c23 --- Comment #23 from Michal Zugec <mzugec@novell.com> 2008-04-11 08:10:28 MST --- http://en.opensuse.org/SUSE_Linux_Lifetime : 10.1 is not supported yet, 10.2 will be outdated in november -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=375834 User mt@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=375834#c24 Marius Tomaschewski <mt@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |abittner@stud.fh-heilbronn.de --- Comment #24 from Marius Tomaschewski <mt@novell.com> 2009-01-07 08:58:49 MST --- Do you (or somebody that can reproduct the problem) a line like this in the /etc/fstab? : tmpfs /dev/shm tmpfs defaults,size=132M 0 0 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=375834 User mt@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=375834#c25 --- Comment #25 from Marius Tomaschewski <mt@novell.com> 2009-01-07 09:49:20 MST --- Is the problem fixed when you remove this line and reboot? (Note, that /dev is already a tmpfs). -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=375834 User abittner@stud.fh-heilbronn.de added comment https://bugzilla.novell.com/show_bug.cgi?id=375834#c26 --- Comment #26 from andreas bittner <abittner@stud.fh-heilbronn.de> 2009-01-07 21:22:31 MST --- hmm, this is rather an old bug. i thought the startup order was a matter of the rcnetwork script. if im not mistaken, it has been fixed with some update of the package which contains the enhanced script with better order while bringing up the different kind network interfaces. i wonder about the tmpfs stuff you are now talking about. i am no expert, but whats that gonna change here? the problem this bugreport is about was fixed quite a while back, at least for me. how could i now tell any difference in behaviour? greetings. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=375834 User mt@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=375834#c27 Marius Tomaschewski <mt@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|abittner@stud.fh-heilbronn. | |de | Resolution| |FIXED --- Comment #27 from Marius Tomaschewski <mt@novell.com> 2009-02-13 10:08:50 MST --- (In reply to comment #26)
hmm, this is rather an old bug.
i thought the startup order was a matter of the rcnetwork script.
if im not mistaken, it has been fixed with some update of the package which contains the enhanced script with better order while bringing up the different kind network interfaces.
i wonder about the tmpfs stuff you are now talking about. i am no expert, but whats that gonna change here? the problem this bugreport is about was fixed quite a while back, at least for me.
how could i now tell any difference in behaviour?
greetings.
Yes, you're right - I've overseen comment #21. -- 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.
participants (1)
-
bugzilla_noreply＠novell.com