Re: [Adam Di Carlo <email@example.com>] Re: framebuffer
>He wrote that he has concerned very much if the official kernel with
>vga16fb-support are provided, on debian-devel@JP list.
It's easy enough to make your own alternate kernel.
>I hope that he can work with official boot-flopies team in debian-boot list,
>in order to enable the support of fbdev.
Yes, we'd love to receive patches. He should be working out of the
CVS area; see attached document. I will happily setup CVS accounts to
those who show they know what they're doing.
.....Adam Di Carlo....adam@onShore.com.....<URL:http://www.onShore.com/>
You can access the boot-floppies using CVS; this is particularly useful
if you are actively working on the package.
CVS comes with excellent documentation; in particular, see the 'cvs'
There are various ways to access the CVS repository for the boot-floppies,
depending on your circumstances. However, once you've set up your
CVSROOT variable properly, all the access methods behave identically.
The following are bash commands you can
run to get the CVS area; other shell users should be able to translate
to their shell language easily. Commands with a '#' are comments; you
don't have to type those.
# if you are logged into to va.debian.org, aka cvs.debian.org:
# if you are using 'ssh' to access the area, and you have an account
# on va.debian.org -- this is the recommended method:
# if you are using anonymous (readonly) access:
# you will be prompted for a password -- just hit 'enter'
# if you are using a pserver account (i.e., you need write access but
# do not have an account on va, and you have been given a pserver
# username and password):
# enter the password you have been given
After that, all techniques are the same. Simply check out the sources.
For the lastest (possibly unstable) version, do:
cvs co boot-floppies
For the slink CVS branch, which is probably what you are using if you are
working on translating slink documentation:
cvs co -r adam-boot-floppies_2-1_branch boot-floppies
>From there, you just use 'cvs update' and 'cvs commit' -- see the