dies ist ein simpler Test ausgeführt im Onlineform von kerneltrap, um zu sehen ob das Posting platziert wird oder ob der Spamfilter zuschlägt.
Fedora-ARM 11 is now available!
Details: built for ARMv5 EABI, soft-float, little endian.
Currently there are packages from three yum groups: Base, Core and Web-Server.
A yum-enabled pre-built root filesystem is available along with instructions for working with known platforms (currently Qemu, Sheevaplug)
The Fedora/ARM architecture wiki page has more information:
I came across this code, which was supposed to demonstrate a Prolog program that couldn't be written in Mercury. I couldn't help but rewrite that as:
rank(Xs,Rs) :- pairs_keys_values(Decorated,Xs,Rs), keysort(Decorated,Sorted), numerate(Sorted,1). numerate(,_). numerate([_-N|Rest],N) :- N1 is N + 1, numerate(Rest,N1).
...This computes the rank order of a list of elements. For example
[3,2,4,1], since 40 is the third largest element, etc.
Das Update musste geschaltet werden.Free Sex deswegen jetzt online
I've learnt that solaris 10 x86 doesn't have HME driver. This driver is used for example for older SUN made ethernet cards, and absence of driver for x86 makes them sparc-only hardware (on solaris 10 OS). Linux have driver for HME cards for ages (./linux-sources/drivers/net/sunhme.c comments dated back to 2000 year), both for x86 and sparc.
We started of a blog for Fedora-ARM contributors. You can find the blog over here:
Currently we are in the F-11 bootstrap phase. Once that is done, expect to see some technical problems and probable solutions for new packages that we attempt to bootstrap on ARM.
Colors tend to be a part of our lives and in some cases they can influence how we react and feel. There is also historical evidence of color psychology being used by some of the early cultures. While there are some mainstream psychologists who tend to believe that color does not play a significant part in our behavioral patterns, color psychologists claim otherwise.
Over on the Haskell Cafe mailing list, the topic of which of the following two definitions was better came up:
buildPartitions xs ns = zipWith take ns . init $ scanl (flip drop) xs ns
takeList :: [Int] -> [a] -> [[a]] takeList  _ =  takeList _  =  takeList (n : ns) xs = head : takeList ns tail where (head, tail) = splitAt n xs
...with various parties declaring the first example as "too smart", and others claiming that the second example is newbie level code. Well I'm much too lazy to try to reason out what those snippets might do at a glance. But the type signature was a pretty big hint as to what the intent was. So I fired up
After long time, this time on Arm
I got a crash like
BUG: scheduling while atomic: XXXXX/0x00000004/157, CPU#0
 (dump_stack+0x0/0x14) from  (__schedule+0x70/0x6f8)
 (__schedule+0x0/0x6f8) from  (schedule+0xbc/0xf4)
 (schedule+0x0/0xf4) from  (__down_read+0x100/0x118)
r4 = C046F600
After successfully finding an x86 laptop that is compatible with free software: ASUS EEE PC 1000HE (http://kerneltrap.org/node/17096), I got another order to find an x86 laptop that was bigger (preferably 14.1 inches laptop) and cheaper than ASUS EEE PC 1000HE. So, I went searching for one. After trying some tight-budget laptops that I dismissed because their wireless cards (e.g., Broadcom or newer Ralink cards) or graphics accelerators (e.g., new SiS chipset) were not compatible with free software, I landed on an A*Note 12.1 inches laptop whose vital devices were mostly free software compatible (fingerprint reader and built-in modem are nonvital for me).
Attending an international conference on telecommunication as a speaker, I got a bagpack as a souvenir. Everything was okay but its zippers. They were faulty as one of them shown in `01 - The Faulty Zipper.jpg'. I really should have checked its zippers when I received the bag. Anyway, with some patience I always succeeded in closing the zippers. But, they were really annoying just like when you use proprietary software. You just cannot modify them to make your life easier, and they are demanding more and more control to be taken away from you (e.g., Windows Defender and Genuine Advantage). After six months, a hacker came telling me how I should fix those faulty zippers.
I have black sport shoes with laces that I use daily. One day one of the holes through which the lace makes a loop was torn. So, I had to sew the tear. I bought a black thread used for jeans that should be strong enough and got a tiny needle from my sewing tools so that it could penetrate the shoe easily as well as making many tiny unspotted holes instead of few big ones that would destroy the shoe for sure.
After pondering for weeks on how to jump start programming knowledge I finally decided to become a memer here. Lets see how this goes. My plan is to enter as tester and slowly migrate into developer. The reason being, if you know how to break a system you can build a system that could not be broken easily. Still I have not yet contacted anybody in Kernel Trap for work.
"The most exciting (well, for me personally - my life is apparently too boring for words) was how we had some stack overflows that totally corrupted some basic thread data structures. That's exciting because we haven't had those in a long time.