LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian
User Name
Password
Debian This forum is for the discussion of Debian Linux.

Notices

Reply
 
LinkBack Search this Thread
Old 06-06-2007, 05:35 PM   #1
HowDoIProgramIt
Member
 
Registered: Nov 2006
Location: East Coast, USA (in "the great northeast")
Distribution: Custom / from source; Fedora, Debian, CentOS, Scientific; LFS.
Posts: 94

Rep: Reputation: 15
The Devil in the Details: Redhat User Coming Over to the Dark Side but Getting Lost


Hi, all;

For about the last, uh, eight or nine years, I've been using RedHat based distributions; for a number of reasons, including having pretty much had it with RPM and intertwined dependencies up the keister, I'm drifting over to "the dark side"; I installed Debian "Etch" on my Mac Mini a couple days ago.

I knew there would be some differences; no problem there. Here's where I'm getting lost though:

the mini (it's a G4 mini) has a Sun GEM 10/100/1000 10base-T
ethernet adapter; I can see that happening in kernel.log.
The machine also has an IEEE 1394 (fire-wire) adapter; right
after finding the GEM, according to kernel.log, ohci1394 is
loaded. The long and short of it is that the fire-wire port
ends up with Ethernet over IEEE-1394 enabled, and as eth0;
the Sun GEM then gets bumped somehow to eth1.

I would like to make the GEM eth0; also, I would like to disable
the Ethernet-over-IEEE1394 functionality, as I would like to use
the fire-wire port for other purposes (I would like to hook an
external drive up to it).

I found /etc/network/interfaces, and /etc/network/interfaces/run; I'm not sure at all how to accomplish what I'm trying to accomplish, though; should I disable the loading of "eth1394" first, and would that resolve the other issue automatically?

If so, where and how would I do that? I'm used to a having chkconfig && /etc/rc.d/init.d with all of the OS's services in it, controllable with ntsysv (and chkconfig).

Could someone please tell me what the Debian equivalent is? I'm really liking this distro so far; I just need to get familiar with some of the finer details.

Thanks,

- Larry
 
Old 06-07-2007, 08:32 AM   #2
JimBass
Senior Member
 
Registered: Oct 2003
Location: New York City
Distribution: Debian Sid 2.6.32
Posts: 2,100

Rep: Reputation: 48
I don't think you'd accomplish anything by editing /etc/network/interfaces. That file simply tells the system how to assign addresses to interfaces. Even if you remove the 1394 interface from it, it won't get an address, but it will still be seen as eth0 most likely. I'd do it with blacklisting the modules used to allow the firewire port to have an address, specifically (from your other thread) ip1394 and eth1394.

The place to blacklist modules is /etc/modprobe.d/blacklist. When you open that file, you'll see several things blacklisted already. If by some strange chance your file is blank, the syntax would look something like this:

Code:
blacklist ip1394
blacklist eth1394
That should simply not recognize the firewire port as an ethernet enabled interface, but should still allow it to connect to other devices. I don't have a Mac to test that on, but it seems logical enough.

Chkconfig is redhat only. The tool to use in debian to similiar effect is update-rc.d. Use the man page or the net to figure out the syntax. A simple way to see what is being loaded at each runlevel is just to check /etc/rcX.d/, where X is a runlevel. Anything that starts with the letter S is started at that runlevel, and anything with K is killed. Unlike most other distros, the default in Debian isn't 5, but rather 2 or 3, which confuses new debian users.

The startup scripts in debian are in /etc/init.d. All the start/stop/restart commands take the form /etc/init.d/service start|stop|restart.

Most importantly, you didn't come to the dark side, you left the dark side. All redhat distros are linux lite, for windows users, who have yet to figure out that you can run a machine from the CLI only. All they did was replace .exe with .rpm. The notion of compiling from source or using a man page scares them. Actually, the notion of not having a mouse scares them too. Now you'll see how things really work.

Peace,
JimBass

Last edited by JimBass; 06-07-2007 at 10:05 AM.
 
Old 06-07-2007, 09:53 AM   #3
farslayer
Guru
 
Registered: Oct 2005
Location: Willoughby, Ohio
Distribution: linuxdebian
Posts: 7,231
Blog Entries: 5

Rep: Reputation: 189Reputation: 189
Having switched from Redhat myself several years back.. I would say, once you figure out the differences, you'll never go back.

the Debian Quick Reference card may come in handy when you are trying to locate configuration files etc..
http://people.debian.org/~debacle/re...card-en-lt.pdf

or the much more complete Debian reference manual..
http://www.debian.org/doc/user-manuals#quick-reference

Hrm looks like the card is in need of an update though.. still shows apt-get instead of aptitude
 
Old 06-09-2007, 03:02 PM   #4
HowDoIProgramIt
Member
 
Registered: Nov 2006
Location: East Coast, USA (in "the great northeast")
Distribution: Custom / from source; Fedora, Debian, CentOS, Scientific; LFS.
Posts: 94

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by JimBass
... I'd do it with blacklisting the modules used to allow the firewire port to have an address, specifically (from your other thread) ip1394 and eth1394 ...[/code]
Ok; this is going to drive me nuts. So far, I've tried:

blacklisting eth1394 (ip1394 turned out not to be a module; rather, it was part of a log entry that eth1394 made) That "got rid of" eth0;
after a reboot, according to "ip link show" et al. eth0 no longer existed. But eth1 did. At this point I decided to apply a little brute force,
and currently, "ip link show" currently shows 'lo', 'eth0' and 'sit0'; more on this in a minute...

creating a udev rule in a file I named "/etc/udev/rules.d/010_nic_rules", which contains:
KERNEL=="eth*",SYSFS{address}=="nn:nn:nn:nn:nn:nn",NAME="eth0"
Those specific (SYSFS{address} et al.) instructions were per this article: http://www.debianhelp.co.uk/udev.htm specifically;
the article was consistent with at least three others on the same topic. The one thing about it that seems a little odd is that none of my
other udev rules contain the string "SYSFS{address}"; I double-checked the articles, that's what they say...

And, I've tried creating /etc/modprobe.d/nics with the following contents:
alias eth0 sungem

The best I could get was a system with no eth0 and an unconfigured eth1; each time I booted, I had to bring the card up manually; I mean, I literally had to type:
Code:
ifconfig eth1 a.b.c.d
route add default gw e.f.g.h dev eth0
route add -net 169.254.0.0 netmask 255.255.0.0 dev eth0
echo "search thisdomain.net" > /etc/resolv.conf
echo "nameserver w.x.y.z" >> /etc/resolv.conf
If I omitted "dev eth0" from "route add" I got a "no such device" error; apparrently, part of the system still thought the default device was eth1, even though that device doesn't exist...

According to /var/log/kern.log, when the system starts to boot up, it id's the GEM card and assigns it the name eth0. At some point after that, though, something else changes that to eth1. At this point, I've added another script to change it back (I installed ifrename), and have managed to get the machine to the point where it'll come up after a reboot with networking up on eth0 - complete with a routing table.

Quote:
Chkconfig is redhat only. The tool to use in debian to similiar effect is update-rc.d. Use the man page or the net to figure out the syntax. A simple way to see what is being loaded at each runlevel is just to check /etc/rcX.d/, where X is a runlevel. Anything that starts with the letter S is started at that runlevel, and anything with K is killed. Unlike most other distros, the default in Debian isn't 5, but rather 2 or 3, which confuses new debian users.

The startup scripts in debian are in /etc/init.d. All the start/stop/restart commands take the form /etc/init.d/service start|stop|restart.
Thanks; that helps a lot. The only other thing that's still throwing me is that there's apparently something other than init (via inittab, via rcX.d ...) starting certain services, like NetworkManager and dhcdbd - I can see them running in the process table, and can see their output in /var/log/daemon.log, but, after having grep'd && otherwise searched all over the place for them, I don't have the foggiest clue as to how they're getting started.

And, I'm still not clear as to why I'm having the eth0 / eth1 issue that I am. My guess would have been that after I blacklisted the eth1394 module, I would have only had eth0...

There are actually two reasons why NetworkManager is running is puzzling me; "man NetworkManager" states that
"Only devices that are *not* listed in /etc/network/interfaces or which have been configured "auto" and "dhcp" (with no other options) are managed by NM."
If eth0 is listed in interfaces, and eth1 doesn't exist, then why is it ever even starting?

Unless, when it starts, device assignments are still in flux... unfortunately, that'd potentially open up another can of worms...

Here's the output from kernel.log I was referring to before:
Code:
Jun  9 13:10:22 localhost kernel: sungem.c:v0.98 8/24/03 David S. Miller (davem@redhat.com)
Jun  9 13:10:22 localhost kernel: PHY ID: 4061e4, addr: 0
Jun  9 13:10:22 localhost kernel: eth0: Sun GEM (PCI) 10/100/1000BaseT Ethernet 00:0d:93:75:8a:0c

Jun  9 13:10:22 localhost kernel: eth0: Found BCM5221 PHY

Jun  9 13:10:22 localhost kernel: PCI: Enabling device 0002:20:0e.0 (0000 -> 0002)
Jun  9 13:10:22 localhost kernel: ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[40]  MMIO=[f5000000-f50007ff]  Max Packet=[2048]  IR/IT contexts=[8/8]
Jun  9 13:10:22 localhost kernel: Attempting manual resume
Jun  9 13:10:22 localhost kernel: kjournald starting.  Commit interval 5 seconds
Jun  9 13:10:22 localhost kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jun  9 13:10:22 localhost kernel: usb 2-1: new low speed USB device using ohci_hcd and address 3
Jun  9 13:10:22 localhost kernel: usb 2-1: configuration #1 chosen from 1 choice
Jun  9 13:10:22 localhost kernel: ohci_hcd 0001:10:1b.1: wakeup
Jun  9 13:10:22 localhost kernel: ieee1394: Host added: ID:BUS[0-00:1023]  GUID[000d93fffe758a0c]
Jun  9 13:10:22 localhost kernel: usb 3-1: new low speed USB device using ohci_hcd and address 2
Jun  9 13:10:22 localhost kernel: usb 3-1: configuration #1 chosen from 1 choice
Jun  9 13:10:22 localhost kernel: ts: Compaq touchscreen protocol output

Jun  9 13:10:22 localhost kernel: eth1: Link is up at 10 Mbps, half-duplex.

Jun  9 13:10:22 localhost kernel: Linux agpgart interface v0.101 (c) Dave Jones
Jun  9 13:10:22 localhost kernel: agpgart: Detected Apple UniNorth 2 chipset
Jun  9 13:10:22 localhost kernel: agpgart: configuring for size idx: 4
Jun  9 13:10:22 localhost kernel: agpgart: AGP aperture is 16M @ 0x0 
Jun  9 13:10:22 localhost kernel: usbcore: registered new driver hiddev
Jun  9 13:10:22 localhost kernel: input: NOVATEK USB MULTIMEDIA KEYBOARD as /class/input/input2
Jun  9 13:10:22 localhost kernel: input: USB HID v1.10 Keyboard [NOVATEK USB MULTIMEDIA KEYBOARD] on usb-0001:10:1b.0-1 
Jun  9 13:10:22 localhost kernel: input: NOVATEK USB MULTIMEDIA KEYBOARD as /class/input/input3
Jun  9 13:10:22 localhost kernel: input: USB HID v1.10 Device [NOVATEK USB MULTIMEDIA KEYBOARD] on usb-0001:10:1b.0-1
Jun  9 13:10:22 localhost kernel: input: Logitech as /class/input/input4
Jun  9 13:10:22 localhost kernel: input: USB HID v1.00 Mouse [Logitech] on usb-0001:10:1b.1-1
Jun  9 13:10:22 localhost kernel: usbcore: registered new driver usbhid
Jun  9 13:10:22 localhost kernel: drivers/usb/input/hid-core.c: v2.6:USB HID core driver
Jun  9 13:10:22 localhost kernel: snd-aoa-fabric-layout: found bus with layout 58
Jun  9 13:10:22 localhost kernel: snd-aoa-fabric-layout: Using direct GPIOs
Jun  9 13:10:22 localhost kernel: snd-aoa-fabric-layout: can use this codec
Jun  9 13:10:22 localhost kernel: Adding 3026680k swap on /dev/hda4.  Priority:-1 extents:1 across:3026680k
Jun  9 13:10:22 localhost kernel: EXT3 FS on hda3, internal journal
Jun  9 13:10:22 localhost kernel: apm_emu: APM Emulation 0.5 initialized.
Jun  9 13:10:22 localhost kernel: loop: loaded (max 8 devices)
Jun  9 13:10:22 localhost kernel: SCSI subsystem initialized
Jun  9 13:10:22 localhost kernel: ieee1394: sbp2: Driver forced to serialize I/O (serialize_io=1)
Jun  9 13:10:22 localhost kernel: ieee1394: sbp2: Try serialize_io=0 for better performance
Jun  9 13:10:22 localhost kernel: device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@redhat.com
Jun  9 13:10:22 localhost kernel: snd-powermac no longer handles any machines with a layout-id property in the device-tree, use snd-aoa.

Jun  9 13:10:22 localhost kernel: eth0: Link is up at 10 Mbps, half-duplex.
Jun  9 13:10:22 localhost kernel: eth0: Pause is disabled

Quote:
...default in Debian isn't 5, but rather 2 or 3, which confuses new debian users...
Thanks; yeah, I almost got myself with something there.

Quote:
Most importantly, you didn't come to the dark side, you left the dark side. All redhat distros are linux lite, for windows users, who have yet to figure out that you can run a machine from the CLI only. All they did was replace .exe with .rpm. The notion of compiling from source or using a man page scares them. Actually, the notion of not having a mouse scares them too. Now you'll see how things really work.
All of the RedHat knock-offs I've seen have really sucked - like Mandrivel, for ex. The reason we started using RedHat a long time back was that we could get it to "look and feel" like a SunOS / Solaris box from the console; we've customized the boot scripts to some extent, and changed a few other things around, the net result being that one can pretty easily support both systems without losing their marbles.

I don't generally use a mouse, period; I can't stand GUI interfaces. The first mouse I had hung off the end of my desk for seven months. Essentially, I / we use RedHat / Fedora to get a basic system up and then install our own software from there; it usually saves a lot of time w/respect to loading those packages I wouldn't ordinarily bother to compile anyway.

Since about RedHat 7, it's gotten to be more and more of a mixed blessing; the more they tend towards RPM, the more I tend to head elsewhere. The problem is that I can follow, literally step by step, the RH bootup process, so I can make it do pretty much whatever I want it to in short order - so long as I'm careful not to install anything but a few select packages I / we already know are "safe" via RPM; even then, our policy is to grab the SRPM, build it locally, and then install it.

I'm liking what I see with Debian so far, and I think I'm fairly close to figuring out what's what; I need to develop the same level of comfort with its init process & scripts that I currently have w/RedHat && I'm there...
I know I'm not exactly your typical RedHat / Fedora user, but I think you would be surprised how many others there are like me / us - those who built systems around one distro or another && would love to switch away but haven't yet been able to develop the degree of comfort that they need to w any other distro that's NIH. I / we have tried that, too; the problem there is that keeping everything current is incredibly labor intensive. Which is why we went with the approach that we did in the first place...

"Thank you" to everyone for your help. I really appreciate it. If I can make this transition, life will be a lot easier...

- Larry
 
Old 06-10-2007, 11:20 AM   #5
Norb
LQ Newbie
 
Registered: Aug 2004
Location: The Derby
Distribution: Squeeze AMD64
Posts: 15

Rep: Reputation: 0
I thought I would post this link, you may find it to be of some value.

http://www.togaware.com/linux/survivor/index.html

Norb
 
Old 06-10-2007, 12:53 PM   #6
JimBass
Senior Member
 
Registered: Oct 2003
Location: New York City
Distribution: Debian Sid 2.6.32
Posts: 2,100

Rep: Reputation: 48
Cool. I would have thought that removing the firewire modules would have "dropped" what was eth1 to eth0 as well, but I have never been in a situation where I had to shuffle the names of the interfaces. That is surprising, I would have thought I'd see the same default behavior as you were expecting.

I'm on sid on my laptop and desktop here at home, and etch/sarge on the servers at work. None of them have any mention of NetworkManager or dhcdbd in /var/log/kernel.log. That (and the fact that there are capital letters involved, which isn't usual for Debian) makes me think that those processes are part of your particular X environment? I use KDE on my home systems, and no X is installed on the work machines. That seems like a logical conclusion, particularly if you're on Gnome or one of the other desktop environments.

In regards to getting Deb to start what you want as you want it, you might want to look into things that automate the install process. It is possible you'll find some info on that at the high availability page - http://www.linux-ha.org/HomePage or there may be some other type of automated startup process. It's been a long time since I've played with that, sorry I don't have better info for you on that.

Peace,
JimBass
 
Old 06-10-2007, 01:37 PM   #7
HowDoIProgramIt
Member
 
Registered: Nov 2006
Location: East Coast, USA (in "the great northeast")
Distribution: Custom / from source; Fedora, Debian, CentOS, Scientific; LFS.
Posts: 94

Original Poster
Rep: Reputation: 15
Thanks to all those who helped me get going; thought I should post a follow-up -

at this point, I'm happily running Debian Etch, with exactly what I want installed and running; no more, no less. For anyone who's trying to do something similar to what I am (eg., bring up a skeletal system and then fill in only those missing pieces they want to), without having to resort to going the whole 9 of writing their own boot, etc. scripts, building X && building GNOME, etc.), from what I've seen over the course of the last week, this (Debian) is the way to go.

As with anything different, it took a little time to get used to; personally, I don't think a week is unreasonable to invest in learning how to completely configure a distribution one isn't familiar with, on a hardware platform one had never used previously. I'll take it. The end result absolutely rocks; I couldn't be much happier with it.

At this point, the only way I would go back to the way I'd been putting systems together previously is kicking and screaming.

Some notes, for the benefit of anyone else stuck trying to figure out the same / similar issues:

Somewhere in the Debian documentation I stumbled accross a reference to a package named sysv-rc-conf. It seems to complement update-rc.d nicely, and also seems to have essentially the same command-line syntax as the "chkconfig" utility found in some other distributions / *NIXes.

The problem I was having with the virtual consoles not working once the system had finished booting was apparently related to the way I had "yaboot.conf" set up: the only way I could get Etch's installer to run correctly (again, this is on a Mac Mini) was with 'linux "video=ofonly"'. The installer wrote that setting into my yaboot.conf, though:

append="video=ofonly"

I changed the first entry in yaboot.conf to read:

Code:
image=/boot/vmlinux
        label=Linux_RADEONFB
        read-only
        initrd=/boot/initrd.img
        append="video=radeonfb:800x600-16@75"
(I also included an entry I labeled "Linux_SAFE" with "video=ofonly", just to be on the safe side), ran ybin, and I now have 6 virtual consoles (&& the X server on 7).

Pretty much immediately after getting that working, I went and downloaded. built & installed:

gpm - cutting & pasting text is about the only use I've
ever found for the damn mouse, so ...

screen - need I say more?

I couldn't think of one good reason to keep NetworkManager (period), or a DHCP client on a network that doesn't use DHCP, or avahi (sorry, but even it was appropriate for this setting, "zero-effort networking" has never been anything but a pain in the ass any time I've attempted to use it):
Code:
chmod 000 /etc/dbus-1/event.d/24dhcdbd
chmod 000 /etc/dbus-1/event.d/25NetworkManager
chmod 000 /etc/dbus-1/event.d/26NetworkManagerDispatcher
Turning avahi off proved to be easiest done by creating the following files:

Code:
root@ganymede:~# find /etc/rc?.d -name "K*avahi*"
/etc/rc0.d/K80avahi-daemon
/etc/rc1.d/K80avahi-daemon
/etc/rc2.d/K80avahi-daemon
/etc/rc3.d/K80avahi-daemon
/etc/rc4.d/K80avahi-daemon
/etc/rc5.d/K80avahi-daemon
/etc/rc6.d/K80avahi-daemon
and issuing the following command:
Code:
chmod 000 /etc/init.d/avahi-daemon
Eg., I stopped the service (K[0-9]{2}avahi-daemon} in each runlevel, then chmod'd the script so it cant be started (strictly speaking, that last step shouldn't be necessary; it will keep the service from being started accidentally, etc. though).

So... I now have a PPC platform to develop on, use as a webserver, etc. The gcc that was installed as part of the Debian install is Altivec enabled; I had enough energy to write a quick program to test that aspect of the machine last night. The results were impressive, and reminded me why I had taken such a liking to the little G4 in the first place.

The one thing I never was quite able to figure out was how / why the OS is so dead set on referring to the built-in ethernet adapter (Sun GEM 10baseT) as eth1 and not eth0; I tried pretty much every way I could think of - and all the ways that were suggested - to make that happen; ultimately, the only way I was able to was forcibly (either using 'ip' or the "ifrename" utility; even "iprename", which does its thing based on the adapter's MAC address, gives a warning regarding the reliability of "the swap":
Code:
 
Warning: Interface name is `eth0' at line 1, can't be mapped reliably.
I'm going to try a hunch later and rebuild a kernel without any support for ethernet-over-ieee1394; if the GEM starts appearing as eth0 after that, then it's pretty obvious what the problem is / was.

Thanks again to everyone for your help; I'm diggin' this system...

- Larry
 
Old 07-05-2007, 07:46 PM   #8
titetanium
Member
 
Registered: Mar 2004
Distribution: debian testing/unstable
Posts: 68

Rep: Reputation: 16
This thread has been an interesting read so far. I kind of remember running into the eth0/eth1 problem some time back when configuring Debian from scratch for the first time after getting my feet wet with Knoppix. I did fix the problem, but now I wish I had documented the steps I took to solving that. What I can tell you is that it had nothing to do with installing ifrename to force-brute the system to assign the desire interface to the desired network card....... at least I'm positive I've never gone that route.

More likely, I did something like changing the order in the runlevels with regards to /etc/init.d/networking and /etc/init.d/hotplug. What I remember doing was configuring hotplug to detect my wireless card before my built-in ethernet card was detected so that changed the interface order. But it's been some 4 yrs since I've done that and now this thread reminded me that in some distant future, I'm gonna regret not documenting my steps and posting it so I can do it again and again if I ever ran into that problem.

I'll tell you one thing, Debian really rocks once you've got it configured. I've never tried slackware nor gentoo, and won't even touch rpm based distros with a 10ft pole, (I've heard Gentoo and slackware are somewhat similar except with Gentoo, you have to compile everything you want to install, though they have great documentation).

Last edited by titetanium; 07-05-2007 at 07:48 PM.
 
Old 07-05-2007, 10:06 PM   #9
hitest
Senior Member
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 4,004

Rep: Reputation: 474Reputation: 474Reputation: 474Reputation: 474Reputation: 474
Thumbs up

Quote:
Originally Posted by titetanium
I've never tried slackware nor gentoo, and won't even touch rpm based distros with a 10ft pole, (I've heard Gentoo and slackware are somewhat similar except with Gentoo, you have to compile everything you want to install, though they have great documentation).
Slackware is a wonderful distro, albeit quite different from Debian.
In Slackware you can compile from source, install pre-built packages, or use build scripts. FreeBSD has a very similar installer to Slack.
Slack is a very worthwhile experience.
I'm a huge fan of Debian and am now running Etch on 11 machines ( 2 at home and 9 at work).
 
Old 07-06-2007, 06:11 AM   #10
nx5000
Senior Member
 
Registered: Sep 2005
Location: Out
Posts: 3,307

Rep: Reputation: 52
Quote:
Originally Posted by hitest
In Slackware you can compile from source, install pre-built packages, or use build scripts.
Yeah you can do this in debian too, I do it regularly. I really try to avoid non packaged programs thought, which are few in debian.

For the OP question, I have the same symptoms (which doesn't bother me)
eth0 is the ethernet over firewire. It's not even compiled in my kernel so the module doesn't even exist.
eth1 is my wire ethernet
eth2 is my wireless

ifconfig -a displays
eth1
eth2
irdA
lo

I am quite disappointed by NetworkManager, still. It overwrites and makes strange stuffs to my /etc/network/interfaces (which is a SYSTEM configuration file and I know how to handle it with or without X)
So I don't use it otherwise it fucks my configuration.
I have " auto eth1 " in /etc/network/interfaces and everything just works with eth1.

I guess you could remove eth0 by booting , checking that no module eth/ieee1394 is loaded (maybe move the blacklisted modules in /lib/modules to module-old.ko
Then rm /etc/udev/rules.d/*persistent-net.rules
Reboot
 
Old 07-06-2007, 06:33 AM   #11
hitest
Senior Member
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 4,004

Rep: Reputation: 474Reputation: 474Reputation: 474Reputation: 474Reputation: 474
Smile

Quote:
Originally Posted by nx5000
Yeah you can do this in debian too, I do it regularly. I really try to avoid non packaged programs thought, which are few in debian.
Thanks. So make works in Debian too. I'll go try that:-)

Edit: added later- One of the many things I really love about Debian is dependency checking (absent in slack). Have you encountered weird errors when compiling?

Last edited by hitest; 07-06-2007 at 06:58 AM.
 
Old 07-06-2007, 07:15 AM   #12
nx5000
Senior Member
 
Registered: Sep 2005
Location: Out
Posts: 3,307

Rep: Reputation: 52
Quote:
Originally Posted by hitest
Thanks. So make works in Debian too. I'll go try that:-)

Edit: added later- One of the many things I really love about Debian is dependency checking (absent in slack). Have you encountered weird errors when compiling?
Yes make works

For packaging, check out cdbs and debhelper. Usually, debian/rules files (equivalent of .spec under RH) are very small, everything is done behing the scene.

Yes, sometimes getting some packages from sources will lead to build-dependencies problems.
There are also sometimes some binary-dependency problems so that you can't install at all some packages. Only in testing (I have never encountered one in fact) or unstable.

You can check this debian broken package list.
example in sid:
PHP Code:
nvidia-glx-legacy     1.0.7185-4     

    
nvidia-glx-legacy 1.0.7185-4 depends on nvidia-glx-legacy-71xx 1.0.7185-4
    
nvidia-glx-legacy 1.0.7185-4 conflicts with nvidia-glx-legacy-71xx 1.0.7185-

Look at this post on LQ, it quite powerfull what apt can do
As I'm also testing other distro, I had the same question for Fedora but no answer..
I would really like to switch to something else, I try and try but always come back
Have fun with debian

Last edited by nx5000; 07-06-2007 at 07:17 AM.
 
Old 07-06-2007, 08:37 AM   #13
hitest
Senior Member
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 4,004

Rep: Reputation: 474Reputation: 474Reputation: 474Reputation: 474Reputation: 474
Talking

Quote:
Originally Posted by nx5000
Yes make works

For packaging, check out cdbs and debhelper. Usually, debian/rules files (equivalent of .spec under RH) are very small, everything is done behing the scene.

Yes, sometimes getting some packages from sources will lead to build-dependencies problems.
There are also sometimes some binary-dependency problems so that you can't install at all some packages. Only in testing (I have never encountered one in fact) or unstable.

You can check this debian broken package list.
example in sid:
PHP Code:
nvidia-glx-legacy     1.0.7185-4     

    
nvidia-glx-legacy 1.0.7185-4 depends on nvidia-glx-legacy-71xx 1.0.7185-4
    
nvidia-glx-legacy 1.0.7185-4 conflicts with nvidia-glx-legacy-71xx 1.0.7185-

Look at this post on LQ, it quite powerfull what apt can do
As I'm also testing other distro, I had the same question for Fedora but no answer..
I would really like to switch to something else, I try and try but always come back
Have fun with debian
Cool. Thanks for the links and information:-)
I'm a huge fan of Debian! My two favourite distros in no particular order are Slackware and Debian. If you've never tried Slackware I think it is worth a look, it is rock-solid ( like Debian) and highly customizable.
In August I'm going to try-out FreeBSD 7.0 when it is released. I ran FreeBSD 6.2 awhile ago.
 
Old 07-06-2007, 09:08 AM   #14
rupertwh
Member
 
Registered: Sep 2006
Location: Munich, Germany
Distribution: Debian / Ubuntu
Posts: 292

Rep: Reputation: 46
Quote:
Originally Posted by HowDoIProgramIt
creating a udev rule in a file I named "/etc/udev/rules.d/010_nic_rules", which contains:
KERNEL=="eth*",SYSFS{address}=="nn:nn:nn:nn:nn:nn",NAME="eth0"
Hi,

on my Debian 4.0 box (also pretty new to me, coming from SuSE) there is a file /etc/udev/rules.d/z25_persistent-net.rules with lines like:
Code:
# PCI device 0x10ec:0x8169 (r8169)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:40:f4:ef:32:b2", NAME="eth1"
maybe that will get you somewhere.
 
Old 07-06-2007, 09:19 AM   #15
nx5000
Senior Member
 
Registered: Sep 2005
Location: Out
Posts: 3,307

Rep: Reputation: 52
Yes rupertwh, it's this file. Usually the system will detect non present module or not loaded modules (this is where I am not sure, and why I asked the OP to move the module temporary) and regenerate this file if it does not exists. It would be better to not edit this file for removing a line (to check everything works and will still works when udev is reupdated)
Then you might need to re-order eth0 and eth1 probably manually editing (I don't know other method)


Quote:
My two favourite distros in no particular order are Slackware and Debian. If you've never tried Slackware I think it is worth a look, it is rock-solid ( like Debian) and highly customizable.
In August I'm going to try-out FreeBSD 7.0 when it is released. I ran FreeBSD 6.2 awhile ago.
13years ago I began with linux with slackware at home (after having played with unix at school).
And it was already solid. Then I moved to RedHat 7.3 for some time. Since 2 or 3 years I discovered debian (I'm new to this compared to some members)
I'm currently also playing with Fedora7 after playing with openSuse 10.2 but I'm not that happy about a lot of things.
For BSD, I just don't have the time.. that's my main problem
I would also like to try Hurd..
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
dark side convert with permissions troubles... Jim Yadon Linux - Newbie 5 08-21-2006 08:12 PM
LXer: The Dark Side of the Plugin LXer Syndicated Linux News 0 07-07-2006 08:03 PM
Wanting to go 100% dark side, but..... Slith(++1) Linux - Software 4 12-21-2005 09:28 PM
Debating going to the dark side... RySk8er30 Linux - General 15 03-10-2005 07:01 PM
Help me leave the dark side... Sagar_Indurkhya Slackware 4 09-16-2004 03:50 PM


All times are GMT -5. The time now is 05:13 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration