Re: fdisk implementation [read this before deciding what to do]
Update: After additional consideration and some discussion on the Dragonfly IRC, etc, we have decided to go ahead and put this project on the back burner for now. For one, it may be a while before we can get around to adding disklabel64 support. Also, the Dragonfly community seems to want built in interactive mode and compatibility with the existing disklabel and fdisk tools. Our tools are designed specifically to be run under front end scripts and are not interactive or command line compatible with the existing tools. Sorry about the delay in following up on this. Ok, sorry to hear that. Basically this means I'll go back to work myself Offtopic: BTW, is the IRC channel listed anywhere on the page or in any ailing list message ? I did not know that it existed.
Re: hammer history ls
Hi again, after some hours of sleep I took a look into the hammer sources and pushed my code in there. If anybody else cares about this option, the patch is attached to this mail. You can then basically use: hammer history-count fname to only display a count (I did not care about any formatting here :) as I use it from a script only anyway). And more importantly it is possible to specify a start-tid and end-tid option as the last arguments that are passed to history[-count]! hammer history[-count] fname1 ... fnameN start-tid=0x end-tid=0x Btw when I took a look at the code I realized that there is an offset option that is not documented anywhere in the man pages . Regards, Tobias history-command-change.patch Description: Binary data
Re: fdisk implementation [read this before deciding what to do]
Ok, time for me to reply again :). I started developing on this, as I mentioned in the first post. I have a first working interface draft and started to work on the real fdisk implementation by moving in core code from the dfly fdisk implementation I stopped development however when I read about Vincet's post, as I don't want to do unnecessary development work. I therefore suggest we first check what might come out of this, and I declare myself willing to help wherever needed. If it turns out that the tool is not releasable for some reason whatsoever I will continue working on the fdisk implementation. Does this sound reasonable ? Greetings, Tobias -- Jost Tobias Springenberg jspri...@uos.de If you plan to send me any personal or sensitive information please use GnuPG! My public key can be found at: http://www-lehre.informatik.uos.de/~jspringe/jspringe.gpg
Re: fdisk implementation
On Wed, 9 Jul 2008 10:27:49 -0700 Freddie Cash [EMAIL PROTECTED] wrote: On Tue, Jul 8, 2008 at 10:35 AM, Matthew Dillon [EMAIL PROTECTED] wrote: :just a quick sidenote... while I decided to finally play around with hammer :I had to fiddle around with dragonfly's fdisk implementation and I think it is a mess! :The menu driven mode is horrible, and absolutely not self explaining. :We should definitely adapt the OpenBSD or newer FreeBSD version. :Is there any reason there could occur bigger problems with this ? :Otherwise I'm actually willing to try to port it over during my semester break, :because I really believe it is necessary to do this. :If there is any special super mode I missed about the fdisk we are using right now just let me know! :Regards, :Tobias : :-- :Jost Tobias Springenberg [EMAIL PROTECTED] We could probably use a new fdisk, I think this would be a good project. You may want to have a look at http://www.freshports.org/sysutils/sfdisk/ This is the fdisk tool used in sysinstall, and has a decent interface. It's similar to cfdisk from the Linux-world (but nicer to use IMO). -- Freddie Cash [EMAIL PROTECTED] Ok I guess I will take a look at it tonight and also search for alternatives. I'll have 2 weeks of time during the next 2 months so it should be possible to finish this. Question to the sfdisk, I am not an expert regarding FreeBSD code, but doesn't sfdisk depend on some internal FreeBSD disk abstractions ?? Greetings, Tobi -- Jost Tobias Springenberg [EMAIL PROTECTED] If you plan to send me any personal or sensitive information please use GnuPG! My public key can be found at: http://www-lehre.informatik.uos.de/~jspringe/jspringe.gpg
fdisk implementation
Hi all, just a quick sidenote... while I decided to finally play around with hammer I had to fiddle around with dragonfly's fdisk implementation and I think it is a mess! The menu driven mode is horrible, and absolutely not self explaining. We should definitely adapt the OpenBSD or newer FreeBSD version. Is there any reason there could occur bigger problems with this ? Otherwise I'm actually willing to try to port it over during my semester break, because I really believe it is necessary to do this. If there is any special super mode I missed about the fdisk we are using right now just let me know! Regards, Tobias -- Jost Tobias Springenberg [EMAIL PROTECTED] If you plan to send me any personal or sensitive information please use GnuPG! My public key can be found at: http://www-lehre.informatik.uos.de/~jspringe/jspringe.gpg
Re: New site design
Pushing this forward again as we are close to the 2.0 release. Regardless of the specific design issues and wether or we like the changes of content I believe that it was commonly agreed on the fact that the download dragonfly button is a very good idea. I therefore suppose that we at least add that one to the site as the release is announced! As you are expecting a lot of users willing to try Dfly it should be worth while! On Thu, 29 May 2008 00:14:26 -0400 (EDT) Justin C. Sherrill [EMAIL PROTECTED] wrote: James Frazer put together a nice site redesign based on some discussion we had here before. He sent me a copy of it all, and I'm only now catching up enough to show it: http://www.shiningsilence.com:81/ I'm happy with the layout and content; I'm looking for further suggestions for tweaks. If there's no show-stopping objections, I'd like to move the dragonflybsd.org site to this. -- Jost Tobias Springenberg [EMAIL PROTECTED] If you plan to send me any personal or sensitive information please use GnuPG! My public key can be found at: http://www-lehre.informatik.uos.de/~jspringe/jspringe.gpg
