On Sat, Aug 19, 2023 at 04:36:06PM +0900, lain. wrote:
> Oh, I didn't know that.
> I never use CVS for anything other than OpenBSD ports, so I read the
> handbook which says "you do X", I make notes for future reference so
> that I don't need to open up a browser every time I need to update the
> ports tree, and assume that "cvs -q up -Pd -A" is the CVS equivelant of
> "git fetch && git pull".
> But if that's the case, then I guess I'll need to adjust my notes a bit
> to prevent messing up next time.
> 

You might have caught the problem if you subscribed to the tech@ mailing
list. You could have then queried on the ports@ list about it.

DO NOT post to the tech@ list unless you have created and well tested a
diff. Never ask a general question there. Major code churn is never
desired. Only small diffs making easy to test changes have any chance of
being accepted. Ask about it by showing it on misc@ or ports@ first.

If you are told no, accept that. Even if it is a good idea, it may cause
a major problem for other developers work.

Unlike other OS's, OpenBSD is a system where everything is
unified at every release. You might get told to resubmit your diff after
release.
If you want to run your modification just on your own, go ahead. But the
cost of that is no support.

If you can, buy a cheap older computer or add an extra drive to run
current on. Break things. Learn how to fix things. Screw up the mounting
order in fstab. It won't finish booting. It's pretty easy to fix. But
you must use the editor ed to fix it. Cause maybe you can't mount
something to get to use vi.
Break your disklabel. There is a fix (usually). Go through the mailing
list archives and look at peoples past problems. Give yourself
the same problem before you look at the solution and see what you can do
on your own.
Be sure you "forget" the root password. There is an easy fix for that,
too.

If you understand C, look at the source code. If you understand Perl,
look at what's written in it. Same for ksh.

When you are ready, after learning a lot, consider porting in a program.
But ask about it on ports@ first.

Have a good time. OpenBSD is nice, but requires some effort. It is not
for everyone.

-- 
Chris Bennett

Reply via email to