1 |
On Fri, Sep 23, 2011 at 10:33 AM, Mick <michaelkintzios@×××××.com> wrote: |
2 |
> On Friday 23 Sep 2011 13:58:22 Michael Mol wrote: |
3 |
>> /rant |
4 |
> |
5 |
> This is because Google uses geo-targeting to determine what results you may be |
6 |
> interested in (assuming your geo-location from your IP address), and |
7 |
> |
8 |
> because of the Google data centre that you are getting connected to (updates |
9 |
> of search results and their ranking is not instantaneous across the globe), |
10 |
> and |
11 |
> |
12 |
> because if you are logged in to Google (mail, et al) your search history will |
13 |
> bias the results you may receive, and |
14 |
> |
15 |
> because recent searches (whether logged in or not) are cached and will affect |
16 |
> what you're getting served. |
17 |
> |
18 |
> |
19 |
> People searching for pubs in the UK are bound to get different results to |
20 |
> people searching for pubs in Australia. |
21 |
> |
22 |
> Of course if you want to search for pubs in Australia while you are browsing |
23 |
> from the UK things are going to get tricky ... |
24 |
> |
25 |
> In such cases you want to add: |
26 |
> |
27 |
> The location in the search results: e.g. pubs + Australia (to filter the UK |
28 |
> Google results for Australian pubs), or go to www.google.au and then search |
29 |
> from there for pubs (Australian Google results for pubs). There could be |
30 |
> other more sophisticated ways but can't recall them off hand. |
31 |
> |
32 |
> Now, if someone sends you a non-lmgtfy.com link you can look at the Google TLD |
33 |
> to determine the country the results are from and search accordingly. |
34 |
|
35 |
All great info, if I'm looking for a physical location. Yeah, when I'm |
36 |
looking for the address of a music, I'll search for "the intersection |
37 |
in Grand Rapids, MI". GeoIP and other details take care of the rest, |
38 |
and it actually comes up with the place I saw JoCo and TMBG last |
39 |
weekend. |
40 |
|
41 |
>> I don't want to build a CD from scratch (and doing so looks like it |
42 |
>> would require setting up a fully "generic" box to build). I just want |
43 |
>> to add two files to an existing ISO. |
44 |
>> |
45 |
>> How would I extract boot_catalog and eltorito_boot_image from an existing |
46 |
>> ISO? |
47 |
> |
48 |
> Mount the ISO with loopback and then navigate into it as a normal fs: |
49 |
> |
50 |
> # mkdir /mnt/iso |
51 |
> # mount -o loop LiveCD.iso /mnt/iso |
52 |
> # ls -la /mnt/iso |
53 |
> # cp /mnt/iso/some_file |
54 |
|
55 |
Loopbacks are easy enough. I wasn't sure that the files in question |
56 |
were going to be on the filesystem, or were somewhere else in the ISO |
57 |
image. I was thinking analogously to boot sectors on floppy disks and |
58 |
hard disks; some data isn't directly visible on a filesystem. |
59 |
|
60 |
|
61 |
> -- |
62 |
> Regards, |
63 |
> Mick |
64 |
> |
65 |
|
66 |
|
67 |
|
68 |
-- |
69 |
:wq |