Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Help review the FAQ
75 views
Skip to first unread message
Eitan Adler
Nov 19, 2012, 12:44:18 PM11/19/12
to
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
_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stabl...@freebsd.org"
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
_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stabl...@freebsd.org"
Mehmet Erol Sanliturk
Nov 19, 2012, 1:52:14 PM11/19/12
to
On Mon, Nov 19, 2012 at 9:44 AM, Eitan Adler <li...@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 :
> 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
>
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
Mehmet Erol Sanliturk
Nov 19, 2012, 2:04:03 PM11/19/12
to
> 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
>
> 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
>
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
Andrea Venturoli
Nov 19, 2012, 2:55:31 PM11/19/12
to
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:
> 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
>
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.
Andrea Venturoli
Nov 19, 2012, 2:46:13 PM11/19/12
to
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
>
> 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
>
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.
Eitan Adler
Nov 20, 2012, 2:25:50 PM11/20/12
to
On 19 November 2012 15:07, Aldis Berjoza <grau...@yandex.ru> wrote:
>
>
> 19.11.2012, 22:04, "Andrea Venturoli" <m...@netfence.it>:
I've migrated the comments on the mailing list to the wiki and will
working on fixing them shortly. Content patches are appreciated but
not required. Ideally every row on the wiki will be either green or
red.
Fixing the content is a very long term project.
--
Eitan Adler
>
>
> 19.11.2012, 22:04, "Andrea Venturoli" <m...@netfence.it>:
>> 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
...
>>
>>> 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
I've migrated the comments on the mailing list to the wiki and will
working on fixing them shortly. Content patches are appreciated but
not required. Ideally every row on the wiki will be either green or
red.
Fixing the content is a very long term project.
--
Eitan Adler
Andrea Venturoli
Nov 23, 2012, 8:54:24 AM11/23/12
to
On 11/23/12 10:25, Lars Engels wrote:
> I've seen that on almost every USB MP3 player, Android mobile phones and
> on other USB devices that export an internal memory card.
BTW, my disk drive is SCSI attached, so it's not an USB-only issue.
> But it would be really really really great if someone(TM) would fix it,
> so the workaround is no longer needed...
Yep, that would be really great.
> I've seen that on almost every USB MP3 player, Android mobile phones and
> on other USB devices that export an internal memory card.
BTW, my disk drive is SCSI attached, so it's not an USB-only issue.
> But it would be really really really great if someone(TM) would fix it,
> so the workaround is no longer needed...
Yep, that would be really great.
Lars Engels
Nov 23, 2012, 9:29:09 AM11/23/12
to
Am 23.11.2012 14:54, schrieb Andrea Venturoli:
> On 11/23/12 10:25, Lars Engels wrote:
>> I've seen that on almost every USB MP3 player, Android mobile phones
>> and
>> on other USB devices that export an internal memory card.
>
> BTW, my disk drive is SCSI attached, so it's not an USB-only issue.
So, it's probably a cam layer issue.
> On 11/23/12 10:25, Lars Engels wrote:
>> I've seen that on almost every USB MP3 player, Android mobile phones
>> and
>> on other USB devices that export an internal memory card.
>
> BTW, my disk drive is SCSI attached, so it's not an USB-only issue.
Jakub Lach
Nov 25, 2012, 1:18:21 PM11/25/12
to
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.
--
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.
Jakub Lach
Nov 25, 2012, 1:28:01 PM11/25/12
to
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
"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.
Jakub Lach
Nov 25, 2012, 1:31:11 PM11/25/12
to
Why does Opera take so long to start?
"The usual answer is that DNS on your system is misconfigured. Opera perform
DNS checks when starting up. The browser will not appear on your desktop
until the program either gets a response or determines that the system has
no network connection."
Needs rechecking, I doubt it's still applicable.
--
View this message in context: http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5764058.html
"The usual answer is that DNS on your system is misconfigured. Opera perform
DNS checks when starting up. The browser will not appear on your desktop
until the program either gets a response or determines that the system has
no network connection."
Needs rechecking, I doubt it's still applicable.
--
View this message in context: http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5764058.html
Eitan Adler
Nov 25, 2012, 9:35:54 PM11/25/12
to
On 25 November 2012 13:28, Jakub Lach <jakub...@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?
> 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...
--
Eitan Adler
Jakub Lach
Nov 26, 2012, 9:49:56 AM11/26/12
to
Absolutely not, it's a heavily stripped custom kernel on this machine on
/boot/.
I was pointing to that, if my kernel is 9 MB, there's no way GENERIC could
be
1.5-2.5 MB.
Sorry for confusion.
--
View this message in context: http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5764313.html
/boot/.
I was pointing to that, if my kernel is 9 MB, there's no way GENERIC could
be
1.5-2.5 MB.
Sorry for confusion.
--
View this message in context: http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5764313.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
Volodymyr Kostyrko
Nov 26, 2012, 10:26:55 AM11/26/12
to
26.11.2012 16:49, Jakub Lach:
> ls -la /boot/kernel/kernel
-r-xr-xr-x 1 root wheel 5757970 Nov 26 10:57 /boot/kernel/kernel
However it's very hard to strip kernel further and make it usable for
all machines.
> I was pointing to that, if my kernel is 9 MB, there's no way GENERIC could
> be
> 1.5-2.5 MB.
That's true...
--
Sphinx of black quartz, judge my vow.
> Absolutely not, it's a heavily stripped custom kernel on this machine on
> /boot/.
Do you call this heavily stripped? :)
> /boot/.
> ls -la /boot/kernel/kernel
-r-xr-xr-x 1 root wheel 5757970 Nov 26 10:57 /boot/kernel/kernel
However it's very hard to strip kernel further and make it usable for
all machines.
> I was pointing to that, if my kernel is 9 MB, there's no way GENERIC could
> be
> 1.5-2.5 MB.
--
Sphinx of black quartz, judge my vow.
Bas Smeelen
Nov 26, 2012, 10:34:59 AM11/26/12
to
On 11/26/2012 04:26 PM, Volodymyr Kostyrko wrote:
> 26.11.2012 16:49, Jakub Lach:
>> Absolutely not, it's a heavily stripped custom kernel on this machine on
>> /boot/.
>
> Do you call this heavily stripped? :)
>
> > ls -la /boot/kernel/kernel
> -r-xr-xr-x 1 root wheel 5757970 Nov 26 10:57 /boot/kernel/kernel
>
> However it's very hard to strip kernel further and make it usable for all
> machines.
>
>> I was pointing to that, if my kernel is 9 MB, there's no way GENERIC could
>> be
>> 1.5-2.5 MB.
>
> That's true...
>
i386 kernel with the only devices I need without debug symbols is 4.5MB on
> 26.11.2012 16:49, Jakub Lach:
>> Absolutely not, it's a heavily stripped custom kernel on this machine on
>> /boot/.
>
> Do you call this heavily stripped? :)
>
> > ls -la /boot/kernel/kernel
> -r-xr-xr-x 1 root wheel 5757970 Nov 26 10:57 /boot/kernel/kernel
>
> However it's very hard to strip kernel further and make it usable for all
> machines.
>
>> I was pointing to that, if my kernel is 9 MB, there's no way GENERIC could
>> be
>> 1.5-2.5 MB.
>
> That's true...
>
7.4-STABLE
fb1:/home/Freebee % uname -a
FreeBSD fb1 7.4-STABLE FreeBSD 7.4-STABLE #7: Mon Nov 26 11:27:42 CET
2012 root@fb1:/usr/obj/usr/src/sys/FB1 i386
fb1:/home/Freebee % ls -lh /boot/kernel/kernel
-r-xr-xr-x 1 root wheel 4.6M Nov 26 11:27 /boot/kernel/kernel
amd64 same story on 9.1-RC3 is 6.3MB
[Freebee@sys:~] $ uname -a
FreeBSD sys 9.1-RC3 FreeBSD 9.1-RC3 #0: Wed Oct 31 11:56:55 CET 2012
root@sys:/usr/obj/usr/src/sys/SYS amd64
[Freebee@sys:~] $ ls -hl /boot/kernel/kernel
-r-xr-xr-x 1 root wheel 6.3M Oct 31 11:56 /boot/kernel/kernel
Jakub Lach
Nov 26, 2012, 10:55:07 AM11/26/12
to
Again, sorry for confusion :)
ls -la /boot/kernel/kernel
-r-xr-xr-x 1 root wheel 5842267 25 lis 18:32 /boot/kernel/kernel
Yes, it could be artificially smaller still, but delegating to modules
things
I would load witch each startup would be absurd.
First size was whole directory with modules.
--
View this message in context: http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5764351.html
ls -la /boot/kernel/kernel
-r-xr-xr-x 1 root wheel 5842267 25 lis 18:32 /boot/kernel/kernel
Yes, it could be artificially smaller still, but delegating to modules
things
I would load witch each startup would be absurd.
First size was whole directory with modules.
--
View this message in context: http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5764351.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
Jakub Lach
Nov 26, 2012, 10:57:15 AM11/26/12
to
As a reminder, this isn't a contest in kernel size :)
More useful would be if somebody would check GENERIC
on i386/amd64 for FAQ update.
--
View this message in context: http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5764353.html
More useful would be if somebody would check GENERIC
on i386/amd64 for FAQ update.
--
View this message in context: http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5764353.html
Miroslav Lachman
Nov 26, 2012, 11:12:06 AM11/26/12
to
Jakub Lach wrote:
> As a reminder, this isn't a contest in kernel size :)
>
> More useful would be if somebody would check GENERIC
> on i386/amd64 for FAQ update.
FreeBSD 8.3-RELEASE amd64 GENERIC
> As a reminder, this isn't a contest in kernel size :)
>
> More useful would be if somebody would check GENERIC
> on i386/amd64 for FAQ update.
> ls -lh /boot/kernel/kernel
-r-xr-xr-x 1 root wheel 12M May 8 2012 /boot/kernel/kernel
FreeBSD 8.2-RELEASE-p3 i386 GENERIC
> ls -lh /boot/kernel/kernel
-r-xr-xr-x 1 root wheel 11M Jan 8 2012 /boot/kernel/kernel
FreeBSD 9.0-RELEASE amd64 GENERIC
> ls -lh /boot/kernel/kernel
-r-xr-xr-x 1 root wheel 14M Jan 3 2012 /boot/kernel/kernel
Miroslav Lachman
Jakub Lach
Nov 26, 2012, 11:25:22 AM11/26/12
to
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.
--
View this message in context: http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5764360.html
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.
--
View this message in context: http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5764360.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
Eitan Adler
Nov 26, 2012, 11:50:43 AM11/26/12
to
On 26 November 2012 11:25, Jakub Lach <jakub...@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?
> 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.
--
Eitan Adler
Bas Smeelen
Nov 26, 2012, 3:27:02 PM11/26/12
to
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
> 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.
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
Bas Smeelen
Nov 26, 2012, 3:33:38 PM11/26/12
to
On 11/26/12 16:57, Jakub Lach wrote:
> As a reminder, this isn't a contest in kernel size :)
>
Didn't mean to, I just put it there to state that 1.5 - 2.5 MB for a
> As a reminder, this isn't a contest in kernel size :)
>
GENERIC kernel is not appropriate anymore.
> More useful would be if somebody would check GENERIC
> on i386/amd64 for FAQ update.
Thanks Miroslav Lachman for the reply with the correct sizes for GENERIC
> on i386/amd64 for FAQ update.
kernels.
Change FAQ 8.3 Why is my kernel so big?
Nowadays kernels are compiled in /debug mode by default/. Kernels built
in debug mode contain many symbols that are used for debugging, thus
greatly increasing the size of the kernel. Note that there will be
little or no performance decrease from running a debug kernel, and it is
useful in case of a system panic.
However....
Bas Smeelen
Nov 26, 2012, 3:53:23 PM11/26/12
to
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:
> 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.
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
Jakub Lach
Nov 26, 2012, 3:58:02 PM11/26/12
to
This may be request for new questions, or this can be supplemented
partially in hardware ones I think;
- new default partition layout and it's justification (single partition
nowadays, I believe?)
- default block size and it's justification (is it 4K? why?)
- NCQ support with ada/ahci
- ahci power managment [*]
- why or why not default settings are just fine with SSD
(regarding journaling, SU, trim and what not).
Sorry for requesting content rather than reviewing existing
one, but I think this info important for modern FAQ.
* power-management-support description is lacking,
apm is obsolete, no mention of ahci.
I think this is more of less complete sketch of power
saving facilities in FreeBSD-
http://wiki.freebsd.org/TuningPowerConsumption
--
View this message in context: http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5764423.html
partially in hardware ones I think;
- new default partition layout and it's justification (single partition
nowadays, I believe?)
- default block size and it's justification (is it 4K? why?)
- NCQ support with ada/ahci
- ahci power managment [*]
- why or why not default settings are just fine with SSD
(regarding journaling, SU, trim and what not).
Sorry for requesting content rather than reviewing existing
one, but I think this info important for modern FAQ.
* power-management-support description is lacking,
apm is obsolete, no mention of ahci.
I think this is more of less complete sketch of power
saving facilities in FreeBSD-
http://wiki.freebsd.org/TuningPowerConsumption
--
View this message in context: http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5764423.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
Doug Hardie
Nov 26, 2012, 4:02:48 PM11/26/12
to
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 filesystem
Miroslav Lachman
Nov 26, 2012, 4:15:27 PM11/26/12
to
Bas Smeelen wrote:
> On 11/26/12 16:57, Jakub Lach wrote:
[...]
> On 11/26/12 16:57, Jakub Lach wrote:
> Thanks Miroslav Lachman for the reply with the correct sizes for GENERIC
> kernels.
>
> Change FAQ 8.3 Why is my kernel so big?
>
> Nowadays kernels are compiled in /debug mode by default/. Kernels built
> in debug mode contain many symbols that are used for debugging, thus
> greatly increasing the size of the kernel. Note that there will be
> little or no performance decrease from running a debug kernel, and it is
> useful in case of a system panic.
>
> However....
I think that debug symbols are in another files (*.symbols)
> kernels.
>
> Change FAQ 8.3 Why is my kernel so big?
>
> Nowadays kernels are compiled in /debug mode by default/. Kernels built
> in debug mode contain many symbols that are used for debugging, thus
> greatly increasing the size of the kernel. Note that there will be
> little or no performance decrease from running a debug kernel, and it is
> useful in case of a system panic.
>
> However....
FreeBSD 8.3-RELEASE amd64 GENERIC
> ls -lh /boot/kernel/kernel*
-r-xr-xr-x 1 root wheel 12M May 8 2012 /boot/kernel/kernel
-r-xr-xr-x 1 root wheel 50M May 8 2012 /boot/kernel/kernel.symbols
So a kernel alone has 12MB, with debug symbols 62MB (12+50).
And all *.symbols files can be deleted (if more space on /boot is needed)
I don't know how it should be mentioned in FAQ.
Miroslav Lachman
Bas Smeelen
Nov 26, 2012, 4:20:19 PM11/26/12
to
On 11/26/12 22:02, Doug Hardie wrote:
> 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 filesystem
> It 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.
Right now, when installing a new system it's easiest to reboot to single
> 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 filesystem
> It 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.
user mode after the install and tunefs -j disable 'the filesystems' to
disable journaling of soft updates.
If you want to accomplish this during the install, choose shell at the
disk partitioning part and add slices and/or partitions with gpart and
then newfs them with the appropriate options, then mount them on /mnt
and the appropriate places beneath and continue the install by quitting
the shell.
There are some nice entries on http://wiki.freebsd.org/RootOnZFS
Just substitute the ZFS stuff with the easier gpart and then newfs -U
etc... then make sure the filesystems are mounted under /mnt and
continue the installation.
I hope that I will not confuse you too much with the proposed solution
i.e. use these resources as a guideline. Else see reboot to single user
mode after install above and tunefs
Bas Smeelen
Nov 26, 2012, 4:27:32 PM11/26/12
to
On 11/26/12 22:15, Miroslav Lachman wrote:
> Bas Smeelen wrote:
>> On 11/26/12 16:57, Jakub Lach wrote:
> [...]
>> Thanks Miroslav Lachman for the reply with the correct sizes for GENERIC
>> kernels.
>>
>> Change FAQ 8.3 Why is my kernel so big?
>>
>> Nowadays kernels are compiled in /debug mode by default/. Kernels built
>> in debug mode contain many symbols that are used for debugging, thus
>> greatly increasing the size of the kernel. Note that there will be
>> little or no performance decrease from running a debug kernel, and it is
>> useful in case of a system panic.
>>
>> However....
>
> I think that debug symbols are in another files (*.symbols)
>
> FreeBSD 8.3-RELEASE amd64 GENERIC
>
> > ls -lh /boot/kernel/kernel*
> -r-xr-xr-x 1 root wheel 12M May 8 2012 /boot/kernel/kernel
> -r-xr-xr-x 1 root wheel 50M May 8 2012 /boot/kernel/kernel.symbols
>
> So a kernel alone has 12MB, with debug symbols 62MB (12+50).
> And all *.symbols files can be deleted (if more space on /boot is needed)
> I don't know how it should be mentioned in FAQ.
You are right.
> Bas Smeelen wrote:
>> On 11/26/12 16:57, Jakub Lach wrote:
> [...]
>> Thanks Miroslav Lachman for the reply with the correct sizes for GENERIC
>> kernels.
>>
>> Change FAQ 8.3 Why is my kernel so big?
>>
>> Nowadays kernels are compiled in /debug mode by default/. Kernels built
>> in debug mode contain many symbols that are used for debugging, thus
>> greatly increasing the size of the kernel. Note that there will be
>> little or no performance decrease from running a debug kernel, and it is
>> useful in case of a system panic.
>>
>> However....
>
> I think that debug symbols are in another files (*.symbols)
>
> FreeBSD 8.3-RELEASE amd64 GENERIC
>
> > ls -lh /boot/kernel/kernel*
> -r-xr-xr-x 1 root wheel 12M May 8 2012 /boot/kernel/kernel
> -r-xr-xr-x 1 root wheel 50M May 8 2012 /boot/kernel/kernel.symbols
>
> So a kernel alone has 12MB, with debug symbols 62MB (12+50).
> And all *.symbols files can be deleted (if more space on /boot is needed)
> I don't know how it should be mentioned in FAQ.
From the FAQ I understand with 'kernel so big' the contents of the
/boot/kernel directory is being referred to as a whole?
Thus disabling (commenting) makeoptions DEBUG=-g (which is default the
last couple of releases, since 7?) and then rebuilding and installing
the kernel you get rid if them 'the right way'
So FAQ 8.3 is still right just changing that nowadays it's default for
GENERIC to be build with the debug symbols.
Bas Smeelen
Nov 26, 2012, 4:31:05 PM11/26/12
to
On 11/26/12 22:20, Bas Smeelen wrote:
> On 11/26/12 22:02, Doug Hardie wrote:
>> 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 filesystem
>> It 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.
>
> Right now, when installing a new system it's easiest to reboot to
> single user mode after the install and tunefs -j disable 'the
> filesystems' to disable journaling of soft updates.
When changing the root ( / ) filesystem in single user mode, reboot
> On 11/26/12 22:02, Doug Hardie wrote:
>> 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 filesystem
>> It 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.
>
> Right now, when installing a new system it's easiest to reboot to
> single user mode after the install and tunefs -j disable 'the
> filesystems' to disable journaling of soft updates.
immediately after disabling the soft updates journal otherwise it will
still be enabled. No need for a rescue cd/usb here.
Schaich Alonso
Nov 26, 2012, 4:27:16 PM11/26/12
to
On 2012-11-26 (Monday) 22:15:27 Miroslav Lachman wrote:
> [...]
information IMO is a cleaner and more preferable solution then deleting the
files, and it also reduces the amount of storage space needed for /usr/obj (or
whereever else the kernel's built) by about 1GB on STABLE-9.
Schaich Alonso
> [...]
>
> So a kernel alone has 12MB, with debug symbols 62MB (12+50).
> And all *.symbols files can be deleted (if more space on /boot is needed)
> I don't know how it should be mentioned in FAQ.
>
> Miroslav Lachman
Specifying WITHOUT_KERNEL_SYMBOLS=YES in src.conf to not generate debug
> So a kernel alone has 12MB, with debug symbols 62MB (12+50).
> And all *.symbols files can be deleted (if more space on /boot is needed)
> I don't know how it should be mentioned in FAQ.
>
> Miroslav Lachman
information IMO is a cleaner and more preferable solution then deleting the
files, and it also reduces the amount of storage space needed for /usr/obj (or
whereever else the kernel's built) by about 1GB on STABLE-9.
Schaich Alonso
Bas Smeelen
Nov 26, 2012, 4:51:00 PM11/26/12
to
On 11/26/12 22:27, Schaich Alonso wrote:
> On 2012-11-26 (Monday) 22:15:27 Miroslav Lachman wrote:
>> [...]
>>
>> So a kernel alone has 12MB, with debug symbols 62MB (12+50).
>> And all *.symbols files can be deleted (if more space on /boot is needed)
>> I don't know how it should be mentioned in FAQ.
>>
>> Miroslav Lachman
> Specifying WITHOUT_KERNEL_SYMBOLS=YES in src.conf to not generate debug
> information IMO is a cleaner and more preferable solution then deleting the
> files, and it also reduces the amount of storage space needed for /usr/obj (or
> whereever else the kernel's built) by about 1GB on STABLE-9.
Thanks for this (man 5 src.conf)
> On 2012-11-26 (Monday) 22:15:27 Miroslav Lachman wrote:
>> [...]
>>
>> So a kernel alone has 12MB, with debug symbols 62MB (12+50).
>> And all *.symbols files can be deleted (if more space on /boot is needed)
>> I don't know how it should be mentioned in FAQ.
>>
>> Miroslav Lachman
> Specifying WITHOUT_KERNEL_SYMBOLS=YES in src.conf to not generate debug
> information IMO is a cleaner and more preferable solution then deleting the
> files, and it also reduces the amount of storage space needed for /usr/obj (or
> whereever else the kernel's built) by about 1GB on STABLE-9.
I guess this way is preferred instead of customizing the kernel
configuration file?
From the manpage I understand the symbol files will not get installed,
but will still be build.
To decrease building time, one should modify the kernel configuration
file anyway?
Bas Smeelen
Nov 26, 2012, 5:09:42 PM11/26/12
to
On 11/20/12 20:25, Eitan Adler wrote:
> On 19 November 2012 15:07, Aldis Berjoza <grau...@yandex.ru> wrote:
>>
>> 19.11.2012, 22:04, "Andrea Venturoli" <m...@netfence.it>:
>>> 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
> ...
>
> I've migrated the comments on the mailing list to the wiki and will
> working on fixing them shortly. Content patches are appreciated but
> not required. Ideally every row on the wiki will be either green or
> red.
>
> Fixing the content is a very long term project.
>
>
Probable addition
8.8 I get a lot of 'spurious interrupts detected' messages on a modified
i386 build kernel and my computer does not work right. What did I do wrong?
You have a single processor computer, build your own customized kernel
and disabled
options SMP (multiprocessor).
Probably you also disabled the line below,
device apic # I/O APIC
This is code for the advanced programmable interrupt controller which
also controls interrupts for your attached devices, being ethernet cards
and others.
Do not disable this device.
> On 19 November 2012 15:07, Aldis Berjoza <grau...@yandex.ru> wrote:
>>
>> 19.11.2012, 22:04, "Andrea Venturoli" <m...@netfence.it>:
>>> 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
> ...
>
> I've migrated the comments on the mailing list to the wiki and will
> working on fixing them shortly. Content patches are appreciated but
> not required. Ideally every row on the wiki will be either green or
> red.
>
> Fixing the content is a very long term project.
>
>
Probable addition
8.8 I get a lot of 'spurious interrupts detected' messages on a modified
i386 build kernel and my computer does not work right. What did I do wrong?
You have a single processor computer, build your own customized kernel
and disabled
options SMP (multiprocessor).
Probably you also disabled the line below,
device apic # I/O APIC
This is code for the advanced programmable interrupt controller which
also controls interrupts for your attached devices, being ethernet cards
and others.
Do not disable this device.
Andrea Venturoli
Nov 27, 2012, 2:44:29 AM11/27/12
to
On 11/26/12 23:09, Bas Smeelen wrote:
> Probable addition
> 8.8 I get a lot of 'spurious interrupts detected' messages on a modified
> i386 build kernel and my computer does not work right. What did I do wrong?
>
> You have a single processor computer, build your own customized kernel
> and disabled
> options SMP (multiprocessor).
> Probably you also disabled the line below,
> device apic # I/O APIC
>
> This is code for the advanced programmable interrupt controller which
> also controls interrupts for your attached devices, being ethernet cards
> and others.
> Do not disable this device.
While I don't know about apic, there used to be "KEEP THIS!!!" comments
> Probable addition
> 8.8 I get a lot of 'spurious interrupts detected' messages on a modified
> i386 build kernel and my computer does not work right. What did I do wrong?
>
> You have a single processor computer, build your own customized kernel
> and disabled
> options SMP (multiprocessor).
> Probably you also disabled the line below,
> device apic # I/O APIC
>
> This is code for the advanced programmable interrupt controller which
> also controls interrupts for your attached devices, being ethernet cards
> and others.
> Do not disable this device.
in GENERIC's conf file.
I guess this would be more on the spot than a FAQ you'd read *after*
removing this.
Just my 2c.
bye
av.
Bas Smeelen
Nov 27, 2012, 2:55:29 AM11/27/12
to
On 11/27/2012 08:44 AM, Andrea Venturoli wrote:
> On 11/26/12 23:09, Bas Smeelen wrote:
>
>> Probable addition
>> 8.8 I get a lot of 'spurious interrupts detected' messages on a modified
>> i386 build kernel and my computer does not work right. What did I do wrong?
>>
>> You have a single processor computer, build your own customized kernel
>> and disabled
>> options SMP (multiprocessor).
>> Probably you also disabled the line below,
>> device apic # I/O APIC
>>
>> This is code for the advanced programmable interrupt controller which
>> also controls interrupts for your attached devices, being ethernet cards
>> and others.
>> Do not disable this device.
>
> While I don't know about apic, there used to be "KEEP THIS!!!" comments in
> GENERIC's conf file.
> I guess this would be more on the spot than a FAQ you'd read *after*
> removing this.
>
> Just my 2c.
>
> bye
> av.
You're probably right. It must have been before 6.3-RELEASE, where there are
> On 11/26/12 23:09, Bas Smeelen wrote:
>
>> Probable addition
>> 8.8 I get a lot of 'spurious interrupts detected' messages on a modified
>> i386 build kernel and my computer does not work right. What did I do wrong?
>>
>> You have a single processor computer, build your own customized kernel
>> and disabled
>> options SMP (multiprocessor).
>> Probably you also disabled the line below,
>> device apic # I/O APIC
>>
>> This is code for the advanced programmable interrupt controller which
>> also controls interrupts for your attached devices, being ethernet cards
>> and others.
>> Do not disable this device.
>
> While I don't know about apic, there used to be "KEEP THIS!!!" comments in
> GENERIC's conf file.
> I guess this would be more on the spot than a FAQ you'd read *after*
> removing this.
>
> Just my 2c.
>
> bye
> av.
no KEEP THIS comments in GENERIC.
Though in NOTES it says "Mandatory".
It is a very stupid user error on my side, which I stumbled upon quite a
time ago and maybe not even FAQ worthy then.
Jakub Lach
Nov 27, 2012, 6:26:43 AM11/27/12
to
If it is really mandatory on i386, why there is option at all?
According to man, while apic is mandatory on amd64 there
is no corresponding config or NOTES entry.
--
View this message in context: http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5764584.html
According to man, while apic is mandatory on amd64 there
is no corresponding config or NOTES entry.
--
View this message in context: http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5764584.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
Jakub Lach
Nov 30, 2012, 5:39:15 AM11/30/12
to
officesuite is good, just change OO.org to Apache OpenOffice
convert-back-from-pkgng, make-kernel, release-candidate (I think that even
major releases are technically cut from -STABLE, as fresh -STABLE branch is
made from -CURRENT prior to -RELEASE, but that's minor detail) reread-rc,
use-beastie are all fine.
--
View this message in context: http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5765495.html
convert-back-from-pkgng, make-kernel, release-candidate (I think that even
major releases are technically cut from -STABLE, as fresh -STABLE branch is
made from -CURRENT prior to -RELEASE, but that's minor detail) reread-rc,
use-beastie are all fine.
--
View this message in context: http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5765495.html
Jakub Lach
Dec 7, 2012, 3:36:04 PM12/7/12
to
While it's very, very minute detail, I think that in #officesuite
there should be "Apache OpenOffice" not "Apache Open Office"
as they were very careful even bureaucratic [*] if I reckon correctly,
when choosing new branding.
[*] They have "branding initiative guidelines" and held vote-
https://blogs.apache.org/OOo/entry/openoffice_org_is_now_apache
--
View this message in context: http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5767462.html
there should be "Apache OpenOffice" not "Apache Open Office"
as they were very careful even bureaucratic [*] if I reckon correctly,
when choosing new branding.
[*] They have "branding initiative guidelines" and held vote-
https://blogs.apache.org/OOo/entry/openoffice_org_is_now_apache
--
View this message in context: http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5767462.html
Bas Smeelen
Dec 7, 2012, 4:11:43 PM12/7/12
to
On 12/07/12 21:36, Jakub Lach wrote:
> While it's very, very minute detail, I think that in #officesuite
> there should be "Apache OpenOffice" not "Apache Open Office"
> as they were very careful even bureaucratic [*] if I reckon correctly,
> when choosing new branding.
>
> [*] They have "branding initiative guidelines" and held vote-
> https://blogs.apache.org/OOo/entry/openoffice_org_is_now_apache
Hi Jakub
> While it's very, very minute detail, I think that in #officesuite
> there should be "Apache OpenOffice" not "Apache Open Office"
> as they were very careful even bureaucratic [*] if I reckon correctly,
> when choosing new branding.
>
> [*] They have "branding initiative guidelines" and held vote-
> https://blogs.apache.org/OOo/entry/openoffice_org_is_now_apache
You can file a patch for it
Index: en_US.ISO8859-1/books/faq/book.xml
===================================================================
--- en_US.ISO8859-1/books/faq/book.xml (revision 40304)
+++ en_US.ISO8859-1/books/faq/book.xml (working copy)
@@ -3523,7 +3523,7 @@
<answer>
<para>The open-source <application><ulink
- url="http://www.openoffice.org">Apache Open
Office</ulink></application>
+ url="http://www.openoffice.org">Apache
OpenOffice</ulink></application>
and <application><ulink
url="http://www.libreoffice.org">LibreOffice</ulink></application>
office suites work natively on &os;.</para>
Eitan Adler
Dec 7, 2012, 4:36:13 PM12/7/12
to
On 7 December 2012 16:11, Bas Smeelen <b.sm...@ose.nl> wrote:
> On 12/07/12 21:36, Jakub Lach wrote:
>>
>> While it's very, very minute detail, I think that in #officesuite
>> there should be "Apache OpenOffice" not "Apache Open Office"
>> as they were very careful even bureaucratic [*] if I reckon correctly,
>> when choosing new branding.
>>
>> [*] They have "branding initiative guidelines" and held vote-
>> https://blogs.apache.org/OOo/entry/openoffice_org_is_now_apache
Patch sent to mentor for approval. Thanks!
> On 12/07/12 21:36, Jakub Lach wrote:
>>
>> While it's very, very minute detail, I think that in #officesuite
>> there should be "Apache OpenOffice" not "Apache Open Office"
>> as they were very careful even bureaucratic [*] if I reckon correctly,
>> when choosing new branding.
>>
>> [*] They have "branding initiative guidelines" and held vote-
>> https://blogs.apache.org/OOo/entry/openoffice_org_is_now_apache
--
Eitan Adler
Jakub Lach
Dec 9, 2012, 11:03:03 AM12/9/12
to
Just FYI, "Microsoft Sound System Specification" probably
was meant to be Windows Sound System (?), severely
obsolete standard...
"WSS was based on Analog Devices AD1848 codec chip
with Yamaha OPL3 (YMF262-M) FM synthesis sound chip."
Probably already axed, it was supported by
dev/sound/isa/mss.c and isa/snd/ad1848.c I think.
--
View this message in context: http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5767809.html
was meant to be Windows Sound System (?), severely
obsolete standard...
"WSS was based on Analog Devices AD1848 codec chip
with Yamaha OPL3 (YMF262-M) FM synthesis sound chip."
Probably already axed, it was supported by
dev/sound/isa/mss.c and isa/snd/ad1848.c I think.
--
View this message in context: http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5767809.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
CeDeROM
Dec 9, 2012, 11:19:37 AM12/9/12
to
AdLib ROX! :-)
http://www.datasheetarchive.com/indexer.php?file=DSA00355987.pdf&dir=Datasheet-020&keywords=AD1848%2F1846&database=user-highscore#
http://www.ebay.com/itm/Analog-Devices-AD1848KP-ISA-SoundPort-Opti-82C29A-/200846434225?pt=US_Sound_Cards_Internal_&hash=item2ec3615fb1
At computer demoscene there are still guys that use this stuff to
create muzik :-)
http://www.youtube.com/results?search_query=adlib
Best regards :-)
Tomek
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
http://www.datasheetarchive.com/indexer.php?file=DSA00355987.pdf&dir=Datasheet-020&keywords=AD1848%2F1846&database=user-highscore#
http://www.ebay.com/itm/Analog-Devices-AD1848KP-ISA-SoundPort-Opti-82C29A-/200846434225?pt=US_Sound_Cards_Internal_&hash=item2ec3615fb1
At computer demoscene there are still guys that use this stuff to
create muzik :-)
http://www.youtube.com/results?search_query=adlib
Best regards :-)
Tomek
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
Lars Engels
Dec 10, 2012, 7:30:02 AM12/10/12
to
On Sun, Dec 09, 2012 at 07:47:01AM -0800, Jakub Lach wrote:
> #sound-card-support
>
> First part is fine, assuming man pages will be up to date etc. Not sure
> about
> support for MIDI cards/MPU-401. Is this covered by uart? Don't know whatever
> was "Microsoft® Sound System specification".
>
> #es1370-silent-pcm
>
> That's one thing, but most often silent device is caused by need for proper
> device.hints, as usual with e.g. snd_hda. This could use mention of it.
snd_hda can be configured at runtime from 9.0 on. No need for
device.hints.
> #sound-card-support
>
> First part is fine, assuming man pages will be up to date etc. Not sure
> about
> support for MIDI cards/MPU-401. Is this covered by uart? Don't know whatever
> was "Microsoft® Sound System specification".
>
> #es1370-silent-pcm
>
> That's one thing, but most often silent device is caused by need for proper
> device.hints, as usual with e.g. snd_hda. This could use mention of it.
snd_hda can be configured at runtime from 9.0 on. No need for
device.hints.
Jakub Lach
Dec 10, 2012, 7:53:56 AM12/10/12
to
Ok, but it doesn't change current primary reason of silent devices
(wrong pinout) :)
--
View this message in context: http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5768088.html
(wrong pinout) :)
--
View this message in context: http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5768088.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
Jakub Lach
Dec 10, 2012, 1:52:27 PM12/10/12
to
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
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
Jakub Lach
Dec 12, 2012, 1:45:41 PM12/12/12
to
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
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
Jakub Lach
Dec 13, 2012, 8:35:45 PM12/13/12
to
#uninstall-kerberos
Uh? Reinstalling base will delete kerberos? I don't get this answer.
I thought kerberos was part of base?
--
View this message in context: http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5769224.html
Uh? Reinstalling base will delete kerberos? I don't get this answer.
I thought kerberos was part of base?
--
View this message in context: http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5769224.html
Jakub Lach
Dec 13, 2012, 8:50:54 PM12/13/12
to
#xfree86-root There is no Xwrapper (x11/wrapper) in ports tree. (Port is
expired, whole
answer outdated.)
#xconsole-failure Indeed xconsole throws such error, but not xterm -C.
--
View this message in context: http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5769225.html
expired, whole
answer outdated.)
#xconsole-failure Indeed xconsole throws such error, but not xterm -C.
--
View this message in context: http://freebsd.1045724.n5.nabble.com/Help-review-the-FAQ-tp5762326p5769225.html
Jakub Lach
Dec 14, 2012, 7:23:15 AM12/14/12
to
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
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
Jakub Lach
Dec 15, 2012, 7:55:55 AM12/15/12
to
#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
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
0 new messages