(responding to Ed)
> Why? I said the *entire* /var/cache/system-upgrade/
> directory can be deleted. I said it is no longer used.
I did not understand it that way. My apologies.
/var/cache/system-upgrade/ deleted.
> Google is your friend.
I've had better friends! And many people would agree wi
On 10/27/19 8:43 AM, home user wrote:
(responding to Ed)
> > Question 1
> > (/var/cache/system-upgrade/updates/packages/
> That entire directory can be deleted. It was used by fedup,
> the forerunner to "dnf system-upgrade". No longer used,
> no longer needed.
I did "rm -rf /var/cache/system-up
(responding to Ed)
> > Question 1
> > (/var/cache/system-upgrade/updates/packages/
> That entire directory can be deleted. It was used by fedup,
> the forerunner to "dnf system-upgrade". No longer used,
> no longer needed.
I did "rm -rf /var/cache/system-upgrade/updates/packages/".
-
-bash.1
> My question is how to
> protect 2 kernels from being erased.
I seem to recall I did this once by doing an
rpm --justdb -e kernel
That removes the info that the kernel exists from
the rpm database, but leaves the files.
I'm not absolutely positive that works, just a
dim memory :-).
Hello Tony,
On Sat, 26 Oct 2019 15:50:35 -0400 Tony Nelson
wrote:
> On 19-10-25 22:06:37, Tim via users wrote:
> > On Fri, 2019-10-25 at 16:42 -0400, Tony Nelson wrote:
> > > When DNF upgrades the kernel packages, it removes kernels so that
> > > there are not more than installonly_limit ins
On 10/27/19 2:49 AM, home user wrote:
Question 1:
/var/cache/system-upgrade/updates/packages/ takes up 1.6G and appears to be
full of rpm's (1083 of them), each dated 2015 (various months). I do not know
the fine details of dnf and rpm. Can I safely delete them, or might that break
future pa
On 19-10-25 22:06:37, Tim via users wrote:
On Fri, 2019-10-25 at 16:42 -0400, Tony Nelson wrote:
> When DNF upgrades the kernel packages, it removes kernels so that
> there are not more than installonly_limit installed. It won't
> remove the running kernel.
>
> How do I protect more than the run
As of mid-day Saturday, Oct. 26, here is what '/' filesystem space use
looks like on this work station:
===
bash.2[/]: df -hP
Filesystem Size Used Avail Use% Mounted on
tmpfs 7.8G 1.7M 7.8G 1% /run
/dev/sda6 50G 24G 23G 52% /
/dev/sda7 904G 7.6G
As of mid-day Saturday, Oct. 26, here is what '/' filesystem space use
looks like on this work station:
===
bash.2[/]: df -hP
Filesystem Size Used Avail Use% Mounted on
tmpfs 7.8G 1.7M 7.8G 1% /run
/dev/sda6 50G 24G 23G 52% /
/dev/sda7 904G 7.6G
(replying to Ed and Samuel)
(regarding /usr/bin/sh, /bin/sh, and bash being the same)
ok. Thank-you.
line changed to "#!/usr/bin/bash".
> This line is redundant. ...
ok. Thank-you.
line deleted.
> (when the script is run)
Though the odds are very slim, I want to be sure the delete doesn't
ha
On 10/25/19 7:56 PM, home user wrote:
The script looks like this:
-
#!/usr/bin/sh
# clean out files left behind by the compiling that follows patching or
# updating the kernel and/or the driver for the nvidia graphics card.
rm -rf /var/cache/akmods/nvidia/*
exit $?
This line is redundant
11 matches
Mail list logo
