-----BEGIN PGP SIGNED MESSAGE-----
I got the kernel rpm to build and the install script to work. Once
I rebooted I recieved the following message:
Waiting for device /dev/sda2 to appear: ok
rootfs: major=8 minor=2 devn=2050
input: AT Translated set 2 keyboard isa0060/serio0
Right now I am going to resync my tree up as there have been
changes made since I originally checked out. Has any one seen this
As per procedure, is the general practice in the Openssi to get
everything up and working before checking in or checking in pieces
at at a time. Do I need to wait to submit my changes until I fully
get Openssi working on SuSE Pro 9.2 or should offer the changes I
have done now?
-----BEGIN PGP SIGNATURE-----
Note: This signature can be verified at https://www.hushtools.com/verify
Version: Hush 2.4
-----END PGP SIGNATURE-----
Concerned about your privacy? Follow this link to get
secure FREE email: http://www.hushmail.com/?l=2
Free, ultra-private instant messaging with Hush Messenger
Promote security and make money with the Hushmail Affiliate Program:
From: Brian J. Watson <Brian.J.Watson@hp...> - 2005-07-29 20:33:58
> As per procedure, is the general practice in the Openssi to get
> everything up and working before checking in or checking in pieces
> at at a time. Do I need to wait to submit my changes until I fully
> get Openssi working on SuSE Pro 9.2 or should offer the changes I
> have done now?
Since the OPENSSI-SU branch is not yet completely working, you can
checkin any time you think it's a good time to "checkpoint" your work.
It's completely your choice.
Once the branch is working, like the OPENSSI-FC or OPENSSI-DEBIAN
branches, then the policy is to never checkin anything that will break
the branch. In other words, users should be able to do a checkout from
the repository with your changes, build OpenSSI packages, install them,
and everything should work fine (except for any outstanding bugs).
Hope this helps,