On Thu, 24 Oct 2013, Steve Clark wrote:
Have you looked at /var/log/Xorg.0.log file - it sounds like there is a problem with X.
I have now, but I do not know what to do with the information. I understand line 15 and 111. Any ideas?
[root@localhost log]# grep -n EE Xorg.0.log 15: (WW) warning, (EE) error, (NI) not implemented, (??) unknown. 111:[ 57.736] Initializing built-in extension MIT-SCREEN-SAVER 692:[ 59.651] (EE) PreInit returned 8 for "HDA ATI HDMI HDMI/DP,pcm=3" 694:[ 59.651] (EE) config/hal: NewInputDeviceRequest failed (8) [root@localhost log]#
[ 59.628] (**) HDA ATI HDMI HDMI/DP,pcm=3: always reports core events [ 59.628] (**) evdev: HDA ATI HDMI HDMI/DP,pcm=3: Device: "/dev/input/event6" [ 59.635] (--) evdev: HDA ATI HDMI HDMI/DP,pcm=3: Vendor 0 Product 0 [ 59.635] (WW) evdev: HDA ATI HDMI HDMI/DP,pcm=3: Don't know how to use device [ 59.651] (EE) PreInit returned 8 for "HDA ATI HDMI HDMI/DP,pcm=3" [ 59.651] (II) UnloadModule: "evdev" [ 59.651] (EE) config/hal: NewInputDeviceRequest failed (8) [ 59.661] AUDIT: Wed Oct 23 15:22:43 2013: 2401: client 1 connected from local host ( uid=0 gid=0 pid=2399 ) Auth name: MIT-MAGIC-COOKIE-1 ID: 364 [ 59.722] (II) RADEON(0): EDID vendor "AOC", prod id 42881 [ 59.722] (II) RADEON(0): Using EDID range info for horizontal sync [ 59.722] (II) RADEON(0): Using EDID range info for vertical refresh [ 59.722] (II) RADEON(0): Printing DDC gathered Modelines: [ 59.722] (II) RADEON(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 -hsync -vsync (80.0 kHz eP) [ 59.722] (II) RADEON(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
The last three lines are: [ 1594.436] (II) evdev: ImPS/2 Generic Wheel Mouse: Close [ 1594.436] (II) UnloadModule: "evdev" [ 1594.487] Server terminated successfully (0). Closing log file.
The string ucc does not occur elsewhere in the file.
In case it helps: [root@localhost log]# grep -n hal Xorg.0.log 566:[ 59.462] (II) config/hal: Adding input device ImPS/2 Generic Wheel Mouse 585:[ 59.509] (**) Option "config_info" "hal:/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX_port_logicaldev_input" 592:[ 59.520] (II) config/hal: Adding input device Logitech Logitech Illuminated Keyboard 609:[ 59.525] (**) Option "config_info" "hal:/org/freedesktop/Hal/devices/usb_device_46d_c318_noserial_if1_logicaldev_input" 623:[ 59.569] (II) config/hal: Adding input device Logitech Logitech Illuminated Keyboard 630:[ 59.573] (**) Option "config_info" "hal:/org/freedesktop/Hal/devices/usb_device_46d_c318_noserial_if0_logicaldev_input" 638:[ 59.584] (II) config/hal: Adding input device Sleep Button 645:[ 59.589] (**) Option "config_info" "hal:/org/freedesktop/Hal/devices/computer_logicaldev_input_0" 653:[ 59.600] (II) config/hal: Adding input device Power Button 660:[ 59.606] (**) Option "config_info" "hal:/org/freedesktop/Hal/devices/computer_logicaldev_input" 668:[ 59.615] (II) config/hal: Adding input device Macintosh mouse button emulation 679:[ 59.619] (**) Option "config_info" "hal:/org/freedesktop/Hal/devices/computer_logicaldev_input_1" 686:[ 59.628] (II) config/hal: Adding input device HDA ATI HDMI HDMI/DP,pcm=3 694:[ 59.651] (EE) config/hal: NewInputDeviceRequest failed (8) [root@localhost log]#
Any ideas?
Absent other ideas, I might try re-installing CentOS or re-installing X. I have a pretty good idea how to do the former, but the latter might be harder despite, in principle, being less intrusive.
My understand is that unistalling X will normally take all its dependents will it. That means That I will have to re-install said dependents, possibly listing each one separately. My thought is to /usr/bin/script yum's output into a file. I'd use the file to produce another yum commmand to reinstall X's dependents. Does that seem like a good plan?
To reinstall CentOS, I would back up things that needed backing up. I would use yum to list all installed packages. I would use my grub menu to select the same stanza that I used to do a net-install of CentOS. It might be nice to use a kickstart file, but I do not know how.
After the install, I would restore the directory that listed all my repositories. This is a step I am not sure about. I have a vague recollection that that is not sufficient. What else would I need to do? I would use the yum listing to install everything I have now. Does this seem like a good plan?
On 10/27/2013 07:03 AM, Michael Hennebry wrote:
Absent other ideas, I might try re-installing CentOS or re-installing X. I have a pretty good idea how to do the former, but the latter might be harder despite, in principle, being less intrusive.
My understand is that unistalling X will normally take all its dependents will it. That means That I will have to re-install said dependents, possibly listing each one separately. My thought is to /usr/bin/script yum's output into a file. I'd use the file to produce another yum commmand to reinstall X's dependents. Does that seem like a good plan?
To reinstall CentOS, I would back up things that needed backing up. I would use yum to list all installed packages. I would use my grub menu to select the same stanza that I used to do a net-install of CentOS. It might be nice to use a kickstart file, but I do not know how.
After the install, I would restore the directory that listed all my repositories. This is a step I am not sure about. I have a vague recollection that that is not sufficient. What else would I need to do? I would use the yum listing to install everything I have now. Does this seem like a good plan?
Way too much work. Why not yum reinstall <package names> That will ensure that all package contents are correctly installed......??
On Sun, 27 Oct 2013, Rob Kampen wrote:
On 10/27/2013 07:03 AM, Michael Hennebry wrote:
Absent other ideas, I might try re-installing CentOS or re-installing X. I have a pretty good idea how to do the former, but the latter might be harder despite, in principle, being less intrusive.
My understand is that unistalling X will normally take all its dependents will it. That means That I will have to re-install said dependents, possibly listing each one separately. My thought is to /usr/bin/script yum's output into a file. I'd use the file to produce another yum commmand to reinstall X's dependents. Does that seem like a good plan?
Way too much work. Why not yum reinstall <package names> That will ensure that all package contents are correctly installed......??
Would yum reinstall X reinstall X's dependents? If not, I still need the list of package names that depend on X. Telling yum, at least tentatively, to remove X would seem to be the simplest way.
I really do not want to do any more experiments than I have to.
On Sat, 26 Oct 2013, Michael Hennebry wrote:
Absent other ideas, I might try re-installing CentOS or re-installing X. I have a pretty good idea how to do the former, but the latter might be harder despite, in principle, being less intrusive.
Reinstalling everything with xorg in its name did not help. I don't know how to find out what the trouble with X is.
To reinstall CentOS, I would back up things that needed backing up. I would use yum to list all installed packages. I would use my grub menu to select the same stanza that I used to do a net-install of CentOS. It might be nice to use a kickstart file, but I do not know how.
After the install, I would restore the directory that listed all my repositories. This is a step I am not sure about. I have a vague recollection that that is not sufficient. What else would I need to do?
Is there a command that I could use to record the repositories I am using and restore them after the install?
I would use the yum listing to install everything I have now. Does this seem like a good plan?
On Mon, Oct 28, 2013 at 5:44 PM, Michael Hennebry hennebry@web.cs.ndsu.nodak.edu wrote:
On Sat, 26 Oct 2013, Michael Hennebry wrote:
Absent other ideas, I might try re-installing CentOS or re-installing X. I have a pretty good idea how to do the former, but the latter might be harder despite, in principle, being less intrusive.
Reinstalling everything with xorg in its name did not help. I don't know how to find out what the trouble with X is.
Well, you can probably uninstall X doing
yum groupremove 'X Window System'
But, since I am late in the show I dunno what's the deal with X11 that is causing you such suffering.
To reinstall CentOS, I would back up things that needed backing up. I would use yum to list all installed packages. I would use my grub menu to select the same stanza that I used to do a net-install of CentOS. It might be nice to use a kickstart file, but I do not know how.
After the install, I would restore the directory that listed all my repositories. This is a step I am not sure about. I have a vague recollection that that is not sufficient. What else would I need to do?
Is there a command that I could use to record the repositories I am using and restore them after the install?
IMHO, you could just copy/tar the /etc/yum.repos.d/ and then bring it back in the new install in one way or another.
I would use the yum listing to install everything I have now. Does this seem like a good plan?
-- Michael hennebry@web.cs.ndsu.NoDak.edu "On Monday, I'm gonna have to tell my kindergarten class, whom I teach not to run with scissors, that my fiance ran me through with a broadsword." -- Lily _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Michael Hennebry wrote:
On Sat, 26 Oct 2013, Michael Hennebry wrote:
Absent other ideas, I might try re-installing CentOS or re-installing X. I have a pretty good idea how to do the former, but the latter might be harder despite, in principle, being less intrusive.
Reinstalling everything with xorg in its name did not help. I don't know how to find out what the trouble with X is.
To reinstall CentOS, I would back up things that needed backing up. I would use yum to list all installed packages. I would use my grub menu to select the same stanza that I used to do a net-install of CentOS. It might be nice to use a kickstart file, but I do not know how.
<snip> A trick I learned last week, fighting fedora: yum reinstall * BE SURE to use the backslash; otherwise, it thinks you want to reinstall the directories you're in when you issue the command.
mark
On 10/28/2013 05:44 PM, Michael Hennebry wrote:
On Sat, 26 Oct 2013, Michael Hennebry wrote:
Absent other ideas, I might try re-installing CentOS or re-installing X. I have a pretty good idea how to do the former, but the latter might be harder despite, in principle, being less intrusive.
Reinstalling everything with xorg in its name did not help. I don't know how to find out what the trouble with X is.
To reinstall CentOS, I would back up things that needed backing up. I would use yum to list all installed packages. I would use my grub menu to select the same stanza that I used to do a net-install of CentOS. It might be nice to use a kickstart file, but I do not know how.
After the install, I would restore the directory that listed all my repositories. This is a step I am not sure about. I have a vague recollection that that is not sufficient. What else would I need to do?
Is there a command that I could use to record the repositories I am using and restore them after the install?
I would use the yum listing to install everything I have now. Does this seem like a good plan?
See:
http://www.centos.org/modules/smartfaq/faq.php?faqid=50
On Mon, 28 Oct 2013, Mark LaPierre wrote:
On 10/28/2013 05:44 PM, Michael Hennebry wrote:
On Sat, 26 Oct 2013, Michael Hennebry wrote:
Absent other ideas, I might try re-installing CentOS or re-installing X.
I did a yum reinstall * . gdm or something still hangs. The gdm log suggests it is happy.
After the install, I would restore the directory that listed all my repositories. This is a step I am not sure about. I have a vague recollection that that is not sufficient. What else would I need to do?
Is there a command that I could use to record the repositories I am using and restore them after the install?
I would use the yum listing to install everything I have now. Does this seem like a good plan?
See:
Thank you, but my concern is not specific to X. X I can easily get from install options. I have repositories that are not listed in the install options. My recollection is that there is more to it than restoring a yum directory. There is a bunch of Berkely DB stuff under /var/lib/rpm . Would restoring /etc/yum.repos.d and /var/lib/rpm/Pubkeys be sufficient to activate all the repos from my old install?
Michael Hennebry wrote:
On Mon, 28 Oct 2013, Mark LaPierre wrote:
On 10/28/2013 05:44 PM, Michael Hennebry wrote:
On Sat, 26 Oct 2013, Michael Hennebry wrote:
Absent other ideas, I might try re-installing CentOS or re-installing X.
I did a yum reinstall * . gdm or something still hangs. The gdm log suggests it is happy.
After the install, I would restore the directory that listed all my repositories. This is a step I am not sure about. I have a vague recollection that that is not sufficient. What else would I need to do?
Is there a command that I could use to record the repositories I am using and restore them after the install?
Actually, you could just look at /etc/yum.repos.d. In there, you can also check to see if the repo is enabled, or if there's includes or excludes. We do that here, because there are systems we do *NOT* want some things updated without someone doing it manually, like the ones with very old NVidia cards, where we have to manually rebuild the proprietary drivers, or production systems, where the teams want to test the updates before they go into production. <snip>
mark
The nesting is getting a little deep.
Michael Hennebry wrote:
After the install, I would restore the directory that listed all my repositories. This is a step I am not sure about. I have a vague recollection that that is not sufficient. What else would I need to do?
Michael Hennebry wrote: Is there a command that I could use to record the repositories I am using and restore them after the install?
On Tue, 29 Oct 2013, m.roth@5-cent.us wrote:
Actually, you could just look at /etc/yum.repos.d. In there, you can also check to see if the repo is enabled, or if there's includes or excludes. We do that here, because there are systems we do *NOT* want some things updated without someone doing it manually, like the ones with very old NVidia cards, where we have to manually rebuild the proprietary drivers, or production systems, where the teams want to test the updates before they go into production.
Maybe I was not clear. I'm refering to reinstalling CentOS. My current CentOS hangs after trying to start gdm. My diagnostic efforts have been for nought, so I want to more or less start over. I already have a "list" of all the repositories I want. It's the contents of the aforementioned /etc/yum/repos.d .
I could try to install every single repository by hand. I don't remember how I installed most of them, but I could try. I would probably succeed, but its not a certainty. Following that, I could install all the packages by hand. I could edit my list of installed packages and make a massive yum command.
Michael Hennebry wrote:
The nesting is getting a little deep.
Michael Hennebry wrote:
After the install, I would restore the directory that listed all my repositories. This is a step I am not sure about. I have a vague recollection that that is not sufficient. What else would I need to do?
Michael Hennebry wrote: Is there a command that I could use to record the repositories I am using and restore them after the install?
On Tue, 29 Oct 2013, m.roth@5-cent.us wrote:
Actually, you could just look at /etc/yum.repos.d. In there, you can also check to see if the repo is enabled, or if there's includes or excludes. We do that here, because there are systems we do *NOT* want some things updated without someone doing it manually, like the ones with very old NVidia cards, where we have to manually rebuild the proprietary drivers, or production systems, where the teams want to test the updates before they go into production.
Maybe I was not clear. I'm refering to reinstalling CentOS. My current CentOS hangs after trying to start gdm. My diagnostic efforts have been for nought, so I want to more or less start over. I already have a "list" of all the repositories I want. It's the contents of the aforementioned /etc/yum/repos.d .
I could try to install every single repository by hand. I don't remember how I installed most of them, but I could try. I would probably succeed, but its not a certainty. Following that, I could install all the packages by hand. I could edit my list of installed packages and make a massive yum command.
Ok. What we use here at work are, besides the default repos, rpmfusion (free and non-free), epel, and Adobe (you know why...). For *very* special cases (like NVidia cards that *are* supported), I've got elrepo (with only the things needed for the NVidia card and xorg included from elrepo).
mark
On Tue, Oct 29, 2013 at 11:59 AM, Michael Hennebry hennebry@web.cs.ndsu.nodak.edu wrote:
Maybe I was not clear. I'm refering to reinstalling CentOS. My current CentOS hangs after trying to start gdm. My diagnostic efforts have been for nought, so I want to more or less start over. I already have a "list" of all the repositories I want. It's the contents of the aforementioned /etc/yum/repos.d .
I could try to install every single repository by hand.
I don't remember how I installed most of them, but I could try. I would probably succeed, but its not a certainty. Following that, I could install all the packages by hand. I could edit my list of installed packages and make a massive yum command.
Most repositories will have a 'name-release.rpm' where name is the name of the repository. This will install the entry under /etc/yum/repos.d and set up the gpg key for the rpms. If you have a URL to the repo release rpm, yum can install for you with: yum install URL However, note that your current problem may be related to something you've pulled from a 3rd party repository so you should avoid blindly repeating the process. I'd install/update the package list from the base repositories first, then add EPEL and others with a policy of not overwriting base packages and make sure everything works before installing anything from repos that may overwrite any base packages. I normally keep any in the latter category set as 'enabled = 0' in the repo file and use --enablerepo= on the yum command line when I want something from them.
On Tue, 29 Oct 2013, Les Mikesell wrote:
Most repositories will have a 'name-release.rpm' where name is the name of the repository. This will install the entry under /etc/yum/repos.d and set up the gpg key for the rpms. If you have a URL to the repo release rpm, yum can install for you with: yum install URL
Thank you. That is likely to be useful.
However, note that your current problem may be related to something you've pulled from a 3rd party repository so you should avoid blindly repeating the process. I'd install/update the package list from the
My system had been running for a while without my adding anything new. My expectation is that something glitched and changed something in a manner that had gdb waiting for something that will never happen. I'll never know. I'm not willing to put in another week of effort out of a probably vain hope of discovery.
One change I will make is that I will install and use priorities sooner.
base repositories first, then add EPEL and others with a policy of not overwriting base packages and make sure everything works before installing anything from repos that may overwrite any base packages. I normally keep any in the latter category set as 'enabled = 0' in the repo file and use --enablerepo= on the yum command line when I want something from them.
On Tue, Oct 29, 2013 at 3:47 PM, Michael Hennebry hennebry@web.cs.ndsu.nodak.edu wrote:
However, note that your current problem may be related to something you've pulled from a 3rd party repository so you should avoid blindly repeating the process. I'd install/update the package list from the
My system had been running for a while without my adding anything new. My expectation is that something glitched and changed something in a manner that had gdb waiting for something that will never happen. I'll never know.
But did yum update any packages? There's a certain amount of risk in having uncoordinated 3rd party repos enabled when you do updates even if you aren't intentionally adding/changing anything. Does /var/log/yum.log show anything around the time your problem started.
I'm not willing to put in another week of effort out of a probably vain hope of discovery.
You might try running 'rpm -Va' to see if there are any surprises in the list of differences between the current state and what was installed.
On Tue, 29 Oct 2013, Les Mikesell wrote:
On Tue, Oct 29, 2013 at 3:47 PM, Michael Hennebry hennebry@web.cs.ndsu.nodak.edu wrote:
However, note that your current problem may be related to something you've pulled from a 3rd party repository so you should avoid blindly repeating the process. I'd install/update the package list from the
My system had been running for a while without my adding anything new. My expectation is that something glitched and changed something in a manner that had gdb waiting for something that will never happen. I'll never know.
But did yum update any packages? There's a certain amount of risk in having uncoordinated 3rd party repos enabled when you do updates even if you aren't intentionally adding/changing anything. Does /var/log/yum.log show anything around the time your problem started.
No updates for almost a month.
On Tue, 29 Oct 2013, Les Mikesell wrote:
Most repositories will have a 'name-release.rpm' where name is the name of the repository. This will install the entry under /etc/yum/repos.d and set up the gpg key for the rpms. If you have a
These, for example: [hennebry@localhost rpms]$ ls atrpms-repo-6-6.el6.i686.rpm rpmforge-release-0.5.3-1.el6.rf.i686.rpm epel-release-6-8.noarch.rpm [hennebry@localhost rpms]$ ?
URL to the repo release rpm, yum can install for you with: yum install URL
Michael Hennebry wrote:
On Tue, 29 Oct 2013, Les Mikesell wrote:
Most repositories will have a 'name-release.rpm' where name is the name of the repository. This will install the entry under /etc/yum/repos.d and set up the gpg key for the rpms. If you have a
These, for example: [hennebry@localhost rpms]$ ls atrpms-repo-6-6.el6.i686.rpm rpmforge-release-0.5.3-1.el6.rf.i686.rpm epel-release-6-8.noarch.rpm [hennebry@localhost rpms]$ ?
Urp. I have had conflicts with rpmforge, with (thinking back) epel and/or rpmfusion.
mark
On Tue, 29 Oct 2013, m.roth@5-cent.us wrote:
Michael Hennebry wrote:
On Tue, 29 Oct 2013, Les Mikesell wrote:
Most repositories will have a 'name-release.rpm' where name is the name of the repository. This will install the entry under /etc/yum/repos.d and set up the gpg key for the rpms. If you have a
These, for example: [hennebry@localhost rpms]$ ls atrpms-repo-6-6.el6.i686.rpm rpmforge-release-0.5.3-1.el6.rf.i686.rpm epel-release-6-8.noarch.rpm [hennebry@localhost rpms]$ ?
Urp. I have had conflicts with rpmforge, with (thinking back) epel and/or rpmfusion.
I have rpmforge's priority set to 50, epel defaults to 99. Standard centos repos are set to 1.
On Tue, Oct 29, 2013 at 5:20 PM, Michael Hennebry hennebry@web.cs.ndsu.nodak.edu wrote:
On Tue, 29 Oct 2013, Les Mikesell wrote:
Most repositories will have a 'name-release.rpm' where name is the name of the repository. This will install the entry under /etc/yum/repos.d and set up the gpg key for the rpms. If you have a
These, for example: [hennebry@localhost rpms]$ ls atrpms-repo-6-6.el6.i686.rpm rpmforge-release-0.5.3-1.el6.rf.i686.rpm epel-release-6-8.noarch.rpm [hennebry@localhost rpms]$ ?
Yes you can use a local copy of the rpm and either 'rpm -Uhv' it or 'yum localinstall' it. or:
URL to the repo release rpm, yum can install for you with: yum install URL
If you have the http URL that you used to download the rpm manually, you can just 'yum install URL". Older versions of yum could not do that so the documentation may not mention the simple approach.
On 10/29/2013 4:13 PM, Les Mikesell wrote:
[hennebry@localhost rpms]$ ls
atrpms-repo-6-6.el6.i686.rpm rpmforge-release-0.5.3-1.el6.rf.i686.rpm epel-release-6-8.noarch.rpm [hennebry@localhost rpms]$ ?
Yes you can use a local copy of the rpm and either 'rpm -Uhv' it or 'yum localinstall' it. or:
URL to the repo release rpm, yum can install for you with: yum install URL
If you have the http URL that you used to download the rpm manually, you can just 'yum install URL". Older versions of yum could not do that so the documentation may not mention the simple approach.
you also can...
# rpm -ivh http://path.to/yum/repo/epel-release-6-8.noarch.rpm
and rpm will wget the URL then install the downloaded file. this has worked for a LONG time.
On Tue, 29 Oct 2013, Les Mikesell wrote:
On Tue, Oct 29, 2013 at 5:20 PM, Michael Hennebry hennebry@web.cs.ndsu.nodak.edu wrote:
On Tue, 29 Oct 2013, Les Mikesell wrote:
Most repositories will have a 'name-release.rpm' where name is the name of the repository. This will install the entry under /etc/yum/repos.d and set up the gpg key for the rpms. If you have a
These, for example: [hennebry@localhost rpms]$ ls atrpms-repo-6-6.el6.i686.rpm rpmforge-release-0.5.3-1.el6.rf.i686.rpm epel-release-6-8.noarch.rpm [hennebry@localhost rpms]$ ?
Yes you can use a local copy of the rpm and either 'rpm -Uhv' it or 'yum localinstall' it. or:
I should have been more clear: Are the above .rpm's repository install rpm's?
I was hoping someone could tell me for sure.
URL to the repo release rpm, yum can install for you with: yum install URL
If you have the http URL that you used to download the rpm manually, you can just 'yum install URL". Older versions of yum could not do that so the documentation may not mention the simple approach.
I do not. I started at the base urls given in .repo files and started looking for files that had the right names.
On 10/29/2013 4:49 PM, Michael Hennebry wrote:
I should have been more clear: Are the above .rpm's repository install rpm's?
those rpms install the yum.repos.d file along with the GPG keys for the repository, so by installing the repo RPM, you can then use yum to install anything in that repo.
On Tue, Oct 29, 2013 at 6:49 PM, Michael Hennebry hennebry@web.cs.ndsu.nodak.edu wrote:
Yes you can use a local copy of the rpm and either 'rpm -Uhv' it or
'yum localinstall' it. or:
I should have been more clear: Are the above .rpm's repository install rpm's?
I was hoping someone could tell me for sure.
Yes. They will install an entry under /etc/yum/repos.d with default settings that you may want to edit before using if you want to set priorities or leave it disabled. If you want to check the contents of an rpm before installing, you can use: rpm -qp --list filename.
If you have the http URL that you used to download the rpm manually, you can just 'yum install URL". Older versions of yum could not do that so the documentation may not mention the simple approach.
I do not. I started at the base urls given in .repo files and started looking for files that had the right names.
When you find the name, you've found the URL to get it... Most browsers would have a right-mouse, 'copy link' menu option to put the URL on the clipboard to paste elsewhere.
-
John R Pierce -
Les Mikesell -
m.roth＠5-cent.us -
Mark LaPierre -
Mauricio Tavares -
Michael Hennebry -
Rob Kampen