LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
Reload this Page Debian etch network connection issue
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices


Reply
Page 2 of 2 1 2
  Search this Thread
Old 02-27-2007, 10:01 PM   #16
Quakeboy02
Senior Member
 
Registered: Nov 2006
Distribution: Debian Linux 11 (Bullseye)
Posts: 3,402

Rep: Reputation: 141Reputation: 141

"Sorry, the only reason i'm editing them is because i have to plug in the desktop with debian, run the commands, then plug this laptop in and manually type all the things that come up which sucks with log files heh."

One more question to answer, please. Are you using a router or are you plugging directly into a cable/dsl modem? This just looks suspiciously like the problems I had with moving a wireless bridge between two Linux boxes. I think it could also happen with two different machines that have the same machine name. The first one the router sees works just fine, but the second is flaky as hell.
 
Old 02-27-2007, 10:04 PM   #17
RobertP
Member
 
Registered: Jan 2004
Location: Manitoba, Canada
Distribution: Debian
Posts: 454

Rep: Reputation: 32
If you are using Gnome's network-manager, you may have found a bug in it. The bug report, http://packages.debian.org/testing/net/network-manager , and http://bugs.debian.org/network-manager shows a very large number of errors. The one about disconnecting came from it. You could try removing network-manager and doing the configuration of your network from the command line. It is mostly editing /etc/network/interfaces and running /etc/init.d/networking restart.
 
Old 02-28-2007, 07:35 AM   #18
farslayer
LQ Guru
 
Registered: Oct 2005
Location: Northeast Ohio
Distribution: linuxdebian
Posts: 7,249
Blog Entries: 5

Rep: Reputation: 191Reputation: 191
Quote:
Originally Posted by HCLPfan
Sorry, the only reason i'm editing them is because i have to plug in the desktop with debian, run the commands, then plug this laptop in and manually type all the things that come up which sucks with log files heh.

Personally I would plug in another NIC card.. like a 3Com or Intel, then SSH to the box, you can then run your commands, and copy and paste them on the other machine.. figure out what the problem is, get the on-board NIC working, then pull the add in NIC ..
 
Old 02-28-2007, 09:33 AM   #19
HCLPfan
LQ Newbie
 
Registered: Dec 2004
Location: Dallas, Texas
Posts: 8

Original Poster
Rep: Reputation: 0
Hey guys, my laptop i was using's batter died last night so I couldn't post till now but I just wanted to say thanks for your help. I ended up just resolving the problem by switching back to sarge and all is well now. Thanks anyway.
 
Old 05-09-2009, 08:14 PM   #20
Lucasempire
LQ Newbie
 
Registered: May 2009
Posts: 4

Rep: Reputation: 0
i am having a very similar problem...
i recently installed debian lenny from a netinst disk onto a machine and i am having the same network issues. it is a wired network and i am using a netgear rt314 router. i have all the info that was asked of the op.

Code:
aisha@boxybrown:/var/log$ sudo cat syslog | grep eth0

May  9 16:46:22 localhost kernel: [    4.626537] eth0: Davicom DM9102/DM9102A rev 49 at Port 0xe800, 00:80:ad:7a:16:11, IRQ 18.
May  9 16:46:22 localhost kernel: [   18.700788] eth0: Setting full-duplex based on MII#1 link partner capability of 45e1.
May  9 16:46:23 localhost avahi-daemon[1957]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::280:adff:fe7a:1611.
May  9 16:46:23 localhost avahi-daemon[1957]: New relevant interface eth0.IPv6 for mDNS.
May  9 16:46:23 localhost avahi-daemon[1957]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.8.
May  9 16:46:23 localhost avahi-daemon[1957]: New relevant interface eth0.IPv4 for mDNS.
May  9 16:46:23 localhost avahi-daemon[1957]: Registering new address record for fe80::280:adff:fe7a:1611 on eth0.*.
May  9 16:46:23 localhost avahi-daemon[1957]: Registering new address record for 192.168.0.8 on eth0.IPv4.
May  9 16:46:27 localhost NetworkManager: <info>  eth0: Device is fully-supported using driver 'tulip'.
May  9 16:46:27 localhost NetworkManager: <info>  Now managing wired Ethernet (802.3) device 'eth0'.
May  9 16:46:27 localhost NetworkManager: <info>  Deactivating device eth0.
May  9 16:46:27 localhost avahi-daemon[1957]: Withdrawing address record for 192.168.0.8 on eth0.
May  9 16:46:27 localhost avahi-daemon[1957]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.8.
May  9 16:46:27 localhost avahi-daemon[1957]: Interface eth0.IPv4 no longer relevant for mDNS.
May  9 16:46:27 localhost avahi-daemon[1957]: Withdrawing address record for fe80::280:adff:fe7a:1611 on eth0.
May  9 16:46:27 localhost avahi-daemon[1957]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::280:adff:fe7a:1611.
May  9 16:46:27 localhost avahi-daemon[1957]: Interface eth0.IPv6 no longer relevant for mDNS.
May  9 16:46:27 localhost NetworkManager: <info>  Will activate wired connection 'eth0' because it now has a link.
May  9 16:46:27 localhost NetworkManager: <info>  SWITCH: no current connection, found better connection 'eth0'.
May  9 16:46:28 localhost dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
May  9 16:46:28 localhost NetworkManager: <info>  Will activate connection 'eth0'.
May  9 16:46:28 localhost NetworkManager: <info>  Device eth0 activation scheduled...
May  9 16:46:28 localhost NetworkManager: <info>  Activation (eth0) started...
May  9 16:46:28 localhost NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
May  9 16:46:28 localhost NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) started...
May  9 16:46:28 localhost NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
May  9 16:46:28 localhost NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
May  9 16:46:28 localhost NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) starting...
May  9 16:46:28 localhost NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) successful.
May  9 16:46:28 localhost NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
May  9 16:46:28 localhost NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) complete.
May  9 16:46:28 localhost NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
May  9 16:46:29 localhost NetworkManager: <info>  Activation (eth0) Beginning DHCP transaction.
May  9 16:46:30 localhost NetworkManager: <info>  DHCP daemon state is now 12 (successfully started) for interface eth0
May  9 16:46:30 localhost NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
May  9 16:46:31 localhost NetworkManager: <info>  DHCP daemon state is now 1 (starting) for interface eth0
May  9 16:46:33 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
May  9 16:46:33 localhost avahi-daemon[1957]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.8.
May  9 16:46:33 localhost avahi-daemon[1957]: New relevant interface eth0.IPv4 for mDNS.
May  9 16:46:33 localhost avahi-daemon[1957]: Registering new address record for 192.168.0.8 on eth0.IPv4.
May  9 16:46:33 localhost NetworkManager: <info>  DHCP daemon state is now 4 (reboot) for interface eth0
May  9 16:46:33 localhost NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled...
May  9 16:46:33 localhost NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure Get) started...
May  9 16:46:33 localhost dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.domain_search
May  9 16:46:33 localhost dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
May  9 16:46:33 localhost dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers
May  9 16:46:33 localhost dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.interface_mtu
May  9 16:46:33 localhost NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
May  9 16:46:33 localhost NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure Get) complete.
May  9 16:46:33 localhost NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...
May  9 16:46:33 localhost avahi-daemon[1957]: Withdrawing address record for 192.168.0.8 on eth0.
May  9 16:46:33 localhost avahi-daemon[1957]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.8.
May  9 16:46:33 localhost avahi-daemon[1957]: Interface eth0.IPv4 no longer relevant for mDNS.
May  9 16:46:33 localhost avahi-daemon[1957]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.8.
May  9 16:46:33 localhost avahi-daemon[1957]: New relevant interface eth0.IPv4 for mDNS.
May  9 16:46:33 localhost avahi-daemon[1957]: Registering new address record for 192.168.0.8 on eth0.IPv4.
May  9 16:46:34 localhost NetworkManager: <info>  Activation (eth0) successful, device activated.
May  9 16:46:34 localhost NetworkManager: <info>  Activation (eth0) Finish handler scheduled.
May  9 16:46:34 localhost NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
May  9 16:46:35 localhost avahi-daemon[1957]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::280:adff:fe7a:1611.
May  9 16:46:35 localhost avahi-daemon[1957]: New relevant interface eth0.IPv6 for mDNS.
May  9 16:46:35 localhost avahi-daemon[1957]: Registering new address record for fe80::280:adff:fe7a:1611 on eth0.*.
May  9 16:46:44 localhost kernel: [   43.316019] eth0: no IPv6 routers present
May  9 16:47:19 localhost NetworkManager: <info>  SWITCH: terminating current connection 'eth0' because it's no longer valid.
May  9 16:47:19 localhost NetworkManager: <info>  Deactivating device eth0.
May  9 16:47:19 localhost dhclient: There is already a pid file /var/run/dhclient.eth0.pid with pid 2442
May  9 16:47:19 localhost dhclient: DHCPRELEASE on eth0 to 192.168.0.1 port 67
May  9 16:47:19 localhost avahi-daemon[1957]: Withdrawing address record for 192.168.0.8 on eth0.
May  9 16:47:19 localhost avahi-daemon[1957]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.8.
May  9 16:47:19 localhost avahi-daemon[1957]: Interface eth0.IPv4 no longer relevant for mDNS.
May  9 16:47:20 localhost avahi-daemon[1957]: Withdrawing address record for fe80::280:adff:fe7a:1611 on eth0.
May  9 16:47:20 localhost avahi-daemon[1957]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::280:adff:fe7a:1611.
May  9 16:47:20 localhost avahi-daemon[1957]: Interface eth0.IPv6 no longer relevant for mDNS.
Code:
aisha@boxybrown:~$ sudo ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:80:ad:7a:16:11  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:55 errors:494 dropped:0 overruns:0 frame:0
          TX packets:91 errors:2 dropped:0 overruns:0 carrier:2
          collisions:0 txqueuelen:1000 
          RX bytes:6626 (6.4 KiB)  TX bytes:14446 (14.1 KiB)
          Interrupt:18 Base address:0xe800
Code:
aisha@boxybrown:~$ sudo grep dhclient /var/log/syslog
May  9 14:46:37 boxybrown dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
May  9 14:46:37 boxybrown dhclient: DHCPOFFER from 192.168.0.1
May  9 14:46:37 boxybrown dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
May  9 14:46:37 boxybrown dhclient: DHCPACK from 192.168.0.1
May  9 14:46:37 boxybrown dhclient: bound to 192.168.0.8 -- renewal in 123254 seconds.
May  9 14:47:34 boxybrown dhclient: There is already a pid file /var/run/dhclient.eth0.pid with pid 3963
May  9 14:47:34 boxybrown dhclient: killed old client process, removed PID file
May  9 14:47:34 boxybrown dhclient: DHCPRELEASE on eth0 to 192.168.0.1 port 67
May  9 16:46:33 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
May  9 16:46:33 localhost dhclient: DHCPACK from 192.168.0.1
May  9 16:46:33 localhost dhclient: bound to 192.168.0.8 -- renewal in 108556 seconds.
May  9 16:47:19 localhost dhclient: There is already a pid file /var/run/dhclient.eth0.pid with pid 2442
May  9 16:47:19 localhost dhclient: killed old client process, removed PID file
May  9 16:47:19 localhost dhclient: DHCPRELEASE on eth0 to 192.168.0.1 port 67
Code:
aisha@boxybrown:~$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp

auto eth0
Code:
aisha@boxybrown:~$ lspci
00:00.0 Host bridge: Intel Corporation 82845 845 [Brookdale] Chipset Host Bridge (rev 03)
00:01.0 PCI bridge: Intel Corporation 82845 845 [Brookdale] Chipset AGP Bridge (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 12)
00:1f.0 ISA bridge: Intel Corporation 82801BA ISA Bridge (LPC) (rev 12)
00:1f.1 IDE interface: Intel Corporation 82801BA IDE U100 Controller (rev 12)
00:1f.2 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1 (rev 12)
00:1f.3 SMBus: Intel Corporation 82801BA/BAM SMBus Controller (rev 12)
00:1f.4 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1 (rev 12)
01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400] (rev b2)
02:07.0 Multimedia audio controller: Cirrus Logic CS 4614/22/24/30 [CrystalClear SoundFusion Audio Accelerator] (rev 01)
02:08.0 Communication controller: Conexant HSF 56k Data/Fax/Voice/Spkp Modem (rev 01)
02:09.0 Ethernet controller: Davicom Semiconductor, Inc. 21x4x DEC-Tulip compatible 10/100 Ethernet (rev 31)
Code:
aisha@boxybrown:~$ sudo ifconfig
eth0      Link encap:Ethernet  HWaddr 00:80:ad:7a:16:11  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:72 errors:696 dropped:0 overruns:0 frame:0
          TX packets:91 errors:2 dropped:0 overruns:0 carrier:2
          collisions:0 txqueuelen:1000 
          RX bytes:8062 (7.8 KiB)  TX bytes:14446 (14.1 KiB)
          Interrupt:18 Base address:0xe800 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:560 (560.0 B)  TX bytes:560 (560.0 B)
Code:
aisha@boxybrown:~$ sudo route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
Code:
aisha@boxybrown:~$ lsmod
Module                  Size  Used by
nls_utf8                1760  1 
nls_cp437               5568  1 
vfat                    9184  1 
fat                    40896  1 vfat
nls_base                6820  4 nls_utf8,nls_cp437,vfat,fat
sd_mod                 22200  2 
usb_storage            77024  1 
ppdev                   6500  0 
lp                      8164  0 
speedstep_lib           4516  0 
cpufreq_userspace       3172  0 
cpufreq_conservative     5960  0 
cpufreq_stats           3776  0 
cpufreq_ondemand        6476  0 
freq_table              4224  2 cpufreq_stats,cpufreq_ondemand
cpufreq_powersave       1856  0 
ipv6                  235364  14 
loop                   12748  0 
parport_pc             22500  1 
parport                30988  3 ppdev,lp,parport_pc
pcspkr                  2432  0 
serio_raw               4740  0 
button                  6096  0 
psmouse                32336  0 
i2c_i801                7920  0 
i2c_core               19828  1 i2c_i801
rng_core                3940  0 
shpchp                 25528  0 
pci_hotplug            23460  1 shpchp
iTCO_wdt                9508  0 
intel_agp              22556  1 
agpgart                28776  1 intel_agp
evdev                   8000  3 
dcdbas                  6272  0 
ext3                  105512  1 
jbd                    39444  1 ext3
mbcache                 7108  1 ext3
ide_cd_mod             27652  0 
cdrom                  30176  1 ide_cd_mod
ide_floppy             12704  0 
ide_disk               10496  3 
dmfe                   16568  0 
ata_generic             4676  0 
libata                140416  1 ata_generic
scsi_mod              129324  3 sd_mod,usb_storage,libata
dock                    8304  1 libata
floppy                 47748  0 
uhci_hcd               18672  0 
usbcore               118224  3 usb_storage,uhci_hcd
tulip                  44064  0 
piix                    6568  0 [permanent]
ide_pci_generic         3908  0 [permanent]
ide_core               96136  5 ide_cd_mod,ide_floppy,ide_disk,piix,ide_pci_generic
thermal                15228  0 
processor              32544  1 thermal
fan                     4164  0 
thermal_sys            10856  3 thermal,processor,fan
 
Old 05-10-2009, 09:59 PM   #21
farslayer
LQ Guru
 
Registered: Oct 2005
Location: Northeast Ohio
Distribution: linuxdebian
Posts: 7,249
Blog Entries: 5

Rep: Reputation: 191Reputation: 191
Quote:
Originally Posted by Lucasempire View Post
i recently installed debian lenny from a netinst disk onto a machine and i am having the same network issues. it is a wired network and i am using a netgear rt314 router. i have all the info that was asked of the op.
I think this bug listing might resolve your issue..
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522592

Quote:
If you remove TULIP, remove DMFE, and load DMFE you can get internet
again...

rmmod tulip
rmmod dmfe
modprobe dmfe

then see if you can get an address.. if that works then blacklist the tulip module...
 
Old 05-11-2009, 03:03 PM   #22
Lucasempire
LQ Newbie
 
Registered: May 2009
Posts: 4

Rep: Reputation: 0
thanks farslayer, it reconnected and is staying connected.

how do i blacklist the tulip module?
 
Old 05-11-2009, 03:45 PM   #23
farslayer
LQ Guru
 
Registered: Oct 2005
Location: Northeast Ohio
Distribution: linuxdebian
Posts: 7,249
Blog Entries: 5

Rep: Reputation: 191Reputation: 191
edit the file /etc/modprobe.d/blacklist and add an entry at the bottom for blacklist tulip
 
Old 05-11-2009, 05:57 PM   #24
Lucasempire
LQ Newbie
 
Registered: May 2009
Posts: 4

Rep: Reputation: 0
i added the entry "blacklist tulip" to the bottom of /etc/modprobe.d/blacklist , but upon reboot the same previous condition occurs.

contents of /etc/modprobe.d/blacklist

Code:
# This file lists modules which will not be loaded as the result of
# alias expansion, with the purpose of preventing the hotplug subsystem
# to load them. It does not affect autoloading of modules by the kernel.
# This file is provided by the udev package.

# evbug is a debug tool and should be loaded explicitly
blacklist evbug

# these drivers are very simple, the HID drivers are usually preferred
blacklist usbmouse
blacklist usbkbd

# replaced by e100
blacklist eepro100

# replaced by tulip
blacklist de4x5

# replaced by tmscsim
blacklist am53c974

# watchdog drivers should be loaded only if a watchdog daemon is installed
blacklist acquirewdt
blacklist advantechwdt
blacklist alim1535_wdt
blacklist alim7101_wdt
blacklist booke_wdt
blacklist cpu5wdt
blacklist eurotechwdt
blacklist i6300esb
blacklist i8xx_tco
blacklist ib700wdt
blacklist ibmasr
blacklist indydog
blacklist ixp2000_wdt
blacklist ixp4xx_wdt
blacklist machzwd
blacklist mixcomwd
blacklist mpc8xx_wdt
blacklist mpcore_wdt
blacklist mv64x60_wdt
blacklist pcwd
blacklist pcwd_pci
blacklist pcwd_usb
blacklist s3c2410_wdt
blacklist sa1100_wdt
blacklist sbc60xxwdt
blacklist sbc8360
blacklist sc1200wdt
blacklist sc520_wdt
blacklist scx200_wdt
blacklist shwdt
blacklist softdog
blacklist w83627hf_wdt
blacklist w83877f_wdt
blacklist w83977f_wdt
blacklist wafer5823wdt
blacklist wdt285
blacklist wdt977
blacklist wdt
blacklist wdt_pci

# blacklisted by admin carmelo due to network issues
blacklist tulip
 
Old 05-11-2009, 11:02 PM   #25
farslayer
LQ Guru
 
Registered: Oct 2005
Location: Northeast Ohio
Distribution: linuxdebian
Posts: 7,249
Blog Entries: 5

Rep: Reputation: 191Reputation: 191
Sorry looks like my blacklist directions are incorrect..

follow this guide instead to properly blacklist that module.

http://wiki.debian.org/KernelModuleBlacklisting
 
Old 05-12-2009, 06:46 PM   #26
Lucasempire
LQ Newbie
 
Registered: May 2009
Posts: 4

Rep: Reputation: 0
thanks again, networking is running well.
 
  


Reply
Page 2 of 2 1 2

Tags
dropping, etch, networking


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


Similar Threads
Thread Thread Starter Forum Replies Last Post
update Debian testing etch RC1 to etch stable cccc Debian 11 01-08-2007 10:02 PM
Internet Connection issue with 2 Network interfaces Andrea_44 Ubuntu 1 10-05-2006 03:08 PM
Debian Etch poptop, cannot connect issue... kbutcher5 Linux - Networking 1 06-27-2006 10:07 AM
Debian Etch Half Network Problem KRiSX.cjb.net Debian 4 06-06-2006 05:26 PM
No Network Connection With Debian al042077 Linux - Networking 2 06-25-2005 11:39 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 04:59 PM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
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
Open Source Consulting | Domain Registration