Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×
User Journal

Journal Journal: Projects... what to do next...

It's been a long sommer... long because a simple project turned out to be not so simple...

I decided to redo our guest half bath.   It was cramped, and I wish I photo documented everything I did but it's too late so... oh well.  In hindsight, if anyone wants to redo their bath... my adivice is to plan on stripping everthing down to the studs and plan on having to rip up 5 floors just to get down to the subfloor.

Needless to say this project went way beyond my deadline.

Many things were just comical... down to before even starting - which is what prompted the start of the project.

/----Sink & counter
| /- Window
|O|   |
| /(o)| <- toilet
+| |--+
\      <- door
  \------- enter
This is the best ascii representation of the 1/2 bath... and it's also nearly to scale.  There was really no room to move inside this Water Closet... There was a huge countertop taking up most of the space, the toilet & tank was so big it was in the way of the door way, the counter was cut at an angle so you could actually get into the bathroom without having to be a gymnast.  Then there was the fact that they were puke green sink and toilet... a great color to hide the dirt and other nonmentionables, but not very... well.. it just looked like crap.

Redid the tile floor which was an inch higher then the connecting rooms floor (also tile), which after ripping it up, and ripping up the lanolium under, and ripping up another lanolium under, and then ripping up some paper like flooring, and then ripping up some fiber board, I got to the subfloor... after that I new why it was an inch taller.

One of the walls collaps it was so brittle, and under the heating duct was broken with a 6 inch gap that must have dried out the wall board and made it brittle.  We had some issues with the register at the end of this duct and I could see why there was no heat coming through... it was all leaking into the crawl space under the half bath...

The other wall had a section of wall that was patched (where a medicine cabanet use to be) some time ago collapse when sanding since the previous owner patched it with cardboard.

it's going much better now though... I just want to get it done.

Journal Journal: Source Code Control 1

So I hit the last straw this past week with our SCCS system. At work, after doing some major changes to the software project and verifying the integrity of the software in my local development environment, I decided to check in about 80 files into the main repository. This was a good time to check in because another engineer needed to modify a couple of header files I had checked out. The files I was going to check in were c, assember (68k and PPC), header files, and a couple of other propriatary formates.

We have some home grown tools for handling check in and check out that really use SCCS for the back end.

After it had committed all the asembler files and most of the header files, it burped on a couple of header files complaining that I didn't have them checked out.

Very annoying - now I have to stop and roll back, since some lamer in our development group didn't tell me they needed a file I had and probably just blew my p file away.

I go to roll back and the guy that asked me earlier if I could surrender the files he needed had already checked out a couple of the files I just checked in - More annoying, but understandable.

He rolls back my changes for me - already other engineers are starting to notice that files are not compiling due to half the headers being in. The way our system works is that the local environment uses the headers from the main repository if there isn't a local version.

I roll everything back so then everyone can work again.

Then I go to the next issue, figuring out who blew my lock away. Checking the put logs (since our system doesn't track extraction) I guess the version and after a few tries figure out that there were about 15 revisions to both files since I checked them out, and both had some major rewrites, and the contents were also split into smaller header files. Found out the engineer that blew away my p file, and he told me that he did it because I wasn't at my desk when he came by origionally. I asked him why he didn't email, and he siad he was rushed - Really damb annoying now, and not understandable.

So... after this experience, I'm on a campain at work to move us away from SCCS (or just the whole file reserving technique) and go to something like CVS where there are no file reservations.

I've been working on mantis and I am using CVS with that and it's very slick on reconciling the diffs in most cases. Thought this would be an option.

I also looked at Subversion, it was last year when I first saw it and thought it was rather buggy - but I have heard from a source that I trust that it has come a long way since last year and is fairly stable. I like the idea that it can track file/directory renaming or moving, and that it tracks revisions on a transaction basis instead of per file.

I also looked at ClearCase, but a friend at another company hates it and says it is only as reliable as your IT department is competant. He said he lost his whole project because someone deleted it from the repository - by accident - and could not restore it. Not to mention the cost of training for our IT department.

I'd like to go with a community supported package because (in my experience) our vendor supported packages (specifically the kernel we use in our hardware platform) sucked. The amount we payed for support and the actuall support we got were completely off. Everytime we called about an issue, they would ask us what BSP we were using and we would tell them that it's our own board design and we didn't buy something off the shelf, and they would say, well it works for us on this BSP - but that's another issue.

The other reason is that the bean counters here always look at our exempt employees (I think they call us exempt because we are exempt from being payed overtime) are a fixed cost, so why not make them work twice as long instead of paying for training or buying new software.

At the moment I have looked over RCS, CVS, Subversion, GnuArch and other payware packages - I was looking for some balanced input as to what the benefits of one over another are as well as a definitive matrix breakdown of what features are are included in what - especially comparred to SCCS.

Some of the slack I am getting from most of the engineers about moving away from SCCS is that we don't have the time - we are maintaining two main versions of the product as well as bug fixes on those two plus a third and then a subbranch of one of the main versions - I argue that we could maintain the code with better ease if these were brances and tags with CVS.

The other reason is that a few engineers don't trust automated tools to reconcile the diffs between the my changes, the origional, and a thrid person. I try to explain that it wont commit until you update, and that you have to reconcile the code where diff gets confused, but he's worried about where it doesn't think it's confused and actually does the murge wrong. I'm not sure how to convince them that it can reliably figure out diff merges.

All are software enginners are in one location, but occasionally they work from home, but use a checkpoint client to log in... so I don't think we need something to handle co-locations, but it wouldn't be a negative.

Any and all input would be greatly appreciated.

User Journal

Journal Journal: THX-1138 1

You look inactive, but you are the lucky one that got the UID 1138.


Journal Journal: Ofoto International 1

Ofoto has just launched 4 new European sites. Ofoto UK, Ofoto France, Ofoto Germany, and Ofoto EU. All four are really just the same site and backend with different languages and whether you want to deal with UK Pounds or Euros.

It has the same familiar interface as the US site with the exception that they cannot print calendars and other fancy stuff yet.

The most noticeable downfall of this site is that the backend database is not linked to the Ofoto US site. This means that you have to create an Ofoto EU account even if you already have an Ofoto US account. I thought this was kind-a lame, but I figured it had to do with the EU Privacy Protection Directive.

Oh, but it gets even lamer. Let's say you want to send pictures to friends in Europe and the states - if you order them from your Ofoto US account they will all be printed in the US and shipped to the respective locations in the states and Europe - if you order them from your EU Ofoto account they will all be printed in the EU and shipped to the respective locations in the states and Europe. This may not seem like an issue except that international shipping is pricy and slow. I ordered photos to be sent to Europe and it took over a month to get there and cost $25 - I also had photos printed for myself and it took about 4 days to ship it state-to-state and cost $3.50.

I wrote to support about how to print orders from Ofoto US in Ofoto EU printing centers, and they said I needed to open an EU account, upload the images, and print them from the EU account. Well that's great except I sent rolls of film to Ofoto, so I don't have digital images, and ofoto only gives you a web preview of the actual high-res picture. Since ofoto will not scan film, I would have to order a photo CD from them ($10 + shipping) in order to get the high-res images, wait four days for it to get to me and then upload it to the other Ofoto site. To me this is super lame. What is the point? There is nothing technically that would stop them from being able to print these images remotely.

To me it sounds like two completely different companies where the new European company just bought the rights to use the software that the US company developed and were too lazy to change the logo.

Slashdot Top Deals

CCI Power 6/40: one board, a megabyte of cache, and an attitude...