Re: FreeBSD Status Reports due August 5th, 2008
On Wed, Jul 30, 2008 at 7:03 AM, Jeroen Ruigrok van der Werven <[EMAIL PROTECTED]> wrote: > -On [20080730 06:22], Brad Davis ([EMAIL PROTECTED]) wrote: >>On Tue, Jul 29, 2008 at 01:17:27AM +0200, Niclas Zeising wrote: >>> I assume you mean Friday August 5th, 2008? >> >>Of course you are right, that is what I get for hurrying. > > In my part of the world Friday in August is either the 1st or the 8th, but > not the 5th. > Of course you are right. 5th of August 2008 is a Tuesday. That is what I get for being up too late ;) Regards! //Niclas ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
consolekit on 7.0-STABLE i386
hello my trouble FreeBSD static 7.0-STABLE FreeBSD 7.0-STABLE #23: Mon Jul 28 18:10:51 MSD 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/STATIC i386 top_output- |874 root17 00 8296K 2660K waitvt 1 0:00 0.00% console-kit-daemon| ---vmstat_output--- | procs memory pagedisks faults cpu r b w avmfre flt re pi pofr sr ad4 ad6 in sy cs us sy id 0 19 0 1113M29M 493 1 0 0 265 129 0 0 133 45119 4588 8 5 87 0 20 0 1113M29M 249 0 2 0 3311 0 0 22 157 7872 2262 5 7 88 0 19 0 1113M29M 346 0 0 0 148 0 0 0 110 78963 1793 4 9 87 0 19 0 1113M29M 115 0 0 0 0 0 0 0 105 5743 1731 13 1 85 0 19 0 1113M29M 318 0 0 0 138 0 0 0 108 78837 1732 3 10 87 0 19 0 1113M29M 112 0 0 032 0 0 1 100 5549 1682 11 1 88 0 19 0 1113M29M 297 0 0 0 136 0 0 2 122 78880 1749 6 7 87 | consolekit in |waitvt state, influencing on high volumes in procs-b |please any solution? /Vladimir Ermakov ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: consolekit on 7.0-STABLE i386
On Wed, 30 Jul 2008, sam wrote: hello my trouble FreeBSD static 7.0-STABLE FreeBSD 7.0-STABLE #23: Mon Jul 28 18:10:51 MSD 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/STATIC i386 top_output- |874 root17 00 8296K 2660K waitvt 1 0:00 0.00% console-kit-daemon| ---vmstat_output--- | procs memory pagedisks faultscpu r b w avmfre flt re pi pofr sr ad4 ad6 in sy cs us sy id 0 19 0 1113M29M 493 1 0 0 265 129 0 0 133 45119 4588 8 5 87 0 20 0 1113M29M 249 0 2 0 3311 0 0 22 157 7872 2262 5 7 88 0 19 0 1113M29M 346 0 0 0 148 0 0 0 110 78963 1793 4 9 87 0 19 0 1113M29M 115 0 0 0 0 0 0 0 105 5743 1731 13 1 85 0 19 0 1113M29M 318 0 0 0 138 0 0 0 108 78837 1732 3 10 87 0 19 0 1113M29M 112 0 0 032 0 0 1 100 5549 1682 11 1 88 0 19 0 1113M29M 297 0 0 0 136 0 0 2 122 78880 1749 6 7 87 | consolekit in |waitvt state, influencing on high volumes in procs-b I don't understand what the problem is. It looks like consolekit is sleeping and not using any CPU. "waitvt" just indicates where in the kernel it's sleeping. I don't understand what you mean by "high volumes in procs-b". -- Nate Eldredge [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
General questions about virtual memory
Hi, all. I apologize for not posting a question specific to FreeBSD (I'll study about that later), but I'm looking for some help understanding a few things and I don't know where else to turn. Using FreeBSD to give me concrete examples of how certain things work is okay, since I do use FreeBSD and I intend to read and study books covering the design and implementation of FreeBSD. I recently picked up one of my old college textbooks, "Modern Operating Systems" (Tanenbaum, an older edition, but I'm not sure which one since the book is at home and I am not) with a strong desire to read it cover-to-cover and get a solid foundation of the concepts described therein. The chapter on virtual memory has left me with some questions, and if anyone would be willing to help me understand (either on or off list) a few things that aren't clear, I would very much appreciate it. Examples of some specific questions that I have include: WRT translation of virtual addresses to physical addresses, where does the hardware stop and the software begin? Explanation: who determines the format of the page tables (CPU or OS)? Who populates and maintains the page tables? Where does the translation lookaside buffer reside? Who maintains the TLB? Also WRT page tables, how does the OS and the MMU adjust for different sizes of physical RAM? Wouldn't the page tables for a system with 512 MB of RAM will be fewer than the page tables for a system with 2 GB of RAM? How does the CPU know how many page table entries there are? I have a few more questions, but for starters this is the kind of information I'm seeking. I'm just not getting a clear enough picture from the textbook I'm reading now. (It makes me wish I was still in college so I could dump my questions on my college professor. :) If anyone is willing to help me understand this, I would greatly appreciate it. I would also value your input if there are other resources (people, mailing lists, books, web pages, etc.) that you want to recommend instead of taking some time to help teach me. Thank you, Kevin ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Symbols in a Module
Jeroen Ruigrok van der Werven <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED] wrote: > > I am compiling an AFS module. The module won't load. Dmesg reports > > undefined symbol _vn_lock. nm reports that the symbol exists and is > > undefined. > > > > How do I compile (defined) symbols into my module? > > You add the appropriate source file or library. > > _vn_lock, sounds like sys/vnode.h, which in turn on 7-STABLE needs > sys/kern/vfs_vnops.c. Wrong answer; vn_lock is already in the kernel. The problem lies somewhere else, but there isn't enough information to figure out where. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Laptop suggestions?
Matt Olander <[EMAIL PROTECTED]> writes: > [re http://www.ixsystems.com/products/bsd-laptop.html] Will it be available with a big FreeBSD logo on the lid? :) DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: General questions about virtual memory
Hi, On Wednesday 30 July 2008 13:59:53 FreeBSD Hackers wrote: > Examples of some specific questions that I have include: > > WRT translation of virtual addresses to physical addresses, where does the > hardware stop and the software begin? Explanation: who determines the > format of the page tables (CPU or OS)? Who populates and maintains the > page tables? Where does the translation lookaside buffer reside? Who > maintains the TLB? it depends ... different architectures use different models. In i386 most of the above is done by hardware aided by software (i.e. the software has to flush the hardware TLB when it knows that the entries are no longer up to date ...) > Also WRT page tables, how does the OS and the MMU adjust for different > sizes of physical RAM? Wouldn't the page tables for a system with 512 MB > of RAM will be fewer than the page tables for a system with 2 GB of RAM? > How does the CPU know how many page table entries there are? This suggest that you don't understand virtual memory at all. Go back to the start of the chapter and re-read. The page directories and page tables describe a *virtual* address space. For a given architecture the *virtual* address space has a fixed size (4GB for i386), so the page table structure is always the same size (though it might be sparsely populated). Inside the page table you store *physical* addresses, the size of which is defined by the hardware. Also note that the physical addresses of your RAM might not necessarily start at zero and go for XX MB ... you need additional bookkeeping to track that (see core map, free lists, ...). The size of the PTE is defined by hardware and doesn't change at runtime. > I have a few more questions, but for starters this is the kind of > information I'm seeking. I'm just not getting a clear enough picture from > the textbook I'm reading now. (It makes me wish I was still in college so > I could dump my questions on my college professor. :) > > If anyone is willing to help me understand this, I would greatly appreciate > it. I would also value your input if there are other resources (people, > mailing lists, books, web pages, etc.) that you want to recommend instead > of taking some time to help teach me. google, wikipedia, the FreeBSD articles, ... all there at your fingertips. -- /"\ Best regards, | [EMAIL PROTECTED] \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | [EMAIL PROTECTED] / \ ASCII Ribbon Campaign | Against HTML Mail and News ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: General questions about virtual memory
> > This suggest that you don't understand virtual memory at all. Go back to > the > start of the chapter and re-read. The page directories and page tables > describe a *virtual* address space. For a given architecture the *virtual* > address space has a fixed size (4GB for i386), so the page table structure > is > always the same size (though it might be sparsely populated). Inside the > page Ack! As soon as I read this I realized the mistake I had made in my thinking. This was a dumb question, and I knew better than to ask. Somehow I had confused myself. - 8< - If a read request is made to a virtual address who's data has been swapped out, the CPU traps to the OS to fix the problem. Assuming there are no free page frames for the new data, a page frame is selected and evicted to make room for the new page. Whatever page was chosen belongs to a process somewhere in the system. When that page frame gets swapped, the PTE pointing to that page frame must be updated to indicate that that data is no longer in RAM. How does the OS find that PTE? Does it search through every entry of every page table for every process in the system until it finds it? Kevin ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: General questions about virtual memory
On Wed, Jul 30, 2008 at 07:59:53AM -0400, FreeBSD Hackers wrote: > Hi, all. I apologize for not posting a question specific to FreeBSD (I'll > study about that later), but I'm looking for some help understanding a few > things and I don't know where else to turn. Using FreeBSD to give me > concrete examples of how certain things work is okay, since I do use FreeBSD > and I intend to read and study books covering the design and implementation > of FreeBSD. > > I recently picked up one of my old college textbooks, "Modern Operating > Systems" (Tanenbaum, an older edition, but I'm not sure which one since the > book is at home and I am not) with a strong desire to read it cover-to-cover > and get a solid foundation of the concepts described therein. The chapter > on virtual memory has left me with some questions, and if anyone would be > willing to help me understand (either on or off list) a few things that > aren't clear, I would very much appreciate it. You could try picking up one of Tanenbaum's other books: "Structured Computer Organization", which among other things cover virtual memory from a hardware perspective. (At least my copy does. It is the third edition, which is not the latest.) > > Examples of some specific questions that I have include: > > WRT translation of virtual addresses to physical addresses, where does the > hardware stop and the software begin? Explanation: who determines the > format of the page tables (CPU or OS)? Who populates and maintains the page > tables? Where does the translation lookaside buffer reside? Who maintains > the TLB? It can vary a bit between different architectures, but in general the format of the page tables is determined by the CPU. The TLB is located inside the CPU (so it can be accessed quickly, it is after all just a specialized cache.) The page tables are normally populated and maintained by the OS, the CPU just reads them. The TLB is typically maintained in hardware, but there are systems where it has to be updated by the OS. > > Also WRT page tables, how does the OS and the MMU adjust for different sizes > of physical RAM? Wouldn't the page tables for a system with 512 MB of RAM > will be fewer than the page tables for a system with 2 GB of RAM? How does > the CPU know how many page table entries there are? The page tables are typically used for mapping between virtual and physical addresses (and also for access rights to the mapped memory). This means that the size of the page table depends primarily on the size of the virtual memory which is not dependent on the actual RAM installed. The page tables are typically a tree-like structure, where the top level is a fairly small (typically one page) fixed-size array which contains pointers to the next level of the page table. In that level there are either yet another array of entries each of which is either a pointer to another level, or a page descriptor. You walk down the tree until you either find a descriptor for the page you are looking for or an entry saying that pages further down that branch has not been allocated. How many levels there are is system dependent. IIRC the i386 only uses a two-level format (three levels when using PAE), while the Motorola 68030 could have as many as seven levels. > > I have a few more questions, but for starters this is the kind of > information I'm seeking. I'm just not getting a clear enough picture from > the textbook I'm reading now. (It makes me wish I was still in college so I > could dump my questions on my college professor. :) > > If anyone is willing to help me understand this, I would greatly appreciate > it. I would also value your input if there are other resources (people, > mailing lists, books, web pages, etc.) that you want to recommend instead of > taking some time to help teach me. You could try picking up one of Tanenbaum's other books: "Structured Computer Organization", which among other things cover virtual memory from a hardware perspective, including examples for how the page tables are organized for a couple of example architectures. -- Erik Trulsson [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Laptop suggestions?
Am 30.07.2008 um 15:17 schrieb Dag-Erling Smørgrav: Matt Olander <[EMAIL PROTECTED]> writes: [re http://www.ixsystems.com/products/bsd-laptop.html] Will it be available with a big FreeBSD logo on the lid? :) If you need something like that, a partially eaten white apple would be much more appropriate anyway. (Which reminds me - I didn't understand the motivation behind the original question either... Even more and more Linux users are giving up running it on their Macs, installing Mac OS instead. Looks contagious...) Achim
Re: Laptop suggestions?
Achim Patzner <[EMAIL PROTECTED]> writes: > Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes: > > Matt Olander <[EMAIL PROTECTED]> writes: > > > [re http://www.ixsystems.com/products/bsd-laptop.html] > > Will it be available with a big FreeBSD logo on the lid? :) > If you need something like that, a partially eaten white apple would > be much more appropriate anyway. (Which reminds me - I didn't > understand the motivation behind the original question either... Even > more and more Linux users are giving up running it on their Macs, > installing Mac OS instead. Looks contagious...) I don't understand what Macs have to do with this - we're talking about iX Systems's made-for-BSD laptop. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: General questions about virtual memory
On Wednesday 30 July 2008 18:07:51 FreeBSD Hackers wrote: > > This suggest that you don't understand virtual memory at all. Go back to > > the > > start of the chapter and re-read. The page directories and page tables > > describe a *virtual* address space. For a given architecture the > > *virtual* address space has a fixed size (4GB for i386), so the page > > table structure is > > always the same size (though it might be sparsely populated). Inside the > > page > > Ack! As soon as I read this I realized the mistake I had made in my > thinking. This was a dumb question, and I knew better than to ask. > Somehow I had confused myself. > > - 8< - > > If a read request is made to a virtual address who's data has been swapped > out, the CPU traps to the OS to fix the problem. Assuming there are no > free page frames for the new data, a page frame is selected and evicted to > make room for the new page. Whatever page was chosen belongs to a process > somewhere in the system. When that page frame gets swapped, the PTE > pointing to that page frame must be updated to indicate that that data is > no longer in RAM. How does the OS find that PTE? Does it search through > every entry of every page table for every process in the system until it > finds it? You should have quoted (and I suppose read) my entire message: >.. you need additional bookkeeping > to track that (see core map, free lists, ...) Wikipedia really does a good job explaining all this. -- /"\ Best regards, | [EMAIL PROTECTED] \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | [EMAIL PROTECTED] / \ ASCII Ribbon Campaign | Against HTML Mail and News ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: General questions about virtual memory
On Wed, 30 Jul 2008, FreeBSD Hackers wrote: If anyone is willing to help me understand this, I would greatly appreciate it. I would also value your input if there are other resources (people, mailing lists, books, web pages, etc.) that you want to recommend instead of taking some time to help teach me. As a slightly less orthodox suggestion, I learned a lot of this from the "practice" side rather than the "theory" side, and it seems like maybe this is where some of your questions lie. In addition to a textbook, you might find it useful to get a copy of the manual for your favorite CPU, which will explain, at the level of assembly language, how all these features work. (They are usually available free on the manufacturer's website, though you may have to hunt around a bit or register for a developer program or something.) You can read it in conjunction with the FreeBSD kernel source to see an actual example. I found this approach very instructive. -- Nate Eldredge [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Locale woes.
Hi,
I have some problem with locales on FreeBSD 6.3. The attached test case fails
with uncaught std::runtime_error exception:
shell::wilx:~/tmp> locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_ALL=
shell::wilx:~/tmp> ./codecvt_test "abcdŠ<"
terminate called after throwing an instance of 'std::runtime_error'
what(): locale::facet::_S_create_c_locale name not valid
zsh: abort (core dumped) ./codecvt_test "abcdŠ<"
shell::wilx:~/tmp> locale -a |grep en_US.UTF-8
en_US.UTF-8
I don't understand why? It works without change on both Windows and
Gentoo/Linux.
--
VH
// codecvt_test.cpp : Defines the entry point for the console application.
//
#include
#include
#include
#include
#include
#include
std::wstring
towstring(const std::string& src)
{
std::wstring outstr;
typedef std::codecvt CodeCvt;
std::locale loc ("");
const CodeCvt & cdcvt = std::use_facet(loc);
std::mbstate_t state = {0};
char const * const from_first = src.c_str ();
size_t const from_size = src.size ();
char const * const from_last = from_first + from_size;
char const * from_next = from_first;
// XXX: Intentionally allocate only half the size of the input.
std::vector dest (from_size / 2);
wchar_t * to_first = &dest.front ();
size_t to_size = dest.size ();
wchar_t * to_last = to_first + to_size;
wchar_t * to_next = to_first;
CodeCvt::result result;
size_t converted = 0;
while (true)
{
result = cdcvt.in (
state, from_first, from_last,
from_next, to_first, to_last,
to_next);
if ((result == CodeCvt::partial || result == CodeCvt::ok)
&& from_next != from_last)
{
to_size = dest.size () * 2;
dest.resize (to_size);
converted = to_next - to_first;
to_first = &dest.front ();
to_last = to_first + to_size;
to_next = to_first + converted;
continue;
}
else if (result == CodeCvt::ok && from_next == from_last)
break;
else
{
assert (0);
break;
}
}
converted = to_next - to_first;
outstr.assign (dest.begin (), dest.begin () + converted);
return outstr;
}
int main (int argc, char * argv[])
{
if (argc < 2)
{
std::cerr << "codecvt_test string\n";
return 1;
}
std::string str (argv[1]);
std::wstring wstr = towstring (str);
std::wcout << std::hex;
for (std::wstring::const_iterator it = wstr.begin (); it != wstr.end ();
++it)
std::wcout << static_cast(*it) << " ";
std::wcout << "\n";
std::wcout.imbue (std::locale (""));
std::wcout << wstr << std::endl;
return 0;
}
signature.asc
Description: OpenPGP digital signature
Re: Laptop suggestions?
Am 30.07.2008 um 18:40 schrieb Dag-Erling Smørgrav: I don't understand what Macs have to do with this - we're talking about iX Systems's made-for-BSD laptop. The thread started with someone asking for a mobile computer that would support FreeBSD sufficiently and nobody came up with something fitting the bill (and being available somewhere). Considering the picture you're seeing at any place where more than two hardcore Unix users assemble you're seeing a majority of Macs. There has to be an obvious reason for that... I tried to break that habit more than once but right now the only comfortable way of running FreeBSD on a laptop is VMware Fusion on a Mac. Reading this entire thread convinced me even more. Achim
Re: Laptop suggestions?
> right now the only comfortable way of running FreeBSD on a laptop is VMware Fusion on a Mac. It depends on what you consider to be "comfortable". My primary machine is an old Dell Inspiron 6000 (running the RELENG_7 branch) and the only hardware compatibility issue I've ever had was that suspend/hibernate doesn't work (display doesn't come back on). I'm much more comfortable with ignorable ACPI issues on old (but perfectly capable) hardware than running everything through a VM on a brand new top-of-the-line machine. While this message is entirely anecdotal, I'm sure there are quite a few other people happily running FreeBSD on a variety of machines (albeit, somewhat aged hardware) which doesn't come near the specifications outlined in the original post. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Laptop suggestions?
On Wed, Jul 30, 2008 at 04:31:10PM -0400, L Campbell wrote: > It depends on what you consider to be "comfortable". My primary machine is > an old Dell Inspiron 6000 (running the RELENG_7 branch) and the only > hardware compatibility issue I've ever had was that suspend/hibernate > doesn't work (display doesn't come back on). vbetool post? Joerg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Locale woes.
Václav Haisman wrote, On 30.7.2008 20:40: Hi, I have some problem with locales on FreeBSD 6.3. The attached test case fails with uncaught std::runtime_error exception: [...] I am able to run the test case successfuly when I compile it with STLport. So it seems there is something odd going on with just the libstdc++ that ships with GCC. On the other hand, it works fine with GCC 4.1.2 on Gentoo/Linux. -- wilx signature.asc Description: OpenPGP digital signature
Re: Laptop suggestions?
> From: Achim Patzner <[EMAIL PROTECTED]> > Date: Wed, 30 Jul 2008 22:20:28 +0200 > Sender: [EMAIL PROTECTED] > > Am 30.07.2008 um 18:40 schrieb Dag-Erling Smørgrav: > > I don't understand what Macs have to do with this - we're talking > > about > > iX Systems's made-for-BSD laptop. > > The thread started with someone asking for a mobile computer that > would support FreeBSD sufficiently and nobody came up with something > fitting the bill (and being available somewhere). Considering the > picture you're seeing at any place where more than two hardcore Unix > users assemble you're seeing a majority of Macs. There has to be an > obvious reason for that... I tried to break that habit more than once > but right now the only comfortable way of running FreeBSD on a laptop > is VMware Fusion on a Mac. Reading this entire thread convinced me > even more. I have been running for the last two years in a ThinkPad T43 and it works fine. ATI graphics work well as does everything except the modem. Since I don't have any access to any dialup network service any more, I don't think I care, although I do carry an old PCMCIA modem card, just in case. Suspend also does not work reliably, but I don't normally suspend my system, anyway, so I don't notice that, either. Atheros wireless, Broadcomm Ethernet, graphics, DRI, USB all just work and have worked since V6.1 days. That said, I suspect that my next laptop with be a Mac with either VMware or Parallels, My wife already runs one and it's pretty nice. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgp42tCPCHiOv.pgp Description: PGP signature
Re: Laptop suggestions?
2008/7/30 Matt Olander <[EMAIL PROTECTED]>: > On Jul 25, 2008, at 3:23 PM, Jeremy Messenger wrote: > >> Maybe you can wait for this: >> >> http://www.ixsystems.com/products/bsd-laptop.html > > Hi everyone! I actually had our prototype of this laptop up at the OSCON > show in Portland and it was pretty well received. > Everything works for the most part although we're still tweaking some things > for ACPI. > > I'll have one at the FreeBSD booth at LinuxWorld in San Francisco next week, > August 5-7. We'll announce as soon as this thing is 100% and we're > comfortable bringing the product line up as an item that we're comfortable > supporting long term. Most likely, available to the general public in > September. > Any chances it will be available with trackpoint instead of touchpad? :) Thanks, -- Mateusz Guzik ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Laptop suggestions?
Matt Olander wrote: http://www.ixsystems.com/products/bsd-laptop.html Hi everyone! I actually had our prototype of this laptop up at the OSCON show in Portland and it was pretty well received. Everything works for the most part although we're still tweaking some things for ACPI. I'll have one at the FreeBSD booth at LinuxWorld in San Francisco next week, August 5-7. We'll announce as soon as this thing is 100% and we're comfortable bringing the product line up as an item that we're comfortable supporting long term. Most likely, available to the general public in September. best, -matt h nice! battery life? ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Laptop suggestions?
On Jul 30, 2008, at 3:42 PM, Julian Elischer wrote: Matt Olander wrote: http://www.ixsystems.com/products/bsd-laptop.html Hi everyone! I actually had our prototype of this laptop up at the OSCON show in Portland and it was pretty well received. Everything works for the most part although we're still tweaking some things for ACPI. I'll have one at the FreeBSD booth at LinuxWorld in San Francisco next week, August 5-7. We'll announce as soon as this thing is 100% and we're comfortable bringing the product line up as an item that we're comfortable supporting long term. Most likely, available to the general public in September. best, -matt h nice! battery life? I haven't done any battery life testing yet but I will. We just put NetBSD current on there late last night and one of our guys is surfing the net right now with one of the prototypes. We'll run it through some tests over this weekend on FreeBSD 7 and post some relevant specs up on the site next week. I'll let everyone know when we update :-P We've got a couple of minimalist stickers on there but we're hoping to ship it with a fun BSD sticker kit. I put the huge FreeBSD Mall bumper sticker on the lid of mine ;-) -matt ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Laptop suggestions?
0n Wed, Jul 30, 2008 at 11:04:38PM +0200, Joerg Sonnenberger wrote: >On Wed, Jul 30, 2008 at 04:31:10PM -0400, L Campbell wrote: >> It depends on what you consider to be "comfortable". My primary machine is >> an old Dell Inspiron 6000 (running the RELENG_7 branch) and the only >> hardware compatibility issue I've ever had was that suspend/hibernate >> doesn't work (display doesn't come back on). > >vbetool post? Is vbetool in ports ? I cant find it mentioned anywhere in INDEX-*. -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Laptop suggestions?
On Thu, Jul 31, 2008 at 08:25:04AM +0800, Wilkinson, Alex wrote: > >vbetool post? > > Is vbetool in ports ? I cant find it mentioned anywhere in INDEX-*. Can't find it either. ENOFREEBSD :) http://www.codon.org.uk/~mjg59/vbetool/ Joerg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Laptop suggestions?
On Wed, 30 Jul 2008 at 18:35 -, Mateusz Guzik wrote: > 2008/7/30 Matt Olander <[EMAIL PROTECTED]>: > > On Jul 25, 2008, at 3:23 PM, Jeremy Messenger wrote: > > > >> Maybe you can wait for this: > >> > >> http://www.ixsystems.com/products/bsd-laptop.html > > Any chances it will be available with trackpoint instead of > touchpad? :) I like that it has a serial port on it. What does it have for audio? A line-in connection would also be very welcome. Also, how about 3 buttons on the touchpad? I really like having a middle button. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Laptop suggestions?
On Wed, Jul 30, 2008 at 5:20 PM, Achim Patzner <[EMAIL PROTECTED]> wrote: > Am 30.07.2008 um 18:40 schrieb Dag-Erling Smørgrav: >> >> I don't understand what Macs have to do with this - we're talking about >> iX Systems's made-for-BSD laptop. > > The thread started with someone asking for a mobile computer that > would support FreeBSD sufficiently and nobody came up with something > fitting the bill (and being available somewhere). Considering the > picture you're seeing at any place where more than two hardcore Unix > users assemble you're seeing a majority of Macs. There has to be an > obvious reason for that... I tried to break that habit more than once > but right now the only comfortable way of running FreeBSD on a laptop > is VMware Fusion on a Mac. Reading this entire thread convinced me > even more. Please define "comfortable". I've been running FreeBSD 7.0 pretty comfortably on my HP nx6320 for several months now. I never attempted to use neither Bluetooth nor the fingerprint reader, so I don't miss them. The only real drawback I've found was that the memory card reader does not work. I also ran 8.0-CURRENT on a HP 6910p because 7.0 did not support the WI-FI card. -- Carlos Santos Working, but not speaking (or advertising) for HP :-) ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Pls sanity check my semtimedop(2) implementation
On Fri, Jul 18, 2008 at 11:58 AM, Jilles Tjoelker <[EMAIL PROTECTED]> wrote:
> On Sat, Jul 12, 2008 at 07:11:26PM -0400, Michael B Allen wrote:
>> Below is a semtimedop(2) implementation that I'm using for FreeBSD. I
>> was hoping someone could look it over and tell me if they think the
>> implementation is sound.
>
>> [snip semtimedop implementation that uses SIGALRM and relies on EINTR]
>
>> The code seems to work ok but when stressing the FreeBSD build of my app
>> I have managed to provoke errors related to concurrency (usually when a
>> SIGALRM goes off). The Linux build works flawlessesly so I'm wondering
>> about this one critical function that is different.
>
> In your implementation, the SIGALRM signal may happen before you even
> call semop(2). If so, most likely the semop(2) will hang arbitrarily
> long.
Indeed. And I reconnoiter that condition is likely to happen if called
with a sufficiently small timeout value.
> Another dirty fix is to try non-blocking semop(2) several times with
> sleeps in between.
Actually that seems to work pretty well.
If I force the nanosleep codepath to be used always, the application
actually works pretty well under load. I wonder if the overhead of
managing the signal and timer is worth the trouble.
For posterity, below is the current implementation of semtimedop(2)
for FreeBSD. Further ideas are welcome.
void
_timeval_diff(struct timeval *tv1, struct timeval *tv2, struct timeval *tvd)
{
tvd->tv_sec = tv1->tv_sec - tv2->tv_sec;
tvd->tv_usec = tv1->tv_usec - tv2->tv_usec;
if (tvd->tv_usec < 0) {
tvd->tv_usec = 100 - tvd->tv_usec;
tvd->tv_sec--;
}
}
void
signal_ignore(int s, siginfo_t *si, void *ctx)
{
}
int
_semtimedop(int semid, struct sembuf *array, size_t nops, struct
timespec *_timeout)
{
struct timeval timeout, before, after;
struct itimerval value, ovalue;
struct sigaction sa, osa;
int ret;
if (_timeout) {
timeout.tv_sec = _timeout->tv_sec;
timeout.tv_usec = _timeout->tv_nsec / 1000;
if (gettimeofday(&before, NULL) == -1) {
errno = EFAULT;
return -1;
}
if (timeout.tv_sec == 0 && timeout.tv_usec < 5000) {
struct timeval tsleep, tend;
struct sembuf wait;
wait = *array;
wait.sem_flg |= IPC_NOWAIT;
tsleep.tv_sec = 0;
tsleep.tv_usec = 1;
timeradd(&before, &timeout, &tend);
for ( ;; ) {
struct timeval tnow, tleft;
struct timespec ts;
ret = semop(semid, &wait, nops);
if (ret == 0) {
return 0;
} else if (errno != EAGAIN) {
break;
}
if (gettimeofday(&tnow, NULL) == -1) {
errno = EFAULT;
break;
}
if (timercmp(&tnow, &tend, >=)) {
errno = EAGAIN;
break;
}
timersub(&tend, &tnow, &tleft);
if (tsleep.tv_usec > tleft.tv_usec)
tsleep.tv_usec = tleft.tv_usec;
ts.tv_sec = 0;
ts.tv_nsec = tsleep.tv_usec * 1000;
nanosleep(&ts, NULL);
tsleep.tv_usec *= 10;
}
return -1;
}
memset(&value, 0, sizeof value);
value.it_value = timeout;
memset(&sa, 0, sizeof sa);
sa.sa_sigaction = signal_ignore;
sa.sa_flags = SA_SIGINFO;
sigemptyset(&sa.sa_mask);
sigaction(SIGALRM, &sa, &osa);
if (setitimer(ITIMER_REAL, &value, &ovalue) == -1) {
sigaction(SIGALRM, &osa, NULL);
return -1;
}
}
ret = semop(semid, array, nops);
if (_timeout) {
ret = setitimer(ITIMER_REAL, &ovalue, NULL);
if (ret < 0)
errno = EFAULT;
sigaction(SIGALRM, &osa, NULL);
}
if (ret == -1) {
if (_timeout) {
struct timeval elapsed;
if (gettimeofday(&after, NULL) == -1) {
} else {
_timeval_diff(&after, &before, &elapsed);
if (timercmp(&elapsed, &timeout, >=))
errno = EAGAIN;
}
}
return -1;
}
return 0;
}
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
