| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8
Comments:
<0> my server is on intel celeron debian sarge 32 bit what kernel i need ?
<0> kernel-image-2.6.8-11-amd64-generic - Linux kernel image for version 2.6.8 on generic x86_64 systems
<0> kernel-image-2.6.8-11-amd64-k8 - Linux kernel image for version 2.6.8 on AMD64 systems
<0> kernel-image-2.6.8-11-amd64-k8-smp - Linux kernel image for version 2.6.8 on AMD64 SMP systems
<1> **** **** ****
<0> kernel-image-2.6.8-11-em64t-p4 - Linux kernel image for version 2.6.8 on Intel EM64T systems
<0> kernel-image-2.6.8-11-em64t-p4-smp - Linux kernel image for version 2.6.8 on Intel EM64T SMP systems
<0> ?
<1> painfully remembers me why the **** i named this kernel death_and_pain
<1> debianpow: don't paste in here
<0> ok
<2> you need i386, since you have an intel celeron
<1> just get an x86 kernel and drop the looking into amd64 bit
<0> on mjy server i have this 5
<0> not good ?
<2> damn M$ Geniune Advantage :(
<2> where is the cl*** action lawsuit over their bull****?
<0> i found that one kernel-image-2.6.8-2-386 - Linux kernel image for version 2.6.8 on 386.
<0> its ok ?
<2> kill switches, deactivation, breach of contract...
<0> i found that one kernel-image-2.6.8-2-386 - Linux kernel image for version 2.6.8 on 386. can i teake that one ?
<2> Jon Stewart should have stabbed Bill Gates in the *eyeball* with a *pencil* the other night...
<0> **** off
<3> debianpow: kernel-image-2.6.8-2-386 is what ya want to install yes
<2> awol: don't waste your keystrokes, he seems unable to read...
<3> ph0bia: that could be true for all/most newbies....
<4> woohoo! up and running with Etch
<5> PDP-7 going down
<5> p
<5> ...
<2> wow, old skewl
<5> PDP-7 coming up
<5> p
<5> ...
<5> Welcome to AT&T System V Unix
<2> haha
<5> login:
<2> joshua
<5> p***word:
<2> pencil
<5> joshua@alamo-pdp#
<2> list games
<5> Chess
<5> Backgammon
<5> Blackjack
<5> Rain
<5> Animals
<5> Global Thermonuclear War
<2> I'll take Global Thermonuclear Warfare for 5,000 Alex!
<5> panic: segmentation fault in kernel
<5> ring ring ring
<5> error
<6> eh
<7> was that an emulator
<7> because i love old unicies
<7> ph0bia: was that an emu?
<8> hello
<9> hi
<9> I'm trying to use update-rc.d to remove a link from rc2.d only, using update-rc.d inetutils-inetd stop 20 2 .
<9> it reports startup links already exist
<9> and the link in rc2.d still exists
<9> is it not possible to remove a link from a single runlevel?
<9> guess not
<10> i get a delay of like 10 seconds when switching from X to console in etch, anyone else had this problem?
<2> there is a slight delay on my computer, maybe 2 or 3, but I figure it is the monitor switching video modes
<10> my X fully freezes up for an unusual amount of time before switching
<10> i am going to go back to sarge if i dont get this sorted out
<2> guessing it is something to do with the video driver, what card are you using?
<10> geforce 6200
<2> hrm should be perfectly supported
<2> using XOrd?
<2> Xorg, even
<10> used same drivers and same hardware on sarge and slackware, with no problem
<10> ph0bia, yes
<2> on your sarge install, what kernel were you using?
<2> 2.6.8?
<10> 2.6.19.1
<2> ahh so you rolled your own, and presumably did so again on etch
<10> no im actually using the stock etch kernel atm
<2> ahh 2.6.17.something iirc
<10> guess ill try building my own and see if that improves something
<2> I'd suggest rolling up a 2.6.19.2
<2> its gotta be something in there, one would think
<10> could be, ive got about 40 unncessary modules loaded :P
<2> could have something to do with it :)
<10> 2nd question, you any good at setting up a linux box to route internet to another pc?
<2> have done it yah
<2> I usually have to refer to the minihowto as I don't do it that often
<10> maybe i should have a look at that.. however ive done this before on slack with no problem
<10> im not sure what im doing wrong here
<10> let me fire up the other computer
<2> first time I ever did it was with slack
<10> alright
<10> this computer im on now is connected to the internet via a router
<10> i have another computer connected to the 2nd NIC of this computer
<10> the other computer can ping anything on the LAN including the router, but nothing outside of that
<10> something seems to be restricting it and i cant work out what
<2> you have all the iptables forwarding stuff loaded/enabled in the kernel right?
<10> yes
<10> the forwarding is working, otherwise i couldnt ping the router from the 2nd computer
<10> router=192.168.1.1, 2nd comp=192.168.2.2
<2> return route issue from the router
<10> pardon?
<2> does the router know that packets destined for 192.168.2.0 go via 192.168.1.1
<2> or are you using nat?
<2> I guess actually the router itself wouldn't be able to return the ping if that were the case...
<10> umm i dont know.. i just did the same thing as id do on slack and it doesnt work
<2> well if you are able to ping through the debian box to the router, it would seem that the debian box has to be working for forwarding at least
<10> yeah well thats what i thought
<2> unless those ping replies aren't REALLY coming from the router :)
<10> spose ill do a custom kernel and see how it goes
<10> maybe masquerading isnt loaded or something
<2> still, you'd think those pings wouldn't get through
<2> if after you ping that router from wks2, check arp -a and compare the mac address
<10> what im thinking is the forwarding is working from within the lan but theres some necessary module missing
<2> see if it matches the mac address on the router
<10> arp on here or the 2nd one?
<2> my suspiscion is that it will actually be the mac address of wks1
<2> on the 2nd on
<2> e
<10> hopefully it has it..
<2> it will if you ping then arp
<2> it will keep it in the arp cache for awhile
<2> another way to test that would be to try to ssh to the IP of the router from wks2, and see if wks1 actually responds with ssh login instead :)
<10> hmm youre right
<2> heh
<2> seen this before...
<10> i just pinged the router and done an arp and it shows up as this pc
<2> heh
<10> im really confused now
<2> its a prob with the iptables config
<2> it is dnatting the wrong way, essentially
<10> i never even had iptables installed on slack..
<2> well I'm not sure if you still can, but in the older kernels all you needed was ip masq and then echo 1 to /proc/net/forward or something like that
<2> I forget exactly...
<2> the last couple of times I've done this, I've used the iptables config guide at debianadministration.org and/or the howto
<10> yeah ive echoed that
<10> let me do it again just to try
<2> it was /proc/net/ipv4/forward maybe... I can't recall precisely
<10> yep, still get this pc's mac
<10> it must be this kernel, ive tried everything
<2> yah, roll up a 2.6.19.x and maybe it will solve both issues :)
<10> hopefully
<2> I find the all-modules packagaes kernels to be terribly annoying
<2> packaged, even
<10> etch is going if it doesnt :)
<10> yeah i do too.. i just havent been ****ed building my own yet
Return to
#debian
or
Go to some related
logs:
#winxp
gentoo ebuild -* missing keyword
manuteb
#redhat
#netbsd
#visualbasic
#csharp
#bsd
#nhl
theenglishmansion wmv
|
|