Re: [SLUG] Keeping up with Kernel releases?
On Mon, Dec 10, 2001 at 04:21:00PM +1100, Jonathan Kelly wrote: > Hi All, > > I was wondering what others do in regards to keeping up-to-date with > kernel releases. Doesn't anyone know a good site that gives an overview The other posters in this thread have given some pretty good advice; a tip that may save you disk space is using 'cp -al' to copy kernel trees. What that does is hardlink everything in both directories. When you apply a patch, patch realises it is hardlink'ed and skip the file. If it has to do something it deletes and recreates the file. Very handy. Anand -- linux.org.au/conf/ | "Knowledge is of two kinds: we know a Attend. Learn. Advocate. | subject ourselves, or we know where we can 6-9 Feb 2002, Brisbane. | find information upon it." -- Samuel Johnson -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
Re: [SLUG] Keeping up with Kernel releases?
On Mon, Dec 10, 2001 at 04:21:00PM +1100, Jonathan Kelly wrote: > I was wondering what others do in regards to keeping up-to-date with > kernel releases. Doesn't anyone know a good site that gives an overview > of what's happening in the kernel? It's getting harder to know these > days what to go with. I had some bad experiences with going with the > latest and greatest recently, and decided to go down the Alan Cox > branch (2.4.13-ac8), as that seemed a bit more conservative (and stable). > That seems to be a bit behind the times now as their upto 2.4.17 pre > releases. Well, the ChangeLogs are usually posted both at www.kernel.org (in the right subdirectory) and wherever the release announcements are made (initially to the kernel mailing list and then to places like linuxtoday.com and others). Also, it's definitely worth reading the kernel-traffic summaries each week and then following the links from there to the kernel mailing list archives for the threads that apply to you (http://kt.zork.net). Linux Weekly News (http://www.lwn.net) also has a good summary of the kernel archives each week which is worth reading. As far as "keeping up with the Smiths" goes, you need to decide what your aims are. Grabbing a kernel that has just been release places you in the "willing to test and not going to cry when something eats your filesystem" category (whether you like it or not). Assuming you prefer to wait a little while to let others test it first, it then depends on what new features the kernel offers. My method is this: for most of this year I have been following the -ac kernel series pretty closely. I would read the ChangeLog and see which areas were likely to affect the hardware and features I used (Alan is excellent at including all the features he added/touched). I would then wait a day or two to see if there was an "oops .. it eats filesystems" bug fix and then install it on various machines that I could afford to have nuked to test. Only once in the last year did this method bite me: one -ac kernel had problems booting with the BIOS in certain Dell laptops and, of course, my laptop had that BIOD so I got an oops almost immediately after booting. No data was lost, though and I just booted back to the old kernel and way off again. My opinion here is that it's important to really know what level of risk you are comfortable with what level of risk you are comfortable with. Watch the relase announcements carefully. When the maintainer or the person supplying the patches says "be careful, this is a big merge", listen to them! I avoided a number of -ac kernels and pretty much everything from 2.4.13 to 2.4.15 (wisely, as it turned out) because there was a lot of merging going on from Alan's tree to the Linus tree and this was in conjunction with other changes, so there were bound to be a few missteps. Things seem to have settled down again and 2.4.16 is running happily on one machine. The short answer to your question is that there is no (as far as I know) big "dummies guide to recent kernel changes" around, but reading the kernel-traffic archives and the LWN archives should give you a pretty good idea. Cheers, Malcolm -- Save the whales. Collect the whole set. -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
Re: [SLUG] Keeping up with Kernel releases?
* This one time, at band camp, Jonathan Kelly said: > Hi All, > > I was wondering what others do in regards to keeping up-to-date with > kernel releases. Doesn't anyone know a good site that gives an overview > of what's happening in the kernel? It's getting harder to know these > days what to go with. I had some bad experiences with going with the > latest and greatest recently, and decided to go down the Alan Cox > branch (2.4.13-ac8), as that seemed a bit more conservative (and stable). > That seems to be a bit behind the times now as their upto 2.4.17 pre > releases. Keep an eye on something like http://freshmeat.net/projects/linux/ IIRC they also have a mailling alert for updates to the project. HTH Greeno -- Greeno <[EMAIL PROTECTED]> GnuPG Key : 1024D/B5657C8B Key fingerprint = 9ED8 59CC C161 B857 462E 51E6 7DFB 465B B565 7C8B Imagine working in a secure environment and finding the string _NSAKEY in the OS binaries without a good explanation -Alan Cox 04/05/2001 -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
Re: [SLUG] Keeping up with Kernel releases?
On Mon, Dec 10, 2001 at 04:21:00PM +1100, Jonathan Kelly wrote: > Hi All, > > I was wondering what others do in regards to keeping up-to-date with > kernel releases. Doesn't anyone know a good site that gives an overview > of what's happening in the kernel? It's getting harder to know these > days what to go with. I had some bad experiences with going with the Kernel Traffic (kt.zork.net) posts weekly summaries of the Linux Kernel mailing list, and is worth reading to find out about recent developments and issues. Linux Weekly News (www.lwn.net) is also worth reading. I also tend to check the ChangeLogs of new kernels before installing them; if they don't involve any fixes to any drivers I use, I usually don't bother installing them (unless there's a big security fix or something like that). -Andrew. -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
[SLUG] Keeping up with Kernel releases?
Hi All, I was wondering what others do in regards to keeping up-to-date with kernel releases. Doesn't anyone know a good site that gives an overview of what's happening in the kernel? It's getting harder to know these days what to go with. I had some bad experiences with going with the latest and greatest recently, and decided to go down the Alan Cox branch (2.4.13-ac8), as that seemed a bit more conservative (and stable). That seems to be a bit behind the times now as their upto 2.4.17 pre releases. Cheers, Jonathan Kelly. Sydney. -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
RE: [SLUG] http access
Actually 404 is "file not found" so check your /var/loh/http logs for where the error occured... thanks, George Vieira Systems Manager Citadel Computer Systems P/L -Original Message- From: George Vieira Sent: Monday, 10 December 2001 12:20 PM To: 'Christopher Booth' Cc: Sydney Linux Users Group (E-mail) Subject: RE: [SLUG] http access possibly that it's listening on 127.0.0.1 and not on all devices.. look for Listen directive or similar thanks, George Vieira Systems Manager Citadel Computer Systems P/L -Original Message- From: Christopher Booth [mailto:[EMAIL PROTECTED]] Sent: Monday, 10 December 2001 12:20 PM To: [EMAIL PROTECTED] Subject: [SLUG] http access Hi guys, I seem to remember a similar problem someone had a while back, but couldn't find it in the archives. On the local system, if I type http://localhost it comes up with my default page. but if I type http://ausmasodp-121m which is my hostname I get a 404 error which I also get by typing the ip address into the browser. I am on Mandrake 8.1, on another box Mandrake 8.0 this works but I can't find any obvious differences in how they are set up. Any ideas on how to get this to work ? Chris -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
RE: [SLUG] http access
possibly that it's listening on 127.0.0.1 and not on all devices.. look for Listen directive or similar thanks, George Vieira Systems Manager Citadel Computer Systems P/L -Original Message- From: Christopher Booth [mailto:[EMAIL PROTECTED]] Sent: Monday, 10 December 2001 12:20 PM To: [EMAIL PROTECTED] Subject: [SLUG] http access Hi guys, I seem to remember a similar problem someone had a while back, but couldn't find it in the archives. On the local system, if I type http://localhost it comes up with my default page. but if I type http://ausmasodp-121m which is my hostname I get a 404 error which I also get by typing the ip address into the browser. I am on Mandrake 8.1, on another box Mandrake 8.0 this works but I can't find any obvious differences in how they are set up. Any ideas on how to get this to work ? Chris -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
[SLUG] http access
Hi guys, I seem to remember a similar problem someone had a while back, but couldn't find it in the archives. On the local system, if I type http://localhost it comes up with my default page. but if I type http://ausmasodp-121m which is my hostname I get a 404 error which I also get by typing the ip address into the browser. I am on Mandrake 8.1, on another box Mandrake 8.0 this works but I can't find any obvious differences in how they are set up. Any ideas on how to get this to work ? Chris -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
[SLUG] [Fwd: Unix courses etc]
This might be of interest to some people - Wollongong area.
"Franklin, Robert" wrote:
"Franklin, Robert" <[EMAIL PROTECTED]>
> Remember me? I'm a teacher of Electrical Engineering at Wollongong TAFE. We
> run short courses in UNIX (OS2) via Linux, Introduction to Local Area
> Networks (ITLAN), PC Servicing 1 and 2, various C/C++ courses, 4GL etc.
>
> Our enrolments for Semester 1, 2002 will be on the 31st of January, 2002 and
> the 1st of February, 2002.
>
> There are other courses your SLUG people might be interested in as well.
> Please visit our website:
>
> www.speedlink.com.au/~electro
>
> Cheers.
>
> Robert Franklin
--
Terry Collins {:-)}}} Ph(02) 4627 2186 Fax(02) 4628 7861
email: [EMAIL PROTECTED] www: http://www.woa.com.au
Wombat Outdoor Adventures
"People without trees are like fish without clean water"
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
Re: [SLUG] vnunet.com Linux lined up as virus target
On Fri, 7 Dec 2001, Rev Simon Rumble wrote: > > Why buy it? McAfee's uvscan for Linux is available free, and the updates > > which people pay a pile for are free as well. The beautiful naiupdt.pl > > means that you're always up to date, automatically. > > Details please? The McAfee site is a dog's breakfast and I can't find > any mention to "free Linux software". I presume you mean free beer? Yeah, it's beer-free. I'm having some troubles finding where I got the original binary from, although I do still have the tarball locally. The .dat updates can be gotten from ftp://ftp.nai.com/pub/datfiles/english/ Ignore the files which are labelled elnx41[46]0.zip - they contain .so files, which I don't know how to activate. The tarball I got and used was called vlnx407l.tar.Z. Unfortunately, there's no remote 'find' command to be used over FTP connections. I can't see anything in the licencing for the software to allow me to put it up on another FTP site somewhere, either. -- --- #include Matthew Palmer [EMAIL PROTECTED] -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
Re: [SLUG] Star Office 5.2 Email 501 Error Message
Almost certainly the problem is in RH 7.1 sendmail. By default this implementation will only accept email from the localhost. RH have clamped down on security in 7.1. Look in /usr/share/sendmail*/cf/redhat.mc for details and how to overcome the restriction. On Sun, 9 Dec 2001, Raena Lea-Shannon wrote: > I am running Red Hat 7.1 and installed > Star Office 5.2. I can receive email and > newsgroups and post to newsgroups but > cannot send mail. I get a 501 Error > Message Invalid Domain Name. I have > checked a re-checked the Domain Name and > it is not incorrect. I have a horrible > feeling it is something to to do with > the sendmail Red Hat 7.1 default set up. > > > Any help would be greatly appreciated. > > RLS > > -- Howard. LANNet Computing Associates - Your Linux people Contact detail at http://www.lannetlinux.com "We are either doing something, or we are not. 'Talking about' is a subset of 'not'." -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
[SLUG] Star Office 5.2 Email 501 Error Message
I am running Red Hat 7.1 and installed Star Office 5.2. I can receive email and newsgroups and post to newsgroups but cannot send mail. I get a 501 Error Message Invalid Domain Name. I have checked a re-checked the Domain Name and it is not incorrect. I have a horrible feeling it is something to to do with the sendmail Red Hat 7.1 default set up. Any help would be greatly appreciated. RLS -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
Re: [SLUG] Am I using ext3 or not?
Just to follow up and let everyone know what happened: ACting on some tips in some of the mail archives Mary linked to, I got rid of the initrd on the grounds that I didn't need it and it was one extra spot where complications could occur... After a reboot, it all works fine I'm tempted to blame redhat's mkinitrd script, but considering the amount of time i spent trying to find out how to learn it (~2 minutes), it's probably more to do with me than redhat the lesson here would seem to be something I should have learnt ages ago - KISS - if you don't need an initrd, don't use one. Thanks to the people who pointed me in the right direction :) -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
