Re: gpart is junk
Am 28.09.12 11:31, schrieb Steffen Daode Nurpmeso: Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote: | but still not anywhere as readable as bsdlabel. | | | I did specifically say 'machine readable'. The XML is well-formed, |XML is stupid. everything you can do with XML can be better described |using ancient style text format Or, if all fails, YAML-is-JSON, which is much easier and cheaper to parse (than ML), but still a well-defined standard and, in comparison, human readable. These days I use Lua with its nice table-definition syntax for config files in many programs. Of course sandboxed, and with most functions turned off in the sandbox. The files are very readable, but of course you pay the price on including the Lua interpreter (although it's small). ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: gpart is junk
but still not anywhere as readable as bsdlabel. I did specifically say 'machine readable'. The XML is well-formed, XML is stupid. everything you can do with XML can be better described using ancient style text format ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: gpart is junk
On Fri, 28 Sep 2012 09:19:12 +0200 (CEST) Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote: but still not anywhere as readable as bsdlabel. I did specifically say 'machine readable'. The XML is well-formed, XML is stupid. everything you can do with XML can be better described using ancient style text format This statement is meaningless. XML *is* an 'ancient style text format' - only with a (very large) collection of standards describing the format, and an (even larger) collection of software for processing text in that format. And better is a judgment call. For instance, it's hard for me to consider any text format that doesn't support both external validation and autocompletion in popular editors as better than XML. Of course, those do require a schema of some kind, and I can't seem to find one for the document in kern.geom.confxml. mike -- Mike Meyer m...@mired.org http://www.mired.org/ Independent Software developer/SCM consultant, email for more information. O ascii ribbon campaign - stop html mail - www.asciiribbon.org ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: gpart is junk
Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote: | but still not anywhere as readable as bsdlabel. | | | I did specifically say 'machine readable'. The XML is well-formed, |XML is stupid. everything you can do with XML can be better described |using ancient style text format Or, if all fails, YAML-is-JSON, which is much easier and cheaper to parse (than ML), but still a well-defined standard and, in comparison, human readable. --steffen ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
RE: gpart is junk
On Wed, 26 Sep 2012, Desmond da Peoples wrote: On Mon, 17 Sep 2012, Daniel Eischen wrote: On Mon, 17 Sep 2012, Tom Evans wrote: On Sun, Sep 16, 2012 at 8:12 PM, Jeff Anton an...@hesiod.org wrote: ^E my point is that all this information needs to be together in one human and machine readable form. We need to be able to look at the whole picture of a device and say that makes sense then do it. And this shouldn't be from some GUI junk either. In a file, this information can be kept as a reference, as a confirmation that partitioning hasn't changed unexpectedly, and modified if needed in a clear manner. (Sorry to pick at just parts of your email^E) The current GEOM configuration is available from a sysctl in machine readable format - check out kern.geom.confxml. If you are concerned kern.geom.confxml is far from readable. kern.geom.conftxt is closer, but still not anywhere as readable as bsdlabel. about your partitions changing underneath you, storing and then comparing output from this sysctl gives you a simple way to determine what. A human readable version can be obtained from the gpart tool. IMHO, gpart and GEOM are fantastic. gpart is a much simpler tool to use than fdisk, and fully understands every kind of disk partitioning you can throw at it, whilst fdisk is only a tool for playing with MBR. The gpart man page explains clearly and concisely how to use it. GEOM provides a clear framework that anything can plug in to, from labels to whole disk encryption. It is not simple. All I want is Solaris format utility (partition and label). For someone such as myself- and others- who use PowerPC(64)/POWER systems, gpart is far from being junk. Fdisk is basically useless on an APM table or to even create such. You also have the choice of creating a partition scheme with a Linux live CD and then adjusting the partition types with gpart. You can use gparted. Maybe you haven't noticed that gpart givess you the option of different partition tables from the start. gpart is a low-level tool to be used by someone who knows exactly what they are doing. It is not useful for someone who just wants to partition and label a disk and doesn't have hours of free time to read and understand gpart. I want the capability of the old installer. Where is that? Ahh, I found it - I guess it is /usr/sbin/bsdinstall :-) -- DE ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: gpart is junk
On Thu, Sep 27, 2012 at 3:05 PM, Daniel Eischen deisc...@freebsd.org wrote: On Mon, 17 Sep 2012, Tom Evans wrote: The current GEOM configuration is available from a sysctl in machine readable format - check out kern.geom.confxml. If you are concerned kern.geom.confxml is far from readable. kern.geom.conftxt is closer, but still not anywhere as readable as bsdlabel. I did specifically say 'machine readable'. The XML is well-formed, contains all relevant information, and is unarguably machine readable. Cheers Tom ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
RE: gpart is junk
Date: Mon, 17 Sep 2012 08:54:41 -0400 From: deisc...@freebsd.org To: tevans...@googlemail.com CC: an...@hesiod.org; freebsd-hackers@freebsd.org Subject: Re: gpart is junk On Mon, 17 Sep 2012, Tom Evans wrote: On Sun, Sep 16, 2012 at 8:12 PM, Jeff Anton an...@hesiod.org wrote: … my point is that all this information needs to be together in one human and machine readable form. We need to be able to look at the whole picture of a device and say that makes sense then do it. And this shouldn't be from some GUI junk either. In a file, this information can be kept as a reference, as a confirmation that partitioning hasn't changed unexpectedly, and modified if needed in a clear manner. (Sorry to pick at just parts of your email…) The current GEOM configuration is available from a sysctl in machine readable format - check out kern.geom.confxml. If you are concerned about your partitions changing underneath you, storing and then comparing output from this sysctl gives you a simple way to determine what. A human readable version can be obtained from the gpart tool. IMHO, gpart and GEOM are fantastic. gpart is a much simpler tool to use than fdisk, and fully understands every kind of disk partitioning you can throw at it, whilst fdisk is only a tool for playing with MBR. The gpart man page explains clearly and concisely how to use it. GEOM provides a clear framework that anything can plug in to, from labels to whole disk encryption. It is not simple. All I want is Solaris format utility (partition and label). -- DE For someone such as myself- and others- who use PowerPC(64)/POWER systems, gpart is far from being junk. Fdisk is basically useless on an APM table or to even create such. You also have the choice of creating a partition scheme with a Linux live CD and then adjusting the partition types with gpart. You can use gparted. Maybe you haven't noticed that gpart givess you the option of different partition tables from the start. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: gpart is junk
On 16.09.2012 23:12, Jeff Anton wrote: The whole geom system may be very important and may be the way to move forward. But if it is so important, it's important to bring forward all the important functionality that we know from the past, i.e. fdisk and bsdlabel or their real useful equivalents well documented. Hi, Jeff. Sometimes to move forward you need to learn something new and not just typing familiar old commands. * There are several different GEOM classes in use in the 7.x and 8.0+. GEOM_PART class is the default beginning from 8.0, in the previous FreeBSD versions another geom classes used. * gpart(8) utility works with GEOM objects of class GEOM_PART. If there is no objects - no one to work with. * You need to read gpart(8) about -f flag and commit/undo/show commands. -- WBR, Andrey V. Elsukov signature.asc Description: OpenPGP digital signature
Re: gpart is junk
On Sun, Sep 16, 2012 at 8:12 PM, Jeff Anton an...@hesiod.org wrote: … my point is that all this information needs to be together in one human and machine readable form. We need to be able to look at the whole picture of a device and say that makes sense then do it. And this shouldn't be from some GUI junk either. In a file, this information can be kept as a reference, as a confirmation that partitioning hasn't changed unexpectedly, and modified if needed in a clear manner. (Sorry to pick at just parts of your email…) The current GEOM configuration is available from a sysctl in machine readable format - check out kern.geom.confxml. If you are concerned about your partitions changing underneath you, storing and then comparing output from this sysctl gives you a simple way to determine what. A human readable version can be obtained from the gpart tool. IMHO, gpart and GEOM are fantastic. gpart is a much simpler tool to use than fdisk, and fully understands every kind of disk partitioning you can throw at it, whilst fdisk is only a tool for playing with MBR. The gpart man page explains clearly and concisely how to use it. GEOM provides a clear framework that anything can plug in to, from labels to whole disk encryption. Cheers Tom ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: gpart is junk
IMHO, gpart and GEOM are fantastic. anyway it is MUCH easier and faster to edit disklabels with bsdlabel -e than with gpart. Unfortunately since some time bsdlabel cannot edit labels if ANY of partitions are open. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: gpart is junk
On 17 Sep 2012 12:58, Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote: IMHO, gpart and GEOM are fantastic. anyway it is MUCH easier and faster to edit disklabels with bsdlabel -e than with gpart. Unfortunately since some time bsdlabel cannot edit labels if ANY of partitions are open. You may be more familiar with manually editing slice tables, but it is very easy to mess up. Chris ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: gpart is junk
On Mon, 17 Sep 2012, Tom Evans wrote: On Sun, Sep 16, 2012 at 8:12 PM, Jeff Anton an...@hesiod.org wrote: … my point is that all this information needs to be together in one human and machine readable form. We need to be able to look at the whole picture of a device and say that makes sense then do it. And this shouldn't be from some GUI junk either. In a file, this information can be kept as a reference, as a confirmation that partitioning hasn't changed unexpectedly, and modified if needed in a clear manner. (Sorry to pick at just parts of your email…) The current GEOM configuration is available from a sysctl in machine readable format - check out kern.geom.confxml. If you are concerned about your partitions changing underneath you, storing and then comparing output from this sysctl gives you a simple way to determine what. A human readable version can be obtained from the gpart tool. IMHO, gpart and GEOM are fantastic. gpart is a much simpler tool to use than fdisk, and fully understands every kind of disk partitioning you can throw at it, whilst fdisk is only a tool for playing with MBR. The gpart man page explains clearly and concisely how to use it. GEOM provides a clear framework that anything can plug in to, from labels to whole disk encryption. It is not simple. All I want is Solaris format utility (partition and label). -- DE___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
