On Fri, 2009-07-03 at 13:06 -0400, William Case wrote:
> #2 A Bug vs a Nitpick
>
> ... sometimes there are things that are wrong that are, to me, more of
> a Nitpick than a bug. I am often reticent to use bugzilla for
> something that is minor
There are reporting options about rating whether the bug is very
important, or not. I've no qualms about reporting things like misspelt
words in the GUI, but as a low priority bug. The maintainer can fix
them up, but won't bother pushing out the update just for that fault.
They'll wait for more important bugs to be fixed, then all the fixes
will be pushed out in one go.
> #4 Giving back help on the users list
>
> I often recognize problems brought up on the Fedora users mailing list,
> and have the sure-fire solution while others respond with solutions that
> are terribly wrong.
I'd say to always correct wrong advice, though you'd have to be able to
tell the difference. Letting wrong advice stand does harm to other
people. I see that more in other place, though (e.g. Ubuntu or Windows
forums, where idiots give out the most stupid suggestions).
Tentatively offer things that you're unsure about, or outright ask if
what you think might be right is, in fact, right. Most questions are
looked at by more people than those that you notice replying. If you're
off base, someone will probably say something.
> #5 Fedora 11 LAN installation
>
> I have a two computer (sometimes three computer) LAN in my house. Both
> are F10 to be F11. In the past, to keep it simple, I have installed the
> newest Fedora version on each machine by burning the .iso to disk(s) and
> then doing two separate installs. I was thinking that this time -- just
> for the hell of it -- I would do something fancier like install F11 on
> the second machine using the LAN.
If you can do an install from disc in about 15 minutes, that's a good
speed. If it takes significantly longer, then disc reading is your
slowdown, and doing a network install will improve things a lot, for the
second install. However, the set up time for just one more computer
might negate that advantage.
I've done HTTP installs, where a webserver serves out the files found on
the install disc. SELinux can be a problem if you try to serve directly
from the disc, and you'll still have slow disc read speeds to contend
with. The only advantage of working that way is for other computers
without DVD/CD drives. Copying the install disc files to a directory on
your harddrive that your webserver serves out makes for rapid installs,
although the initial copy everything on the disc to your hard drive is
slow.
You can do network installs where it looks at the downloaded ISO file
over the network. So you don't have to burn any discs.
Using one computer as a cache for your updates can significantly cut
down on your download count. If you run close to your ISP limit, that
can be a big help.
One of the simplest ways I've installed over multiple computers was:
1. Download and burn the network install disc.
2. Download the install DVD ISO and put it on a removable drive
(could be a hard drive, could be a memory stick, it doesn't
matter).
3. Boot a computer from the network install disc, with that
removable drive plugged in, as well.
4. Use the option to install from local disc, and pick the plugged
in removable drive.
It was fast (only a small thing came from the slow disc, the start up of
the installation), and simple to manage. And since you don't need to
use a network, you can take your two install thingies around to a
friend's place, and update their computers, very easily.
--
[tim@localhost ~]$ uname -r
2.6.27.25-78.2.56.fc9.i686
Don't send private replies to my address, the mailbox is ignored. I
read messages from the public lists.
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
