--- Natarajan K <natarajan_kannan@xxxxxxxxxxx> wrote:
Suresh Ramasubramanian wrote:
Gopalarathnam V. [1/12/2004 5:33 PM] :I've myself seen many a
Atleast "their" installer isn't robust enough!
they couldn't read ainstallations aborting in the middle just because
printing out the infamousfile from the cdrom, or something like that
Debian woody (I suggestederror messages:
Sending kill signals...
Sending termination signals...
That was one major reason my friend installed
RedHat!him to) on his system unable to do away with
middle of an install ..
Arre baba, if you get a corrupt package in the
something will be definitely broken if youcontinue to install it.
At least redhat has some sanity checking for that.
Now, again, what is not all that robust about a
Its not the case always. For eg. let us consider the
package A is corrupt and there are no packages
depending on it. Why
would you need to abort the installation of the OS
for that package. Why
cant the installer proceed?? Even in the case of
dependencies the onus
is on the installer to remove the packages dependent
on the corrupt
I had this experience in Fedora Core 1.
Still wondering why RedHat is refusing to pack apt
as a frontend to
their rpm package manager????