Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #203870 > unrolled thread
| Started by | "Stephen P. Molnar" <s.molnar@sbcglobal.net> |
|---|---|
| First post | 2019-01-03 16:00 +0100 |
| Last post | 2019-01-04 16:00 +0100 |
| Articles | 20 on this page of 94 — 25 participants |
Back to article view | Back to linux.debian.user
Upgrade Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-01-03 16:00 +0100
Fwd: Upgrade Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-01-03 17:20 +0100
Re: Fwd: Upgrade Problem steve <dlist@bluewin.ch> - 2019-01-03 17:40 +0100
Re: Upgrade Problem Brad Rogers <brad@fineby.me.uk> - 2019-01-03 18:30 +0100
Re: Upgrade Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-01-03 18:40 +0100
Re: Fwd: Upgrade Problem deloptes <deloptes@gmail.com> - 2019-01-03 17:40 +0100
Re: Fwd: Upgrade Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-01-03 18:20 +0100
Re: Fwd: Upgrade Problem deloptes <deloptes@gmail.com> - 2019-01-03 18:40 +0100
Re: Fwd: Upgrade Problem Greg Wooledge <wooledg@eeg.ccf.org> - 2019-01-03 19:00 +0100
Re: Fwd: Upgrade Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-01-03 20:40 +0100
Re: Fwd: Upgrade Problem Greg Wooledge <wooledg@eeg.ccf.org> - 2019-01-03 20:50 +0100
Re: Fwd: Upgrade Problem Greg Wooledge <wooledg@eeg.ccf.org> - 2019-01-03 20:50 +0100
Re: Fwd: Upgrade Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-01-03 21:20 +0100
Re: Fwd: Upgrade Problem deloptes <deloptes@gmail.com> - 2019-01-03 21:30 +0100
Re: Fwd: Upgrade Problem Nicolas George <george@nsup.org> - 2019-01-03 21:40 +0100
Re: Fwd: Upgrade Problem deloptes <deloptes@gmail.com> - 2019-01-03 22:20 +0100
Re: Fwd: Upgrade Problem Frank Weißer <linux@weisser-ol.de> - 2019-01-04 10:30 +0100
Re: Fwd: Upgrade Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-01-03 21:40 +0100
Re: Fwd: Upgrade Problem Nicolas George <george@nsup.org> - 2019-01-03 22:30 +0100
Re: Fwd: Upgrade Problem Roberto C. Sánchez <roberto@debian.org> - 2019-01-03 23:00 +0100
Re: Fwd: Upgrade Problem Nicolas George <george@nsup.org> - 2019-01-03 23:30 +0100
Re: Fwd: Upgrade Problem deloptes <deloptes@gmail.com> - 2019-01-04 01:30 +0100
Re: Fwd: Upgrade Problem Nicolas George <george@nsup.org> - 2019-01-04 11:20 +0100
Re: Fwd: Upgrade Problem Roberto C. Sánchez <roberto@debian.org> - 2019-01-04 13:40 +0100
Re: Fwd: Upgrade Problem Nicolas George <george@nsup.org> - 2019-01-04 13:40 +0100
Re: Fwd: Upgrade Problem deloptes <deloptes@gmail.com> - 2019-01-04 19:00 +0100
Re: Fwd: Upgrade Problem Nicolas George <george@nsup.org> - 2019-01-04 19:40 +0100
Re: Fwd: Upgrade Problem Gene Heskett <gheskett@shentel.net> - 2019-01-04 20:00 +0100
Re: Fwd: Upgrade Problem Roberto C. Sánchez <roberto@debian.org> - 2019-01-04 20:40 +0100
Re: Fwd: Upgrade Problem Roberto C. Sánchez <roberto@debian.org> - 2019-01-04 21:20 +0100
Re: Fwd: Upgrade Problem Brian <ad44@cityscape.co.uk> - 2019-01-04 21:20 +0100
Re: Fwd: Upgrade Problem Brian <ad44@cityscape.co.uk> - 2019-01-04 20:40 +0100
Re: Fwd: Upgrade Problem Gene Heskett <gheskett@shentel.net> - 2019-01-04 22:10 +0100
Re: Fwd: Upgrade Problem mick crane <mick.crane@gmail.com> - 2019-01-05 08:20 +0100
Re: Fwd: Upgrade Problem deloptes <deloptes@gmail.com> - 2019-01-04 20:50 +0100
Re: Fwd: Upgrade Problem Brian <ad44@cityscape.co.uk> - 2019-01-04 20:40 +0100
Re: Fwd: Upgrade Problem deloptes <deloptes@gmail.com> - 2019-01-04 20:50 +0100
Re: Fwd: Upgrade Problem Andy Smith <andy@strugglers.net> - 2019-01-03 23:10 +0100
Re: Fwd: Upgrade Problem Curt <curty@free.fr> - 2019-01-04 14:10 +0100
Re: Fwd: Upgrade Problem Gene Heskett <gheskett@shentel.net> - 2019-01-04 03:30 +0100
Re: Fwd: Upgrade Problem Greg Wooledge <wooledg@eeg.ccf.org> - 2019-01-04 14:20 +0100
Re: Fwd: Upgrade Problem Gene Heskett <gheskett@shentel.net> - 2019-01-04 14:50 +0100
Re: Fwd: Upgrade Problem Greg Wooledge <wooledg@eeg.ccf.org> - 2019-01-04 15:00 +0100
Re: Fwd: Upgrade Problem deloptes <deloptes@gmail.com> - 2019-01-04 19:30 +0100
Re: Fwd: Upgrade Problem Nicolas George <george@nsup.org> - 2019-01-04 19:40 +0100
Re: Fwd: Upgrade Problem deloptes <deloptes@gmail.com> - 2019-01-04 21:00 +0100
Re: Upgrade Problem Joe <joe@jretrading.com> - 2019-01-04 21:30 +0100
Re: Upgrade Problem deloptes <deloptes@gmail.com> - 2019-01-04 23:00 +0100
Re: Fwd: Upgrade Problem Gene Heskett <gheskett@shentel.net> - 2019-01-04 19:50 +0100
Re: Fwd: Upgrade Problem deloptes <deloptes@gmail.com> - 2019-01-05 01:40 +0100
Re: Fwd: Upgrade Problem Gene Heskett <gheskett@shentel.net> - 2019-01-05 06:30 +0100
Re: Fwd: Upgrade Problem <tomas@tuxteam.de> - 2019-01-04 15:50 +0100
Re: Fwd: Upgrade Problem David Wright <deblis@lionunicorn.co.uk> - 2019-01-04 18:10 +0100
Re: Fwd: Upgrade Problem Nicolas George <george@nsup.org> - 2019-01-03 21:40 +0100
Re: Fwd: Upgrade Problem Nicolas George <george@nsup.org> - 2019-01-03 19:00 +0100
Re: Fwd: Upgrade Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-01-03 19:00 +0100
Re: Fwd: Upgrade Problem deloptes <deloptes@gmail.com> - 2019-01-03 20:20 +0100
Re: Fwd: Upgrade Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-01-03 20:50 +0100
Re: Fwd: Upgrade Problem deloptes <deloptes@gmail.com> - 2019-01-03 21:40 +0100
Re: Fwd: Upgrade Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-01-03 21:50 +0100
Re: Fwd: Upgrade Problem deloptes <deloptes@gmail.com> - 2019-01-03 22:10 +0100
Re: Fwd: Upgrade Problem songbird <songbird@anthive.com> - 2019-01-04 03:20 +0100
Re: Fwd: Upgrade Problem deloptes <deloptes@gmail.com> - 2019-01-04 09:10 +0100
Re: Fwd: Upgrade Problem Gene Heskett <gheskett@shentel.net> - 2019-01-04 03:40 +0100
Re: Upgrade Problem Felix Miata <mrmazda@earthlink.net> - 2019-01-04 04:50 +0100
Re: Upgrade Problem Andy Smith <andy@strugglers.net> - 2019-01-04 09:50 +0100
Overhead of LVM (Re: Upgrade Problem) rhkramer@gmail.com - 2019-01-04 14:20 +0100
Re: Overhead of LVM (Re: Upgrade Problem) Reco <recoverym4n@enotuniq.net> - 2019-01-04 14:30 +0100
Re: Overhead of LVM (Re: Upgrade Problem) rhkramer@gmail.com - 2019-01-05 05:10 +0100
Re: Overhead of LVM (Re: Upgrade Problem) Reco <recoverym4n@enotuniq.net> - 2019-01-05 08:40 +0100
Re: Upgrade Problem Richard Hector <richard@walnut.gen.nz> - 2019-01-04 21:10 +0100
Re: Upgrade Problem Stefan Krusche <linux@stefan-krusche.de> - 2019-03-10 14:30 +0100
Re: Upgrade Problem Nicolas George <george@nsup.org> - 2019-01-04 11:20 +0100
Re: Upgrade Problem Patrick Bartek <nemommxiv@gmail.com> - 2019-01-03 18:20 +0100
Re: Upgrade Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-01-03 18:40 +0100
Re: Upgrade Problem Patrick Bartek <nemommxiv@gmail.com> - 2019-01-04 03:20 +0100
Re: Upgrade Problem Matthew Crews <mailinglists@mattcrews.com> - 2019-01-04 03:50 +0100
Re: Upgrade Problem Andy Smith <andy@strugglers.net> - 2019-01-04 10:00 +0100
Re: Upgrade Problem Felix Miata <mrmazda@earthlink.net> - 2019-01-04 10:40 +0100
Re: Upgrade Problem David Wright <deblis@lionunicorn.co.uk> - 2019-01-04 17:30 +0100
Re: Upgrade Problem Felix Miata <mrmazda@earthlink.net> - 2019-01-04 19:50 +0100
Re: Upgrade Problem David Wright <deblis@lionunicorn.co.uk> - 2019-01-04 21:30 +0100
Re: allocating disk space (was: Upgrade Problem) Felix Miata <mrmazda@earthlink.net> - 2019-01-05 01:40 +0100
Re: allocating disk space (was: Upgrade Problem) David Wright <deblis@lionunicorn.co.uk> - 2019-01-10 01:10 +0100
Re: allocating disk space Felix Miata <mrmazda@earthlink.net> - 2019-01-11 08:20 +0100
Re: allocating disk space David Wright <deblis@lionunicorn.co.uk> - 2019-01-13 14:20 +0100
Re: Upgrade Problem Brian <ad44@cityscape.co.uk> - 2019-01-04 11:50 +0100
Re: Upgrade Problem Reco <recoverym4n@enotuniq.net> - 2019-01-04 13:00 +0100
Re: Upgrade Problem Greg Wooledge <wooledg@eeg.ccf.org> - 2019-01-04 14:30 +0100
Re: Upgrade Problem songbird <songbird@anthive.com> - 2019-01-03 20:00 +0100
Re: Upgrade Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-01-03 20:40 +0100
Re: Upgrade Problem David Wright <deblis@lionunicorn.co.uk> - 2019-01-03 21:00 +0100
Re: Upgrade Problem Greg Wooledge <wooledg@eeg.ccf.org> - 2019-01-03 21:10 +0100
Re: Upgrade Problem Michael Stone <mstone@debian.org> - 2019-01-04 16:00 +0100
Page 3 of 5 — ← Prev page 1 2 [3] 4 5 Next page →
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Date | 2019-01-04 14:20 +0100 |
| Message-ID | <xcxyi-Jv-5@gated-at.bofh.it> |
| In reply to | #203932 |
On Thu, Jan 03, 2019 at 09:22:49PM -0500, Gene Heskett wrote: > In this case, I hate to sound like > an ass, but perhaps a re-install is in the future, doing the reinstall > to a new drive [...] Come on, people. Show some sense. (And yes, this includes the OP.) He simply has a full root file system. He has shown the df output at least twice now. (A full root file system clearly and plainly shown by df despite the OP claiming he is certain he's not out of space, no less.)
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2019-01-04 14:50 +0100 |
| Message-ID | <xcy1k-Tc-15@gated-at.bofh.it> |
| In reply to | #203967 |
On Friday 04 January 2019 08:15:11 Greg Wooledge wrote: > On Thu, Jan 03, 2019 at 09:22:49PM -0500, Gene Heskett wrote: > > In this case, I hate to sound like > > an ass, but perhaps a re-install is in the future, doing the > > reinstall to a new drive [...] > > Come on, people. Show some sense. (And yes, this includes the OP.) > > He simply has a full root file system. He has shown the df output at > least twice now. > > (A full root file system clearly and plainly shown by df despite the > OP claiming he is certain he's not out of space, no less.) I don't have an argument against any of that Greg, but lets clarify one thing here and now for the OP. Several responders keep using the "/root" to describe what you clearly intend to be interpreted as the root of the filesystem, AKA "/" when in 99.99% of the installs /root is the sysadmin's home DIRECTORY, and not the root of the filesystem. So lets all quit using /root as the base of the filesystem, it is not, / is. /root is normally roots home directory, root being user #1 and there is quite a large diff. My own reinstall to a new, much larger disk, recommendation still stands, that the OP would be back to a working system where he could remount that old drive to his new install and recover the data he needs to continue his project, much faster than he'll be able to fix this install. IOW, the most expedient way to get the OP back up to speed on whatever it is that he may be working on. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Date | 2019-01-04 15:00 +0100 |
| Message-ID | <xcyaZ-Wp-5@gated-at.bofh.it> |
| In reply to | #203973 |
On Fri, Jan 04, 2019 at 08:44:27AM -0500, Gene Heskett wrote: > My own reinstall to a new, much larger disk, recommendation still stands, > that the OP would be back to a working system where he could remount > that old drive to his new install and recover the data he needs to > continue his project, much faster than he'll be able to fix this > install. IOW, the most expedient way to get the OP back up to speed on > whatever it is that he may be working on. All he has to do is find whatever's taking up an unexpected amount of space in his root file system, and get rid of it. This is an essential system management skill that he HAS to learn, which he will continue to use well beyond the current crisis. Reinstalling on a larger disk to "fix" this is like buying a new car every time you run out of gasoline.
[toc] | [prev] | [next] | [standalone]
| From | deloptes <deloptes@gmail.com> |
|---|---|
| Date | 2019-01-04 19:30 +0100 |
| Message-ID | <xcCoi-3BF-7@gated-at.bofh.it> |
| In reply to | #203975 |
Greg Wooledge wrote: > All he has to do is find whatever's taking up an unexpected amount of > space in his root file system, and get rid of it. This is an essential > system management skill that he HAS to learn, which he will continue > to use well beyond the current crisis. > > Reinstalling on a larger disk to "fix" this is like buying a new car > every time you run out of gasoline. almost like my brother in law who is buying a new notebook every 2 years because the old one is getting slow. You can imagine which OS it is :) So I was thinking perhaps this is good for the economy, because if most of the users were like me, there wouldn't be any economic growth in the past years.
[toc] | [prev] | [next] | [standalone]
| From | Nicolas George <george@nsup.org> |
|---|---|
| Date | 2019-01-04 19:40 +0100 |
| Message-ID | <xcCxX-3EP-7@gated-at.bofh.it> |
| In reply to | #204000 |
[Multipart message — attachments visible in raw view] — view raw
deloptes (12019-01-04): > So I was thinking perhaps this is good for the economy, because if most of > the users were like me, there wouldn't be any economic growth in the past > years. It really is not, because the resources invested in the old computer are wasted (unless somebody gets it and recycles it). It is the same scheme than in Chaplin's _The Kid_: breaking a window to let a glazier sell a new one. Alas, the idiotic way most people evaluate the economy, the GDP, often makes it seem that kind of thing is good. But according to the GDP, being stuck in traffic is good for the economy. Regards, -- Nicolas George
[toc] | [prev] | [next] | [standalone]
| From | deloptes <deloptes@gmail.com> |
|---|---|
| Date | 2019-01-04 21:00 +0100 |
| Message-ID | <xcDNo-4kw-13@gated-at.bofh.it> |
| In reply to | #204002 |
Nicolas George wrote: > It really is not, because the resources invested in the old computer are > wasted (unless somebody gets it and recycles it). It is the same scheme > than in Chaplin's _The Kid_: breaking a window to let a glazier sell a > new one. > > Alas, the idiotic way most people evaluate the economy, the GDP, often > makes it seem that kind of thing is good. But according to the GDP, > being stuck in traffic is good for the economy. > > Regards, I asked why he does not reinstall, but didn't get meaningful answer - only, I can not do it and it takes too much time. One can not argue with educated people, so I gave up. This is just an example how it works for most of the people. I am sure if he were working for the money he spends, he were reinstalling.
[toc] | [prev] | [next] | [standalone]
| From | Joe <joe@jretrading.com> |
|---|---|
| Date | 2019-01-04 21:30 +0100 |
| Message-ID | <xcEgr-4JU-19@gated-at.bofh.it> |
| In reply to | #204021 |
On Fri, 04 Jan 2019 20:46:53 +0100 deloptes <deloptes@gmail.com> wrote: > > I asked why he does not reinstall, but didn't get meaningful answer - > only, I can not do it and it takes too much time. > > One can not argue with educated people, so I gave up. > This is just an example how it works for most of the people. I am > sure if he were working for the money he spends, he were reinstalling. Reinstalling looks good until you've done it, the old installation is history, and over the next few weeks you realise how much time you had spent over the last few years tweaking your computer to get it the way you like it. And no, you cannot at the same time a) clear out the cruft, choose different and better software and do the partitioning better and b) just backup the old /etc and restore it. Been there, done all that... Apart from the fact that reinstalling becomes attractive only after you've really broken it badly, beyond the point where you can do dpkg --get-selections and suchlike. Nobody ever reinstalls before they desperately need to. -- Joe
[toc] | [prev] | [next] | [standalone]
| From | deloptes <deloptes@gmail.com> |
|---|---|
| Date | 2019-01-04 23:00 +0100 |
| Message-ID | <xcFFw-5tc-7@gated-at.bofh.it> |
| In reply to | #204029 |
Joe wrote: > Reinstalling looks good until you've done it, the old installation is > history, and over the next few weeks you realise how much time you had > spent over the last few years tweaking your computer to get it the way > you like it. > > And no, you cannot at the same time a) clear out the cruft, choose > different and better software and do the partitioning better and b) just > backup the old /etc and restore it. > > Been there, done all that... > > Apart from the fact that reinstalling becomes attractive only after > you've really broken it badly, beyond the point where you can do dpkg > --get-selections and suchlike. Nobody ever reinstalls before they > desperately need to. Might be true for linux ... for the MS crap it is a must, so I learned doing backups (linux usb stick) and when I have to refresh my wife's or sister's PC, I would restore the last backup I took right after refreshing the PC the last time - you need some time to catch up with all the updates, but it is less if you start from 10y ago. It means this OS was not meant to be operated more than 3-5y even if you do not do much on it it gets slower and slower as if a counter is running somewhere. I personally do not reinstall - PCs and servers are up to date - they were installed some 10-15y ago. Migrated a lot of things though - bigger disks, new motherboards etc. As times go by and things get more and more complex a proper planning is required even for doing small things like adding additional disks, but ... this falls into category sysadmin - a role I avoid to play unless required. regards
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2019-01-04 19:50 +0100 |
| Message-ID | <xcCHE-3Ir-13@gated-at.bofh.it> |
| In reply to | #204000 |
On Friday 04 January 2019 13:24:39 deloptes wrote: > Greg Wooledge wrote: > > All he has to do is find whatever's taking up an unexpected amount > > of space in his root file system, and get rid of it. This is an > > essential system management skill that he HAS to learn, which he > > will continue to use well beyond the current crisis. > > > > Reinstalling on a larger disk to "fix" this is like buying a new car > > every time you run out of gasoline. > > almost like my brother in law who is buying a new notebook every 2 > years because the old one is getting slow. You can imagine which OS it > is :) > > So I was thinking perhaps this is good for the economy, because if > most of the users were like me, there wouldn't be any economic growth > in the past years. I see that too, darn it. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | deloptes <deloptes@gmail.com> |
|---|---|
| Date | 2019-01-05 01:40 +0100 |
| Message-ID | <xcIam-72E-3@gated-at.bofh.it> |
| In reply to | #204006 |
Gene Heskett wrote: >> So I was thinking perhaps this is good for the economy, because if >> most of the users were like me, there wouldn't be any economic growth >> in the past years. > > I see that too, darn it. Suddenly I spotted something that fits our discussion by the worst example - Apple. https://www.youtube.com/watch?v=_XneTBhRPYk
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2019-01-05 06:30 +0100 |
| Message-ID | <xcMGZ-1ok-3@gated-at.bofh.it> |
| In reply to | #204052 |
On Friday 04 January 2019 19:32:18 deloptes wrote: > Gene Heskett wrote: > >> So I was thinking perhaps this is good for the economy, because if > >> most of the users were like me, there wouldn't be any economic > >> growth in the past years. > > > > I see that too, darn it. > > Suddenly I spotted something that fits our discussion by the worst > example - Apple. > https://www.youtube.com/watch?v=_XneTBhRPYk We've been victimized by that too. We bought a video editor in the fading days of NTSC, had a pair of G5's. Within a month we had a fire. They were filled with plastic moldings to direct the cooling air to the hot spots that I thought was pretty sharp engineering, until I realized a fan failure was guaranteed to destroy it in about a minute. Shitty $3 fans, Apple, because we had opened it to verify the fire was out, refused to warranty a thing, quoteing nearly $8500 for a new one. We found another system for 3 G's that got us to the hi-def age in 2008. Apple has never learned that screwing your top of the line customer means he will never darken the apple door again. And AFAIK, no Apple product has ever had a rack screw in its ears at that station since. That whole package, big crt monitors, software and a weeks on-site install and tutoring, cost us north of $25 grand, and we got about a months use out of it. Such memories aren't easily forgotten. Cheers, Gene Heskett --
[toc] | [prev] | [next] | [standalone]
| From | <tomas@tuxteam.de> |
|---|---|
| Date | 2019-01-04 15:50 +0100 |
| Message-ID | <xcyXp-1rO-39@gated-at.bofh.it> |
| In reply to | #203973 |
[Multipart message — attachments visible in raw view] — view raw
On Fri, Jan 04, 2019 at 08:44:27AM -0500, Gene Heskett wrote: > On Friday 04 January 2019 08:15:11 Greg Wooledge wrote: > > > On Thu, Jan 03, 2019 at 09:22:49PM -0500, Gene Heskett wrote: > > > In this case, I hate to sound like > > > an ass, but perhaps a re-install is in the future, doing the > > > reinstall to a new drive [...] > > > > Come on, people. Show some sense. (And yes, this includes the OP.) > > > > He simply has a full root file system. He has shown the df output at > > least twice now. > > > > (A full root file system clearly and plainly shown by df despite the > > OP claiming he is certain he's not out of space, no less.) > > I don't have an argument against any of that Greg, but lets clarify one > thing here and now for the OP. Several responders keep using the "/root" > to describe what you clearly intend to be interpreted as the root of the > filesystem, AKA "/" when in 99.99% of the installs /root is the > sysadmin's home DIRECTORY, and not the root of the filesystem. No, but /root is customarily in the root file system (mounted on /), and it happens some times that there are things forgotten in there (e.g. from manually installed packages, admin sessions squirreling away backups of things, etc). Not a recommended pattern, but it happens. I did interpret the proposals to look into /root in this vein. Cheers -- t
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2019-01-04 18:10 +0100 |
| Message-ID | <xcB8R-2W9-7@gated-at.bofh.it> |
| In reply to | #203967 |
On Fri 04 Jan 2019 at 08:15:11 (-0500), Greg Wooledge wrote: > On Thu, Jan 03, 2019 at 09:22:49PM -0500, Gene Heskett wrote: > > In this case, I hate to sound like > > an ass, but perhaps a re-install is in the future, doing the reinstall > > to a new drive [...] > > Come on, people. Show some sense. (And yes, this includes the OP.) > > He simply has a full root file system. He has shown the df output at > least twice now. > > (A full root file system clearly and plainly shown by df despite the OP > claiming he is certain he's not out of space, no less.) That's rather unfair. songbird asked after space/inodes and the OP responded with "so far as I know". With space in so many places, it would be easy for someone to overlook no space on /. (Which is why I replied "yes, but we don't" and asked for df to be posted). On posting the output, the OP asked "could this e [sic] a problem?". I see no "claim". AFAICT the OP's query was not directly replied to until today, though obviously it, or the other df listing, was read by others, continuing the discussion on several fronts. Stepping back and reading this thread, it seems that there are a lot of "solutions" being thrown in before the OP has been encouraged to find out what the true root (pun intended) of the problem is. As Felix hinted/suggested, I thought rather harshly, the problem might not be caused by what you can see, but by what you can't. The OP needs to examine the filesystem usage and see if that squares with the free space, not go round deleting things (or shopping). Most people's systems evolve (unless they're fresh install types) and the history of the system might need to be taken into account. Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Nicolas George <george@nsup.org> |
|---|---|
| Date | 2019-01-03 21:40 +0100 |
| Message-ID | <xchWy-86y-9@gated-at.bofh.it> |
| In reply to | #203894 |
[Multipart message — attachments visible in raw view] — view raw
Stephen P. Molnar (2019-01-03): > Thank you for your helpful comment. Unfortunately. I am an Organioc > Chemist, not an IT person. Therefore, I am only a user. Then ask your sysadmin. Regards, -- Nicolas George
[toc] | [prev] | [next] | [standalone]
| From | Nicolas George <george@nsup.org> |
|---|---|
| Date | 2019-01-03 19:00 +0100 |
| Message-ID | <xcfrI-6xn-13@gated-at.bofh.it> |
| In reply to | #203884 |
[Multipart message — attachments visible in raw view] — view raw
Stephen P. Molnar (2019-01-03): > root@AbNormal:/home/comp# ldconfig > ldconfig: Writing of cache data failed: No such file or directory At this point, I would suggest: strace ldconfig > root@AbNormal:/home/comp# sbin/ldconfig > -bash: sbin/ldconfig: No such file or directory You should re-read the commands you type, the mistake is obvious. Regards, -- Nicolas George
[toc] | [prev] | [next] | [standalone]
| From | "Stephen P. Molnar" <s.molnar@sbcglobal.net> |
|---|---|
| Date | 2019-01-03 19:00 +0100 |
| Message-ID | <xcfrI-6xn-9@gated-at.bofh.it> |
| In reply to | #203884 |
On 01/03/2019 12:35 PM, deloptes wrote: > deloptes wrote: > >> man ldconfig -> cache default is /etc/ld.so.cache >> >> Was it altered and you forgot? Or is it someting wrong with the default >> cache file >> >> $ ls -al /etc/ld.so.cache >> -rw-r--r-- 1 root root 176004 Jan 1 21:56 /etc/ld.so.cache > as root try > > touch /etc/ld.so.cache > > run manually ldconfig and perform the upgrade again > > check if you have also the rest of ldconfig - at least /etc/ld.so.conf > > best would be if you had backup and knew what was there before > > regards > Thanks for the suggestion. However: root@AbNormal:/home/comp# ldconfig ldconfig: Writing of cache data failed: No such file or directory root@AbNormal:/home/comp# sbin/ldconfig -bash: sbin/ldconfig: No such file or directory root@AbNormal:/home/comp# This seems to me as being rather strange, because ldconfig is installed in sbin. -- Stephen P. Molnar, Ph.D. Consultant www.molecular-modeling.net (614)312-7528 (c) Skype: smolnar1
[toc] | [prev] | [next] | [standalone]
| From | deloptes <deloptes@gmail.com> |
|---|---|
| Date | 2019-01-03 20:20 +0100 |
| Message-ID | <xcgH7-7rs-1@gated-at.bofh.it> |
| In reply to | #203887 |
Stephen P. Molnar wrote: > root@AbNormal:/home/comp# ldconfig > ldconfig: Writing of cache data failed: No such file or directory Try touch /etc/ld.so.cache and repeat > root@AbNormal:/home/comp# sbin/ldconfig > -bash: sbin/ldconfig: No such file or directory > root@AbNormal:/home/comp# It is /sbin/ldconfig regards
[toc] | [prev] | [next] | [standalone]
| From | "Stephen P. Molnar" <s.molnar@sbcglobal.net> |
|---|---|
| Date | 2019-01-03 20:50 +0100 |
| Message-ID | <xchaa-7Ba-9@gated-at.bofh.it> |
| In reply to | #203891 |
On 01/03/2019 02:10 PM, deloptes wrote: > Stephen P. Molnar wrote: > >> root@AbNormal:/home/comp# ldconfig >> ldconfig: Writing of cache data failed: No such file or directory > Try > > touch /etc/ld.so.cache > > and repeat > >> root@AbNormal:/home/comp# sbin/ldconfig >> -bash: sbin/ldconfig: No such file or directory >> root@AbNormal:/home/comp# > It is /sbin/ldconfig > > regards > > > root@AbNormal:/home/comp# touch /etc/ld.so.cache root@AbNormal:/home/comp# /sbin/ldconfig /sbin/ldconfig: Writing of cache data failed: No such file or directory -- Stephen P. Molnar, Ph.D. Consultant www.molecular-modeling.net (614)312-7528 (c) Skype: smolnar1
[toc] | [prev] | [next] | [standalone]
| From | deloptes <deloptes@gmail.com> |
|---|---|
| Date | 2019-01-03 21:40 +0100 |
| Message-ID | <xchWy-86y-1@gated-at.bofh.it> |
| In reply to | #203897 |
Stephen P. Molnar wrote:
> root@AbNormal:/home/comp# touch /etc/ld.so.cache
> root@AbNormal:/home/comp# /sbin/ldconfig
> /sbin/ldconfig: Writing of cache data failed: No such file or directory
Tell us which version you have
$ cat /etc/debian_version
9.6
check and post here if you are out of space
$ df -hl
...
...
[toc] | [prev] | [next] | [standalone]
| From | "Stephen P. Molnar" <s.molnar@sbcglobal.net> |
|---|---|
| Date | 2019-01-03 21:50 +0100 |
| Message-ID | <xci6d-89I-1@gated-at.bofh.it> |
| In reply to | #203906 |
On 01/03/2019 03:31 PM, deloptes wrote: > cat /etc/debian_version root@AbNormal:/home/comp# cat /etc/debian_version 9.6 root@AbNormal:/home/comp# df -hl Filesystem Size Used Avail Use% Mounted on udev 3.9G 0 3.9G 0% /dev tmpfs 789M 18M 772M 3% /run /dev/sda1 23G 23G 0 100% / tmpfs 3.9G 18M 3.9G 1% /dev/shm tmpfs 5.0M 8.0K 5.0M 1% /run/lock tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup /dev/sda7 1.9G 6.5M 1.7G 1% /tmp /dev/sda5 9.2G 6.0G 2.8G 69% /var /dev/sda8 416G 103G 292G 27% /home /dev/sdc1 20G 301M 19G 2% /sdc1 /dev/sdc2 439G 169G 270G 39% /sdc2 /dev/sdb1 1.8T 288G 1.5T 17% /sdb1 tmpfs 789M 4.0K 789M 1% /run/user/110 tmpfs 789M 28K 789M 1% /run/user/1000 root@AbNormal:/home/comp# -- Stephen P. Molnar, Ph.D. Consultant www.molecular-modeling.net (614)312-7528 (c) Skype: smolnar1
[toc] | [prev] | [next] | [standalone]
Page 3 of 5 — ← Prev page 1 2 [3] 4 5 Next page →
Back to top | Article view | linux.debian.user
csiph-web