Newsgroups: gmane.linux.distributions.grml.user Date: Sat, 07 Oct 2006 16:08:26 -0400
Newsgroups: gmane.linux.distributions.grml.user Date: Sat, 07 Oct 2006 16:08:26 -0400
On Thu, 05 Oct 2006 23:19:25 +0200, Michael Prokop wrote:
>> Does any package replace the file /etc/apt/sources.list? > > No. > > By default /etc/apt/sources.list is a symlink to > /etc/apt/sources.list.grml but if you modify the file on your own > (removing the symlink therefore) it won't be touched anymore.
Oh, I was just working on /etc/apt/sources.list, and I didn't know it is symlinked.
Just for the archive, the file /etc/apt/sources.list.grml did get updated, and so is my modification. Luckily, I have backups.
Lesson learned: remove the symlink before editing /etc/apt/sources.list.
thanks
T
> Lesson learned: remove the symlink before editing /etc/apt/sources.list.
Yes, or use vim - then the symlink is removed automatically when editing /etc/apt/sources.list and you don't have to care about it. :)
mika
Newsgroups: gmane.linux.distributions.grml.user Date: Tue, 15 Aug 2006 10:32:11 +0200
My network is not initiated on grml 0.7 hd install boot up. I have to manually started it up afterward. I'm wondering why this is happening.
Is it because my network service is not up?
$ grep network /etc/runlevel.conf 35 - S /etc/init.d/networking
Is it because I've changed my dhcp client from pump to dhclient?
or something else?
>> My network is not initiated on grml 0.7 hd install boot up. I have to >> manually started it up afterward. I'm wondering why this is happening. > >> - Is it because my network service is not up? > >> grep network /etc/runlevel.conf >> 35 - S /etc/init.d/networking > >> - Is it because I've changed my dhcp client from pump to dhclient? > >> - or something else? > > Does '/etc/init.d/networking start' right after bootup work for you?
IIRC, no. but I'm really not sure.
> How does your /etc/network/interfaces look like? Does it contain a "auto > $INTERFACE"?
No, it does not contain the "auto $INTERFACE":
$ cat /etc/network/interfaces # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # For more sample entries take a look at /etc/network/interfaces.examples
# The loopback interface # automatically added when upgrading auto lo iface lo inet loopback
And it is the same as what I get from booting from the Live-CD.
> And finally what does 'grep ifup /etc/runlevel.conf' return?
$ grep ifup /etc/runlevel.conf 18 - S /etc/init.d/ifupdown-clean 36 - S /etc/init.d/ifupdown 39 - - /etc/init.d/ifupdown-scripts-zg2
Again, same as from the Live-CD, expect the extra ifupdown-scripts-zg2 line.
rings any bells?
> $ cat /etc/network/interfaces > # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # > For more sample entries take a look at /etc/network/interfaces.examples
> # The loopback interface > # automatically added when upgrading > auto lo > iface lo inet loopback
Ok, there is no configuration for your device. :)
> And it is the same as what I get from booting from the Live-CD.
Sure. The loopback interface is initiated "manually" and all network devices are started via "ifconfig $DEVICE up ; pump -i $DEVICE".
> > And finally what does 'grep ifup /etc/runlevel.conf' return?
> $ grep ifup /etc/runlevel.conf > ...
Ok.
> rings any bells?
How do you bring up your network? :) Seems like you are using a DHCP based setup.
If you want to do it automatically start grml-network and configure it according to your needs. Or manually configure /etc/network/interfaces, take a look at /etc/network/interfaces.examples for some configuration examples.
If you want to use dhcp with the same setup as from live-cd mode make sure that CONFIG_DHCP='yes' is set in /etc/grml/autoconfig and the binary "pump" is available.
-mika-
> Sure. The loopback interface is initiated "manually" and all network > devices are started via "ifconfig $DEVICE up ; pump -i $DEVICE".
hmmm… that seems to have something to do with my messing with my DHCP client software.
> How do you bring up your network? :) Seems like you are using a DHCP > based setup.
Currently I manually start it up with:
dhclient
> If you want to do it automatically start grml-network and configure it > according to your needs. Or manually configure /etc/network/interfaces, > take a look at /etc/network/interfaces.examples for some configuration > examples.
I took a look at how my Debian Sarge does. Would the following 2 lines good enough for eth0, without relying on pump?
# The primary network interface auto eth0 iface eth0 inet dhcp
> >> My network is not initiated on grml 0.7 hd install boot up. I have to > >> manually started it up afterward. I'm wondering why this is > >> happening.
> >> - Is it because I've changed my dhcp client from pump to dhclient?
> > What do you mean with 'changed my dhcp client from pump do dhclient'? > > How did you change it?
> I'm running grml 0.7 on hd install, so I removed the pump package and > installed the dhclient, ie, the dhcpcd package, by
> apt-get install pump- dhcpcd
> To me, pump is more RedHat's choice, and dhclient has always been > Debian's. Hope we have dhclient as the dhcp client for grml in the > future. But that's only my personal flavor though.
You can invoke manually whatever you like (dhclient is available by default on grml as well). But pump is used inside grml-autoconfig because it's faster than dhclient.
The Debian way of life is to configure /etc/network/interfaces like:
auto eth0 iface eth0 inet dhcp
if you want to use DHCP for eth0. You don't have to care what's running in the background. It just works.
-mika-
> Currently I manually start it up with:
> dhclient
Ok, as written in my other mail configure /etc/network/interfaces.
> > If you want to do it automatically start grml-network and configure it > > according to your needs. Or manually configure > > /etc/network/interfaces, take a look at > > /etc/network/interfaces.examples for some configuration examples.
> I took a look at how my Debian Sarge does. Would the following 2 lines > good enough for eth0, without relying on pump?
> # The primary network interface > auto eth0 > iface eth0 inet dhcp
Yes.
> PS. How does my Debian Sarge know which DHCP client that I uses, ie, > which one to use to talk to DHCP server?
Take a look at the source of ifupdown for details.
mika
Newsgroups: gmane.linux.distributions.grml.user Date: Tue, 15 Aug 2006 15:15:21 -0500
> after an apt-get upgrade to grml 0.8 I seem to be missing my loopback lo > device > (ifconfig just shows my eth0 device after startup). > My /etc/network/interfaces contains:
> # The loopback interface automatically added when upgrading auto lo > iface lo inet loopback
> Has anybody else seen this? I only noticed this because thunderbird and > firefox started behaving oddly and > Java debugging stopped working (Java debugging needs to listen to a > localhost port).
Oh, interesting. I changed the 'ifconfig lo 127.0.0.1 up' to 'ifup lo' and now it runs only in live-cd mode as it should be working on hd-installations - due to autostartup of networking - in any case. Hmmmm. :)
What does:
# grep -e ifup -e network /etc/runlevel.conf
return? As a reference take a look at:
# grep -e ifup -e network /etc/runlevel.conf.hdinstall 15 - 0,6 /etc/init.d/wpa-ifupdown 18 - S /etc/init.d/ifupdown-clean 35 - S /etc/init.d/networking 36 - S /etc/init.d/ifupdown
Is anything missing on your system?
If not a "ifconfig lo 127.0.0.1 up" put into /etc/init.d/bootlocal.last should fix the issue in the meantime for your.
But I'd be happy to find the reason for the problem on your box.
mika
> > Is anything missing on your system?
> The difference to your output from this grep is that 35 - 0,6 > /etc/init.d/networking has 0,6 where your version has S. I > presume those are runlevels or something like that;
Ok, this means that the networking script will be executed only in runlevels 0 (halt) and 6 (reboot) but not on startup of your system.
Just replace the '0,6' of the networking line with a 'S' (runlevel S is used to initialize the system on boot, see 'man init' for more information). This will fix your problem.
mika