* Beavis [2007-10-22 18:29]:
yes, excellent idea, that is exactly what you should do! Instead of
doing teh boring, pretty riskless 10 minutes taking 4.2 upgrade everybody
could easily do, you should figure out which files are pf, update them,
figure out that the kernel doesn't build because of changes through the
network stack, patch for a week or two until you have a kernel that
builds, figure out pfctl, netstat and friends don't work, another
week...
a bit (about when these boring wackos that just upgrade install 4.3)
later when you have a kernel that boots and a userland that seems to
work with it, you have a totally unique system! nobody else is running
that!
ok, nobody else sees the crashes you do, but hey, they're all boring
wackos.
--
Henning Brauer, hb@bsws.de, henning@openbsd.org
BS Web Services, http://bsws.de
Full-Service ISP - Secure Hosting, Mail and DNS Services
Dedicated Servers, Rootservers, Application Hosting - Hamburg & Amsterdam
| Cliffe | Re: [RFC 0/5] [TALPA] Intro to a linux interface for on access scanning |
| Amit K. Arora | [RFC] Heads up on sys_fallocate() |
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
| Andrew Morton | Re: [RFC/PATCH] Documentation of kernel messages |
| David Miller | [GIT]: Networking |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Radu Rendec | Endianness problem with u32 classifier hash masks |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
git: | |
