You should consider including all printer driver updates in the vanilla catalog:
BrotherPrintDrivers2.6.dmg
CanonPrintDrivers2.6.dmg
EPSONPrinterDrivers.dmg (v2.7)
FujiXeroxPrinterDrivers2.1.dmg
GestetnerPrinterDrivers2.1.dmg
GutenprintPrinterDrivers2.0.dmg
HPPrinterDrivers2.6.dmg
InfotecPrinterDrivers2.1.dmg
LanierPrinterDrivers2.1.dmg
LexmarkPrinterDrivers.dmg (v2.5)
NRG7PrinterDrivers.dmg
RicohPrinterDrivers2.1.dmg
SamsungPrinterDrivers.dmg (v2.1)
SavinPrinterDrivers2.1.dmg
XeroxPrinterDrivers2.1.dmg
They don’t show up in Software Update unless you also have a printer of that model already installed.
Sorry, I cannot test those easily and they do not fit the ‘common case’ that OS_vanilla’s attempt to satisfy. If someone else wants to test them and stay aware of updates, we can make a separate ‘printersMasterList.catalog’, but I’d suspect a lot more folks are concerned with bloat and incorrect bundled drivers, so they’d rather use custom packages(e.g. deployed via Munki)/MCX/puppet to get their driver and printer in place.
Just my 2¢, please let me know if you feel I’m assessing the situation incorrectly. Thanks,
That comment was directed at yoshi for the sudden inclusion of the Canon drivers.
I’d recommend an all or nothing approach for catalogs that are designed for the general case.
I personally include them in my base image as we have most brands of printers across our campuses. Not to mention what notebook users have at home.
I don’t mean to sound harsh here, but…
See the difference between the iTunes sha1’s? This is why there’s a cooling off period. Apple deprecated the first iTunes the day after release, although both download links are still active in the cdn.
Also, FYI the iLife support update is not necessary for 10.6.8. Thanks to n8 and bw for posting, it helps me verify sha1’s and all that, I do appreciate it.
[QUOTE][u]Quote by: Allister[/u][p]I don’t mean to sound harsh here, but…
See the difference between the iTunes sha1’s? This is why there’s a cooling off period. Apple deprecated the first iTunes the day after release, although both download links are still active in the cdn.
Also, FYI the iLife support update is not necessary for 10.6.8. Thanks to n8 and bw for posting, it helps me verify sha1’s and all that, I do appreciate it.
Allister[/p][/QUOTE]
Not harsh at all. I didn’t know Apple did that with updates. Also, the iLife support update for some reason was included on the svn I had downloaded (still included as of this writing). That’s the only reason I had included it in my post. May want to take a look at that when you get a chance. Glad the updates helped you out.
Does it actually help you at all to post these updates we find? I’ve noticed the SVN doesn’t get updated as fast as I need it to, so I update my catalog files manually, so if it helps, i’ll continue to post what I find, but if it doesn’t help, I won’t spend the time to post it.
Yes, it most definitely helps(I compare sha1’s every time). And my cop-out for dragging my feet before committing to svn is… well it’s svn(can’t change that, not an owner on the repo) and
Please, please understand the cooling-off period is strongly suggested. 7 business days shouldn’t be asking too much, iTunes stopped coming out with different packages(for the same version number) on the 26th. I’ve been searching for the Macworld client management session Josh Wisenbaker gave, but could only find this presentation:
[url]http://www.seminars.apple.com/seminarsonline/clientmgmt/apple/index.html?s=203&locs=us_en[/url]
And I discussed this with the folks on the dev list here:
[url]http://groups.google.com/group/instadmg-dev/browse_thread/thread/7c9c7c05edb5fad2/ef5ff06827192e87?lnk=gst&q=cooling-off#ef5ff06827192e87[/url]
Comments are closed