Computing desk | ||
---|---|---|
< January 1 | << Dec | January | Feb >> | January 3 > |
Welcome to the Wikipedia Computing Reference Desk Archives |
---|
The page you are currently viewing is an archive page. While you can leave answers for any questions shown below, please ask new questions on one of the current reference desk pages. |
I'm interested in the sorts of research design used in IT for PhD students. You have to contribute something new, but say your research involves coding something - how do you evaluate it to show it is new? Do you show that no one has ever been able to write such a program before that does such and such? Or do you show that it does the same thing as another program, but using less disk space, or else what? I'm enrolled in a PhD in IT, but having trouble refining the topic, as I know how to program alright, but I haven't had much formal training in the discipline as it works in academia. Thanks in advance, IBE ( talk) 10:47, 2 January 2012 (UTC)
Thanks - these replies help a great deal. I know to ask my supervisors, but they are on holidays, and I also can't sit there chatting about how the discipline works in general in academia - and I always get good replies here. In fact, I come to Wikipedia when I'm at my wits' end, and it at least restores my sanity, so thankyou. Note that the stuff about my personal situation wasn't the exact question, just background to help focus the answers - the questions were as listed, and about the general situation, so you've given a lot of help. Any more info is much appreciated. IBE ( talk) 08:45, 3 January 2012 (UTC)
Hi, I was trying to consolidate several backup generations using rsync's hardlink ("--link-dest=") feature, to save some space.
What I have:
/oldbackupdir /oldbackupdir/backup0 /oldbackupdir/backup1
What I am trying to create:
/newbackupdir /newbackupdir/backup0 /newbackupdir/backup1
With the difference that files that are identical between backup0 and backup1 will be hard-linked.
Step 1:
rsync -aPv /oldbackupdir/backup0/ /newbackupdir/backup0/
Step 2, try #1:
rsync -aPv --link-dest=/newbackupdir/backup0/ /oldbackupdir/backup1/ /newbackupdir/backup1/
And this is where everything breaks: I'm not getting any hardlinks, even though I know some files are identical (same md5sum).
Step 2, try #2:
rm -rf /newbackupdir/backup1/ # Clean everything up for a new attempt rsync -aPv --link-dest=../backup0/ /oldbackupdir/backup1/ /newbackupdir/backup1/
I read somewhere that one should use relative path names for link-dest, but it doesn't help, either.
Step 2, try #3+4: Repeat the above two steps with rsync -aPvc --link-dest=, as the file creation/modification times might be different between the backups, but the md5sums are the same for identical files between backup generations, and -c should switch from time/date-dependent to md5sum-dependent detection.
Same result though, no hardlinks. :-(
Step 2, try #5:
rm -rf /newbackupdir/backup1/ # Clean everything up for a new attempt rsync -aPv --link-dest=../backup0/ /oldbackupdir/backup0/ /newbackupdir/backup1/
Intentionally copying the wrong (backup0 instead of backup1) source to the backup1 directory does create hardlinks.
What the heck am I doing wrong? --
188.105.112.97 (
talk) 15:48, 2 January 2012 (UTC)
The red, however, isn't red enough, and counter-intuitively for me resulting in a slightly purplish look where it should be white or gray, especially gray. Store's run out of the model, but I can still return it Great price though, and a rare matte. What should I do? 66.108.223.179 ( talk) 20:39, 2 January 2012 (UTC)
Computing desk | ||
---|---|---|
< January 1 | << Dec | January | Feb >> | January 3 > |
Welcome to the Wikipedia Computing Reference Desk Archives |
---|
The page you are currently viewing is an archive page. While you can leave answers for any questions shown below, please ask new questions on one of the current reference desk pages. |
I'm interested in the sorts of research design used in IT for PhD students. You have to contribute something new, but say your research involves coding something - how do you evaluate it to show it is new? Do you show that no one has ever been able to write such a program before that does such and such? Or do you show that it does the same thing as another program, but using less disk space, or else what? I'm enrolled in a PhD in IT, but having trouble refining the topic, as I know how to program alright, but I haven't had much formal training in the discipline as it works in academia. Thanks in advance, IBE ( talk) 10:47, 2 January 2012 (UTC)
Thanks - these replies help a great deal. I know to ask my supervisors, but they are on holidays, and I also can't sit there chatting about how the discipline works in general in academia - and I always get good replies here. In fact, I come to Wikipedia when I'm at my wits' end, and it at least restores my sanity, so thankyou. Note that the stuff about my personal situation wasn't the exact question, just background to help focus the answers - the questions were as listed, and about the general situation, so you've given a lot of help. Any more info is much appreciated. IBE ( talk) 08:45, 3 January 2012 (UTC)
Hi, I was trying to consolidate several backup generations using rsync's hardlink ("--link-dest=") feature, to save some space.
What I have:
/oldbackupdir /oldbackupdir/backup0 /oldbackupdir/backup1
What I am trying to create:
/newbackupdir /newbackupdir/backup0 /newbackupdir/backup1
With the difference that files that are identical between backup0 and backup1 will be hard-linked.
Step 1:
rsync -aPv /oldbackupdir/backup0/ /newbackupdir/backup0/
Step 2, try #1:
rsync -aPv --link-dest=/newbackupdir/backup0/ /oldbackupdir/backup1/ /newbackupdir/backup1/
And this is where everything breaks: I'm not getting any hardlinks, even though I know some files are identical (same md5sum).
Step 2, try #2:
rm -rf /newbackupdir/backup1/ # Clean everything up for a new attempt rsync -aPv --link-dest=../backup0/ /oldbackupdir/backup1/ /newbackupdir/backup1/
I read somewhere that one should use relative path names for link-dest, but it doesn't help, either.
Step 2, try #3+4: Repeat the above two steps with rsync -aPvc --link-dest=, as the file creation/modification times might be different between the backups, but the md5sums are the same for identical files between backup generations, and -c should switch from time/date-dependent to md5sum-dependent detection.
Same result though, no hardlinks. :-(
Step 2, try #5:
rm -rf /newbackupdir/backup1/ # Clean everything up for a new attempt rsync -aPv --link-dest=../backup0/ /oldbackupdir/backup0/ /newbackupdir/backup1/
Intentionally copying the wrong (backup0 instead of backup1) source to the backup1 directory does create hardlinks.
What the heck am I doing wrong? --
188.105.112.97 (
talk) 15:48, 2 January 2012 (UTC)
The red, however, isn't red enough, and counter-intuitively for me resulting in a slightly purplish look where it should be white or gray, especially gray. Store's run out of the model, but I can still return it Great price though, and a rare matte. What should I do? 66.108.223.179 ( talk) 20:39, 2 January 2012 (UTC)