On Dec 27 06:17:37, new_guy wrote:
That's what upgrades are for.
> Would it be feasible to get a snapshot today and follow -current for
You would just use the snaphots. Is that "reinstalling" for you?
> I understand the implications of being current and that things might
So why do you want to use it in production?
> I'm OK with that... I just don't want to reinstall a -release
That's about one hour of work twice a year - what's wrong with that? Why
do you want to stay -current? What problem are you trying to solve, or
what are you trying to achieve by doing that?
Jan
| Heiko Carstens | Re: -mm merge plans for 2.6.23 -- sys_fallocate |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Vladislav Bolkhovitin | Re: Integration of SCST in the mainstream Linux kernel |
| Ingo Molnar | Re: suspend2 merge (was Re: [Suspend2-devel] Re: CFS and suspend2: hang in atomic ... |
git: | |
| Sander | 'struct task_struct' has no member named 'mems_allowed' (was: Re: 2.6.20-rc4-mm1) |
| David Miller | [GIT]: Networking |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Natalie Protasevich | [BUG] New Kernel Bugs |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| Hans Reiser | Re: silent semantic changes with reiser4 |
| Nick Piggin | [ANNOUNCE] new new aops patchset |
| Christoph Hellwig | Re: [patch 01/15] security: pass path to inode_create |
| johnrobertbanks | Re: Reiser4. BEST FILESYSTEM EVER. |
