Sorry, not the SAME problem.. My just recorded iso doesn't work,... Sorry again..
-- Tomás A. Schertel tschertel[at]gmail.com tomas[at]archlinux-br.org ---------------------------------------------- Arch Linux User http://www.archlinux-br.org/ Linux Registered User #304838 ---------------------------------------------- On Thu, Sep 25, 2008 at 23:58, Tomás Acauan Schertel <[EMAIL PROTECTED]>wrote: > I had this problem too... > > -- > Tomás A. Schertel > tschertel[at]gmail.com > tomas[at]archlinux-br.org > ---------------------------------------------- > Arch Linux User > http://www.archlinux-br.org/ > Linux Registered User #304838 > ---------------------------------------------- > > > > On Thu, Sep 25, 2008 at 22:12, Chris Brannon <[EMAIL PROTECTED]> wrote: > >> Hi list, >> I'm new to Arch. The other day, I downloaded the ISO mentioned in the >> subject >> line. I remastered the image, because I needed some extra programs. I'm >> blind. I added a screenreader and a text-to-speech engine to the ISO, >> so that I could have spoken feedback during the install. I also added >> alsa-utils, alsa-lib, and a few miscellaneous packages. >> I burned the CD and booted the system. Arch started talking to me, and >> everything seemed ok. >> >> After a few minutes, I started noticing strange behavior. The system >> froze >> when I tried to execute a command. >> For instance, after typing "ps" at the bash prompt, the system locked up. >> It was unable to load the ps executable or one of its shared libraries >> from >> the CD. Sometimes, it would print the message "input-output error", and >> return to a working bash prompt. I could hear my CD-ROM drive clicking >> whenever >> it tried to load the executable. It just sat there for five or more >> minutes, >> spinning and clicking. >> I also noticed that Arch is writing data to its unionfs. Most of the data >> seems to be written to /var/log. Should a live CD be writing to logfiles? >> >> My problems could be caused by one of several things. >> 1. A broken CD-ROM drive. (I doubt it, because the drive is 3 weeks old). >> 2. A mistake while remastering the ISO. >> 3. Some sort of error from the original ISO. >> >> Has anyone else had trouble with this image? If not, then the issue must >> be caused by my hardware or personal configuration. >> >> Regards, >> -- Chris >> > >
