Hi, On Sat, Apr 17, 2010 at 10:21:58AM +0200, Patrik Olsson wrote: > On Fri, 2010-04-16 at 04:28 +0200, olafbuddenha...@gmx.net wrote:
> Is it necessary to have access to the CVS server to do the conversion > from CVS to Git? Depends on the import tool used. For simple cases (which I'm pretty sure all the hurdextras translators are), git-cvsimport does fine -- and this one works perfectly well with only anonymous CVS access. > Should the different translators go into different repositories? Yeah, I think so. No point in lumping them together... (IMHO, all the interesting translators should actually go into the main Hurd tree -- but there is no consensus about that; and also, most of the hurdextras translators don't have copyright assignments, and thus can't really go into the main tree :-( ) > > Whoops, sorry, I meant "ps" :-( > > I had a look, and I couldn't find any really obvious things that needs > fixing. The obvious thing is the --help output: it misses many formats and fields. Looking at the source code was the only way for me to find out how to get the information I need... IIRC while looking at this part of the code, I also discovered some other things that are messy -- but I don't remember the details anymore. > utils/ps.c:377: /* Try to avoid showing non-hurd processes if this > isn't a native-booted hurd system (because there would be lots of > them). Here we use a simple heuristic: Is the 5th process a hurd > process (1-4 are typically: proc server, init, kernel, boot default > pager (maybe); the last two are know not to be hurd processes)? */ Hm... I wonder whether we shouldn't just drop that code. It probably hasn't been used in something like 15 years... (The initial development -- before the Hurd was self-hosting -- was done using a different Mach-based system for hosting, and running the Hurd servers next to them while debugging. Other remnants of that are the "ux" bits in "boot".) > utils/ps.c:389: /* Something is fucked, we can't get the state bits > for PS. Default to showing everything. */ > > But I have no idea how to fix those things. Nah, that's not meant as a TODO item I think. By the sound of it, it's just a fallback, in case of things going wrong outside the control of ps itself... Haven't actually checked the code though. -antrik-