I have the same thing with crossmounts between a couple of machines. Situations where you need to reboot both simultaniously are rare though.
What you can do is be a good administrator and change your init scripts. eg make sure you have a scripts to forcibly unmount your nfs mounts before doing unmount -f.
jeez... you have complete control of how the machine boots/shutsdown cause it all done via scripts. so use that power..
someone posted link to the Royal warrants FAQ down below, http://www.royal.gov.uk/faq/warrant.htm, and it turns out the crest i see on my pack of JP Blue is not that of one of the Royals! Anyone know what crest it is?
it's a shield with 3 little boat type things stacked top-left, grid top-right, castle below with suns on either side of it. lions rampant on either side and surmounted by a knights helmet with a crown on it.
Are John Player's taking the piss with a fake look-alike royal appointment? Or is the crest and appointment real?
(guaranteed someone on slashdot is into to heraldry)
he was the guy who arranged for Digital to ship one of their hot new Alpha systems to Linus. And this was when Alpha was still really new (eg 93 or something). Linus did the basic port to it in something like 2 weeks. The first ever port of linux.
He's been pushing linux inside DEC/Compaq ever since. Mad Dog had the kind of standing to push linux at the boardroom level. So Compaq's pro-linux attitude is due to him in no small way.
He also been a great Ambassador for linux, and has been an active member of Linux International for a very long time.
One of linux's more low-profile, but most influential proponents.
so easy, you have to reinstall them if you add a component from the NT cd.
And so easy when some application (usually MS) takes it upon itself to upgrade files that are also upgraded by a SP. Which version is the correct one? The one from the SP or the one the application installed? And maybe the app can't work with the version from the SP? So how do you install the SP? Or reinstall it if you've changed some vital config, eg changed the NIC?
And this kind of thing has infinite permutations, leading to hours and hours of NT admin fun. And hey, if it wasn't for NT admin's would never be able to claim overtime! Damm those Unix boxes that just purr away for months and months without a glitch. How can you ever earn money from them?
Yes service packs... gotta love them. you really do. {God, Allah, prefferred deity} bless NT!
and don't forget, in addition to buying a motherboard, you'll most likely also need a new power supply.
The Athlon needs a minimum of a 300W peak PSU, and i don't know of any cases outside of big server cases that ship with 300W+. Most desktops and small towers have 200W, and midi/full towers tend be around 230-250W. Run an athlon in one of those and it'll be unstable as hell.
High power PSU's are pretty tricky to find aswell.
linux does support threads, and has since about 1.2. There was a recent discussion about it on linux-kernel. What i understood from it was that threads and processes are both created by the kernel's 'clone' call - which takes arguments to specify whether to share memory/stack/etc..
everything else uses that, in fact the traditional Unix process system creation calls are just C lib wrappers around linux clone(). Just as the thread library calls are.
So it seems linux supports threads pretty well, just the userspace library wasn't up to it until glibc.
They make a huge difference to the stability of linux's nfs interoperability. The standard kernel nfs is horribly broken. I've used linux as an nfs server to linux, solaris x86 and MACH clients, and it works very reliably once you use knfsd. (but i've only tested with a couple of clients, not 60).
see ftp://ftp.varesearch.com/pub/support/hjl/knfsd/
Designed by ARM Ltd. (UK company). Licensed by a lot of companies, eg intel. RISC-like, 32-bit. Currently available at up to 233MHz or so. Intel says they'll produce 600MHz+ versions in the near future.
Extremely low power consumption. Less than a Watt peak for the 233MHz version (~450mW @ 160MHz), just a few mW idle.
Supported by linux (eg the Netwinder). Company in England has an SA-110 ATX motherboard iirc. Also used in things like RAID controllers (Mylex's new one i think) and Empeg (car mp3 player -> www.empeg.com).
your right. there's a problem with PCI which maps into memory at 1GB.. hence limiting physical RAM to 1GB. But I think it might have changed in 2.2.11 or so to 2GB (not sure).
Tru64 supports scatter-gather mapping. ie arbitrary PCI address spaces can be mapped on demand to arbitrary address spaces. Also, the pyxis chipset used on a lot of PCI alpha's (PC164xx) has quite sophisticated scatter-gather support, ie cut-down page tables and a tlb (similar to the way most cpu's support virtual memory). But linux doesn't support this, and just uses direct mappings..:(
NT does run on a 64 bit cpu (like Linux and NetBSD) but it only uses 32 bits (like Linux)
linux is fully 64bit on Alpha!!! (UltraSparc kernel aswell, not sure about app's). The kernel is 64bit. The C libraries are fully 64bit. The App's are fully 64 bit. Linux is 64 bit clean!!!!!!
in fact the reason there's no netscape for Alpha is precisely because it's all 64bit and NS isn't 64bit clean.
if you write an OpenGL app you don't need to know anything about DRI or GLX or whatever. The call to create the viewable is an OpenGL call. It's then up to the OpenGL library to do whatever is needed, be it using glx/dri or plain X to create the window. ie:
app opengl library screen.
OpenGL is incredibly portable for this very reason cause you do not need to worry about glx/directX/whatever - that part is handled by the library.
Re:Forked road or forked tongue
on
Is X The Future?
·
· Score: 1
ok.. so how's that like win3.x? and how is a wm+X like win3.x on top of win3.x?
that's just silly.. Slashdot+X already is a guaranteed flamefest, and it's ill-informed and/or mailicious crap like yours that causes it.
As for that killing brits thing: that's a bit sad. You're either trolling, or again making stupid comments about things you don't understand.
Re:Forked road or forked tongue
on
Is X The Future?
·
· Score: 1
running X is the functional equivalent of running Windows 3.x. It sits on top the real OS. Adding a modern WM like E or KWM with the baggage of either KDE or GNOME is the functional equivalent of running Win3.x on top of Win3.x
Do you actually have any understanding of X? Find out what it is (and what it isn't), and how it works before spouting out crap like the above.
uhmmm... GLX = OpenGL for X.. it uses the same mechanisms to talk to the X server as anything else.
Also, you don't write a programme for DRI or GLX. You write for OpenGL.
OpenGL is the API, and DRI/GLX is the backend. So you write an OpenGL app, and the OpenGL library implements the DRI/GLX part, using whichever one is available at runtime. So an OpenGL app doesn't have to know anything about how it actually get's displayed, be it via DirectX/vendor driver/DRI/GLX, doesn't matter.
Slashdot Mirror
I have the same thing with crossmounts between a couple of machines. Situations where you need to reboot both simultaniously are rare though.
What you can do is be a good administrator and change your init scripts. eg make sure you have a scripts to forcibly unmount your nfs mounts before doing unmount -f.
jeez... you have complete control of how the machine boots/shutsdown cause it all done via scripts. so use that power..
Replying to myself (bad form i know):
someone posted link to the Royal warrants FAQ down below, http://www.royal.gov.uk/faq/warrant.htm, and it turns out the crest i see on my pack of JP Blue is not that of one of the Royals! Anyone know what crest it is?
it's a shield with 3 little boat type things stacked top-left, grid top-right, castle below with suns on either side of it. lions rampant on either side and surmounted by a knights helmet with a crown on it.
Are John Player's taking the piss with a fake look-alike royal appointment? Or is the crest and appointment real?
(guaranteed someone on slashdot is into to heraldry)
John Player's have the Queens crest and "By Agreement with John Player & Sons" written underneath.
JP Blue, finest smokes in the world.. just a shame you can never find them outside of ireland.
he was the guy who arranged for Digital to ship one of their hot new Alpha systems to Linus. And this was when Alpha was still really new (eg 93 or something). Linus did the basic port to it in something like 2 weeks. The first ever port of linux.
He's been pushing linux inside DEC/Compaq ever since. Mad Dog had the kind of standing to push linux at the boardroom level. So Compaq's pro-linux attitude is due to him in no small way.
He also been a great Ambassador for linux, and has been an active member of Linux International for a very long time.
One of linux's more low-profile, but most influential proponents.
service packs are *easy* aren't they?
so easy, you have to reinstall them if you add a component from the NT cd.
And so easy when some application (usually MS) takes it upon itself to upgrade files that are also upgraded by a SP. Which version is the correct one? The one from the SP or the one the application installed? And maybe the app can't work with the version from the SP? So how do you install the SP? Or reinstall it if you've changed some vital config, eg changed the NIC?
And this kind of thing has infinite permutations, leading to hours and hours of NT admin fun. And hey, if it wasn't for NT admin's would never be able to claim overtime! Damm those Unix boxes that just purr away for months and months without a glitch. How can you ever earn money from them?
Yes service packs... gotta love them. you really do. {God, Allah, prefferred deity} bless NT!
that was a deficiency in the earlier libc5.
glibc aka libc6 has built-in posix threads. so this problem should be solved.
and don't forget, in addition to buying a motherboard, you'll most likely also need a new power supply.
The Athlon needs a minimum of a 300W peak PSU, and i don't know of any cases outside of big server cases that ship with 300W+. Most desktops and small towers have 200W, and midi/full towers tend be around 230-250W. Run an athlon in one of those and it'll be unstable as hell.
High power PSU's are pretty tricky to find aswell.
that bit about threads is wrong.
linux does support threads, and has since about 1.2. There was a recent discussion about it on linux-kernel. What i understood from it was that threads and processes are both created by the kernel's 'clone' call - which takes arguments to specify whether to share memory/stack/etc..
everything else uses that, in fact the traditional Unix process system creation calls are just C lib wrappers around linux clone(). Just as the thread library calls are.
So it seems linux supports threads pretty well, just the userspace library wasn't up to it until glibc.
you can also run md RAID5 on top of nbd...
have you tried H.J. Lu's knfsd nfs patches?
They make a huge difference to the stability of linux's nfs interoperability. The standard kernel nfs is horribly broken. I've used linux as an nfs server to linux, solaris x86 and MACH clients, and it works very reliably once you use knfsd. (but i've only tested with a couple of clients, not 60).
see ftp://ftp.varesearch.com/pub/support/hjl/knfsd/
is it true the Picturebook has 3 mice buttons?
Also does the camera work in linux?
Any ideas on what will power the wearables of the next century?
StrongARM are nice.
Designed by ARM Ltd. (UK company). Licensed by a lot of companies, eg intel. RISC-like, 32-bit. Currently available at up to 233MHz or so. Intel says they'll produce 600MHz+ versions in the near future.
Extremely low power consumption. Less than a Watt peak for the 233MHz version (~450mW @ 160MHz), just a few mW idle.
Supported by linux (eg the Netwinder). Company in England has an SA-110 ATX motherboard iirc. Also used in things like RAID controllers (Mylex's new one i think) and Empeg (car mp3 player -> www.empeg.com).
have a look at www.empeg.com - car MP3 player which runs linux.
Uses a StrongARM SA-110 CPU, which draws something like ~500mW peak and something in the region of 5-10mW idle.
your right. there's a problem with PCI which maps into memory at 1GB.. hence limiting physical RAM to 1GB. But I think it might have changed in 2.2.11 or so to 2GB (not sure).
:(
Tru64 supports scatter-gather mapping. ie arbitrary PCI address spaces can be mapped on demand to arbitrary address spaces. Also, the pyxis chipset used on a lot of PCI alpha's (PC164xx) has quite sophisticated scatter-gather support, ie cut-down page tables and a tlb (similar to the way most cpu's support virtual memory). But linux doesn't support this, and just uses direct mappings..
it's not a 'mode' switch. it uses truncated pointers and kernel support for a 32bit addr. space.
is that you ken?
:)
NT does run on a 64 bit cpu (like Linux and NetBSD) but it only uses 32 bits (like Linux)
linux is fully 64bit on Alpha!!! (UltraSparc kernel aswell, not sure about app's). The kernel is 64bit. The C libraries are fully 64bit. The App's are fully 64 bit. Linux is 64 bit clean!!!!!!
in fact the reason there's no netscape for Alpha is precisely because it's all 64bit and NS isn't 64bit clean.
there's another mode, vm86 mode, which is spefically for running 16bit code within a protected mode enviroment. it provides a virtual real mode.
windows9x/nt use it for dos compatibility. Linux supports it to a certain extent to help dosemu. Freebsd has more generalised support for it iirc.
dammed html..
App {- opengl functions -} OpenGL Library {- glx/dri/X11/directX/whatever -} Screen
sorry you're wrong.
if you write an OpenGL app you don't need to know anything about DRI or GLX or whatever. The call to create the viewable is an OpenGL call. It's then up to the OpenGL library to do whatever is needed, be it using glx/dri or plain X to create the window. ie:
app opengl library screen.
OpenGL is incredibly portable for this very reason cause you do not need to worry about glx/directX/whatever - that part is handled by the library.
ok.. so how's that like win3.x? and how is a wm+X like win3.x on top of win3.x?
that's just silly.. Slashdot+X already is a guaranteed flamefest, and it's ill-informed and/or mailicious crap like yours that causes it.
As for that killing brits thing: that's a bit sad.
You're either trolling, or again making stupid comments about things you don't understand.
running X is the functional equivalent of running Windows 3.x. It sits on top the real OS. Adding a modern WM like E or KWM with the baggage of either KDE or GNOME is the functional equivalent of running Win3.x on top of Win3.x
Do you actually have any understanding of X? Find out what it is (and what it isn't), and how it works before spouting out crap like the above.
uhmmm... GLX = OpenGL for X.. it uses the same mechanisms to talk to the X server as anything else.
Also, you don't write a programme for DRI or GLX. You write for OpenGL.
OpenGL is the API, and DRI/GLX is the backend. So you write an OpenGL app, and the OpenGL library implements the DRI/GLX part, using whichever one is available at runtime. So an OpenGL app doesn't have to know anything about how it actually get's displayed, be it via DirectX/vendor driver/DRI/GLX, doesn't matter.
i meant howto wharf wm* apps... :)
(sorry i wasn't very clear).
could you elaborate on how to do that please?
or maybe pointers to documentation.
ta..