Re: setup.exe deleted some files
I'm adapting to all the changes since B20. I have adopted the following changes in the way I do things: 1) make sure my backups are *really* working before any upgrades 2) institute protected programs; by linking items in /bin to /localbin 3) now that I better understand setup, go with the flo 4) put locally written pgms into /localbin to leave /bin cygwin only I thank you all for your replies to this thread. Now that I'm retired I have more time to deal with problems changes. - Paul McFerrin Christopher Faylor wrote: On Tue, Sep 25, 2007 at 08:32:26AM -0400, Larry Hall (Cygwin) wrote: Paul McFerrin wrote: Can you really *expect* that someone running B20 for 5+ years can remember from which package to select so you will not lose a particular program that you've been using for years. Heck I didn't even know it was part of the linux util package. I never used a Linus system before. The cal command was introduced back in SVR2 days (~1976)! Way before Linux came on the scene! Yes, I'm showing my age. No I don't expect you to remember details of your ancient install. I would expect that you'd recognize that quite allot has likely changed in the interim and that you might need to do a little leg-work to get everything you had back to the way you like it. I don't believe Cygwin is unusual in this respect. Any 6+ year old distribution is going to have changes that may seem a little jarring to those that may be seeking to have everything just the way they had it. Of course, if you feel that these realities don't live up to your expectations, you are free to stick with the versions you have for as long as they do what you want. There's all that plus the fact that B20 didn't actually have packages anyway. That was more-or-less the point of subsequent releases - allowing people to choose what they wanted. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: setup.exe deleted some files
Paul McFerrin wrote: Can you really *expect* that someone running B20 for 5+ years can remember from which package to select so you will not lose a particular program that you've been using for years. Heck I didn't even know it was part of the linux util package. I never used a Linus system before. The cal command was introduced back in SVR2 days (~1976)! Way before Linux came on the scene! Yes, I'm showing my age. No I don't expect you to remember details of your ancient install. I would expect that you'd recognize that quite allot has likely changed in the interim and that you might need to do a little leg-work to get everything you had back to the way you like it. I don't believe Cygwin is unusual in this respect. Any 6+ year old distribution is going to have changes that may seem a little jarring to those that may be seeking to have everything just the way they had it. Of course, if you feel that these realities don't live up to your expectations, you are free to stick with the versions you have for as long as they do what you want. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: setup.exe deleted some files
On Tue, Sep 25, 2007 at 08:32:26AM -0400, Larry Hall (Cygwin) wrote: Paul McFerrin wrote: Can you really *expect* that someone running B20 for 5+ years can remember from which package to select so you will not lose a particular program that you've been using for years. Heck I didn't even know it was part of the linux util package. I never used a Linus system before. The cal command was introduced back in SVR2 days (~1976)! Way before Linux came on the scene! Yes, I'm showing my age. No I don't expect you to remember details of your ancient install. I would expect that you'd recognize that quite allot has likely changed in the interim and that you might need to do a little leg-work to get everything you had back to the way you like it. I don't believe Cygwin is unusual in this respect. Any 6+ year old distribution is going to have changes that may seem a little jarring to those that may be seeking to have everything just the way they had it. Of course, if you feel that these realities don't live up to your expectations, you are free to stick with the versions you have for as long as they do what you want. There's all that plus the fact that B20 didn't actually have packages anyway. That was more-or-less the point of subsequent releases - allowing people to choose what they wanted. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: setup.exe deleted some files
Christopher Faylor wrote: On Tue, Sep 25, 2007 at 08:32:26AM -0400, Larry Hall (Cygwin) wrote: Paul McFerrin wrote: Can you really *expect* that someone running B20 for 5+ years can remember from which package to select so you will not lose a particular program that you've been using for years. Heck I didn't even know it was part of the linux util package. I never used a Linus system before. The cal command was introduced back in SVR2 days (~1976)! Way before Linux came on the scene! Yes, I'm showing my age. No I don't expect you to remember details of your ancient install. I would expect that you'd recognize that quite allot has likely changed in the interim and that you might need to do a little leg-work to get everything you had back to the way you like it. I don't believe Cygwin is unusual in this respect. Any 6+ year old distribution is going to have changes that may seem a little jarring to those that may be seeking to have everything just the way they had it. Of course, if you feel that these realities don't live up to your expectations, you are free to stick with the versions you have for as long as they do what you want. There's all that plus the fact that B20 didn't actually have packages anyway. That was more-or-less the point of subsequent releases - allowing people to choose what they wanted. Indeed. Why did I forget that? ;-) I guess that provides others who want to upgrade from B20 to something current another way of getting all that they're likely to want/need/be used to - install everything. Gulp. Now the flood gates have been opened! ;-) -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: setup.exe deleted some files
Paul McFerrin wrote: When I inadvertantly ran setup to perform an upgrade of my B20 environment the other week, I noticed that it deleted some files in my /bin directory. One particular file was cal.exe which I use more frequently than a real calendar. Is this normal or was it a fluke. I restored it from my backups. Also deleted were egrep.exe and fgrep.exe. http://cygwin.com/cgi-bin2/package-grep.cgi?grep=%2Fbin%2Fcal http://cygwin.com/cgi-bin2/package-grep.cgi?grep=%2Fbin%2Fegrep I don't think it's reasonable to expect 'setup.exe' to upgrade your packages from a B20 installation since too much has changed since then. The key is to find the packages with the utilities you want and install them. You can see from the links above, what you want still exists. Just install the appropriate package. Can anyone explain the logic setup uses to determine which files to delete? Was it caused by some menu items not being checked with keep? If you uninstall a package, it removes the files for that package. If you ask for an upgrade, it removes the old files and installs the new ones. Of course, that assumes that the packages were installed with 'setup.exe' to begin with. If not, all bets are off. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: setup.exe deleted some files
On Mon, Sep 24, 2007 at 05:40:25PM -0400, Larry Hall (Cygwin) wrote: Paul McFerrin wrote: When I inadvertantly ran setup to perform an upgrade of my B20 environment the other week, I noticed that it deleted some files in my /bin directory. One particular file was cal.exe which I use more frequently than a real calendar. Is this normal or was it a fluke. I restored it from my backups. Also deleted were egrep.exe and fgrep.exe. http://cygwin.com/cgi-bin2/package-grep.cgi?grep=%2Fbin%2Fcal http://cygwin.com/cgi-bin2/package-grep.cgi?grep=%2Fbin%2Fegrep I don't think it's reasonable to expect 'setup.exe' to upgrade your packages from a B20 installation since too much has changed since then. The key is to find the packages with the utilities you want and install them. You can see from the links above, what you want still exists. Just install the appropriate package. Can anyone explain the logic setup uses to determine which files to delete? Was it caused by some menu items not being checked with keep? If you uninstall a package, it removes the files for that package. If you ask for an upgrade, it removes the old files and installs the new ones. Of course, that assumes that the packages were installed with 'setup.exe' to begin with. If not, all bets are off. Yeah, I hear ya. B20 sure was great. Sigh. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: setup.exe deleted some files
Can you really *expect* that someone running B20 for 5+ years can remember from which package to select so you will not lose a particular program that you've been using for years. Heck I didn't even know it was part of the linux util package. I never used a Linus system before. The cal command was introduced back in SVR2 days (~1976)! Way before Linux came on the scene! Yes, I'm showing my age. Larry Hall (Cygwin) wrote: Paul McFerrin wrote: When I inadvertantly ran setup to perform an upgrade of my B20 environment the other week, I noticed that it deleted some files in my /bin directory. One particular file was cal.exe which I use more frequently than a real calendar. Is this normal or was it a fluke. I restored it from my backups. Also deleted were egrep.exe and fgrep.exe. http://cygwin.com/cgi-bin2/package-grep.cgi?grep=%2Fbin%2Fcal http://cygwin.com/cgi-bin2/package-grep.cgi?grep=%2Fbin%2Fegrep I don't think it's reasonable to expect 'setup.exe' to upgrade your packages from a B20 installation since too much has changed since then. The key is to find the packages with the utilities you want and install them. You can see from the links above, what you want still exists. Just install the appropriate package. Can anyone explain the logic setup uses to determine which files to delete? Was it caused by some menu items not being checked with keep? If you uninstall a package, it removes the files for that package. If you ask for an upgrade, it removes the old files and installs the new ones. Of course, that assumes that the packages were installed with 'setup.exe' to begin with. If not, all bets are off. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
