Larry Linder wrote:
> Because we are in a little town (wide spot in road) the DSL is not the most
> reliable. That is why I down loaded the 8 disks from another source and
> wanted to update systems to SL 5.5.
> This install try was an update and not a new installation.
> There have been a lot of
What you want to do, can be done with a combination of parted
and resize2fs. Take good backups first. It would have been
easier if you were using LVM.
basic strategy, resize2fs to shrink /usr/local file system,
then parted to shrink /usr/local partition,
then parted to grow /usr partition.
The
Because we are in a little town (wide spot in road) the DSL is not the most
reliable. That is why I down loaded the 8 disks from another source and
wanted to update systems to SL 5.5.
This install try was an update and not a new installation.
There have been a lot of additions to this system, fo
Larry Linder wrote:
When installing SL5.5 over SL5.4 about mid way into the Disk 2 I get an Error
message to REBOOT.
204 Meg on /mnt/sysimage/usr
When I look at /mnt it is empty after reboot.
My guess is that update ran out of disk space, and the the sysimage/usr is
removed after ERROR is de
On Thu, 22 Jul 2010, Larry Linder wrote:
When installing SL5.5 over SL5.4 about mid way into the Disk 2 I get an Error
message to REBOOT.
204 Meg on /mnt/sysimage/usr
When I look at /mnt it is empty after reboot.
During an install, the partition that is going to become /
would be mounted on
When installing SL5.5 over SL5.4 about mid way into the Disk 2 I get an Error
message to REBOOT.
204 Meg on /mnt/sysimage/usr
When I look at /mnt it is empty after reboot.
My guess is that update ran out of disk space, and the the sysimage/usr is
removed after ERROR is detected and REBOOT mess
