[NTLUG:Discuss] Discuss Digest, Vol 69, Issue 9
John Swink
jswink at brick.com
Mon Sep 8 16:13:37 CDT 2008
PLEASE REMOVE ME FROM YOU MAILING LIST.
YOUR EMAILS ARE BYPASSING MY OUTLOOK LACK OF SECURITY.
I HAVE TRIED TO UNSUBSCRIBE AND IT APPARENTLY FAILED.
JSwink at Brick.com
John Swink, PE (Maryland)
Acme Brick Company
DFW Sales
801 Airport Freeway
Euless, TX 76040-4313
817-714-9523 Cell (preferred)
682-503-5109 Office
JSwink at Brick.com <mailto:JSwink at Brick.com>
682-503-5102 Fax (if you must)
-----Original Message-----
From: discuss-bounces at ntlug.org [mailto:discuss-bounces at ntlug.org] On
Behalf Of discuss-request at ntlug.org
Sent: Monday, September 08, 2008 4:03 PM
To: discuss at ntlug.org
Subject: Discuss Digest, Vol 69, Issue 9
Send Discuss mailing list submissions to
discuss at ntlug.org
To subscribe or unsubscribe via the World Wide Web, visit
http://www.ntlug.org/mailman/listinfo/discuss
or, via email, send a message with subject or body 'help' to
discuss-request at ntlug.org
You can reach the person managing the list at
discuss-owner at ntlug.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Discuss digest..."
Today's Topics:
1. eth0 died on reboot (Dennis Kaptain)
2. Re: Sept presentation. (Ted Gould)
3. Re: Administrative Priviledges (Ted Gould)
4. Re: DVD writing problems. (terry)
5. Re: DVD writing problems. (Steve Baker)
6. Re: eth0 died on reboot (terry)
7. Re: Backing up an FC6 desktop? (terry)
8. Re: Backing up an FC6 desktop? (terry)
9. OT: tapes and buffers (Fred James)
----------------------------------------------------------------------
Message: 1
Date: Mon, 8 Sep 2008 11:03:08 -0700 (PDT)
From: Dennis Kaptain <dkaptain at yahoo.com.mx>
Subject: [NTLUG:Discuss] eth0 died on reboot
To: discuss at ntlug.org
Message-ID: <4872.45438.qm at web58702.mail.re1.yahoo.com>
Content-Type: text/plain; charset=iso-8859-1
I removed an unused pci card from my PC. After I restarted it, eth0 was
dead. (no I didn't remove my network card ;-) )
The network card is built into the motherboard.
Using another computer, I have verified that the port on the router and
the cable are both good.
Does anybody have any ideas what I could try next?
Thanks
Dennis
[root at amor ~]# service network restart
Shutting down loopback interface: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0:
Determining IP information for eth0...PING 192.168.1.254 (192.168.1.254)
from 192.168.1.65 eth0: 56(84) bytes of data.
--- 192.168.1.254 ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time
2999ms
, pipe 3
failed.
[FAILED]
[root at amor ~]#
What happens during network restart on /var/log/messages:
tail -f /var/log/messages
Sep 8 12:24:50 amor kernel: ADDRCONF(NETDEV_UP): eth0: link is not
ready
Sep 8 12:24:50 amor dhclient: DHCPREQUEST on eth0 to 255.255.255.255
port 67
Sep 8 12:24:58 amor dhclient: DHCPREQUEST on eth0 to 255.255.255.255
port 67
Sep 8 12:25:06 amor dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
port 67 interval 5
Sep 8 12:25:11 amor dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
port 67 interval 14
Sep 8 12:25:25 amor dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
port 67 interval 21
Sep 8 12:25:46 amor dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
port 67 interval 10
Sep 8 12:25:56 amor dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
port 67 interval 10
Sep 8 12:26:05 amor dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
port 67 interval 1
Sep 8 12:26:07 amor dhclient: No DHCPOFFERS received.
Sep 8 12:26:07 amor dhclient: Trying recorded lease 192.168.1.65
Sep 8 12:26:07 amor avahi-daemon[2606]: Joining mDNS multicast group on
interface eth0.IPv4 with address 192.168.1.65.
Sep 8 12:26:07 amor avahi-daemon[2606]: New relevant interface
eth0.IPv4 for mDNS.
Sep 8 12:26:07 amor avahi-daemon[2606]: Registering new address record
for 192.168.1.65 on eth0.IPv4.
Sep 8 12:26:10 amor avahi-daemon[2606]: Withdrawing address record for
192.168.1.65 on eth0.
Sep 8 12:26:10 amor avahi-daemon[2606]: Leaving mDNS multicast group on
interface eth0.IPv4 with address 192.168.1.65.
Sep 8 12:26:10 amor avahi-daemon[2606]: Interface eth0.IPv4 no longer
relevant for mDNS.
Here from dmesg, eth0 is found and a driver e10001 is installed:
dmesg
e1000e: Intel(R) PRO/1000 Network Driver - 0.2.0
e1000e: Copyright (c) 1999-2007 Intel Corporation.
ACPI: PCI Interrupt 0000:00:19.0[A] -> GSI 20 (level, low) -> IRQ 20
PCI: Setting latency timer of device 0000:00:19.0 to 64
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.02 (26-Jul-2007)
iTCO_wdt: Found a ICH8 or ICH8R TCO device (Version=2, TCOBASE=0x0460)
iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
eth0: (PCI Express:2.5GB/s:Width x1) 00:16:76:c4:cd:10
eth0: Intel(R) PRO/1000 Network Connection
eth0: MAC: 4, PHY: 6, PBA No: ffffff-0ff
ACPI: PCI Interrupt 0000:00:1f.3[B] -> GSI 21 (level, low) -> IRQ 21
here from lsmod and lspci it looks like the driver really is installed
and the card really was seen
lsmod | grep e1000e
e1000e 84709 0
lspci
00:19.0 Ethernet controller: Intel Corporation 82566DC Gigabit Network
Connection (rev 02)
__________________________________________________
Correo Yahoo!
Espacio para todos tus mensajes, antivirus y antispam ?gratis!
Reg?strate ya - http://correo.yahoo.com.mx/
------------------------------
Message: 2
Date: Mon, 08 Sep 2008 13:34:05 -0500
From: Ted Gould <ted at gould.cx>
Subject: Re: [NTLUG:Discuss] Sept presentation.
To: NTLUG Discussion List <discuss at ntlug.org>
Message-ID: <1220898845.17421.4.camel at shi>
Content-Type: text/plain; charset="us-ascii"
On Sun, 2008-09-07 at 20:34 -0500, Chris Cox wrote:
> I know at least two people asked me about presenting in September...
> but I don't remember who.... so... first person to reply WITH
> topic (for the Calendar page), wins!!
>
> Let me know.. Sept meeting is on 9/20.
I was one of those, but there is no an event at my son's school so I'd
rather go in Oct. I'd be happy to let the other person go. Well,
unless it's something I really want to see :)
--Ted
------------------------------
Message: 3
Date: Mon, 08 Sep 2008 13:36:29 -0500
From: Ted Gould <ted at gould.cx>
Subject: Re: [NTLUG:Discuss] Administrative Priviledges
To: chef11994 at sbcglobal.net, NTLUG Discussion List <discuss at ntlug.org>
Message-ID: <1220898989.17421.6.camel at shi>
Content-Type: text/plain; charset="us-ascii"
On Sun, 2008-09-07 at 10:55 -0700, Allen Meyers wrote:
> At boot of kubuntu I was presented with an error message I had
> never seen before and was wondering if someone could share the
> possible why's
> Message was Starting without administrative priviledges
Typically this is a program that needs to run with elevated privileges
but does not have them. I'm not as sure about Kubuntu, but on standard
Ubuntu you can run the program with a "gksu" before it and you will get
prompted for you password to give the program administrative privileges.
--Ted
------------------------------
Message: 4
Date: Mon, 8 Sep 2008 13:48:03 -0500
From: terry <trryhend at gmail.com>
Subject: Re: [NTLUG:Discuss] DVD writing problems.
To: "NTLUG Discussion List" <discuss at ntlug.org>
Message-ID:
<f61662290809081148h21baa0des4f40ffcc43011064 at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On Sat, Sep 6, 2008 at 9:20 PM, Steve Baker <steve at sjbaker.org> wrote:
> I'm planning to upgrade my main box from SuSE 9.3 to OpenSuSE 11.0, so
I
> need to burn a DVD full of freshly downloaded goodies. Sadly, my
aging
> CD-Writer can't write DVD's - so I went out and bought a shiney new
$40
> Pioneer DVR-116D and a box of DVD-RW disks - which the drive claims to
> be able to write at 20x. It claims to be able to write all of the
> combinations of -RW, -R, +RW, etc.
>
> I'm using K3b for burning disks...been using it for years.
>
> I can burn CD-ROMs with the new drive - no problem - so it's obviously
> connected up alright. But K3b refuses to burn an iso-DVD.
>
> It picks up the drive name OK - it recommended that I turn on IDE DMA
> for it - which I did - and it recommended that I remove the drive's
> entry in /etc/fstab - which I did. I tried upgrading to the latest
> version of K3b - it doesn't make a difference. It looks like K3d
> doesn't recognise that there is a disk in the tray - it keeps telling
me
> to load a disk and no matter what I do with the drive's disk tray -
K3d
> just doesn't seem to notice.
>
> Seems weird that it can detect that a CD is in the drive but not a
DVD.
>
> At this point, I'm completely stuck. I can't imagine how this could
be
> going wrong. Help!
>
> -- Steve.
>
>
Are you sure you have a good DVD+R disk in the drive? - Maybe what you
have
is a defective DVD disk?
--
<><
------------------------------
Message: 5
Date: Mon, 08 Sep 2008 13:59:22 -0500
From: Steve Baker <steve at sjbaker.org>
Subject: Re: [NTLUG:Discuss] DVD writing problems.
To: trryhend at gmail.com, NTLUG Discussion List <discuss at ntlug.org>
Message-ID: <48C5760A.3070806 at sjbaker.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
terry wrote:
> Are you sure you have a good DVD+R disk in the drive? - Maybe what you
have
> is a defective DVD disk?
>
>
Well, the problem was with DVD-RW's - nor DVD+R's. However, I just
bought a box of DVD+R's
and the drive writes them just fine (which means I can finally get SuSE
11.0 installed).
So CD-R's, DVD+R's, non-blank DVD-RW's and video DVD's all work just
fine - but blank
DVD-RW's aren't recognised.
It couldn't be a single blank disk that's the problem because I tried
several disks out of the same
batch. It also can't be that the entire batch of disks are bad because
I tried doing this:
1) Take a blank DVD-RW.
2) Write to it with a different computer (works OK)
3) Put the disk into my machine.
4) The drive recognises it just fine.
5) Tell it to erase the disk...which it does without problems.
6) ...and it immediately says that there is no disk in the drive.
So that must have been a "good" disk - yet it fails.
Oh well - I'll just by DVD+RW's in future and write it off to
experience. But the drive
box - and what K3b reads from the actual drive - both say that it can
write DVD-RW's.
Very weird.
-- Steve.
------------------------------
Message: 6
Date: Mon, 8 Sep 2008 14:01:16 -0500
From: terry <trryhend at gmail.com>
Subject: Re: [NTLUG:Discuss] eth0 died on reboot
To: "NTLUG Discussion List" <discuss at ntlug.org>
Message-ID:
<f61662290809081201s182f5dd1pff3fdd9f0d1db714 at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
1) Test the NIC with ethtool
ethtool eth0
2) Set static IP and see if you can ping that IP 2b) See if you can
ping
router
ifconfig eth0 192.168.1.91
ping 192.168.1.91
ping 192.168.1.1
3) Try a live CD
(...or USB)
On Mon, Sep 8, 2008 at 1:03 PM, Dennis Kaptain
<dkaptain at yahoo.com.mx>wrote:
> I removed an unused pci card from my PC. After I restarted it, eth0
was
> dead. (no I didn't remove my network card ;-) )
> The network card is built into the motherboard.
>
> Using another computer, I have verified that the port on the router
and the
> cable are both good.
>
> Does anybody have any ideas what I could try next?
>
> Thanks
> Dennis
>
>
> [root at amor ~]# service network restart
> Shutting down loopback interface: [ OK ]
> Bringing up loopback interface: [ OK ]
> Bringing up interface eth0:
> Determining IP information for eth0...PING 192.168.1.254
(192.168.1.254)
> from 192.168.1.65 eth0: 56(84) bytes of data.
>
> --- 192.168.1.254 ping statistics ---
> 4 packets transmitted, 0 received, +3 errors, 100% packet loss, time
2999ms
> , pipe 3
> failed.
> [FAILED]
> [root at amor ~]#
>
> What happens during network restart on /var/log/messages:
> tail -f /var/log/messages
> Sep 8 12:24:50 amor kernel: ADDRCONF(NETDEV_UP): eth0: link is not
ready
> Sep 8 12:24:50 amor dhclient: DHCPREQUEST on eth0 to 255.255.255.255
port
> 67
> Sep 8 12:24:58 amor dhclient: DHCPREQUEST on eth0 to 255.255.255.255
port
> 67
> Sep 8 12:25:06 amor dhclient: DHCPDISCOVER on eth0 to
255.255.255.255port 67 interval 5
> Sep 8 12:25:11 amor dhclient: DHCPDISCOVER on eth0 to
255.255.255.255port 67 interval 14
> Sep 8 12:25:25 amor dhclient: DHCPDISCOVER on eth0 to
255.255.255.255port 67 interval 21
> Sep 8 12:25:46 amor dhclient: DHCPDISCOVER on eth0 to
255.255.255.255port 67 interval 10
> Sep 8 12:25:56 amor dhclient: DHCPDISCOVER on eth0 to
255.255.255.255port 67 interval 10
> Sep 8 12:26:05 amor dhclient: DHCPDISCOVER on eth0 to
255.255.255.255port 67 interval 1
> Sep 8 12:26:07 amor dhclient: No DHCPOFFERS received.
> Sep 8 12:26:07 amor dhclient: Trying recorded lease 192.168.1.65
> Sep 8 12:26:07 amor avahi-daemon[2606]: Joining mDNS multicast group
on
> interface eth0.IPv4 with address 192.168.1.65.
> Sep 8 12:26:07 amor avahi-daemon[2606]: New relevant interface
eth0.IPv4
> for mDNS.
> Sep 8 12:26:07 amor avahi-daemon[2606]: Registering new address
record for
> 192.168.1.65 on eth0.IPv4.
> Sep 8 12:26:10 amor avahi-daemon[2606]: Withdrawing address record
for
> 192.168.1.65 on eth0.
> Sep 8 12:26:10 amor avahi-daemon[2606]: Leaving mDNS multicast group
on
> interface eth0.IPv4 with address 192.168.1.65.
> Sep 8 12:26:10 amor avahi-daemon[2606]: Interface eth0.IPv4 no longer
> relevant for mDNS.
>
>
> Here from dmesg, eth0 is found and a driver e10001 is installed:
> dmesg
> e1000e: Intel(R) PRO/1000 Network Driver - 0.2.0
> e1000e: Copyright (c) 1999-2007 Intel Corporation.
> ACPI: PCI Interrupt 0000:00:19.0[A] -> GSI 20 (level, low) -> IRQ 20
> PCI: Setting latency timer of device 0000:00:19.0 to 64
> iTCO_wdt: Intel TCO WatchDog Timer Driver v1.02 (26-Jul-2007)
> iTCO_wdt: Found a ICH8 or ICH8R TCO device (Version=2, TCOBASE=0x0460)
> iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
> eth0: (PCI Express:2.5GB/s:Width x1) 00:16:76:c4:cd:10
> eth0: Intel(R) PRO/1000 Network Connection
> eth0: MAC: 4, PHY: 6, PBA No: ffffff-0ff
> ACPI: PCI Interrupt 0000:00:1f.3[B] -> GSI 21 (level, low) -> IRQ 21
>
> here from lsmod and lspci it looks like the driver really is installed
and
> the card really was seen
> lsmod | grep e1000e
> e1000e 84709 0
>
> lspci
> 00:19.0 Ethernet controller: Intel Corporation 82566DC Gigabit Network
> Connection (rev 02)
>
> __________________________________________________
> Correo Yahoo!
> Espacio para todos tus mensajes, antivirus y antispam ?gratis!
> Reg?strate ya - http://correo.yahoo.com.mx/
>
> _______________________________________________
> http://www.ntlug.org/mailman/listinfo/discuss
>
--
<><
------------------------------
Message: 7
Date: Mon, 8 Sep 2008 15:38:28 -0500
From: terry <trryhend at gmail.com>
Subject: Re: [NTLUG:Discuss] Backing up an FC6 desktop?
To: jktaber at charter.net, "NTLUG Discussion List" <discuss at ntlug.org>
Message-ID:
<f61662290809081338n679f5d30w3cb489ecc0cefa2d at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On Sun, Sep 7, 2008 at 8:34 AM, John K. Taber <jktaber at charter.net>
wrote:
>
> Mondo at first looked attractive for backing up my FC6 desktop. But
> Googling the forums
> reveals that Mondo has a problem with LVM, which I have.
>
> I like the idea of a bootable backup media (I'm thinking CDs), and
> complete restore.
>
> Any ideas?
>
>
> _______________________________________________
> http://www.ntlug.org/mailman/listinfo/discuss
Doing it to CD's if you need to use multiple CDs, it's complicated and
I've not done that. If you can fit it onto a single CD or DVD, that's
pretty easy, just create an iso image of the files and burn to CD.
Most of the CD burner software packages will do that for you. Or you
can do it manually.
See:
man mkisiofs
I have had good luck doing it across networks and it's a little easier.
If you have another PC on your network with plenty of HD space, you
could back up across the network.
The whole drive:
dd if=/dev/hda1 | ssh user at host 'gzip - > /home/user/image.gz'
(where user is valid username of other system)
(where host is hostname or IP of other system)
Just the /home dir
rsync -Cavz /home -Cavz user at host:/home/user/backup
(where user is valid username of other system)
(where host is hostname or IP address of other system)
(this places all your user directories and accompanying files in
a directory called "backup")
rsync -Cavz /home/user -Cavz user at host:/home/user/backup
(where /home/user is the username of only the user that needs
backing up)
(where user is valid username of other system)
(where host is hostname or IP address of other system)
(this places only your one user's files in a directory called
"backup")
Large enough USB drive:
tar -cvzf /media/disk/home.tgz /home
(after plugging in the device and mounting it under /media/disk
)
(this gives you a tar'd and compressed file containing all
user directories and accompaning files)
Large enough USB drive:
tar -cvzf /media/disk/home.tgz /home/user
(after plugging in the device and mounting it under
/media/disk )
(where user is username that needs to be backed up)
(this gives you a tar'd and compressed file containing only
one user and accompaning files)
There are some auto-backup tools you can use, you might look at
freshmeat.net or just do a google search
You could sift through
http://freshmeat.net/search/?q=backup§ion=projects&Go.x=0&Go.y=0
for relevant packages. Or:
http://freshmeat.net/search/?q=backup+restore§ion=projects&Go.x=0&Go
.y=0
--
<><
------------------------------
Message: 8
Date: Mon, 8 Sep 2008 15:56:47 -0500
From: terry <trryhend at gmail.com>
Subject: Re: [NTLUG:Discuss] Backing up an FC6 desktop?
To: "NTLUG Discussion List" <discuss at ntlug.org>
Message-ID:
<f61662290809081356h365c4ca3i42ff221480470f9f at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
If this is a Desktop PC and you are wanting to do an upgrade and you
have /home on a separate partition, just leave that partition
un-formatted and do fresh FC9 install. If you don't have /home on a
separate drive or partition, copy it to one.
In the case of just adding another drive:
fdisk /dev/hdb
(make a linux partition)
(If the new partition is /dev/hdb1):
mkfs.ext3 /dev/hdb1
reboot
mkdir /mnt/hdb1
mount /dev/hdb1 /mnt/hdb1
cp -a /home /mnt/hdb1
or
cp -a /home/user /mnt/hdb1
On Sun, Sep 7, 2008 at 8:34 AM, John K. Taber <jktaber at charter.net>
wrote:
> Mondo at first looked attractive for backing up my FC6 desktop. But
> Googling the forums
> reveals that Mondo has a problem with LVM, which I have.
>
> I like the idea of a bootable backup media (I'm thinking CDs), and
> complete restore.
>
> Any ideas?
>
>
> _______________________________________________
> http://www.ntlug.org/mailman/listinfo/discuss
>
--
<><
------------------------------
Message: 9
Date: Mon, 08 Sep 2008 16:02:21 -0500
From: Fred James <fredjame at fredjame.cnc.net>
Subject: [NTLUG:Discuss] OT: tapes and buffers
To: NTLUG Discussion List <discuss at ntlug.org>
Message-ID: <48C592DD.50003 at fredjame.cnc.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
All
This came up in a discussion of backups and tapes ...
I was told that a tape has a minimum write speed, below which it
"shoe shines" - that is when the buffer runs out the tape stops,
reverses and repositions while waiting for the buffer to have something
to write again.
I was told that multi-threading (multi-buffering?) was the/an answer
- a way to always have a buffer of data to write to the tape, and
therefore stop "shinning shoes"
I have watched GUI displays of the tape writing process (or for burning
a CD, for that matter) during which the "buffer" indicator would
fluctuate from full to varying degrees of not so full, through out the
process.
My question is how does the buffer work (or is that dependent on the
particular software?) - does it fill and then not accept new data until
it is empty again, or is it more like a pipe (input only limited by the
capacity of the buffer, and output anytime there is anything in the
buffer)?
Or am I asking the question wrong?
Thank you in advance for any help you may be able to offer
Regards
Fred James
------------------------------
_______________________________________________
Discuss mailing list
Discuss at ntlug.org
http://www.ntlug.org/mailman/listinfo/discuss
End of Discuss Digest, Vol 69, Issue 9
**************************************
More information about the Discuss
mailing list