Re: [SLUG] Delay between booting and going to gdm login screen
On Thu, 18 Dec 2003, Grant Parnell wrote: On Wed, 17 Dec 2003, Andrew Monkhouse wrote: Hi, I recently did a clean install of RedHat 9 onto my system (and run the updates), and initially had it booting to runlevel 3. I later changed that in inittab to go to runlevel 5. Now when I boot, it stops at the terminal login screen until I press enter a few times, then it starts X and goes to the graphical login screen. This is not a case of me being impatient: if I leave it at the terminal login screen for a few hours, it will still be there. Then when I press enter a few times, it will start X and go to the graphical login screen. snip Apart from that... you might modify the line in /etc/inittab that starts X to log all output to a file if it's an X problem. That was a good suggestion. I had to do multiple levels of logging, since logging the line in inittab only told me that the next script was running. So then I had to log the next set of scripts then the next level of scripts ... But got there eventually - turns out that for some reason my environmental variable for ORACLE_HOME is not set when the gdm script runs, so it pauses to find out what the correct value should be. Now I have to find out why the Oracle scripts are even being called when starting gdm. But at least I know where I am going now. Thankyou. Regards, Andrew _ Get less junk mail with ninemsn Premium. Click here http://ninemsn.com.au/premium/landing.asp -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [slug] networking problems
Hello Sluggers! I think this is an accurate summation of my problems. ¨Linux Ethernet-Howto by Paul Gortmaker v2.9, Aug 25, 2003 This is the Ethernet-Howto, which is a compilation of information about which ethernet devices can be used for Linux, and how to set them up. Note that this Howto is focused on the hardware and low level driver aspect of the ethernet cards, and does not cover the software end of things like ifconfig and route. That information is found in various other Linuxdocumentation. snip... 1.1. New Versions of this Document New versions of this document can be retrieved from: Ethernet-HOWTO http://metalab.unc.edu/mdw/HOWTO/Ethernet-HOWTO.html or for those wishing to use FTP and/or get non-HTML formats: Sunsite HOWTO Archive ftp://metalab.unc.edu/pub/Linux/docs/HOWTO/ ,.snip. 2.9.3. All cards detected but two fail to work in PCI machine Version 1 of the PCI spec allowed for some slots to be bus master and some slots to be slave (non-bus master) slots. To avoid the problems associated with people putting BM cards into slave slots, the v2 of the PCI spec said that all slots should be BM capable. Hovever most PCI chipsets only have four BM pins, and so if you have a five slot board, chances are that two slots share one of the BM pins! This allows the board to meet the requirements of the v2 spec (but not the intent). So if you have a bunch of cards, and two of them fail to work, they may be in slots that share a BM pin.¨ Now to test it... Regards, Nicholas Tomlin. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
[SLUG] iptables (debian)
Hi, Just recently tried out debian on one of my old machines in place of a redhat system I had been using for the past year. But I am having trouble with an iptables firewall script which keeps insisting on spraying stuff to my terminal (tty1,2,3...) even though its being syslogged into /var/log/messages with syslog priority of 'info' using a LOG target. It doesn't just print to any tty; it assiduously finds the one I'm currently on and prints to that (ie the one currently on-screen locally). It doesn't seem to happen when I log in remotely but still, this is starting to get me down. example (iptables 'seems' to print this both to tty and /var/log/messages... ) - IN=ppp0 OUT= MAC= SRC=63.154.36.125 DST=203.206.0.244 LEN=48 TOS=0x00 PREC=0x00 TTL=110 ID=12283 DF PROTO=TCP SPT=3830 DPT=135 WINDOW=8760 RES=0x00 SYN URGP=0 IN=ppp0 OUT= MAC= SRC=63.154.36.125 DST=203.206.0.244 LEN=48 TOS=0x00 PREC=0x00 TTL=110 ID=12305 DF PROTO=TCP SPT=3830 DPT=135 WINDOW=8760 RES=0x00 SYN URGP=0 - (I compiled and installed a 2.4.13 kernel over the 'vanilla' 2.2.20 and am wondering if the LOG facility of iptables and syslogd are the problem. Have also disabled any '(x)console/tty' items from /etc/syslog.conf ) It can't be a big thing. Can anyone help? Thanks, Daniel. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] Intel EtherExpress Pro 100 - debian
First things first thanks to Mary, Dan, CTD David for their help with this. I tried the tulip module, which also failed to install. The error from the tulip module and the eepro100 module is init_module:No such device ifconfig does not list eth0 and there is no eth0 in my /dev directory. Could the problem be that debian doesn't know about the ethernet card? How do I tell debian that the card is there and to use it? I'm happy with a dodgy driver for just as long as it takes me to %s/stable/unstable/g in my sources.list apt-get update apt-get dist-upgrade wherupon I can probably get hold of the e100 driver with the minimum of fuss. Does that make any sense? I've just got a sneaking suspicion I could download kernel sources, burn to cd, unpack in my debian, compile install the same and I still won't be able to get onto the net. Having said that, I really have no clue. Thanks again, Hal -- ___ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] iptables (debian)
On Sat, 2003-12-20 at 22:26, Daniel Bush wrote: am wondering if the LOG facility of iptables and syslogd are the problem. Have also disabled any '(x)console/tty' items from /etc/syslog.conf ) It's always possible you missed something... In any case, I always found on my Debian systems that to be sane and happy I would do the following: rm /dev/console ln -s /dev/tty2 /dev/console [where 2 was a vt I removed the getty from and had it just for logging] That, in turn, is a trick I learned from years and years ago on Xenix systems when the default resulting in the same effect you're describing - caused because /dev/console was pointing at /dev/tty0 - which results in any and all console [virtual] ttys being sprayed. I never actually saw anything like /dev/tty0 being linked to /dev/console, but it sure seemed that way on my Debian boxes. This all assumes that replacing /dev/console as I suggest is a sane and ok idea - Lord knows I could have been committing some horrible faux pas. I'm sure the Debian people out there in our lovely community will have a more authoritative answer for you; it hasn't ever seemed to be a problem on my lovely shiny Gentoo machines... :) AfC Toronto -- Andrew Frederick Cowie Operational Dynamics Consulting Pty Ltd Australia +61 2 9977 6866 North America +1 646 472 5054 http://www.operationaldynamics.com/ -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] Intel EtherExpress Pro 100 - debian
On Sun, 2003-12-21 at 15:01, Hal Ashburner wrote: Does that make any sense? I've just got a sneaking suspicion I could download kernel sources, burn to cd, unpack in my debian, compile install the same and I still won't be able to get onto the net. Having said that, I really have no clue. This is how I once installed Debian woody on my system (which has an Intel PRO 100VE). Firstly, I did a base install of Debian with compilers and kernel-headers-2.4.18-bf24. Along with this, I had downloaded the source for the e100 module from Intel's website. I then compiled the modules by doing ./configure;make After performing 'make', rather than doing 'make install' -- I mounted a vfat-formatted floppy and copied *.o to the floppy disk. Then, during the install -- after installing the modules off the CD -- just before choosing the 'configure and load modules' bit, I switched over to the 2nd virtual terminal (alt+f2) and mounted /floppy. I then cd'd to /lib/modules/2.4.18-bf24/kernel/drivers/net/ and ran: cp /floppy/* ./ I then unmounted /floppy and returned to the normal install where I then continued to the module configuration where I loaded 'e100' from the list of network card drivers. Hope this helps. -- - Chris -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] Open Source in Iraq.
At Thu, 18 Dec 2003 15:06:56 +1100, Jeff Waugh wrote: quote who=David Killen An interesting article I found about the possibilities of Open Source in Iraq Interestingly enough, we just kicked off a mailing list for GNOME in Iran. Hopefully we don't get a GNOME/KDE-Iran/Iraq war on our hands. Aren't Americans banned from exporting things to Iran or something? How does this affect GNOME? (or is this just a user list at the moment) (Luckily Debian hasn't got any developers in any of the 6(?) US-banned countries so hasn't had to deal with this issue yet) -- - Gus -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
RE: [SLUG] iptables (debian)
It doesn't just print to any tty; it assiduously finds the one I'm currently on and prints to that (ie the one currently on-screen locally). It doesn't seem to happen when I log in remotely but still, this is starting to get me down. I've noticed this with the Shorewall firewall. It was driving me nuts, until I read their FAQ Shorewall is writing log messages all over my console making it unusable! Answer: If you are running Shorewall version 1.4.4 or 1.4.4a then check the errata. Otherwise, see the 'dmesg' man page (man dmesg). You must add a suitable 'dmesg' command to your startup scripts or place it in /etc/shorewall/start. Under RedHat, the max log level that is sent to the console is specified in /etc/sysconfig/init in the LOGLEVEL variable. (http://www.shorewall.net/FAQ.htm#faq16) I added dmesg -n 2 to the Shorewall startup script (it could also go in another startup script) and haven't seen anything since. Cheers, Julian. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
