On Thursday 21 June 2007 12:34, demerphq wrote:
> On 6/21/07, Kern Sibbald <[EMAIL PROTECTED]> wrote:
> > Not so good things:
> > 1. It is pretty big pig -- it squats in 500MB of memory, uses about 60GB 
of
> >     disk, and it took over an hour to boot up the first time, and quite a 
long
> >     time the second time; after defragging the disk, it boots in a 
reasonable
> >     time.
> 
> If you want to see a very interesting analysis of some of the serious
> issues with Vista and their new anti-drm measures and what their costs
> are in terms of system stability and their attitude towards their user
> base see
> 
> http://www.cs.auckland.ac.nz/~pgut001/pubs/vista_cost.html

Yes, thanks.  I read it some time ago, but I'm sure that some of the sys 
admins on this list will be interested if they haven't read it yet.

> 
> > 2. Although the new directory structure has more reasonable directory 
names
> >    (shorter and no spaces), they have provided "junctions" to the old 
names
> >    for compatibility. Unfortunately few third party programs such
> >    as Bacula know about junctions, so they get confused, and typically
> >    this manifests itself as references to files/directories that do not 
seem
> >    to exist ...
> 
> > 6. Due to junctions not being really downward compatible, the Bacula menu
> >     links to the conf files complain that the file does not exist.  By the
> >     way, junctions have been around for a while, but were apparently never
> >     used in a default install.  However, on Vista, there are a lot of
> >     junctions in the default install.
> 
> [snip]
> > 3. Junctions are another story, and I have no idea how much work that is
> >    going to be.
> 
> As you say junctions are not new with Vista, they have existed for
> ages on NTFS filesystems.  For instance I use junctions occasionally
> when i support friends who have been foolish enough to install
> development software (especially open source related stuff like
> cygwin) into a path with spaces in it.
> 
> If you arent already aware of it you probably should have a poke
> around the sysinternals site (now owned by MS) for advanced windows
> diagnostics utilities. While im not too happy about MS buying out the
> sysinternals guys (although im happy for the guys who got rich out of
> it :-) one modest bonus from it was that they are now releasing their
> full utility set as a single zip, which makes life much easier. I
> swear by filemon and procexp personally, especially the latter.

Yes, I noticed in looking at the Microsoft site that they had bought out the 
sysinternals guys.  That is fine with me if Microsoft lets them work on what 
they want, and pays them to do it too.

> 
> Anyway, returning to on topic you should have a look at the junction 
utility:
> 
> http://www.microsoft.com/technet/sysinternals/FileAndDisk/Junction.mspx

Yes, I had mentally flagged that for download, but junctions haven't yet hit 
the top of my priority list, though for Win32 users on Vista, they will be 
*very* important.

> 
> Afaik Perl knows how to deal with Junctions, so ill have a poke around
> to see whats up, certainly Bacula should know about them and deal with
> them gracefully.

Gee, I would *much* appreciate that.

Regards,

Kern

> 
> Yves
> -- 
> perl -Mre=debug -e "/just|another|perl|hacker/"
> 

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bacula-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-devel

Reply via email to