From: "Scott Ford" <scott@adaptiveit.us>
To: "'Speakup is a screen review system for Linux.'"
<speakup@braille.uwo.ca>
Subject: RE: live Ubuntu cd with Orca
Date: Fri, 24 Nov 2006 20:26:51 -0500 [thread overview]
Message-ID: <001e01c71030$ca037f90$7301a8c0@A55> (raw)
In-Reply-To: <20061124231702.GA1158@taylor.homelinux.net>
Lorenzo,
I had major difficulty, just like you. I had to get my daughter to
help. I will attempt to describe what needs to be done. However do it at
your own risk. I had my partitions set up ahead of time. I have my hard
drive setup as follows. Partition one NTFS, 2 fat 32, 3 swap, 4 logical, 5
ext3 /home, and 6 ext3 / . Now in order to setup the partition on the
ubuntu setup there must be places setup in each graphical column.
In my case I had to have media for the first two partitions. Then for my
third partition I chose swap. Finally set /home, and / to the final
partitions. I had help with eye balls, I hope that this can provide some
clues for you guys. Good luck
-----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]
On Behalf Of Lorenzo Taylor
Sent: Friday, November 24, 2006 6:17 PM
To: Speakup is a screen review system for Linux.
Subject: Re: live Ubuntu cd with Orca
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I had problems with the partitioner too, but I need to find where to report
the bugs I found.
First off, I wanted something other than the default big / partition
formatted as ext3, but if I changed anything in the partitioner and clicked
"forward" Orca stopped speaking and even restarting it didn't help. Then I
tried using Speakup, mkfs... and a text-based partitioner to set things up
ahead of the installer and then went to the installer and told it to
manually edit partitions and clicked forward from there.
It went to the mount point selection window, but no matter how many times I
specified where I wanted the "/" root file system it gave me the error "no
root file system" and wouldn't let me go any further. I decided to just
stick with the defaults for now, but I have had problems with ext3
corrupting the entire file system on a kernel panic and didn't want to use
it for that reason. If anyone has any suggestions either where to report
this or how to get to the next step, please let me know.
Thanks,
Lorenzo
- --
I've always found anomalies to be very relaxing. It's a curse.
- --Jadzia Dax: Star Trek Deep Space Nine (The Assignment) -----BEGIN PGP
SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFFZ31uG9IpekrhBfIRAitjAKCE91+o8yMbmHG/za4nX0fDNlDhmACgr8oF
/tc3zLKu9MHf3CWYDtsbDwE=
=LygZ
-----END PGP SIGNATURE-----
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.409 / Virus Database: 268.14.14/548 - Release Date: 11/23/2006
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
Daniel Crone
` John covici
` Kenny Hitt
` Lorenzo Taylor
` Scott Ford
` Chris Norman
` Scott Ford
` Buddy Brannan
` John covici
` Lorenzo Taylor
` Henrik Nilsen Omma
` Scott Ford
` John covici
` Lorenzo Taylor
` Scott Ford [this message]
` randy turner
` Marcel Oats
` randy turner
` Marcel Oats
` randy turner
` obvious question but...? Karen Lewellen
` Lorenzo Taylor
` live Ubuntu cd with Orca Chris Norman
` John covici
` Scott Ford
` randy turner
` Scott Ford
` Chris Norman
` Chris Norman
` Henrik Nilsen Omma
Daniel Crone
` Lorenzo Taylor
` Chris Norman
Daniel Crone
Daniel Crone
Daniel Crone
Daniel Crone
` randy turner
` Scott Ford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001e01c71030$ca037f90$7301a8c0@A55' \
--to=scott@adaptiveit.us \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).