Re: No update notifications since upgrade
Yesterday I did a fresh install of the 64b KK final release. Within 30 minutes I got a notification of updates and security fixes. This was after the install procedure checked on line for updates and stuff and installed them.
I also noticed something else... The LiveCD that I used was one I burned a week ago. The ISO passed the md5sum test and so did the CD itself.
I used it to create a 64b KK LiveUSB stick on a friends year old HP dvt6 laptop. The creation went beautifully, even though it was the first time I had created a LiveUSB using the LiveCD that was running the HP, while it was running the HP !!
Anyway, I booted that LiveCD in this Sony notebook. It took 5 minutes before it began to initialise the 3D screen. Meanwhile, it was throwing all sorts of sr0 read errors, block errors, can't find xxxx errors. It was looking awful. I aborted the process. I thought that perhaps the CD had been scratched but the surface was pristine. So, I ran another md5sum check on the LiveCD. Normally, it takes about 250-300 seconds to do an md5sum on a CD. This check was going on for almost 10 minutes. I was about to abort it when the check completed and reported an accurate md5sum value!.
After a moment's reflection I realised that I had burned that LiveCD on my Acer laptop. I burned a new LiveCD using this Sony and it checked out on both md5sums, the CD check taking only 268 seconds. Rebooting, the LiveCD flashed through the boot process and gave me a desktop within a couple of minutes.
Moral: LiveCD work best in the burner they were burned in. AND, LiveUSBs are more reliable on any machine that can boot from the USB port.
Oh, usbautomount did not install from the LiveCD and when I plugged in a USB stick or tried to find the other partition on this HD, I got zilched. Installing usbautomount from the repository fixed that.
Yesterday I did a fresh install of the 64b KK final release. Within 30 minutes I got a notification of updates and security fixes. This was after the install procedure checked on line for updates and stuff and installed them.
I also noticed something else... The LiveCD that I used was one I burned a week ago. The ISO passed the md5sum test and so did the CD itself.
I used it to create a 64b KK LiveUSB stick on a friends year old HP dvt6 laptop. The creation went beautifully, even though it was the first time I had created a LiveUSB using the LiveCD that was running the HP, while it was running the HP !!
Anyway, I booted that LiveCD in this Sony notebook. It took 5 minutes before it began to initialise the 3D screen. Meanwhile, it was throwing all sorts of sr0 read errors, block errors, can't find xxxx errors. It was looking awful. I aborted the process. I thought that perhaps the CD had been scratched but the surface was pristine. So, I ran another md5sum check on the LiveCD. Normally, it takes about 250-300 seconds to do an md5sum on a CD. This check was going on for almost 10 minutes. I was about to abort it when the check completed and reported an accurate md5sum value!.
After a moment's reflection I realised that I had burned that LiveCD on my Acer laptop. I burned a new LiveCD using this Sony and it checked out on both md5sums, the CD check taking only 268 seconds. Rebooting, the LiveCD flashed through the boot process and gave me a desktop within a couple of minutes.
Moral: LiveCD work best in the burner they were burned in. AND, LiveUSBs are more reliable on any machine that can boot from the USB port.
Oh, usbautomount did not install from the LiveCD and when I plugged in a USB stick or tried to find the other partition on this HD, I got zilched. Installing usbautomount from the repository fixed that.
Comment