i'm not an FP troll, but i do believe this is my third this week. hmmm.
btw, i'd like to add:
the gators rule your sorry ass.
also, it made me happy to see someone actually flaming me about football. i didn't think you fucking dweebs had enough of a life to know what football was.
the real relative limit of ext2 is the lack of a journal, not performance speed.
as to the question of why the benchmarks look weird - duh, you have to create files larger than RAM, or everything gets buffered. ext2 wasn't actually writing to disk, it was writing to RAM.
back to benchmarking 101 for you.
Re:Kernel 2.4.13 is out..yay....
on
Linux 2.4.13
·
· Score: -1
we ARE the quality control process, dumbass.
Re:OT: These Fucking Trolls
on
Linux 2.4.13
·
· Score: -1
i'm just stunned that you were stupid enough to reply to that.
thanks!
Re:OT: These Fucking Trolls
on
Linux 2.4.13
·
· Score: -1
which ones?!
ules/ieee1394_syms.ver:105:41: warning: "__ver_hpsb_nodeid_get_entry" redefined
/exports/src/linux/include/linux/modules/ieee139 4_ core.ver:107:1: warning: this is the location of the previous definition
/exports/src/linux/include/linux/modules
And before you tell me to use patches, let me tell you that I've never gotten a single patch to work.
Yeah, it's their fault you're stupid, stupid. I will be you $413 that if you install a clean copy of 2.4.12 and type patch -p0 $tmppiggy.gz; \
echo "SECTIONS {.data : { input_len =.; LONG(input_data_end - input_data) input_data =.; *(.data) input_data_end =.; }}" > $tmppiggy.lnk; \
ld -m elf_i386 -r -o piggy.o -b binary $tmppiggy.gz -b elf32-i386 -T $tmppiggy.lnk; \
trollin for 2.4.13!
Re:Fucking fuck fuck
on
Linux 2.4.13
·
· Score: -1
cock + you. in fact, it was my cock. how do you feel about that, mr spork?
TROLLING FOR SONGFIGHT!!!
this is very relevant, also topical: www.songfight.org is releasing an SP4 for YOUR ASS. please surf/listen.
tks.
i will unleash mighty blights of troll power upon slashpoop in retribution for the war on irak.
intel is even this very minute embedding me into the Trollorama 4000 XP chip.
ph33r.
just title the article, "I am addict to pr0n and.."
that linux boxes don't crash, so HA is pretty much a waste of time and money.
home of the 420 day uptime,
for jorgelina!
n/t
two first posts in a row and 4 this week.
you bitches are bitches.
i'm not an FP troll, but i do believe this is my third this week. hmmm.
btw, i'd like to add:
the gators rule your sorry ass.
also, it made me happy to see someone actually flaming me about football. i didn't think you fucking dweebs had enough of a life to know what football was.
that no one, and i mean no one, gives a flying fuck about star office.
this.
UF ownz j0o.
24-10, uf.
and no one cared, would it still have been posted?
is everyone off jerking off while they read ku3498d3c31rbuttshine or something?
alex brown wants to eat your babies.
trolling for the mighty gators!
UG going for it on 4th and 13.
and they didn't make it. that makes them bitches like you slow-ass nonposter.
trolling for the mighty gators!
with crackers while i first post.
the real relative limit of ext2 is the lack of a journal, not performance speed.
as to the question of why the benchmarks look weird - duh, you have to create files larger than RAM, or everything gets buffered. ext2 wasn't actually writing to disk, it was writing to RAM.
back to benchmarking 101 for you.
we ARE the quality control process, dumbass.
i'm just stunned that you were stupid enough to reply to that.
thanks!
which ones?!
9 4_ core.ver:107:1: warning: this is the location of the previous definition
ules/ieee1394_syms.ver:105:41: warning: "__ver_hpsb_nodeid_get_entry" redefined
/exports/src/linux/include/linux/modules/ieee13
/exports/src/linux/include/linux/modules
!!
actually, i think it's high time windows XP implements full ext2 read/write support.
.note -R .comment -S /exports/src/linux/vmlinux $tmppiggy; \
.data : { input_len = .; LONG(input_data_end - input_data) input_data = .; *(.data) input_data_end = .; }}" > $tmppiggy.lnk; \
jcopy -O binary -R
gzip -f -9 $tmppiggy.gz; \
echo "SECTIONS {
ld -m elf_i386 -r -o piggy.o -b binary $tmppiggy.gz -b elf32-i386 -T $tmppiggy.lnk; \
first kernel!
And before you tell me to use patches, let me tell you that I've never gotten a single patch to work.
.data : { input_len = .; LONG(input_data_end - input_data) input_data = .; *(.data) input_data_end = .; }}" > $tmppiggy.lnk; \
Yeah, it's their fault you're stupid, stupid. I will be you $413 that if you install a clean copy of 2.4.12 and type patch -p0 $tmppiggy.gz; \
echo "SECTIONS {
ld -m elf_i386 -r -o piggy.o -b binary $tmppiggy.gz -b elf32-i386 -T $tmppiggy.lnk; \
trollin for 2.4.13!
cock + you. in fact, it was my cock. how do you feel about that, mr spork?
_KERNEL__ -I/exports/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -c -o ip_forward.o ip_forward.c
gcc -D__KERNEL__ -I/exports/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -c -o ip_options.o ip_options.c
gcc -D__KERNE
trollin for 2.4.13!
I'm lost...
no, you're a stupid fucking karma whore is what you are. go download the fucking thing and find out.
this is my cock.