Re: text format
on groff i've used this cmd to format the text groff -Tascii normal.txt | sed 's/^/ /'$1 formatted.txt on nroff what would be the cmd? On Jun 12, 2012, at 4:44 AM, Polytropon wrote: On Tue, 12 Jun 2012 01:50:15 +, pwnedomina wrote: On 11-06-2012 23:40, Alejandro Imass wrote: On Mon, Jun 11, 2012 at 5:57 PM, i pwnpwnedom...@gmail.com wrote: hi, sometime ago i asked a question about how to format a text, some people told me to use groff, but i would like to know how was file http://ipwn.altervista.org/files/Stoll,%20Clifford%20-%20The%20Cuckoo%27s%20Egg.txt fomatted. thanks in advance. Most probably nroff / groff Take a look at the info from the authoring tools at rfceditor: http://www.rfc-editor.org/formatting.html *formatted. i've downloaded NroffEdit but when i open the ASCII text i want to convert/format, it says Not a valid nroff I-D what should i do? Erm, you did open the output file (as pointed to), _not_ the source file? You're trying to edit text in a document you've scanned. :-) The output text can be edited with any text editor (vi, emacs, joe, mcedit, whichever is your favourite), but it will be kept in this format as it _has been_ generated that way (past tense). In order to change formatting, you need the SOURCE file with the macros. (Compare: HTML files rendered by browser: output looks different than input; to change it, you need to edit the HTML source.) You can compare that to editing a man page: You need the page's source (like found in /usr/src/share/examples/mdoc/example.1). The text's SOURCE file would have looked similarly I assume. THAT is the input format you need for the NroffEdit WYSIWYG text editor. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... --- JID:ipwn#cih.ms HP:ipwn.altervista.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
text format
hi, sometime ago i asked a question about how to format a text, some people told me to use groff, but i would like to know how was file http://ipwn.altervista.org/files/Stoll,%20Clifford%20-%20The%20Cuckoo%27s%20Egg.txt fomatted. thanks in advance. --- JID:ipwn#cih.ms HP:ipwn.altervista.org PGP.sig Description: This is a digitally signed message part
ascii text format
algouth this is not a freebsd specific text, i need to format some texts under freebsd for they appear in the center of the page when opened in a browser, but i dont want to use HTML for format them, i just want to add tabulation to my *.txt. what software/tool can i use for format my *.txt? there is command on VIM like set textwidth but this is not suitable for me. any help i appreciate. i add an example on a temporary host for make sure all understand. (i need to format the text for he appear like the example good.txt) http://one.xthost.info/temphost/good.txt http://one.xthost.info/temphost/bad.txt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ascii text format
Jonathan McKeown wrote: On Friday 21 November 2008 12:49:16 pwn wrote: algouth this is not a freebsd specific text, i need to format some texts under freebsd for they appear in the center of the page when opened in a browser, but i dont want to use HTML for format them, i just want to add tabulation to my *.txt. what software/tool can i use for format my *.txt? there is command on VIM like set textwidth but this is not suitable for me. any help i appreciate. i add an example on a temporary host for make sure all understand. (i need to format the text for he appear like the example good.txt) http://one.xthost.info/temphost/good.txt http://one.xthost.info/temphost/bad.txt You seem to be fighting against your tools rather than working with them - the browser will strip out your whitespace and reflow your text anyway unless you prevent it somehow (pre tags?) so you might be better off just using HTML/CSS to control the format. However, you could look at various tools for processing text, depending exactly what you're trying to do: the manpages for fmt, groff, and pr might all offer some ideas. Jonathan yes, i want that the text appears displayed such as manpages like, how can i accomplish this task? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
freebsd installation order
immediately after the installation of FreeBSD what steps should be performed by order 1 - Configuring the FreeBSD Kernel 2 - The Cutting Edge 3 - Updating FreeBSD Is this the proper order? there is some set of rules to be followed post-installation? since, i do not find any reference mentioning the order that should be followed immediately after installation i would like to be informed if possible what will be the proper order to facilitate the maintenance of the operating system and the installation of new applications without conflicts or problems with ports. thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd installation order
andrew clarke escreveu: On Wed 2008-10-29 13:43:23 UTC+, pwn ([EMAIL PROTECTED]) wrote: immediately after the installation of FreeBSD what steps should be performed by order 1 - Configuring the FreeBSD Kernel 2 - The Cutting Edge 3 - Updating FreeBSD Is this the proper order? there is some set of rules to be followed post-installation? since, i do not find any reference mentioning the order that should be followed immediately after installation i would like to be informed if possible what will be the proper order to facilitate the maintenance of the operating system and the installation of new applications without conflicts or problems with ports. Re: Configuring the FreeBSD Kernel. Depending on your hardware and software requirements you may need to configure the supplied GENERIC kernel, or perhaps even build your own custom kernel and configure that. These days I think many people just use the GENERIC kernel and configure it from /boot/loader.conf. For a desktop machine it may just be a single entry to load a kernel module for your sound card. If you do use a GENERIC kernel this has the advantage that you can run freebsd-update whenever there are important security updates to the kernel itself, and then those updates become immediately active after a reboot. There is no need to rebuild the kernel, and very little downtime. Re: The Cutting Edge. In simple terms I would not bother with any of this unless you want to be actively involved in the development of the operating system. If you just want something that works reliably, stick with FreeBSD-RELEASE and use freebsd-update when you want to upgrade your FreeBSD version (eg. from 6.3 to 6.4). freebsd-update is brilliant and really makes updating fairly painless. Which leads me to... Re: Updating FreeBSD. Every FreeBSD sysadmin should read this. You should know how to install packages from the command-line using pkg_add (see the section called Installing Applications: Packages and Ports), and if you want to use the Ports system, learn how to use portsnap (another brilliant tool). Also, if you're using the Ports system (to build and install software from source code) I also recommend using portmaster, which isn't talked about in the Handbook, but is leaps and bounds over portupgrade (my personal opinion). thank you. Regards Andrew Andrew, nice answer very enlightening, the steps you mention im already familiar with them. at this moment im using a customised kernel, FreeBSD 7.1-PRERELEASE and all ports tree updated, i just want to know the ascending order that should be followed after an installation, thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd installation order
Jerry McAllister escreveu: On Wed, Oct 29, 2008 at 01:43:23PM +, pwn wrote: immediately after the installation of FreeBSD what steps should be performed by order 1 - Configuring the FreeBSD Kernel 2 - The Cutting Edge 3 - Updating FreeBSD Is this the proper order? I would say, first update FreeBSD src and rebuild. Then update the ports tree Then, if you must, configure a custom kernel - or if nothing is critical, just skip that. Then, install what ports you want and start running. As for cutting edge, do you mean tracking CURRENT? If so, if you are using it to get in on FreeBSD development, then do that now and daily.If it is a server for something, then don't do that. Just periodically or if some important patch comes put, pull in the latest security fixes with update. jerry just to clarify I would say, first update FreeBSD src and rebuild. Then update the ports tree Re:both this task can be done using csup or cvsup and using the samples provided in /usr/share/examples/cvsup/ Then, if you must, configure a custom kernel Re:(taking a look on hardware and editing generic for example) As for cutting edge, do you mean tracking CURRENT? Re:yes, but i dont want get in on FreeBSD dev team, so i guess STABLE is enought. there is some set of rules to be followed post-installation? since, i do not find any reference mentioning the order that should be followed immediately after installation i would like to be informed if possible what will be the proper order to facilitate the maintenance of the operating system and the installation of new applications without conflicts or problems with ports. thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd installation order
Jerry McAllister escreveu: On Wed, Oct 29, 2008 at 05:56:01PM +, pwn wrote: Jerry McAllister escreveu: On Wed, Oct 29, 2008 at 01:43:23PM +, pwn wrote: immediately after the installation of FreeBSD what steps should be performed by order 1 - Configuring the FreeBSD Kernel 2 - The Cutting Edge 3 - Updating FreeBSD Is this the proper order? I would say, first update FreeBSD src and rebuild. Then update the ports tree Then, if you must, configure a custom kernel - or if nothing is critical, just skip that. Then, install what ports you want and start running. As for cutting edge, do you mean tracking CURRENT? If so, if you are using it to get in on FreeBSD development, then do that now and daily.If it is a server for something, then don't do that. Just periodically or if some important patch comes put, pull in the latest security fixes with update. jerry just to clarify I would say, first update FreeBSD src and rebuild. Then update the ports tree Re:both this task can be done using csup or cvsup and using the samples provided in /usr/share/examples/cvsup/ Yup. That is what I use. Then, if you must, configure a custom kernel Re:(taking a look on hardware and editing generic for example) Unless you are running something where absolute maximum performance is critical, don't bother removing things from the kernel. Just limit customizing to adding those things you need that are not in by default - some drivers, maybe. As for cutting edge, do you mean tracking CURRENT? Re:yes, but i dont want get in on FreeBSD dev team, so i guess STABLE is enought. So, yup. You seem to have it. jerry on this page http://www.freebsd.org/doc/en/books/handbook/kernelconfig-building.html it says: Tip: By default, when you build a custom kernel, all kernel modules will be rebuilt as well. If you want to update a kernel faster or to build only custom modules, you should edit /etc/make.conf before starting to build the kernel: isnt enought editing the configuration file? part of the devices listed there use modules that do not interest me which can i delete or comment, why the use of /etc/make.conf ? also, its possible to automate all this pos-installation tasks in order to get things running fast and optimized? (i know /etc/make.conf can be used for this) but there are other methods that require spendless time? there is some set of rules to be followed post-installation? since, i do not find any reference mentioning the order that should be followed immediately after installation i would like to be informed if possible what will be the proper order to facilitate the maintenance of the operating system and the installation of new applications without conflicts or problems with ports. thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd installation order
Jerry McAllister escreveu: On Wed, Oct 29, 2008 at 06:39:16PM +, pwn wrote: Jerry McAllister escreveu: On Wed, Oct 29, 2008 at 05:56:01PM +, pwn wrote: Jerry McAllister escreveu: On Wed, Oct 29, 2008 at 01:43:23PM +, pwn wrote: immediately after the installation of FreeBSD what steps should be performed by order 1 - Configuring the FreeBSD Kernel 2 - The Cutting Edge 3 - Updating FreeBSD Is this the proper order? I would say, first update FreeBSD src and rebuild. Then update the ports tree Then, if you must, configure a custom kernel - or if nothing is critical, just skip that. Then, install what ports you want and start running. As for cutting edge, do you mean tracking CURRENT? If so, if you are using it to get in on FreeBSD development, then do that now and daily.If it is a server for something, then don't do that. Just periodically or if some important patch comes put, pull in the latest security fixes with update. jerry just to clarify I would say, first update FreeBSD src and rebuild. Then update the ports tree Re:both this task can be done using csup or cvsup and using the samples provided in /usr/share/examples/cvsup/ Yup. That is what I use. Then, if you must, configure a custom kernel Re:(taking a look on hardware and editing generic for example) Unless you are running something where absolute maximum performance is critical, don't bother removing things from the kernel. Just limit customizing to adding those things you need that are not in by default - some drivers, maybe. As for cutting edge, do you mean tracking CURRENT? Re:yes, but i dont want get in on FreeBSD dev team, so i guess STABLE is enought. So, yup. You seem to have it. jerry on this page http://www.freebsd.org/doc/en/books/handbook/kernelconfig-building.html it says: Tip: By default, when you build a custom kernel, all kernel modules will be rebuilt as well. If you want to update a kernel faster or to build only custom modules, you should edit /etc/make.conf before starting to build the kernel: It would take more time to edit /etc/make.conf than you would save in the kernel build.If you are doing lots of kernel builds while doing development, maybe then this would be worthwhile, but kernel builds do not take enough time on modern machines to bother speeding them up trivial amounts. Basically, this is saying you can fix things up so that it only builds those modules that you are changing when you do a rebuild and skips the others. This is not relevant to general system performance, just kernel builds. jerry i got it =), although, imho kernel builds always affect system performance.(maybe not in general) i was just asking myself a away for simplify at extreme this tasks that sometime can take many time, i guess after configure FreeBSD on a machine i should copy some configuration files like, /etc/make.conf and a custom kernel in attempt to avoid repetitive tasks. isnt enought editing the configuration file? part of the devices listed there use modules that do not interest me which can i delete or comment, why the use of /etc/make.conf ? also, its possible to automate all this pos-installation tasks in order to get things running fast and optimized? (i know /etc/make.conf can be used for this) but there are other methods that require spendless time? there is some set of rules to be followed post-installation? since, i do not find any reference mentioning the order that should be followed immediately after installation i would like to be informed if possible what will be the proper order to facilitate the maintenance of the operating system and the installation of new applications without conflicts or problems with ports. thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
