new fedora logos, wallpapers, access to resources
by Bart Kalita
Hi All,
I'm thinking about creating some new wallpapers for FC3.
I've made some for FC2 and had some if minimal response. Still I'm
interested in a possibility to access to FC logos for FC3 even in a test
1 version.
Can anybody help and tell me where to find those logos may it be on the
ISOs or ftp?
And by the way is there any particular reason why there are so few FC
wallpapers?
--
__________________________________________________________
Bart Kalita MCP
Registered Linux user #347493 Fedora Core 3 test 1
www.bart-domain.com www.astradine.no-ip.org
19 years, 8 months
enable the 256 colors support in xterm?
by Dan Nicolaescu
Can the FC3 xterm be compiled with support for 256 colors enabled?
(i.e. configure with --enable-256-color)
This would enable applications to take advantage of a higher number
of colors.
For example, the next version of Emacs will have support for 256 color
xterms.
(This support is not present in emacs-21.3 but it can probably be
easily backported, if desired. It would probably be an ~200 lines
patch). With that support, syntax coloring in emacs running in an
xterm looks almost identical to emacs running in X11. This is great
for using emacs over slow connections.
Thanks.
--dan
19 years, 8 months
How can I Installation of Fedora Core2 through NFS?
by malik malik
Dear friends
I have 4 systems. I am not willing to spend more time to install each and every system. I heard we can install fedora core2 through NFS. plz let me know, how we can install fedora core2 through the NFS?
plz let me in brief..
guna.
---------------------------------
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
19 years, 8 months
Re: test plans
by Kyrre Ness Sjobak
> On Thu, Jul 29, 2004 at 04:35:01PM -0400, Christopher Aillon wrote:
> > Mozilla's basic functionality test suite (smoketest) which includes
> > plugins testing is at http://www.mozilla.org/quality/smoketests/index.html
>
> Similiarly OpenOffice has a qadev cvs module which has lots of qa tests, and
> there is a quicker smoketest 10erTest_680.sxw document which runs through some
> basic sanity tests. With OOo UNO interface its relative trivial to write
> tests in e.g. python to automate OOo specific tests like document load/convert
> comparisons.
>
> C.
Yep. But wouldn't it be good to include a pointer to these instructions
high up in the release-notes of the test-releases, or/and somewhere that
is easyly seen (motd+users desktops?) I tested fc2-t3, but heard nothing
of such instructions.
Kyrre Ness Sjøbæk
19 years, 8 months
test plans
by Havoc Pennington
Hi,
I'd like to see some more detailed test plans for the Fedora desktop.
These need not be complicated or long, just a set of basic things we
want to try out in each of the major apps and in the OS itself.
Here are some notes I have on things we might include. I know that some
of these tests would not pass at the moment, no need to point that out
;-)
- basic run through a login session; log in, log out, launch some
apps; does anything embarassing happen
- install previous version of the OS; log in to a user account,
play with some things, change settings; tar up and save the
user home directory; install current version of the OS,
and unpack same user home directory; repeat the above basic
run through a login session
- develop list of major apps that must be tested, check basic
functionality of each. e.g. browser, office, mail, IM, etc.
- input methods work in these apps
- printing works properly in all 10 languages from these major apps
- Windows printers are detected and shown automatically in print
dialog
- CUPS printers are detected and shown automatically in print dialog
- in Nautilus, verify that Windows file shares appear automatically
and the files there can be opened on double click, specifically
check MS Office files
- verify that plugging in several representative USB storage devices
results in them appearing on the desktop and working
- verify that if a local USB printer is plugged in, it is automatically
configured and made available
- verify that on plugging a network cable the link is automatically
brought up and dhcp run
- verify that wireless networking can be used without resorting
to the command line at all
- login to FC1/2, login to FC3 same homedir, run through
major apps and check for confusion with shared NFS homedir
- login on two different machines, same homedir, with same FC
version, check for badness
- login twice on same machine same user and check for badness
- test lockdown of settings, ensure desktop behaves properly and
user can't avoid the lockdown
- test X on some list of video hardware; automated smoke test
- accessibility, e.g. test screen reader and onscreen keyboard
- correct fonts used in 10 languages for set of common font
names
- suite of Microsoft documents to be imported correctly
(screenshots of correct appearance?)
- suite of web pages to render correctly
- cut-and-paste to/from a big matrix of sources/targets
- out of disk space, behavior on login and when saving
from the major apps
- set date/time backward, see if desktop or login breaks
- run any test suites we have for specific components
- verify that all browser plugins work (including
the proprietary ones available from third parties)
- verify important MIME associations, e.g. .doc opens in
OpenOffice.org, etc.
- test use of an Active Directory account for Linux login
As you can see from the list, the plans need to be more specific, and
point to the files (tarred up homedirs, web pages, office documents,
etc.) to be used.
Havoc
19 years, 8 months
