Hey all, The FAQ for FreeBSD needs a significant amount of updating and changing. The first step in that process is to figure out what needs to be changed. If you can a take a moment and thoroughly review just one question and add your comments and concerns it would be immensely helpful. http://wiki.freebsd.org/ThwackAFAQ -- Eitan Adler
On Mon, Nov 19, 2012 at 9:44 AM, Eitan Adler <lists at eitanadler.com> wrote:> Hey all, > > The FAQ for FreeBSD needs a significant amount of updating and > changing. The first step in that process is to figure out what needs > to be changed. > > If you can a take a moment and thoroughly review just one > question and add your comments and concerns it > would be immensely helpful. > > http://wiki.freebsd.org/ThwackAFAQ > > -- > Eitan Adler >The following points may be inspected : 4.4.1. What kind of hard drives does FreeBSD support? Requires complete rewrite . 4.4.5. Which CD-ROM drives are supported by FreeBSD? 4.4.6. Which CD-RW drives are supported by FreeBSD? SATA devices ? DVD RW ? Blue-Ray RW ? burncd is not used any more . 6.3. Where can I get CDE for FreeBSD? CDE become open source ( LGPL ). http://en.wikipedia.org/wiki/Common_Desktop_Environment http://cdesktopenv.org/ http://sourceforge.net/projects/cdesktopenv/ 9.2. How do I move my system over to my huge new disk? 9.3. Will a "dangerously dedicated" disk endanger my health? 9.6. Why can I not edit the disk label on my ccd(4)? Requires some rewrite with respect do bsdinstall , because sysinstall is not used any more in new distributions . 11.7. What is a virtual console and how do I make more? 11.8. How do I access the virtual consoles from X? Application with KMS effects ? Thank you very much . Mehmet Erol Sanliturk
On Mon, Nov 19, 2012 at 9:44 AM, Eitan Adler <lists at eitanadler.com> wrote:> Hey all, > > The FAQ for FreeBSD needs a significant amount of updating and > changing. The first step in that process is to figure out what needs > to be changed. > > If you can a take a moment and thoroughly review just one > question and add your comments and concerns it > would be immensely helpful. > > http://wiki.freebsd.org/ThwackAFAQ > > -- > Eitan Adler >Bibliography http://www.amazon.com/Complete-FreeBSD-Documentation-Source/dp/0596005164/ref=sr_1_1?s=books&ie=UTF8&qid=1353351576&sr=1-1&keywords=The+Complete+FreeBSD The Complete FreeBSD: Documentation from the Source Product Details Paperback: 714 pages Publisher: O'Reilly Media; 4th edition (May 6, 2003) Language: English ISBN-10: 0596005164 ISBN-13: 978-0596005160 Thank you very much . Mehmet Erol Sanliturk
On 11/19/12 18:44, Eitan Adler wrote:> Hey all, > > The FAQ for FreeBSD needs a significant amount of updating and > changing. The first step in that process is to figure out what needs > to be changed. > > If you can a take a moment and thoroughly review just one > question and add your comments and concerns it > would be immensely helpful. > > http://wiki.freebsd.org/ThwackAFAQ >Under: removable-drives Would it be worth mentioning no /dev/xxxs1 is created when the device is plugged in after boot? E.G. 1: I have a Zip Drive which is /dev/da1. Everything is fine if a disk is in when I boot, but if I insert the media after boot, /dev/da1s1 is not there. I need to "mount /dev/da1 /mnt": this also fails, but now I have /dev/da1s1 and can mount it. E.G. 2: I connect my Android phone with an USB cable: it will be /dev/da7. Again I have no /dev/da7s1 until I "dd count=0 if=/dev/random of=/dev/da7". Same happens with CompactFlash, MMC, SD, etc... bye av.
On 11/19/12 18:44, Eitan Adler wrote:> Hey all, > > The FAQ for FreeBSD needs a significant amount of updating and > changing. The first step in that process is to figure out what needs > to be changed. > > If you can a take a moment and thoroughly review just one > question and add your comments and concerns it > would be immensely helpful. > > http://wiki.freebsd.org/ThwackAFAQ >Under serial-communication: Shouldn't USB to serial converters be mentioned? I believe the most common modems nowadays are GSM/3G, which usually plug in through USB, but in fact show up as a ttyU/cuaU. There are several working mobile modems; few are listed in the hardware compatibility page. bye av.
Please include some SSD recommended practice. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5764053.html Sent from the freebsd-stable mailing list archive at Nabble.com.
Why is my kernel so big? "As long as you make sure you follow the steps above, you can build your kernel normally, and you should notice a fairly large size decrease; most kernels tend to be around 1.5 MB to 2 MB." Not really, stripped amd64 kernel is about 9 MB currently... -- View this message in context: http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5764056.html Sent from the freebsd-stable mailing list archive at Nabble.com.
On 25 November 2012 13:28, Jakub Lach <jakub_lach at mailplus.pl> wrote:> Why is my kernel so big? > > "As long as you make sure you follow the steps above, you can build your > kernel normally, and you should notice a fairly large size decrease; most > kernels tend to be around 1.5 MB to 2 MB." > > Not really, stripped amd64 kernel is about 9 MB currently...Is this the size of GENERIC on release media? -- Eitan Adler
On 26 November 2012 11:25, Jakub Lach <jakub_lach at mailplus.pl> wrote:> Thanks! > > Regarding FAQ, some info about journalling should be added to > "Chapter 9 Disks, File Systems, and Boot Loaders", especially now, > when SU+J is default.which question does this apply to, or is this a request for new questions? -- Eitan Adler
On 11/26/12 17:25, Jakub Lach wrote:> Thanks! > > Regarding FAQ, some info about journalling should be added to > "Chapter 9 Disks, File Systems, and Boot Loaders", especially now, > when SU+J is default.Add to FAQ 9.4 Which partitions can safely use Soft Updates? I have heard that Soft Updates on / can cause problems. Journaled Soft Updates (SU+J) is now default on FreeBSD 9.x-RELEASE installs. This feature keeps a journal on soft updates which avoids a background filesystem check and speeds up a filesystem check during boot to a few seconds or less. For history and technical details see: http://jeffr-tech.livejournal.com/22716.html and http://www.*bsdcan*.org/2010/schedule/attachments/141_suj-slides.pdf This can also be enabled/disabled with tunefs -j enable | disable For more information see man 8 tunefs ---------------- New FAQ 9.28 I have heard about TRIM for Solid State Drives (SSD), is it supported by FreeBSD? The TRIM filesystem flag is very useful for devices that use flash-memory (SSD for instance) and support the BIO_DELETE command. This flag is not enabled by default and can be enabled/disabled with tunefs -t enable | disable For more information see man 8 tunefs -t enable | disable Turn on/off the TRIM enable flag. If enabled, and if the under- lying device supports the BIO_DELETE command, the file system will send a delete request to the underlying device for each freed block. The trim enable flag is typically set when the underlying device uses flash-memory as the device can use the delete command to pre-zero or at least avoid copying blocks that have been deleted. Important when using tunefs: This utility does not work on active file systems. To change the root file system, the system must be rebooted after the file system is tuned. FIlesystems have to be mounted read-only or not mounted at all
On 11/26/12 21:27, Bas Smeelen wrote:> On 11/26/12 17:25, Jakub Lach wrote: >> Thanks! >> >> Regarding FAQ, some info about journalling should be added to >> "Chapter 9 Disks, File Systems, and Boot Loaders", especially now, >> when SU+J is default.Please also add: SU+J does not work (yet) with dump on a live filesystem i.e. use snapshot. If you want to use snapshot (dump -L) then disable the soft updates journal for that filesystem> > Add to FAQ 9.4 Which partitions can safely use Soft Updates? I have > heard that Soft Updates on / can cause problems. > > Journaled Soft Updates (SU+J) is now default on FreeBSD 9.x-RELEASE > installs. > This feature keeps a journal on soft updates which avoids a background > filesystem check and speeds up a filesystem check during boot to a few > seconds or less. > For history and technical details see: > http://jeffr-tech.livejournal.com/22716.html > and > http://www.*bsdcan*.org/2010/schedule/attachments/141_suj-slides.pdf > > This can also be enabled/disabled with tunefs -j enable | disable > For more information see man 8 tunefs > > ---------------- > > New FAQ 9.28 I have heard about TRIM for Solid State Drives (SSD), is > it supported by FreeBSD? > > The TRIM filesystem flag is very useful for devices that use > flash-memory (SSD for instance) and support the BIO_DELETE command. > This flag is not enabled by default and can be enabled/disabled with > tunefs -t enable | disable > For more information see man 8 tunefs > -t enable | disable > Turn on/off the TRIM enable flag. If enabled, and if the > under- > lying device supports the BIO_DELETE command, the file > system > will send a delete request to the underlying device for each > freed block. The trim enable flag is typically set when the > underlying device uses flash-memory as the device can use > the > delete command to pre-zero or at least avoid copying > blocks that > have been deleted. > > Important when using tunefs: > This utility does not work on active file systems. To change the > root > file system, the system must be rebooted after the file system is > tuned. > > FIlesystems have to be mounted read-only or not mounted at all
On 26 November 2012, at 12:53, Bas Smeelen wrote:> On 11/26/12 21:27, Bas Smeelen wrote: >> On 11/26/12 17:25, Jakub Lach wrote: >>> Thanks! >>> >>> Regarding FAQ, some info about journalling should be added to >>> "Chapter 9 Disks, File Systems, and Boot Loaders", especially now, >>> when SU+J is default. > > Please also add: > SU+J does not work (yet) with dump on a live filesystem i.e. use snapshot. > If you want to use snapshot (dump -L) then disable the soft updates journal for that filesystemIt would be helpful to include information on how to do that during install (still trying to figure that out myself), and using the recover CD for when you forget to do it during install.
On Sun, 9 Dec 2012 08:03:03 -0800, Jakub Lach wrote: > Probably already axed, it was supported by > dev/sound/isa/mss.c and isa/snd/ad1848.c I think. Add text and items enhancing knowledge for later and latest kit, by all means, but - just speaking generally - "Careful with that axe, Eugene!" cheers, Ian
Exactly, I assumed mss.c was history already, because I looked only in modules, while there is plenty isa stuff in src/sys/dev/sound/isa still! /usr/src/sys/dev/sound/isa $ ls -a . ad1816.h mss.c sb16.c sndbuf_dma.c .. ess.c mss.h sb8.c ad1816.c gusc.c sb.h sbc.c Sorry. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5768186.html Sent from the freebsd-stable mailing list archive at Nabble.com.
I think HAST (hastd) is faq-worthy, as since release 9, it covers area previously vocally missed by some. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5768880.html Sent from the freebsd-stable mailing list archive at Nabble.com.
After _following_ recommendations (0600) in #xconsole-failure, there is xterm error as well as xconsole one still. So definitely something is amiss. On the side note, revisited "What security features are present in &os;" should mention ProPolice. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5769298.html Sent from the freebsd-stable mailing list archive at Nabble.com.
#missing-hw-float There is no longer npx option in 9 GENERIC i386 kernel, so there is nothing to delete accidentally. Traces of npx on my system (amd64) are: $ locate npx /usr/src/share/man/man4/man4.i386/npx.4 /usr/src/sys/i386/include/npx.h /usr/src/sys/i386/isa/npx.c /usr/src/sys/pc98/include/npx.h + NOTES content. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5769493.html Sent from the freebsd-stable mailing list archive at Nabble.com.