Re: Samba and XP support discussion. Where is the XP shares?

On Tue, 2007-02-06 at 06:04 +0000, Tom Bruno (crweb) wrote:
> >
> > To continue the question, what should be done in order to include this
> > into the formal release?
> >
> > And, I noticed you said that the current upk build process is broken,
> > what exactly were the problems you run into? build-helper.sh still is
> > able to build all the way to a developer upk.
> 
> The problem isn't the upk build process.
> 
> Major problems that made this release difficult:
> 
> 1.) Version number check.  I had to increase the version of my
> firmware, or decrease the version stored in  cur_uboot, cur_kernel,
> cur_rootfs. I could not flash alternative numbers, or lower version
> numbers. This makes reflashing and testing difficult.
> 
> 2.) I used 0.63 as my base, I had to name my firmware 0.64 to get it
> to flash (see #1).  However the upk would still not flash because I
> only included root.cramfs and uImage.  Error message was that I had to
> update uboot.  This shouldn't not happen, i didn't need to include
> uboot but the version checks made it so i had to.  Work around, i had
> to go into the OSD and change cur_uboot to 0.64.  Forcing me to
> include uboot is dangerous. changing cur_uboot is impossible without a
> serial cable making my firmware useless to normal users and testers
> without serial cable.
> 
> 3.) Cannot reflash to official neuros firmware because of #1 and #2 my
> versions are higher than Neuros versions.  Making it hard for users,
> myself, and impossible again for non serial users to revert away from
> custom firmware. (have to manually edit
> cur_uboot,cur_kernel,cur_rootfs in OSD env)
> 
> 4.) Cannot reflash my firmware after I messed it up. See #1, I messed
> up some stuff and had to repack my rootfs.  I could not reflash 0.64 i
> had to update my version to 0.65,  repeat #1, #2, #3.
> 
> The logic in flashing needs to be fixed.
Yes, the logic needs to be tighten up.

For now, you just need to use emergency upgrade with the backdoor, you
do NOT need to mess with the version number at all unless you want to,

1. rename your upk to r3.upk;
2. put it under [CF|SD|MS]/newpackage;
3. under /newpackage, create a dummy file called
'disable_upk_version_check'. 
4. recycle OSD power, it will ignore version and update.

/MG

--~--~---------~--~----~------------~-------~--~----~
FOR REALTIME DISCUSSION GO TO IRC #neuros on freenode

You received this message because you are subscribed to the Google Groups "Neuros-DM320" group.
To post to this group, send email to Neuros-DM320Hardware <at> googlegroups.com
To unsubscribe from this group, send email to Neuros-DM320Hardware-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/Neuros-DM320Hardware
-~----------~----~----~----~------~----~------~--~---