didn’t know about this so i always used a little http proxy (tinyproxy) on my server, but this is not needed as i just learned;
i’ll probably buy a nokia n900 to (finally!) replace my nice htc touch hd which is broken because of windows mobile (how could htc do this, after all?!).
i was quite surprised about the price differences between digitec.ch and mobilezone and swisscom-shop;
- price with extending my contract another year at swisscom shop: about chf 750.-
- price with extending my contract another 2 years at mobilezone: about chf 730.-
- price WITHOUT CONTRACT at digitec: chf 690.-
strange eh?
following situation
- i’m living near olten (egerkingen)
- normally i work in aarau, so i have a subscription for egerkingen – aarau
- sometimes i have to visit clients around zurich
now you think: “easy, you’ll just have to buy a ticket from aarau to zurich”… but that isnt the case:
if the train stops in aarau (and its enough if it just stops, no need to change the train or something), you may buy a ticket aarau – zurich and won’t have any problem. but if the train goes directly from olten to zurich, without stop in aarau, you have to buy a ticket olten – zurich, or you’ll have to pay a monetary fine (CHF 80.-)…as if you would not have any ticket at all!
but…. what is the difference for sbb?
just wanted to create a little post about the possibility and my experiences with the upgrade;
- to allow the update, steps as described on this howtogeek post are needed.
- the upgrade must be run from your running windows 7 rc installation, not from the cd or usb-stick
- it will take around 30 minutes to complete
there were only a few problems after the upgrade;
- nvidia driver was still working, but no games had antialiasing nor anisotropic filtering – after upgrading the driver, this works fine again
- according to the upgrade compatibility check hamachi would have to be reinstalled, i just removed it
- tricky: daemon tools (sptd) has problems after the upgrade, however, this can be fixed like described on this blog
this was strange;
usually, when xrandr outputs the following:
-
Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 1680 x 1680
-
VGA-0 connected 1680×1050+0+0 (normal left inverted right x axis y axis) 465mm x 291mm
-
1680×1050 60.0*+
-
1600×1000 60.0
-
1280×1024 75.0 60.0
-
1440×900 59.9
-
1280×960 60.0
-
1152×864 75.0
-
1152×720 60.0
-
1024×768 75.0 60.0
-
832×624 74.6
-
800×600 75.0 60.3
-
640×480 75.0 59.9
-
720×400 70.1
-
DVI-0 connected (normal left inverted right x axis y axis)
-
1360×768 59.8
-
1152×864 60.0
-
1024×768 60.0
-
800×600 60.3
-
640×480 59.9
-
LVDS connected 1680×1050+0+0 (normal left inverted right x axis y axis) 331mm x 207mm
-
1680×1050 60.1*+ 50.1
-
1400×1050 60.0
-
1280×1024 59.9
-
1440×900 59.9
-
1280×960 59.9
-
1280×854 59.9
-
1280×800 59.8
-
1280×720 59.9
-
1152×768 59.8
-
1024×768 59.9
-
800×600 59.9
-
640×480 59.4
-
S-video disconnected (normal left inverted right x axis y axis)
(don’t ask me where dvi-0 comes from…)
one would think a simple xrandr --output VGA-0 --auto would activate the second monitor. however, this doesn’t change anything. instead, i have to use the following:
xrandr --output VGA-0 --auto --same-as LVDS
after closing the notebook lid, i get a picture on my monitor… but i may not turn off lvds or dvi-0, or the monitor (on vga) will turn off…
just installed the new ubuntu beta ond my notebook which i use for work. i need vmware on it for the xp vm that i have to use at work.
as always with new kernels and x-servers, vmware doesn’t just work even when using the newest version (6.5.3). in order to get it to work more or less, i needed to do the following things:
- start the installer with a special option and killing all tries to compile the modules, as described in here: blog post by Sebastian Mogilowski
- add the
line export VMWARE_USE_SHIPPED_GTK=forceto the file/etc/vmware/bootstrap, as described in this vmware thread (go to page 3)
i think it’s really time to change to virtualbox which is completely open, has better integration and works more reliable…
little problem, smart solution;
i’m backing up my citrix xenserver vm’s using the command
-
xe template-export
i write the backup directly to a cifs-mounted share on the network. however, i need to compress those images, ideally before i send them over the network. the problem is that the template-export command doesn’t support writing to stdout, which would allow me to pipe it through gzip.
fortunately, there’s a way which allows me to pipe it through gzip nevertheless. i’m using a fifo;
1st step: create a fifo
-
mkfifo gzipfifo
2nd: start gzip and let it wait for data from the fifo and write to another file (in my case on the cifs-share)
-
gzip -c > /mnt/backup/PMIRZ_Firewall_Demo.xva.gz < gzipfifo &
3rd: write your backup to the fifo, instead of the mounted volume
NHAAAA, just noticed that the template-export command doesn’t want to write to files that already exist… but the above works for other things as well
just had a little problem to fix;
when i opened an encrypted or signed message in thunderbird, the error “the enigmime service is not available” was shown. however, enigmail and thunderbird were installed and even setting the path to the gpg binary manually doesn’t fix the problem.
however, it’s not too difficult to fix;
-
apt-get remove –purge enigmail
this uninstalls enigmail, including global settings. it’s not enough however, you’ll have to open thunderbird and remove it using the extras – add-on’s dialogue. afterwards, you may reinstall enigmail and it works as always.
well, not much to say, just read it.
seems like there is a quite bad problem with HP Universal Print Driver 4.7 (and older) when used on a Citrix Server. According to some forum threads, the issues were resolved in version 4.7.2, however, this version is not available for public download, one needs to contact HP support to get it.
as I did this, and I want to help other admins, here is a link: Download HP Universal Print Driver 4.7.2 (PCL5, PCL6 and PS)
Note: I did not test the driver yet, but it was obtained from HP directly
Update: just changing the driver on the printserver did not help so far….
Update 2: seems like we could fix the problem by using the newly released specific driver for the hp color laserjet 5550 instead of the universal print driver
hi everyone!
i’m still there, and of course, from time to time, i need a new pc =)
this time i replaced my core2duo e6600 (2.4ghz) on a msi p965 neo-f with 2gb memory on it with my new:
- core i7 920 (2.66ghz)
- gigabyte ga-ex58-ud5 (with heatpipes, onboard power button, debug leds and everything…)
- 3x 2gb kingston ddr3 hyper-x
- and a zalman cnps-9900 led cooler
the machine now runs nicely, however (more…)
from my military service! after 21 weeks it’s finally done!
it would be too much to write about it, so i thought i’d just post my pictures, you can find them here: Pictures taken during my military service
happy new year
Jan 4th, 2009 by iSO in uncategorized
well, 4 days late, but I still wanted to wish everyone a good start into the new year.
i wasn’t writing for some time, this is because i’m doing military service. i’m placed in Bülach, my Unit is called the “Uem/FU RS 62-1 Kp.1 Zug 3″. before xmas, i finished the 8th week, so there are still 13 left….
http://secunia.com/blog/37/ …. i thought it was a terrible situation, however i still was shocked.
would be interesting how the situation looks with various linux distributions which have a central update mechanism for software.
i was experiencing a new problem (well, it isn’t really a problem, it’s just annoying) when i opened an ssh connection to my server at OVH and i wasn’t active for let’s say about 10 minutes. when i wanted to enter a new command, the session always closed with the error:
Read from remote host xxx: Connection reset by peer
Connection to xxx closed.
sadly i couldn’t find out what exactly made this behave like this (i believe it has to do with m0n0wall, but the connection timeout there is set to 3600 seconds, so i don’t know why it happens), as it was never a problem until then. but i found an easy workaround that keeps the connection alive:
put this line into you ~/.ssh/config
-
ServerAliveInterval 120
this sends some data through the ssh connection every 120 seconds and avoided the connection from being closed.
