Re: Partitioning
So where do the kernels go when you don't have a /boot partition? I'm now using a seperate /boot partition but it's full now. So is it possible to change this? Alvin Oga wrote: /boot is NOT needed ... - /boot was needed in the old days to guarantee that the boot kernel was occupying the 1st 1024 cylinders -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: upgrade->dead system, help.
Hmmm...interesting...i was starting to think it was all my doing while all i really did was the usual update. Sofar i haven't been able to figure it out..at all. I've made a completely new 2.4.22 kernel, and the exact same thing happened, freeze after the INIT: version 2.85 booting message. None of my older custom build 2.4.22 kernels will get past that point either anymore. 2.4.18 and 2.2.19 go through the boot process without problems. All the 2.4.22 kernels on my system have worked fine untill now. Anyways..after that i installed the debian kernel package 2.4.22-686. As a side note...that one uses an init.rd which none of my custom kernels did and this kernel does boot without problems. Which is not to say that the problem is only there with non initrd kernels, just thought i'd mention it. I've not build a new custom kernel but plan to do so tomorrow, with a freshly downloaded source, although i have little hope that one will work. I'm not a linux guru at all, which is why i hesitate to say this but me thinketh something is buggy somewhere especially since i'm not the only one having experienced this. It happened to me Friday aswell by the way. Since it happens when sysinit starts i'm inclined to think something is amiss there, though i have no clue as to what and i'm not skilled enough to find out. Cheers. César wrote: Last friday I had the same exact problem. I'll tell you if I guess a solution. Cesar - wil <[EMAIL PROTECTED]> wrote: Hi, Sorry I have very little info on this...no logs or anything:( Running SID, with a custom 2.4.22 kernel, ext3 file system. HD was checked with the diagnostic utility from IBM, including surface (advanced) check and was fine. Did an update via dselect yesterday and after that the whole system has died. When i boot the process stops at INIT: version 2.85 booting followed by a blinking cursor. When i ran the upgrade the thing striking me as very odd was under "new packages to install" 'kernel-headers 2.5.x.x.' were mentioned. Not sure of the exact version anymore but it was 2.5 for sure. I think it was 2.5.99. I was kinda flabbergasted by that and saw no reason why those kernel headers should be installed...since i'm on 2.4. So i went back into the dselect selection 'mode' and set that kernel package to 'purge' so it wouldn't install. This gave me a load of ' depends on kernel-headers 2.5.x.x. ' like from gcc and so on. Struck me as utterly weird aswell cause my system never had anything 2.5.xxx kerlnel related stuff on it...anyways...thinking 'dpkg knows best' i let it have it's way and the package in question was installed. After getting the packages during install/configure something went wrong aswell but silly me didn't pay too much attention since this happens quite a lot with unstable and always gets resolved quickly...and never ended in something like i'm having now. Can't imagine the cause to be those kernel headers even if it's weird they were installed, but one of the 20 orso packages which got updated. An older 2.4.18 kernel does go thru the entire boot process but with may many errors mostly in the line of 'can't find /var/xx' After that i tried toms floppy linux to boot the system. mount /dev/hda9 results in just getting the'special device not found message'. And hda9 happens to be /var. fdisk shows hda9 as there and as ext3 but i think the complete filesystem went out da door on that partition. e2fsck gives me a 'the superbloack could not be read or does not' etc..etc..etc. Any ideas on how to get out of this one?...and why this happened? Cheers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: upgrade->dead system, help.
Hiya, Well, as mysterious as this whole thing started it also ended. Today i did an update which updated the following packages on my system binutils_2.14.90.0.7-1_i386.deb debconf-i18n_1.3.20_all.deb debconf_1.3.20_all.deb fakeroot_0.8.1_i386.deb fontconfig_2.2.1-9_i386.deb libc6-dev_2.3.2.ds1-9_i386.deb libc6_2.3.2.ds1-9_i386.deb libfontconfig1_2.2.1-9_i386.deb linux-kernel-headers_2.5.999-test7-bk-6_i386.deb locales_2.3.2.ds1-9_all.deb Just for the hell of it i tried to boot one of my custom 2.4.22 and wadda ya know, each and everyone of those kernels now works again. I'm *really really really* curious as to which package caused all this kernel trouble for me and some others, but also glad my custom kernels are fully operational again. Also i'm still wondering what this linux-kernel-headers_2.5.999-test7-bk-6_i386.deb "linux-kernel-headers - Linux Kernel Headers for development" is doing on my system. Is this package at all related to the 2.5.x kernels?(since i don't run anything 2.5 related) cheerios Stephen J. Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello all, I am encountering this problem as well. I have been able to narrow it down to the kernel itself. If I use a debian standard kernel (2.4.22 or 2.6.0-test9) it boots fine. if I use a kernel I compiled myself (This kernel worked fine before the upgrade) it just stops at the INIT: version 2.65 booting line. I have tried building both initrd and non-initrd kernels but no joy. Could it be a particular kernel option I have (or have not selected) I hope this helps someone figure this issue out. Regards, Stephen. On Saturday 01 Nov 2003 11:54 am, wil wrote: Hiya, Thanks for the tip but I wonder if it is the kernel, this kernel has been running stable for weeks...why would it suddenly crap out after an upgrade/install of some new/updated packages. A bit more on the 2.4.18, as i mentioned that one does go through the complete boot but it couldn't get to /var. Well, i forgot that the 2.4.18 i was running didn't have ext3 enabled so i changed the fstab ext3 entries to ext2 and that 2.4.18 kernel now boots fineand my /var is still there...and as far as i can tell nothing went missing at all. (no clue as to why toms image didn't want to mount hda9 though) A previous 2.4.22 kernel doesn't boot either and stopped aswell right after INIT: version 2.85 booting. I will try a standard debian kernel later tonight but i expect that one won't go past init either.. cheers Hi, Sorry I have very little info on this...no logs or anything:( Running SID, with a custom 2.4.22 kernel, ext3 file system. HD was checked with the diagnostic utility from IBM, including surface (advanced) check and was fine. Did an update via dselect yesterday and after that the whole system has died. When i boot the process stops at INIT: version 2.85 booting followed by a blinking cursor. When i ran the upgrade the thing striking me as very odd was under "new packages to install" 'kernel-headers 2.5.x.x.' were mentioned. Not sure of the exact version anymore but it was 2.5 for sure. I think it was 2.5.99. I was kinda flabbergasted by that and saw no reason why those kernel headers should be installed...since i'm on 2.4. So i went back into the dselect selection 'mode' and set that kernel package to 'purge' so it wouldn't install. This gave me a load of ' depends on kernel-headers 2.5.x.x. ' like from gcc and so on. Struck me as utterly weird aswell cause my system never had anything 2.5.xxx kerlnel related stuff on it...anyways...thinking 'dpkg knows best' i let it have it's way and the package in question was installed. After getting the packages during install/configure something went wrong aswell but silly me didn't pay too much attention since this happens quite a lot with unstable and always gets resolved quickly...and never ended in something like i'm having now. Can't imagine the cause to be those kernel headers even if it's weird they were installed, but one of the 20 orso packages which got updated. An older 2.4.18 kernel does go thru the entire boot process but with may many errors mostly in the line of 'can't find /var/xx' After that i tried toms floppy linux to boot the system. mount /dev/hda9 results in just getting the'special device not found message'. And hda9 happens to be /var. fdisk shows hda9 as there and as ext3 but i think the complete filesystem went out da door on that partition. e2fsck gives me a 'the superbloack could not be read or does not' etc..etc..etc. Any ideas on how to get out of this one?...and why this happened? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Stable Debian == obsolete??
I think woody is for those who really need seriously stable machine to act as a server. I'm on SID mostly because of the security 'issue' of SARGE. SID tends to have more broken stuff, but security updates get there fast. SARGE is 'more stable' but it can take longer before a security update gets to testing, and i still found myself apt pinning to get some packages from SID so i ended up with 'running testing' but a load of packages from SID in there. Alas, even SID is stable for me, except for the custom 2.4.22 kernels not wanting to boot past INIT last weekend (fixed now after today's update) i've never had really serious problems with it. I know you didn't ask for 'which one?' but if you ask em you might aswell go to SID. cheerios Chema wrote: [snip snap snip] > Well, thats my sad history ;-P > > But, of course, I'm pushing the reset, and starting again. But would like some guidance this time. > > The "Getting Debian" page mentions that: > > A network installation of the "testing" distribution will provide you with the very latest packages, whereas any CD images of "testing" that you download would be outdated very quickly. > > So the network installation of Sarge is my new bet. But I want to know, how really unstable is it? I don't think most people could live with Woody, so is it test the most used distro? > > I have lurked the release information, and have not seen any bug that scares me, but any warnings regarding the Athlon XP Thoroughbred, Geforce 4 Ti, emacs, PostgreSQL, perl and any other indispensable program would be preciated. > > I would also suggest stating more prominently the age of Woody and the prices that its stability entails. > > Thanks! > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: linux-kernel-headers foul-up
Thanks for explaining this in the other thread aswell. What i wanted to ask, could this package be the cause of custom 2.4.22 kernels not going past INIT (today's update fixed this problem) which i and a few other people experienced over the last weekend? The original poster mentioned both mplayer and xawtv breakage, both i use because the server(mplayer self compiled)acts as a vcr aswell. Does this mean i should not recompile either one and leave them as is? And last question, if this new splitting stuff causes breakage who will solve this? is this a debian issue, a linux issue or should the sources of for example mplayer be changed? Every time i start to think 'i'm getting the hang of linux' things like this happen...lib stuff...compile stuff...at times i think i need spiked mountain shoes to climb the learning curve ;) cheers Colin Watson wrote: It includes the files in /usr/include/linux and /usr/include/asm which used to be part of libc6-dev. This is simply a packaging reorganization. Programs written that way always had a sword of potential breakage hanging over them. The standard way to deal with this at the moment, suboptimal though it is, is to copy the header files you need from the kernel and include them in your own package; that way you're safe from changes to glibc. The move to 2.6 headers was necessary in order to support NPTL in glibc. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: linux-kernel-headers foul-up
Well, I'm having serious problems with Mplayer, actually with mencoder to be exact. I have a load of automated 'vcr' recording scripts. These scripts have always worked and have given out the right kind of files with the right kind of bitrate(given in the script) correct timings, correct audio...and so...in short...perfectly fine mpeg 4 recordings. Right now running one of those scripts, so it's not me making a command mistake, result in an avi with the wrong bitrate, wrong timing/length(not running for the total given time), utterly messed up sound and so on.FUBAR. This is with an mplayer/mencoder version compiled from CVS which worked fine before this header stuff came along last friday, last time i did a compile of the mplayer source was about 2 weeks ago. So mencoder does run, but it has become useless. So apart from compile time this whole thing also messes up at least some already compiled programms. Cheerios csj wrote: > Xine also fails to compile (ditto nvrec, a low overhead recording > program). My conclusion: all video applications are affected. > This is as far as compiling goes. I've seen no problems with a > previously working program suddenly failing to run. The original poster mentioned both mplayer and xawtv breakage, both i use because the server(mplayer self compiled)acts as a vcr aswell. Does this mean i should not recompile either one and leave them as is? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
df and du results on / strange
Running SID with latest packages Nothing but problems here since last weekend...here's another one. / is ext2, all others are ext3. I get a almost 100% use of / But with du i'm geting nowhere near 1.9GB total which is the size of my / , in total i get to 568419 used on / if i take du's output as truth. The real thruth is there's about 130MB free space on / , cause trying to copy more that that to / results in 'no space left on device'. What am i missing here? Cheerios df gives me this: Filesystem 1K-blocks Used Available Use% Mounted on /dev/hda6 1984016 1878036 3568 100% / /dev/hda115522 9216 5505 63% /boot /dev/hda7 8596736875368 7366336 11% /usr /dev/hda8 4421384570088 3668800 14% /home /dev/hda9 1545036185308 1295792 13% /var /dev/hdb1 38448276 16203304 20291872 45% /share/vcr /dev/hdb2 76928480 68151820 4868852 94% /share/music /dev/hdc1 76944512 32828 73003072 1% /share/mp3 du -s /* | sort -nr | less : 84289532/share (seperate partition) 842564 /usr(seperate partition) 537284 /home (seperate partition) 394203 /proc 152500 /var(seperate partition) 98056 /root 52728 /lib 13152 /etc 9216/boot (seperate partition) 4496/backup 3032/sbin 2640/bin 72 /dev 16 /tmp 4 /rcs 4 /mnt 4 /lost+found 4 /initrd 4 /floppy 4 /cdrom 0 /vmlinuz.old 0 /vmlinuz-2.4.22.20102003 0 /vmlinuz-2.4.22-1-686 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: df and du results on / strange
(/me looks up thinking when will i not be noob anymore) These are the kinda things i tend to learn the hard way, as in today running into a full partition under linux for the first time ever, except for the boot partition but that one is so small it's easy to keep an overall view. I never knew su reports blocks used..so thanks for the elaborate explanation Any console utils or commands which show the 'real', or unreal if you look at it differently, space useage? Cheers. Bob Proulx wrote: [snip other interesting stuff] Also remember that du reports disk blocks used. A disk block will be different sizes on different filesystems. This is not the same as the disk space used. A three byte file takes up three bytes of used space but fits in one (likely 512 byte frag) disk block. Again, this is usually tuned by different filesystems and is one of the reasons different filesystems have different performance. Yes, it can be confusing. Bob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: df reports negative partition size
Not sure if this is related but i have have weirdness with df aswell
http://lists.debian.org/debian-user/2003/debian-user-200311/msg00575.html
And i don't have thousands and thousands of tiny files to explain
for the difference in reported size, nor could i find open
files with lsof.
cheers
Ernst Plüss wrote:
Hi all
If I run df -h on my debian machine, I get the following output
debian:~/tmp$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/hda3 -3233790934511k 1.0k 0.0k 11% /
If i do a cat /proc/partitions I get
debian:~/tmp$ cat /proc/partitions
major minor #blocks name
3 0 12714912 hda
3 1 24066 hda1
3 2 136552 hda2
3 3 12546765 hda3
An ideas why df is reporting a negative partition size?
Actually this is only the symptom of my real problem. I tried to install a JDK 1.4 from Sun. Although there sould be somme gigabytes of free diskspace, it's reporting, that there's not enough space to install.
Aftet having a look with df I think the JDK 1.4 installer is useing df and stops after seeing only 1.0k free.
TIA
ErnstÿôèPÔ” ‘
ÿzf¢–Ú y¸šŸû¬z¿ëz«ž²ßåŠËlý×›‰©ÿ¢¸0ŠØZ²æãyËhû§²æìr¸›{ÿÓ®‹›•ï¢{ZrÙb²Ùš²×«þX¬¶ÏÝy¸šŸú+
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: got my woody working, wanted to upgrade, already ruined my system
I think as you say all you have to do, or at least that's how i did it a few times is, update your sources list and point to testing aswell, apt-get update, apt-get dist-upgrade. Seems a whole lot better than downloading 2 iso's again. Stable is very stable...i'm learning to live with it now since last week's mess i had with SID. Stable for my DVR/imap/samba sever, SID/winXP on the desktop beast...so if SID goes bonkers on me i just go back to winXP for a few days and then run an apt update which usually fixes SID :) Testing, wellthat's sorta like grandma, everyone loves her but no one wants her in their house permanently.. So for me from now on, stable and only get backports of stuff if i really really need.. Cheers. David Millet wrote: would it be smarter to just go with the stable release and do an "apt-get -t testing -u dist-upgrade" once i've specified a testing mirror? or should i simply go with the stable release and learn to be happy with that? thanx for your help folks, i totally appreciate any help you can give me on this david -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: got my woody working, wanted to upgrade, already ruined my system
Don't take my word for it, i still consider myself a noob and probably will always do:) But i have been running debian for a long time now, my experience with testing is it sometimes can take a long time for a package to get updated, so if something is broke you can end up being stuck with it for a while. SID is speed of light, if something breaks it usually gets fixed fast. But testing has less broken stuff than SID, so it's kinda choice between more broken stuff(usually nothing major) which gets fixed fast or less broken stuff but the chance of having to wait way longer for an update. This also goes for security related things, stable has security taken care off seperatly, SID moves so fast that if there is a vulnerabilty it will be solved pronto, but with testing it can take longer. So that's a bit more risky. Uptill last weekend i never had something really major go wrong with SID, something did go rather bonkers on a friday relating to my 2.4.22 kernels, and whatever it was 3 days later it was fixed(and i could still run it anyways with older kernels so my system was not 'unusable') That's why i went back to stable with my server, which is something i should have done anyways when that machine got degraded from desktop to server, but i was too lazy to put it all back to stable. So my personal experience is SID for the desktop and stable or woody for a server, this does not mean that stable isn't suitable for the desktop cause it is. Cheers David Millet wrote: huh? am i hearing your right? > you're suggesting i try out sid instead of sarge? for a desktop machine is that the way to go? > anybody else have any input on this? > > david Stable is very stable...i'm learning to live with it now since last week's mess i had with SID. Stable for my DVR/imap/samba sever, SID/winXP on the desktop beast...so if SID goes bonkers on me i just go back to winXP for a few days and then run an apt update which usually fixes SID :) Testing, wellthat's sorta like grandma, everyone loves her but no one wants her in their house permanently.. So for me from now on, stable and only get backports of stuff if i really really need. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Motherboard ASUS a7v600: is anybody using this?
I have the P4800 mobo, same Gbit chip...3c2000/3c940(same thing) Works fine for me with the module sources i downloaded from i think the asus site. cheers I have ordered this motherboard, with 3c940 Gigabit ethernet (with a "Linux" driver on the ASUS website(?!)); and AD1850 "AC'97" etc.) sound. I would appreciate hearing about any issues people have encountered. Alan O.K., sorry. Just noticed the subject line. Checked out the board on the Asus site. It looks O.K. I'm not sure about the ethernet factor, but 3COM will be able to advise you there, they are very obliging. They've generally got a toll-free number, and ask for 'presales'. David. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
fetchmail, when does one loose email?
I've been following the recent threads on fetchmail and i've been reading up on it but i'm not quite clear on when one can loose mail. Right now in fetchmailrc i have "set no bouncemail, antispam -1, batchlimit 50, keep" as defaults. Fetchmail in my case fetches email of several pop3 servers from where it goes into exim and exim passes it on to icourer imap. According to the man page fetchmail under --flush: " What you probably want is the default setting: if you don't specify `-k', then fetchmail will automatically delete messages after successful delivery. " So if i remove 'keep' from the defaults fetchmail will automatically delete messages from the pop server after successful delivery to my MTA, exim in my case, if one goes by the manual. From this it seems that even if the exim setup, or whatever MTA, is a mess...fetchmail will not delete any mail because a delivery would simply not be succesfull. Yet there's loads and loads of people loosing email at one point or another due to a badly configured MTA. In short, am i still at risk of loosing email even if i don't have an antispam filter in exim (so no error 571 will be send from exim to fetchmail). cheers. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: fetchmail, when does one loose email?
Exim passes it on to icourier so everyone on the local network has their mail on an imap server. It all works fine and sofar nothing has ever gone wrong, but i still have 'keep' as default in fetchmail to prevent people loosing their mail in case i screw up somewhere. But as you say, mail boxes on the pop3 server fill up quite fast so i was thinking about ditching the 'keep' option. The thing is if you google left and right there's a lot of people moaning about fetchmail, so i was starting to think about an alternative. Yet when i read the FAQs and man pages it seems to me that fetchmail can only loose mail when the MTA it passes it's mail to is wrongly configured... So my question is more "if the MTA fetchmail passes it's mail to is correctly configured can fetchmail still be the cause of loosing email"...in other words is it always the MTA and it's (mis)configuration being the 'weak link'. And along those lines, "if the MTA fetchmail passes it's mail to is correctly configured is it safe to remove the keep option". cheers Jonathan Dowland wrote: When fetchmail is instructed to keep, it won't delete mail from the remote box, so it is safe. Although, your remote box might fill up quite quickly... In general, a misconfigured MTA will potentially lose you mail. If I may ask, why does exim pass the mail onto courier imap? To test your MTA, try mailing locally and watch for successfuly delivery and bounces, followed by a remote test, and mailing out. At the moment I've been losing mail mostly due to procmail (or, my misconfiguration of procmail). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
kernel building ways
Hi, I'm just trying to build my second kernel... Last time i did it, the kernel-how-to way, resulted in a few module dep errors... So i've searched the web and also came across this one: http://newbiedoc.sourceforge.net/system/kernel-pkg.en.html Now what would be the best way to go about building a new kernel and are the instructions on that site correct? And is kpkg only suitable for debian sources...or could i use this method with the latest stable 2.4.x.x kernel sources if i ever feel the need to go wild:) Thanks Willem
Re: 3c905c
I have a 3c509 and it works peachy...i'm running 2.2r4and if i recall right it also went fine with .r2 without me having to download 3rd party stuff. cheers Willem At 08:33 27-12-2001 -0800, you wrote: On Thursday 27 December 2001 08:17 am, Marcelo Chiapparini wrote: > I will install potato in a machine which have the 3c905c-tx NIC installed. > The Debian install program (for 2.2.r2 in my case) doesn't suppot it. It doesn't? Are you sure? I haven't used a 3c905 w/ Potato in a while, but I'm pretty sure the 3c509 driver works just fine with it. --kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kernel building ways
Hi, Okidoki...thanks for the help. One more thing...i think i'm gonna jumpt to the 2.4 kernel...using the debian kernel packages. Which one would be the most stable? 10 .12 .13 .14 or .16? Cheerios At 13:20 27-12-2001 +0100, you wrote: make-kpkg needs some debian-specific stuff, but debian's kernel-source packages are usually uploaded a few days (2/3) after the official kernel release. Which, after the 2.4.15 fiasco, seems a reasonnable thing to do :) HTH, Romain
Re: "C" Manual
As others have said stear clear of OS specific topics... Even if you want to start using OS specific stuff later on i think it's best to start out with real C++. In my opinion you should even avoid 'plain' C because you'll end up learning things you can ditch in C++ cause there are more effecient and new ways of doing things in ++. And make very sure whatever book you get really really restricts to C++... cause there's a shitload of them that sneak in non C++ stuff like the dreaded conio Cheers, Willem You'll find loads of recommendations and other info on the web and on the C/C++ newsgroups. A word of advice: ignore the whole OS issue when buying general C/C++ books or looking at stuff on the web. The best stuff is not system specific as the language is not, and if you restrict yourself to Linux-specific books you are unnecessarily limiting yourself. If you want to use Linux specific extensions/libraries, that is another matter. Sincerely, Faheem Mitha.
ipchains...masq..spyware..etc..etc
Hi, I've read most that i could find about firewalling/masqing/ipchains etc.. It's not all completely clear yet but i'm getting there...i think. I have to say that i find this one of the biggest barriers of being comphy with linux. I'm runnning a dual boot with XP and although the goal is to ditch windows all together and stick with linux at least with windows and tiny personal firewall i know "nothing" is gonna get past. With linux i don't really get it...i have my own machine connected to the web via cable and it acts as a router for another machine which is connected via a cross cable to a second NIC in my PC... For the sake of the argument lets say i installed some linux thing which has a spyware feature, collects info on my system and sends it home via port 80which in my ruleset is an allowed port because i need that port for the web. How would i ever block such a thing(without knowing in advance that it will call home and to which adress it will connect)and how would i even find out that app actually did something i dind't like. In other wordsis there such a thing as allowing defined applications to communicate while keeping the door closed for other apps unless i ass a rule for that app. And if there is no such thingwhy not... Or am i totally missing the point and still too much in a windows state of mind? Cheers, Willem
Re: ipchains...masq..spyware..etc..etc
Uhmmm... I said i was using tiny personal firewall on windows... My question was about linux...not about windows... cheerios Willem. At 14:41 30-12-2001 +0100, you wrote: >You should use a personal firewall on your Windoze system for that. wsa <[EMAIL PROTECTED]> writes: > feature, collects info on my system and sends it home via port > 80which in my ruleset > > is an allowed port because i need that port for the web. > How would i ever block such a thing(without knowing in advance that it > will call home and > > to which adress it will connect)and how would i even find out that > app actually did something i dind't like.
application level firewalling in linux?(was:ipchains...masq..spyware)
HI, Maybe in my original mail i wasn't very clear judging from the responses i got...so i'll try one more time. I wasn't asking what to do in windows...although i did mention windows which probably made everyone run for the hills:) My question was about linux and how to accomplish security on application level, like what happens in windows with a personal firewall. Because i don't understand how i can achieve full security when opening ports...like port 80 for the web or 110 and so on. Cause as far as i can understand reading all the IPchains documentation if i open that port in linux it wil be open for any application which uses that portand i can't specify that only mozzila or netscape can use that port and any other app can use that port to transfer information. And if there is no need for security on application level why is that? Cheers, Willem
RX mode?
Hi, Just wondering here cause i can't remember seeing this bootmessage before. Had to reinstall linux cause, being a newbie, i made a complete mess of it:) So i did a reinstall, which by default let me setup my first NIC, eth0 eth1 NIC went into the kernel but wasn't configured. So after having it all running again i added: iface eth1 inet static address 192.168.0.1 netmask 255.255.255.0 to the interfaces file in /etc/network/ It all seems to work ok, but during boot i get 'setting RX mode to 1 addresses' on the eth1 NIC. Is this normal, did i forget anything when setting up eth1? And if it's normal is it a security risk. Thanks Willem
firewall script and port 389,1002,1720..
Hi, I was wondering about this. I had a firewall script generated at the firewall site. http://home.hetnet.nl/~wsa30/rc.firewall there's my script. From a different ISP i ran a portscanner and i found the following ports open 21 (normal cause this one is allowed) 389 LDAP 1002 1720 h323hostcall My questions, Why are those last 3 ports open? i've looked around in the rcx.d directories and init.d but i could find nothing about LDAP...so why is this even running? And is there any reason not to block those ports with a few extra rules? And..if someone can find the time to look over the rules in that script...is it a decent and safe script?:) many thanks in advance Willem
kernel 2.4.17...2 strange things
Hi, Today i upgared from potato to woody... with: dselect update apt-get dist-upgrade (just mentioning it cause this might be the wrong way?) And i switched to a 2.4.17 kernel. Now i have 2 NICsdifferent brands...realtek and 3com. eth0, the realtek, connnectiong to the net and eth1 for the LAN, which is a 3com ISAPNP NIC. Both are compiled into the kernel. First thing i noticed that the NICs had switchedrealtek became eth1 and 3com eth0grrr. The other problem is that with my previous 2.2.19 kernel the 3com was detected at IRQ7 and 0x300 which is what it is set to... (checked with the 3com utils) But with 2.4.17 it gives me IRQ12 and base 220which is the PS2 port IRQ...(so no mouse either) I checked again with the 3com utils and the card was still set to 7/300 From what i can tell i did compile the kernel with all the right options including PNPisa. How do i solve this? And another thing...i also noticed that on mounted vfat windows partitions every file and every directory now gets marked as executable... Is this normal? Many thanks Willem
kernel 2.4.17...2 strange things(2)
(never arrived back here so sending this one again) Hi, Today i upgared from potato to woody... with: dselect update apt-get dist-upgrade (just mentioning it cause this might be the wrong way?) And i switched to a 2.4.17 kernel. Now i have 2 NICsdifferent brands...realtek and 3com. eth0, the realtek, connnectiong to the net and eth1 for the LAN, which is a 3com ISAPNP NIC. Both are compiled into the kernel. First thing i noticed that the NICs had switchedrealtek became eth1 and 3com eth0grrr. The other problem is that with my previous 2.2.19 kernel the 3com was detected at IRQ7 and 0x300 which is what it is set to... (checked with the 3com utils) But with 2.4.17 it gives me IRQ12 and base 220which is the PS2 port IRQ...(so no mouse either) I checked again with the 3com utils and the card was still set to 7/300 From what i can tell i did compile the kernel with all the right options including PNPisa. How do i solve this? And another thing...i also noticed that on mounted vfat windows partitions every file and every directory now gets marked as executable... Is this normal? Many thanks Willem
