Remove i386 Packages from Multiarch Aptitude

Geschrieben von silverSl!DE am Mittwoch, 6. November 2013 in Linux


apt-get remove `dpkg --get-selections | grep i386 | awk '{print $1}'`

doublecheck carefully the packages, wich will be purged, then deactivate architecture. dpkg architectures are stored in /var/lib/dpkg/arch.

/var/lib/dpkg# cat arch

# dpkg --remove-architecture i386dpkg

 now arch should be like this:

/var/lib/dpkg# cat arch

0 Kommentare Mehr...
Abstimmungszeitraum abgelaufen.
Derzeitige Beurteilung: 3.11 von 5, 9 Stimme(n) 1635 Klicks

Migrate contacts from Exchange to Zarafa

Geschrieben von silverSl!DE am Dienstag, 20. März 2012 in Linux

Long story... :

I Managed to store my private contacts of my mobile phone in my corporate Exchange-account. That was a pretty simple and efficient way to keep my contacts up to date and sync to multiple devices like smartphones (Windows Mobile, Android, Windows Phone), my workstation and of course my laptop including the WebAccess. To be independent of my corporate Exchange Server, I decided toset up "my OWN Exchange! With Blackjack! AND ... !" ;-) As I wrote earlier: i have an Atom D525 file server running Debian stable for more then one year on it. So, i read a little bit and decided to set up the Community version of Zarafa, since only two users will use it for z-push (contacts, calander, instant mailing). But there is a small problem: I have houndrets of privat contacts in my Exchange account, I collected over the last years...

"Migrate contacts from Exchange to Zarafa" vollständig lesen

0 Kommentare Mehr...
Abstimmungszeitraum abgelaufen.
Derzeitige Beurteilung: 3.13 von 5, 70 Stimme(n) 5324 Klicks

Cannot open '/var/run/rpcbind/rpcbind.xdr'

Geschrieben von silverSl!DE am Freitag, 9. Dezember 2011 in Linux

Da scheinbar viele das Problem haben, hier Jeffs Patch aus den Debian Bugreport logs:
=================================================================== RCS file: /etc/init.d/RCS/rpcbind,v retrieving revision 1.1 diff -b -d -p -t -u -r1.1 /etc/init.d/rpcbind --- /etc/init.d/rpcbind 2011-11-10 10:33:54-05 1.1 +++ /etc/init.d/rpcbind 2011-11-10 10:49:03-05 @@ -20,7 +20,6 @@ test -f /sbin/rpcbind || exit 0 . /lib/lsb/init-functions -OPTIONS="-w" STATEDIR=/var/run/rpcbind if [ -f /etc/default/rpcbind ] then @@ -34,6 +33,12 @@ start () { if [ ! -d $STATEDIR ] ; then mkdir $STATEDIR + else + if [ -e $STATEDIR/portmap.xdr ] || \ + [ -e $STATEDIR/rpcbind.xdr ] + then + set -- -w ${1+"$@"} + fi fi if [ ! -O $STATEDIR ] ; then log_begin_msg "$STATEDIR not owned by root" ===================================================================
0 Kommentare Mehr...
Abstimmungszeitraum abgelaufen.
Derzeitige Beurteilung: 2.62 von 5, 74 Stimme(n) 2494 Klicks

That's why I LOVE Open Source!

Geschrieben von silverSl!DE am Donnerstag, 3. November 2011 in IT

Just found a link to Linus Torvalds explaination about C and C++. BEST! EVER! :-D
From: Linus Torvalds> Subject: Re: [RFC] Convert builin-mailinfo.c to use The Better String Library. Newsgroups: gmane.comp.version-control.git Date: 2007-09-06 17:50:28 GMT (4 years, 8 weeks, 1 day, 17 hours and 45 minutes ago) On Wed, 5 Sep 2007, Dmitry Kakurin wrote: > > When I first looked at Git source code two things struck me as odd: > 1. Pure C as opposed to C++. No idea why. Please don't talk about portability, > it's BS. YOU are full of bullshit. C++ is a horrible language. It's made more horrible by the fact that a lot of substandard programmers use it, to the point where it's much much easier to generate total and utter crap with it. Quite frankly, even if the choice of C were to do nothing but keep the C++ programmers out, that in itself would be a huge reason to use C. In other words: the choice of C is the only sane choice. I know Miles Bader jokingly said "to piss you off", but it's actually true. I've come to the conclusion that any programmer that would prefer the project to be in C++ over C is likely a programmer that I really would prefer to piss off, so that he doesn't come and screw up any project I'm involved with. C++ leads to really really bad design choices. You invariably start using the "nice" library features of the language like STL and Boost and other total and utter crap, that may "help" you program, but causes: - infinite amounts of pain when they don't work (and anybody who tells me that STL and especially Boost are stable and portable is just so full of BS that it's not even funny) - inefficient abstracted programming models where two years down the road you notice that some abstraction wasn't very efficient, but now all your code depends on all the nice object models around it, and you cannot fix it without rewriting your app. In other words, the only way to do good, efficient, and system-level and portable C++ ends up to limit yourself to all the things that are basically available in C. And limiting your project to C means that people don't screw that up, and also means that you get a lot of programmers that do actually understand low-level issues and don't screw things up with any idiotic "object model" crap. So I'm sorry, but for something like git, where efficiency was a primary objective, the "advantages" of C++ is just a huge mistake. The fact that we also piss off people who cannot see that is just a big additional advantage. If you want a VCS that is written in C++, go play with Monotone. Really. They use a "real database". They use "nice object-oriented libraries". They use "nice C++ abstractions". And quite frankly, as a result of all these design decisions that sound so appealing to some CS people, the end result is a horrible and unmaintainable mess. But I'm sure you'd like it more than git. Linus
0 Kommentare Mehr...
Abstimmungszeitraum abgelaufen.
Derzeitige Beurteilung: 3.08 von 5, 75 Stimme(n) 1964 Klicks

Windows Versionen

Geschrieben von silverSl!DE am Mittwoch, 28. September 2011 in Windows

0 Kommentare Mehr...
Abstimmungszeitraum abgelaufen.
Derzeitige Beurteilung: 1.62 von 5, 8 Stimme(n) 1458 Klicks

Top 100 Things you Don't Want the Sysadmin to Say

Geschrieben von silverSl!DE am Mittwoch, 4. Mai 2011 in IT

100. Uh-oh..... 99. Shit!! 98. What the hell!? 97. Go get your backup tape. (You do have a backup tape?) 96. That's SOOOOO bizarre. 95. Wow!! Look at this..... 94. Hey!! The suns don't do this. 93. Terminated??! 92. What software license? 91. Well, it's doing something..... 90. Wow....that seemed fast..... 89. I got a better job at Lockheed... 88. Management says... 87. Sorry, the new equipment didn't get budgetted. 86. What do you mean that wasn't a copy? 85. It didn't do that a minute ago... 84. Where's the GUI on this thing? 83. Damn, and I just bought that pop... 82. Where's the DIR command? 81. The drive ate the tape but that's OK, I brought my screwdriver. 80. I cleaned up the root partition and now there's LOTS of free space. 79. What's this "any" key I'm supposed to press? 78. Do you smell something? 77. What's that grinding sound? 76. I have never seen it do that before... 75. I think it should not be doing that... 74. I remember the last time I saw it do that... 73. You might as well all go home early today ... 72. My leave starts tomorrow. 71. Ooops. 70. Hmm, maybe if I do this... 69. ``Why is my "rm *.o" taking so long?'' 68. Hmmm, curious... 67. Well, my files were backed up. 66. What do you mean you needed that directory? 65. What do you mean /home was on that disk? I umounted it! 64. Do you really need your home directory to do any work? 63. Oracle will be down until 8pm, but you can come back in and finish your work when it comes up tonight. 62. I didn't think anybody would be doing any work at 2am, so I killed your job. 61. Yes, I chowned all the files to belong to pvcs. Is that a problem to you? 60. We're standardizing on AIX. 59. Wonder what this command does? 58. What did you say your (l)user name was...? ;-) 57. You did what to the floppy??? 56. Sorry, we deleted that package last week... 55. NO! Not that button! 54. Uh huh......"nu -k $USER".. no problem....sure thing... 53. Sorry, we deleted that package last week... 52. NO! Not that button! 51. Uh huh......"nu -k $USER".. no problem....sure thing... 50. [looks at workstation] "Say, what version of Dos is this running?" 49. Oops! (said in a quiet, almost surprised voice) 48. YEEEHA!!! What a CRASH!!! 47. What do you mean that could take down the whole network? 46. What's this switch for anyways...? 45. Tell me again what that '-r' option to rm does 44. Say, What does "Superblock Error" mean, anyhow? 43. If I knew it wasn't going to work, I would have tested it sooner. 42. Was that YOUR directory? 41. System coming down in 0 min.... 40. The backup procedure works fine, but the restore is tricky! 39. Hey Fred, did you save that posting about restoring filesystems with vi and a toothpick? More importantly, did you print it out? 38. OH, SH*T! (as they scrabble at the keyboard for ^c). 37. The sprinkler system isn't supposed to leak is it? 36. It is only a minor upgrade, the system should be back up in a few hours. ( This is said on a monday afternoon.) 35. I think we can plug just one more thing in to this outlet strip with out triping the breaker. 34. What is all this I here about static charges destroying computers? 33. I found this rabbit program that is supposed to test system performance and I have it running now. 32. Ummm... Didn't you say you turned it off? 31. The network's down, but we're working on it. Come back after diner. (Usually said at 2200 the night before thesis deadline... ) 30. Ooops. Save your work, everyone. FAST! 29. Boy, it's a lot easier when you know what you're doing. 28. I hate it when that happens. 27. And what does it mean 'rm: .o: No such file or directory'? 26. Why did it say '/bin/rm: not found'? 25. Nobody was using that file /vmunix, were they? 24. You can do this patch with the system up... 23. What happens to a Hard Disk when you drop it? 22. The only copy of Norton Utilities was on THAT disk??? 21. Well, I've got a backup, but the only copy of the restore program was on THAT disk.... 20. What do mean by "fired"? 19. hey, what does mkfs do? 18. where did you say those backup tapes were kept? 17. ...and if we just swap these two disc controllers like this... 16. don't do that, it'll crash the sys........ SHIT 15. what's this hash prompt on my terminal mean? 14. dd if=/dev/null of=/vmunix 13. find /usr2 -name nethack -exec rm -f {}; 12. now it's funny you should ask that, because I don't know either 11. Any more trouble from you and your account gets moved to the 750 10. Ooohh, lovely, it runs SVR4 9. SMIT makes it all so much easier...... 8. Can you get VMS for this Sparc thingy? 5. I don't care what he says, I'm NOT having it on my network 4. We don't support that. We won't support that. 3. ...and after I patched the microcode... 2. You've got TECO. What more do you want? 1. We prefer not to change the root password, it's an nice easy one 0. Just add yourself to the password file and make a directory... -1. This won't affect what you're doing. -2. `We are shutting xxx down from 8.30 to 10.30 on Thursday to install a new tape drive.' The machine was up at about 2pm sans-tape drive -3. `I just have to install these three patches. It should not take more than a few minutes.' The machine was working again about 3 hours later... -4. Umm, did anyone have anything important in /usr? -5. We had to format some tracks, and we seem to have hit an inode track. Half the files are still there though... -6. Ooops, I should really have change directory before doing that chmod -R bin.bin . -7. I just made an extra 2 meg of space in /, I stripped /vmunix. Oh, so that's why ps doesn't work. -8. Ignore the errors. It complains too much. -9. I got these instructions off the net. I'm going to follow them exactly. Let's see if they work. -10. Heard at my workplace when I found emacs wouldn't run : "Oh I took that thing off, it was huge and nobody uses it. It's a stupid editor anyway." --Spoken by an MS-DOS programmer -11. I don't know if this is ethical, but... found @
0 Kommentare Mehr...
Abstimmungszeitraum abgelaufen.
Derzeitige Beurteilung: 2.38 von 5, 8 Stimme(n) 1849 Klicks

NFS Common / NFS Kernel Server startet nicht

Geschrieben von silverSl!DE am Donnerstag, 7. April 2011 in Linux

Heute hatte ich beim Booten (und später im System Probleme mit dem NFS-Client):
Starting NFS common utilities: statd failed!
System: Debian Wheezy (Testing) x86 nach ein wenig googlen, stellte ich schnell fest: Ein häufig vorkommender Bug, der sich über rpc.statd usw erstreckt. nach ein wenig mehr googlen, stellte ich fest: Das zentrale problem ist PORTMAP. nach noch mehr googlen, stellte ich fest: es gibt seit jahren probleme mit NFS in kombination mit Portmap. kurz: spart euch den debugging kram und wechselt auf RPCBIND bis die gefixte Portmapversion in den Ripos ist.
apt-get install rpcbind
Glaubt mir. Die Zeit die auf diesen ganzen Debugging-Sh!t draufgeht, ist es NICHT wert, es sei denn euch ist gerade langweilig, oder ihr könnt einfach nicht anders (wie ich ;-) ) In DEM Fall: Starting NFS common utilities failed! um dem Fehler auf die Schliche zu kommen, mit rootrechten ausführen:
bash -x /etc/init.d/nfs-common start
besser noch mit "bash -ex". dann wird direkt bei dem ersten Fehler abgebrochen. das Ergebnis sieht meist so aus:
statd+ start-stop-daemon --start --oknodo --quiet --exec /sbin/rpc.statd -- + RET=1
Dann kann man noch kontrollieren, ob die Verzeichnisse/Dateien unterhalb von
vorhanden sind. Wenn man DANN festestellt, hier ist AUCH alles in ordnung, stößt man früher oder später (eher später als früher -_- ) auf dein dazugehörigen BUGREPORT: Starting NFS common utilities failed Spätestens DA wird klar: "Hat ja mal wieder SUUPER funktioniert!" Und ich WETTE der nächste Befehl ist:
apt-get install rpcbind
0 Kommentare Mehr...
Abstimmungszeitraum abgelaufen.
Derzeitige Beurteilung: 1.33 von 5, 9 Stimme(n) 2146 Klicks

ATOM Server: HDD Performance

Geschrieben von silverSl!DE am Samstag, 26. Februar 2011 in Linux

Ein weiterer Test um den Datendurchsatz zu testen. Zunächst mein Laptop (XPS M1330| T7250 2x2.0GHz | 2GB DDR2 | Seagate 500GB @ 5400rpm)
# hdparm -tT /dev/sda /dev/sda: Timing cached reads: 2226 MB in 2.00 seconds = 1113.90 MB/sec Timing buffered disk reads: 232 MB in 3.00 seconds = 77.31 MB/sec
Nun mein Server (Gigabyte GA-D525TUD | Atom D525 | 4GB DDR3 | 1x 250GB IDE @ 7200rpm als System u Home alles außer "/boot" verschlüsselt | 4x 1T Hitachi Deskstar 7K1000.C @ 7200rpm im RAID5 Verbund, vollverschlüsselt) Verschlüsselte Systemplatte:
root@homer:/mnt# hdparm -tT /dev/sde /dev/sde: Timing cached reads: 1854 MB in 2.00 seconds = 926.64 MB/sec Timing buffered disk reads: 176 MB in 3.01 seconds = 58.39 MB/sec
Vollverschlüsselter RAID5-Verbund:
root@homer:/mnt# hdparm -tT /dev/md0 /dev/md0: Timing cached reads: 1858 MB in 2.00 seconds = 928.59 MB/sec Timing buffered disk reads: 970 MB in 3.00 seconds = 322.93 MB/sec
Sobald ich Zeit hab versuche ich auch die dd-Schreibraten nachzureichen. Aber ich denke die Werte können sich sehen lassen! :-) PS: Die Temperaturwerte:
root@homer:/mnt# hddtemp /dev/sd* /dev/sda: Hitachi HDS721010CLA332: 37°C /dev/sdb: Hitachi HDS721010CLA332: 38°C /dev/sdc: Hitachi HDS721010CLA332: 40°C /dev/sdd: Hitachi HDS721010CLA332: 39°C /dev/sde: HDS722525VLAT80: 35°C /dev/sde1: HDS722525VLAT80: 35°C /dev/sde2: HDS722525VLAT80: 35°C /dev/sde5: HDS722525VLAT80: 35°C
0 Kommentare Mehr...
Abstimmungszeitraum abgelaufen.
Derzeitige Beurteilung: 2 von 5, 7 Stimme(n) 1368 Klicks

ATOM Server

Geschrieben von silverSl!DE am Freitag, 25. Februar 2011 in Linux

Nur mal so an alle die gegen den Intel Atom als solchen wettern: Hier baue ich gerade ein Raid System auf (Rebuild). Man beachte die Temperatur und die Auslastung der Cores/Threads! ;-) Oben links: Rebuild des RAIDs
# mdadm --details /dev/mda0
Oben rechts: Temperaturüberwachung
$ watch -n 1 sensors
unten: Systemmonitor
$ htop
0 Kommentare Mehr...
Abstimmungszeitraum abgelaufen.
Derzeitige Beurteilung: 1.86 von 5, 7 Stimme(n) 1620 Klicks

Mir egal. Ich hab nichts zu verbergen.

Geschrieben von silverSl!DE am Sonntag, 20. Februar 2011 in IT

Wie oft musste ich mir diese Bequemlichkeitsfloskel schon anhören, wenn ich jemanden auf die Themen Vorratsdatenspeicherung, Abhörung durch den Staat, Patriot Act, etc. versuchte zu sensibilisieren! Aus Bequemlichkeit und Faulheit aber auch Unwissen schluckt die breite Masse die schwachsinnigsten Gesetze. Wenn man sie darauf hinweist, was sich hinter den ganzen Regelungen verbirgt und wie sie WIRKLICH eingesetzt werden hört man immer wieder:
"Mir egal. Ich hab nichts zu verbergen."
Problem des Ganzen: Diejenigen die diese Gesetze umsetzen entweder sich mit der Technik auskennen und die Regelungen missbrauchen können, einfach weil sie es KÖNNEN. ODER mit der Technik nicht immer sooo viel am Hut haben und aus diesem Grund die Möglichkeiten missbrauchen können, weil sie es einfach NICHT anders können. In beiden Fällen besteht die Gefahr zum Missbrauch. Als glanzvolles Beweisstück haben wir nun keinen Geringeren als das Departement of Homeland Security (DHS). :-D Diese US-Behörde(!!!) hat SO fürstlich ins Klo gegriffen, dass die da ihre Finger nicht so schnell herausbekommen! "heise online" Berichtet
Bei der Jagd auf Server und Domains, über die Kinderpornographie verteilt wird, haben US-Behörden versehentlich 84.000 Domains für Tage vom Netz genommen.
Die Besucher dieser Seiten sahen nur noch ein Beschlagnahmungs-Banner des DHS mit dem Hinweis, dass es illegal sei, Kinderpornographie zu erwerben, zu besitzen oder zu verbreiten.
Besonders empört die Betroffenen, dass es für die Sperrung keine Anhörung oder Prüfung gab, ...
jaja Rechtsstaat, Gerechtigkeit, usw. Das Lustige dabei:
Den Fahndern war aber anscheinend nicht aufgefallen, dass es sich dabei um eine extrem beliebte Domain des DNS-Anbieter FreeDNS ( handelt, die rund 84.000 Webseiten – die nicht unter Verdacht standen – versorgt.
:-D :-D :-D Wie GEIL ist DAS denn!? Der absolute OBERHAMMER:
Insbesondere weist er darauf hin, dass die Reputation vieler Unschuldiger gelitten habe, weil tagelang ihr Name mit Kinderpornographie in Verbindung stand.
Ich wette, die Besitzer der 84.000 Domains hatten auch "nichts zu verbergen" -_- ...
Das DHS wollte gegenüber den US-Medien zu dem Vorfall keine Stellung nehmen.
Home of the Brave! :-D LÄCHERLICH Auf wehrlose mit Atombomben werfen! DAS können sie! Aber wehe es versucht sie jemand zur Verantwortung zu ziehen!
0 Kommentare Mehr...
Abstimmungszeitraum abgelaufen.
Derzeitige Beurteilung: 1.38 von 5, 8 Stimme(n) 1071 Klicks

Seite 1 von 3, insgesamt 29 Einträge


Nach Einträgen suchen in

Das Gesuchte nicht gefunden? Gib einen Kommentar in einem Eintrag ab oder nimm per E-Mail Kontakt auf!