code logs -> 2011 -> Fri, 25 Feb 2011< code.20110224.log - code.20110226.log >
--- Log opened Fri Feb 25 00:00:35 2011
00:00
<@ToxicFrog>
As far as I can tell, here is the easy way:
00:00
<@ToxicFrog>
- boot windows liveCD
00:01
<@ToxicFrog>
- copy old /home to new /home using robocopy. Don't forget to exclude juction points or it will create an infinitely-sized copy with broken permissions that can pretty much only be deleted from linux.
00:01
<@ToxicFrog>
- use dir to create a list of all junction points in the old /home
00:01
<@ToxicFrog>
- recreate these in the new /home. Note that you're still in the windows livecd here - no bash to help you.
00:02
<@ToxicFrog>
- remove old /home
00:02
<@ToxicFrog>
- junction new /home to old /home
00:02
<@ToxicFrog>
- reboot
00:02
<@ToxicFrog>
- shoot self
00:03 Phox [Tertius_Vulpe@Nightstar-bb8dd90c.abhsia.telus.net] has left #code ["Gonna be a lot of nick changes"]
00:25
<@McMartin>
Windows is not a Standard POSIX system, and if you try to make it act like one, by, for instance, using junction points at all, you are asking for endless pain and suffering.
00:25
<@McMartin>
You shouldn't be using your user profile at all except when forced by applications in this model, really.
00:25 Vornicus-Latens is now known as Vornicus
00:26
<@McMartin>
(Also, you don't have bash, but you do have Windows PowerShell~)
00:29
<@ToxicFrog>
(not in the recovery console you don't)
00:29
<@McMartin>
(oh, right~)
00:29
<@McMartin>
Also, um
00:29 Derakon[AFK] is now known as Derakon
00:29
<@ToxicFrog>
Re: junction points: that would carry more weight if windows didn't use them all over the fucking place, which is part of the problem here
00:29
<@McMartin>
Why are you mounting stuff inside /home
00:29
<@McMartin>
Er, junction points or reparse points?
00:30
<@McMartin>
Reparse points map to ln -s, junction points map to "mount"
00:30
<@McMartin>
I also assume your "/home" here is C:\Users
00:30
<@McMartin>
I'm not sure if that's what you mean either.
00:31
<@ToxicFrog>
Re: not using the user profile: the issue here is that all well-behaved programs store their stuff in there, and that's also where My Documents etc is, and that's stuff I don't want on the system drive for both safety and space reasons.
00:31
<@ToxicFrog>
Yes, by /home I mean C:/Users
00:31
<@ToxicFrog>
And by junction points I mean junction points
00:32
<@ToxicFrog>
Also, at least according to dir and mklink, the terms are "junction point" and "symlink" and "reparse point" covers both.
00:32
<@McMartin>
I am genuinely curious why you have junction points in C:\Users because I've used stock explorer copy on this since XPSP0.
00:32
<@ToxicFrog>
Because Vista/7 creates a shitload of junction points in there automatically for compatibility with older, poorly-written programs
00:32
<@ToxicFrog>
Like junctioning $HOME/Application Data/ to $HOME/AppData/Roaming
00:32
<@McMartin>
Um
00:32
<@McMartin>
I literally have never seen this
00:33
<@McMartin>
Is this something your vendor's shovelware is adding or something?
00:33
<@McMartin>
Neither Astatine nor my work machine has these visible.
00:33
<@McMartin>
They do not show up on directory queries even if I make direct calls to ntdll.dll to find them.
00:33
<@ToxicFrog>
...no, this is a standard feature of win7
00:34
<@ToxicFrog>
Do a "dir /s /al" on $HOME sometime
00:34
<@McMartin>
Interesting.
00:34
<@McMartin>
I see them, but only then.
00:35
<@McMartin>
If I get any closer to NTFS than that I see no evidence of them.
00:35
<@ToxicFrog>
Huh.
00:35
<@ToxicFrog>
...:wtc:
00:35
<@McMartin>
Or, for that matter, any further away: "start $HOME" with "show me *everything*" on doesn't show them.
00:36
<@ToxicFrog>
So the windows downloader finally finished downloading my free MSDNAA copy of Win7 Pro
00:36
<@ToxicFrog>
Download size: 16GB
00:36
<@ToxicFrog>
Unpacked size: 3.1GB
00:37
<@McMartin>
That said
00:37
<@McMartin>
I routinely do stock Explorer copies of $HOME to backup disks, and they behave appropriately as well.
00:37
< Tamber>
ToxicFrog, ...negative compression? o_O
00:37
<@McMartin>
What are you doing that's the equivalent of cp -r with transparently-follow-symlinks on?
00:38
<@ToxicFrog>
McMartin: "behave appropriately" in what sense?
00:38
<@ToxicFrog>
And, um
00:38
<@ToxicFrog>
I'm not
00:38
<@Vornicus>
THe download includes such things as asian fonts.
00:38
<@ToxicFrog>
Because some of these junctions are circular
00:38
<@McMartin>
That's my point
00:38
<@McMartin>
You have "taking care to avoid X"
00:38
<@McMartin>
I'm not even sure how to ask for X.
00:38
<@ToxicFrog>
Aah
00:38
<@McMartin>
Because the "obvious" ways to do things avoid X as a matter of course
00:39
<@McMartin>
(Alternately, Win7 is compatibility-shimming cmd.exe here and not explorer.exe)
00:39
<@McMartin>
(And thus making, say, NtQueryInformationFile return phantom links)
00:39
<@ToxicFrog>
"robocopy" (the replacement for the now-deprecated xcopy) will default to following symlinks and junction points and thus break horribly.
00:39
<@ToxicFrog>
The /XJ option to it causes it to omit junction points entirely.
00:40
<@ToxicFrog>
Explorer, AFAICT, also follows.
00:40
<@ToxicFrog>
I cannot find any way to copy JPs/symlinks as themselves.
00:41
<@McMartin>
"Ditto" is what you'd need for that.
00:41
<@McMartin>
That's OS X's, because cp follows.
00:42
<@ToxicFrog>
(that said, I have found an easier way, looks like - "go back in time, edit the system configuration to change the location new profiles will be created in before creating your profile, then create your profile")
00:42
<@McMartin>
Ah, does 7 let you do that for the whole profile?
00:42
<@McMartin>
XP, if memory served, only let you set My Documents's location that way.
00:43
<@McMartin>
This still doesn't solve your other problem, which is that I suspect you also want C:\Program Files and C:\Program Files (x86) to be junctioned.
00:43
<@ToxicFrog>
Not officially.
00:44
<@ToxicFrog>
There's a setting somewhere (registry?) that basically defines where C:\Users\ is
00:44
<@McMartin>
Yeah, I was going to say "This is Windows. If there's a well-defined registry key that controls it, it's official."
00:44
<@ToxicFrog>
But it only works reliably for profiles created after it was modified, and thus is best set during installation or, failing that, before you create any real user accounts.
00:44
<@ToxicFrog>
And no, I don't care about Program Files.
00:44
<@McMartin>
Well, yes.
00:46
<@McMartin>
Unless you're doing something *seriously* why-are-you-using-Windows-here with your system you should not have any ACLs specific to a user on the system, and so creating a new primary user, copying data over via Explorer, and nuking the old profile ought to suffice
00:47
<@ToxicFrog>
Well, I'm reinstalling windows anyways
00:47
<@ToxicFrog>
So that'll pretty much happen as a natural side effect of the process
00:47
<@McMartin>
fair
00:47
<@ToxicFrog>
But I find it sorely vexing that there's basically no way to safely relocate a user profile directory after it's created
00:48
<@McMartin>
Profiles also aren't inherited, but I know of no system where they are.
00:48
<@McMartin>
It does seem to be the default expectation though.
00:48
<@ToxicFrog>
Inherited?
00:49
<@McMartin>
"If you change stuff in the default profile that the end user hasn't changed, they do not get these changes applied retroactively"
00:50
<@McMartin>
Which is to say, a user's profile does not have the entry "whatever the default profile currently is" for settings they haven't messed with, or, indeed, available as an option at all.
00:50
<@ToxicFrog>
Aah.
00:51
<@ToxicFrog>
Hrm. I don't suppose you know offhand how (if?) one configures these settings pre-install.
00:51
<@ToxicFrog>
There was a tool for doing that to XP install images (nlite) but I can't find a win7 equivalent.
00:52
<@McMartin>
I've never had to do it myself, no. My interaction with this on XP involved obliterating those changes once we switched to providing what you want via other means.
00:52
<@McMartin>
(Strong and transparent segregation of user, app, and system data is one of our major selling points~)
00:53
<@McMartin>
(But it does via providing something that looks more like a union mount.)
00:53
<@ToxicFrog>
(that's basically exactly what I'm going for here, but since I use this machine for gaming I don't think virtualization is a viable approach~)
00:53
<@McMartin>
(I'm the project lead for this thing. Union mounts on Windows are Not A Toy.)
00:54
<@McMartin>
There's no intrinsic reason this stuff couldn't run on a host, but it shouldn't because the problem space for Windows is too complex to be "safe" outside of a virtual environment.
00:56
<@ToxicFrog>
Yeah, I think I'm just going to have to install normally, use a dummy profile, change the default profile location, create my real profile, and try to prevent things from installing for All Users.
00:56
<@McMartin>
(By which I mean "I spend my half my time on this hip-deep in the kind of compatibility-with-poorly-written-applications stuff that's driving you up the wall, and so once you got what you were going for you'd have a new set of very similar and equally aggravating problems~)
00:56
<@McMartin>
Er
00:56
<@McMartin>
You do want it to install for all users for most apps, because that's dictating where uninstallation info &c goes
00:56
<@McMartin>
If /usr is on your main system disk, most apps should be "all users"
00:57
<@ToxicFrog>
Um
00:57
<@McMartin>
Well, so
00:57
<@McMartin>
Also, it's not called that anymore in 7
00:57
<@ToxicFrog>
The problem with "install for all users" is that then it dumps a bunch of its bits in C:/Users/Public
00:57
<@McMartin>
... OK, we may be talking different things.
00:57
<@ToxicFrog>
Which then go away forever when C: gets erased
00:57
<@McMartin>
I'm thinking of the stuff that now goes in C:\ProgramData
00:58
<@McMartin>
And if C: gets erased, C:\ProgramData\Foo should go because C:\Program Files\Foo is going too
00:58
<@McMartin>
Stuff like your personal settings ought to still be in D:\Users\TF\AppData\Roaming\Foo
00:59
<@McMartin>
(And I think you're still going to get screwed by the registry stuff unless you can also get HKEY_CURRENT_USER's hive to be on D: as well; this is beyond my ken)
00:59
<@McMartin>
(That might be handled by the profile location switch, though)
00:59
<@ToxicFrog>
(I think that that gets stored in $HOME automatically, regardless of where $HOME is)
01:00
<@ToxicFrog>
And, yeah, what I mean by the "all users" thing is
01:00
<@ToxicFrog>
Say I install a game, it gives me the option of "all users" or "just me".
01:00
<@ToxicFrog>
If I choose the former, it puts its start menu entries, desktop entries, etc in C:/Users/Public rather than in $HOME.
01:00
<@ToxicFrog>
I still see them, but they go away when C: does.
01:00
<@McMartin>
Aaah.
01:01
<@McMartin>
Yeah, I'm used to "Just me" meaning "I don't install into Program Files at all"
01:01
<@ToxicFrog>
Note that the game doesn't go away, because it's installed on F:.
01:01
<@McMartin>
"But instead into $HOME"
01:01
<@ToxicFrog>
Aah.
01:01
<@McMartin>
We are in fact talking past each other here.
01:01
<@ToxicFrog>
Yeah, IME, in typical installer usage, "all users vs just me" is "should I put my desktop shortcuts etc in your personal profile or in the shared-by-everyone profile"
01:02
<@McMartin>
Right.
01:02
<@McMartin>
I think you might still have wacky interactions with Add/Remove Programs if you nuked C:, but if you put it on F in the first place you didn't intend to uninstall it anyhow.
01:02
<@ToxicFrog>
Yeah.
01:03
<@ToxicFrog>
Not everything will survive an OS reinstall, but a lot of stuff will if the user settings and user registry are intact.
01:03
<@ToxicFrog>
And IME, the win7 add/remove is a lot more robust than the winXP one, and if it gets confused will just outright ask "so, is this actually installed or not"
01:05
<@ToxicFrog>
My underlying goals here are pretty simple:
01:05
<@ToxicFrog>
- when I destroy windows, I don't want my save files, configurations, and custom shortcuts to go along with it
01:06
<@ToxicFrog>
- I don't want multiple gigabytes of saves and whatnot stored on C:, especially considering how space-hungry win7 is
01:06 Kindamoody is now known as Kindamoody[zZz]
01:07
<@McMartin>
(re: add/remove) Yeah, it is (since Vista, really), but I'd predict the reverse problem
01:07
<@McMartin>
That is, the stuff installed on F would no longer appear in Add/Remove Programs post-wipe
01:07
<@ToxicFrog>
Yeah, but as you noted, I'm not planning to uninstall it anyways.
01:07
<@ToxicFrog>
And in general I take the attitude that if it's not in add/remove, I can safely delete it by hand, an so far this has worked, so.
01:08 * McMartin nods
01:08
<@McMartin>
Anything for which this isn't true Should Not Be Installed To F
01:09
<@McMartin>
Alternately, cannot be
01:09
<@McMartin>
Since it's likely in that case to have a system extension component like a device driver or a software service
01:09 * ToxicFrog nods
01:09
<@ToxicFrog>
As a general rule, utilities get installed to C:, and anything "systemy" (mostly Cygwin, Daemon-Tools, and the virus scanner du jour) always does.
01:11
<@ToxicFrog>
...huh. It occurs to me that at this point my Steam install has outlived four operating systems.
01:13 Alek [omegaboot@Nightstar-96006922.il.comcast.net] has joined #code
01:14
<@McMartin>
Heh
01:14
<@McMartin>
Wait.
01:14
<@McMartin>
When did you *start*?
01:15
< Alek>
it FINALLY finished installing.
01:16
< Alek>
it took about an hour to download the complete update pack, almost a gig... via WU, just had to fix WU's temp files first.
01:16
< Alek>
then about an hour to let it run the install.
01:16
<@ToxicFrog>
Late 2003, and at that point I still had a win98 partition.
01:16
< Alek>
it's waiting to reboot now.
01:16
<@ToxicFrog>
Since then, the same /Games/Steam directory has gone through 2k, XP, and 7.
01:16
< Alek>
what'd I miss of this convo?
01:18
<@ToxicFrog>
Lots of discussion concerning where windows keeps user profiles, pretty much.
01:19
<@ToxicFrog>
And the discovery that the 16GB Windows 7 Professional download contains a single 3GB ISO and nothing else.
01:21
< Alek>
O_o
01:21 * Alek twitches.
01:22
<@ToxicFrog>
Yeah.
01:22
<@ToxicFrog>
It sat there downloading for a few hours, pulling down an even 16GB of data and stuffing it all onto the disk.
01:22
<@ToxicFrog>
Then it "unpacked" for a while.
01:23
<@ToxicFrog>
And when it was done?
01:23
<@ToxicFrog>
ben@leela ~/Desktop/Windows 7 Professional (x64) - DVD (English) $ ls -ltrh
01:23
<@ToxicFrog>
total 3.1G
01:23
<@ToxicFrog>
-rwx------ 1 ben ben 3.1G Aug 6 2009 en_windows_7_professional_x64_dvd_X15-65805.iso
01:27 cpux [chatzilla@Nightstar-c978de34.dyn.optonline.net] has quit [Ping timeout: 121 seconds]
01:30 cpux [chatzilla@Nightstar-c978de34.dyn.optonline.net] has joined #code
01:33 * Alek coughs.
01:33 * Alek suspects DRM was included in the package, and/or rootkits.
01:33
<@ToxicFrog>
Er?
01:33
<@ToxicFrog>
To clarify, this download was from MS themselves
01:34
< Tamber>
12GB of rootkits/DRM? Wow, they really can't optimise! ;)
01:34
< Alek>
like I said.
01:34
<@McMartin>
Also, this is an archive.
01:34
< Alek>
to prevent you from making pirate copies.
01:34
< Alek>
etc.
01:34
<@McMartin>
Archives have documented formats and would show up in the list
01:34
< Alek>
mmeh.
01:34
< Alek>
welp, time to reboot.
01:34 Alek [omegaboot@Nightstar-96006922.il.comcast.net] has quit [[NS] Quit: ]
01:34
< Tamber>
McMartin, shhhhhh, you're ruining the tinfoil hat moment.
01:35
< Tamber>
:)
01:35
<@McMartin>
I am honestly curious what zip -l thinks of the initial download.
01:35
<@McMartin>
Tamber: I resent being forced to defend MS~
01:35
<@McMartin>
(With a handful of exceptions where being VMS-derived instead of Unix derived genuinely has made my life easier)
01:35
<@McMartin>
(Which is, uh, maybe two places)
01:35
<@ToxicFrog>
McMartin: no idea, because (a) it's some wacky custom format documented nowhere on earth and (b) the downloader deleted it as soon as it was unpacked.
01:36
<@ToxicFrog>
My best guess is that despite me requesting "Windows 7, Professional, 64-bit, English", it actually downloads all of the different versions of windows I'm allowed to have, unpacks the one I asked for, and deletes the rest.
01:37
<@McMartin>
Mmm. Plausible.
01:37
<@ToxicFrog>
Or possibly it contains all of the language packs and parts for them and generates the iso on the fly.
01:37
<@McMartin>
(Our corp MSDN stuff comes in bundles of physical discs)
01:37
<@Vornicus>
Pi described that as the case once.
01:38
<@Vornicus>
They master one disc with everything and then assemble the appropriate version by figuring out what the license key says it wants.
01:38
<@ToxicFrog>
(I can order physical discs if I want, but I'd rather have the disc image)
01:39
<@McMartin>
(Aha)
01:39
<@McMartin>
Time to go deal with terrible rush-hour traffic.
01:40
<@ToxicFrog>
Good luck.
01:40
<@McMartin>
New trenchcoat, for less than factory outlet prices \o/
01:41
<@McMartin>
It turns out shopping slightly more upscale than I usually do is cheaper if you have a competent incident commander and pick the right times.
01:42
<@McMartin>
(For the record, the two places Windows beats alternatives I've worked with are: Named Pipes are marginally easier to use than domain sockets and kick the shit out of FIFOs; and their filter-based driver model has permitted a lot of unusually clean architecture when I'm at that level)
01:43
<@McMartin>
(The latter was basically dictated by being full-lockdown closed-source, but the resulting gain in encapsulation and modularity was admirable)
01:44 Alek [omegaboot@Nightstar-96006922.il.comcast.net] has joined #code
01:44
<@ToxicFrog>
(my experience with windows named pipes has been that they are vastly inferior to FIFOs - at least, for the same purpose - by virtue of the fact that you can't treat them like normal files)
01:44
<@ToxicFrog>
(they seem to be more like named network sockets than anything else)
01:46
<@McMartin>
(Yes; they don't replace FIFOs directly; they replace domain sockets)
01:47
<@McMartin>
(But you can give them strings for names instead of shorts in a global namespace -_-)
01:47 Phox [Tertius_Vulpe@Nightstar-bb8dd90c.abhsia.telus.net] has joined #code
01:47
<@McMartin>
(There are ways to name them in the FS too, but dealing with that has tended to cause me more headaches than otherwise)
01:48
<@McMartin>
(They can be made to provide marginally better guarantees about atomicity of perceived packet receipt)
01:48
<@McMartin>
(If you have something where a simple FIFO *is* the best choice, yeah, it's going to beat it out)
01:48
<@ToxicFrog>
(Yeah, my complaint is not so much "they suck" as "they aren't actually useful as a replacement for FIFOs, despite the similarity in names")
01:48
<@McMartin>
(Every time I've considered FIFOs I've always needed full duplex ;_;)
02:09 Stalker [Z@26ECB6.A4B64C.298B52.D80DA0] has quit [Ping timeout: 121 seconds]
02:13 * Alek arghs and stabs WU.
02:13
< Alek>
while it worked on this PC, it's still not working on the other one.
02:14
< Alek>
I'm just gonna download it direct.
02:14
< Alek>
but now there's a question.
02:15
< Alek>
besides the DVD, the 64 bit, and the x86 versions, the latter 2 are subdivided into CHK and FRE .msi's and an .exe, each.
02:16
< Alek>
the .exe is bigger than the CHK and FRE .msi's put together, for each of the bitversions. so I'd rather just download the .msi I need.
02:16
< Alek>
the problem is... what does CHK and FRE mean?
02:17
<@McMartin>
Debug and Release build, respectively.
02:17
<@McMartin>
"checked" and "free"
02:17
< Alek>
hrm.
02:17
< Alek>
so basically, the newest and the most stable?
02:18
< Alek>
and why, then, is the .exe about 3x the size of an .msi?
02:18
<@McMartin>
No idea what their exes are.
02:18
< Alek>
ok, it's actually 3x for the 64bit. x86 is less than 2x.
02:19
<@McMartin>
You want FRE, though.
02:19
<@McMartin>
CHK will be slower and larger
02:19
<@ToxicFrog>
Alek: not "newest and most stable"; "with and without debugging information"
02:19
<@McMartin>
And is only of use if you're using a kernel debugger.
02:19
< Alek>
er.
02:19
<@ToxicFrog>
The former is useful only if you are a developer.
02:19
< Alek>
actually. something interesting.
02:19
< Alek>
the FRE version is actually the bigger one, for both.
02:19
<@ToxicFrog>
Also, my guess would be that the exes include the MSI installer installer
03:00 Stalker [Z@3A600C.A966FF.5BF32D.8E7ABA] has joined #code
03:16
< Alek>
....
03:16
< Alek>
the .msi's were actually "debugging symbols"... both versions.
03:25 Reiv [orthianz@3CF3A5.E1CD01.36D449.95F5A5] has quit [Ping timeout: 121 seconds]
03:29 Reiv [orthianz@3CF3A5.E1CD01.36D449.95F5A5] has joined #code
03:33 gnolam [lenin@Nightstar-38637aa0.priv.bahnhof.se] has quit [[NS] Quit: Z?]
03:35 Alek [omegaboot@Nightstar-96006922.il.comcast.net] has quit [Connection reset by peer]
03:37 Alek [omegaboot@Nightstar-96006922.il.comcast.net] has joined #code
03:46 Stalker [Z@3A600C.A966FF.5BF32D.8E7ABA] has quit [Ping timeout: 121 seconds]
04:06
<@ToxicFrog>
Ok.
04:06
<@ToxicFrog>
sda1 purged of data.
04:06
<@ToxicFrog>
Let's do this.
05:00 * ToxicFrog takes ownership of everything in F:/Games as he should have done last time he installed windows.
05:06 cpux is now known as shade_of_cpux
05:43 celticminstrel [celticminstre@Nightstar-f8b608eb.cable.rogers.com] has quit [[NS] Quit: And lo! The computer falls into a deep sleep, to awake again some other day!]
06:03
<@McMartin>
Ah yes.
06:03
<@McMartin>
Security isn't optional anymore~
06:30 AnnoDomini [annodomini@Nightstar-946c50b0.adsl.tpnet.pl] has joined #code
06:30 mode/#code [+o AnnoDomini] by Reiver
06:42 Derakon is now known as Derakon[AFK]
06:52 Kindamoody[zZz] is now known as Kindamoody
08:19 SmithKurosaki [smith@Nightstar-7820a96a.dsl.teksavvy.com] has joined #code
08:59 Syloqs-AFH [Syloq@NetworkAdministrator.Nightstar.Net] has quit [Connection closed]
09:07 Syloqs_AFH [Syloq@NetworkAdministrator.Nightstar.Net] has joined #code
09:08 Syloqs_AFH is now known as Syloqs-AFH
09:26 Kindamoody is now known as Kindamoody|out
10:26 Rhamphoryncus [rhamph@C06FE3.F5723C.BE3FEB.9D4666] has joined #code
10:37 AbuDhabi [annodomini@Nightstar-0c263ea5.adsl.tpnet.pl] has joined #code
10:38 AnnoDomini [annodomini@Nightstar-946c50b0.adsl.tpnet.pl] has quit [Ping timeout: 121 seconds]
11:01 gnolam [lenin@Nightstar-38637aa0.priv.bahnhof.se] has joined #code
12:09 Vornicus is now known as Vornicus-Latens
12:18 Stalker [Z@3A600C.A966FF.5BF32D.8E7ABA] has joined #code
12:44 Attilla [Some.Dude@Nightstar-92c9199f.cable.virginmedia.com] has joined #code
12:44 mode/#code [+o Attilla] by Reiver
12:54 Tarinaky [Tarinaky@Nightstar-f349ca6d.plus.com] has joined #code
15:13 You're now known as TheWatcher[afk]
15:14 Attilla [Some.Dude@Nightstar-92c9199f.cable.virginmedia.com] has quit [Ping timeout: 121 seconds]
15:14 Attilla [Some.Dude@Nightstar-92c9199f.cable.virginmedia.com] has joined #code
15:14 mode/#code [+o Attilla] by Reiver
17:02 Derakon[AFK] is now known as Derakon
17:20 simon_ [simon@Nightstar-a12ff716.gjk.dk] has quit [Ping timeout: 121 seconds]
17:20 simon_ [simon@Nightstar-a12ff716.gjk.dk] has joined #code
17:31 TarinakyKai [Tarinaky@Nightstar-f349ca6d.plus.com] has joined #code
17:32 Tarinaky [Tarinaky@Nightstar-f349ca6d.plus.com] has quit [Operation timed out]
17:47 Kindamoody|out is now known as Kindamoody
18:00 TarinakyKai is now known as Caeldir
18:00 AbuDhabi is now known as Ed
18:06
<@ToxicFrog>
McMartin: the underlying issue is that it assigns ownership by uuid and uuids do not match across installs of windows even if the usernames do. Last time I got around this by wielding chmod haphazardly as problems arose. This time I'm doing it properly.
19:39 * Alek stabs 7.
19:39
< Alek>
how do I change ownership, again?
19:44 RichardBarrell_d [droid@Nightstar-3b2c2db2.bethere.co.uk] has joined #code
19:55
< Namegduf>
WorM
19:55
< Namegduf>
WorM5RedControl8
19:56
< Stalker>
?
20:05
<@ToxicFrog>
Alek: right-click the file or directory, security, advanced, ownership, change ownership
20:07
<@ToxicFrog>
upgrade to win7: complete
20:07
<@ToxicFrog>
Looks like everything came across fine, too
20:11
< Alek>
also works with whole drive, looks like.
20:12
< gnolam>
There's also takeown, which is the Windows equivalent of chown.
20:13
< Alek>
ok, 6 drives owned.
20:35
< Namegduf>
..crap.
20:35
< Namegduf>
That was a password.
20:35
< Namegduf>
I need to change it now.
20:35
< Namegduf>
Stupid thing.
20:35
< Namegduf>
(I made it from the combination of a bunch of names, heh)
20:36
< Namegduf>
Not a password for anything remotely accessible, at least.
20:37
< Namegduf>
Screen died and I thought it was stuck locked.
20:53
< gnolam>
That's ok. For us, it came out as ****************.
20:57
< Tamber>
-chuckles-
21:09 Reiv [orthianz@3CF3A5.E1CD01.36D449.95F5A5] has quit [Ping timeout: 121 seconds]
21:14 Stalker [Z@3A600C.A966FF.5BF32D.8E7ABA] has quit [Ping timeout: 121 seconds]
21:15 Reiv [orthianz@3CF3A5.E1CD01.36D449.95F5A5] has joined #code
21:36 RichardBarrell_d [droid@Nightstar-3b2c2db2.bethere.co.uk] has quit [Ping timeout: 121 seconds]
22:06 Stalker [Z@2C3C9C.B2A300.F245DE.859909] has joined #code
23:12 Vornicus-Latens is now known as Vornicus
23:16 Caeldir is now known as Tarinaky
23:42 shade_of_cpux is now known as cpux
23:49
<@McMartin>
Mmm. Things that are good feelings:
23:49
<@McMartin>
Spending a while researching libraries for how to best approach a problem, and discovering eventually that the whole thing is a simple one-liner.
--- Log closed Sat Feb 26 00:00:36 2011
code logs -> 2011 -> Fri, 25 Feb 2011< code.20110224.log - code.20110226.log >