Basically i'm looking for the lazy man's way out of maintaining the ports/packages/updates on my OpenBSD system. FreeBSD has a thing called portupgrade that will keep your ports up-to-date and all spiffy. Does OpenBSD have some sort of equivalent package? If so, I haven't been able to find one.
Similarly, is there a script or port or something that will apply the security patches for me? I just upgraded from OpenBSD 3.0 to 3.1 on my firewall and am applying all the patches and its taking FOREVER. I would think there would be some script of program that will patch, recompile and restart software, kernels and services as needed. Part of my problem is that my firewall is a really slow machine, but man this is killing me. Why doesn't someone put the patches into the ports tree so i can just fetch and recompile everything like a port? Is there some reason i'm not aware of that makes this a bad idea?
what i wouldnt give for a
# cd /usr/ports/patches
make && make install && make clean
and then just walk away knowing it would all happen for me. we'd have to supply some information like where to find the kernel configuration file (if you didnt want to use the generic one), but beyond that I don't see why we can't automate it. sigh.. i might post this to the mailing list but i have to put my flame suit on first
Similarly, is there a script or port or something that will apply the security patches for me? I just upgraded from OpenBSD 3.0 to 3.1 on my firewall and am applying all the patches and its taking FOREVER. I would think there would be some script of program that will patch, recompile and restart software, kernels and services as needed. Part of my problem is that my firewall is a really slow machine, but man this is killing me. Why doesn't someone put the patches into the ports tree so i can just fetch and recompile everything like a port? Is there some reason i'm not aware of that makes this a bad idea?
what i wouldnt give for a
# cd /usr/ports/patches
make && make install && make clean
and then just walk away knowing it would all happen for me. we'd have to supply some information like where to find the kernel configuration file (if you didnt want to use the generic one), but beyond that I don't see why we can't automate it. sigh.. i might post this to the mailing list but i have to put my flame suit on first