You're snipping out the context:
Any review, reproduction, retransmission, dissemination
or other use of, or taking of any action in reliance upon, this information by
persons or entities other than the intended recipient is prohibited.
(emphasis mine)
I believe posting it on a publically-accessible website qualifies as making it availible for review by "by persons or entities other than the intended recipient".
bush_assassination_plan.doc The Department Of Homeland Security is pleased to inform you that the enemy of freedom known as "Octagon Most" in online terrorist circles has been eliminated.
Because you usually want *control* of where and how the kernel goes. install just puts it into the default path and (AFAIR, I haven't used it in a bit) updates lilo accordingly. I name my kernels according to version and specific features I compiled in. A naming scheme allows me to roll back to a specific older kernel that I know to be working if something goes wrong.
It's possible to modify the makefile to do that for me, to an extent, but I just don't compile kernels often enough to bother.
I knew some guys in high school who were really in to things like this. They hit college, promptly failed out (because they made straight As in high school without trying, they saw no need to go to class) and are now working at various shit jobs. One works at a gas station, one works at a grocery store, etc. "LAN Gamer" is not a skill that will serve you any good in the near or distant future.
And how exactly "going out and living a little" would have remedied their troubles? I honestly don't see any connection between attending LAN parties semi-freqently and being an utter failure. LAN parties and gaming are about as beneficial as any hobby- small advantages (improved reflexes, better logical thinking- to an extent), minute possibilities for gigantic success (i.e. starting your own game studio and writing the next DooM), a stimulus for socializing, but generally an unproductive use of one's time.
You are correct. However, posting the full text has become a gesture welcome by most readers, it seems. I will refrain from doing so in the future, however, and I aplogize to the author in this case.
Re:Full text:
on
Palmtop NetBSD
·
· Score: 5, Interesting
Erm. I did not realize a quick cut'n'paste aimed at alleviating the slashdot effect would be considered a reprint. Please pardon me, normally it isn't a problem.
In my previous article, I discussed building the latest NetBSD-current and installing it on your system. Today, we take things a little further and use NetBSD's cross-building abilities as a tool to install it on a rather unusual platform â" specifically, the HP Jornada 728 palmtop, which comes with Windows CE (WinCE) embedded. While HP no longer makes this device, you can pick them up used or on auction sites. The process discussed here uses examples from the Jornada 728, but with some tweaking will work on many other types of hardware. You could even install onto standard PC hardware in this manner, if you wanted to be masochistic about it.
Setup This method requires that you already have a NetBSD machine that can physically accept the disk device you want to install onto, and that has the same sort of disklabel(8) as the Jornada, which means that you need the same endian hardware. You're probably best off running standard X86 hardware for this type of installation on this type of palmtop. In this example, I use a Toshiba laptop running NetBSD-current 1.6P to install NetBSD-current 1.6P on my Jornada. I'm using a 512MB flash card to run NetBSD, and am using a PCMCIA adapter to attach the flash card to the laptop during the installation phase. If you're using a desktop, you could use a USB-to-Flash adapter.
Running NetBSD on your Jornada will erase all data from the WinCE operating system. That's OK, because you'll never boot back to Windows once you discover the joys of palmtop UNIX, right? Still, you might want the WinCE data some day, so be certain to back up your device before starting this install! Some people who switch boots between WinCE and NetBSD use the backup tool that comes with WinCE to back up their data to the FAT partition on their flash card. If you do this, be sure to use only the backup tool that came with the Jornada, not a newer version.
NetBSD runs on a whole bunch of hardware that was never intended to run UNIX, so this install isn't really anything special. Each of these unusual platforms has its own unique requirements, which are generally documented on the appropriate port page for that architecture. Check the port page for an instructions document, which in this case is the Using NetBSD/hpcarm page. The directions may be partially obsolete, as code development frequently outpaces the web documentation. Still, it's a good place to start. Also search the mailing list archives for your chosen platform for other people's experiences installing and running NetBSD on that system. Lastly, you'll want to be certain that NetBSD runs on your system â" for example, while the Jornada 720 and 728 are well-supported, the Jornada 820 isn't yet.
Bootstrapping The how-to-use page for hpcarm shows that you need a kernel and a boot loader that runs in the WinCE environment. At this time the page also mentions a root filesystem image, which is not yet available. The only piece you really need to get at this point is the hpcarm boot loader, which is available as a uuencoded file in the NetBSD source tree at/usr/src/sys/arch/hpc/stand/binary/ARM/hpcboot.exe.uu. If you have trouble with uudecode, Google led me to a variety of places from which it could be downloaded. Get the boot loader hpcboot.exe and save it for later. Don't worry about the kernel linked from that page; we'll build our own kernel.
Now go to your existing NetBSD system. We covered the basics of building NetBSD in the last article, including getting the source code and using the build.sh building system. As each platform has its own compiler requirements, make(1), and so on, we need to start by building these tools for the hpcarm architecture. Here, we use the -T flag to specify where to put these tools, and the -m flag to specify the type of machine for which you're building.
No, it's like suing ford because the doors in your car don't lock factory-standard, and fixing them requires a professional mechanic and a pile of manuals, and any further repairs to the car might break the door again. And did I mention the gigantic neon sign on the roof stating "ROB ME PLEASE!"?
Reformatted properly, accidentally selected the incorrect formating option and didn't hit preview:
Do their heads hurt when they watch tv? Or when they watch fluroescent light tubes? Or when they drive on a flood lighted road by night?
Don't be a stupid geek. Don't invent silly "I'm more sensitive than you and need more expensive equipment" mindsets which ultimately drives up the price for the rest of us.
Now, now, he may be misguided, but there's no need to flame him. 75Hz and below is indeed bad (and immediately painful for some) for the eyes on a CRT; on an LCD there is no flicker even at 60Hz, as another poster pointed out, of course, but he may be making judgements based on CRT experience.
Also, I do get a slight headache after looking directly at a fluorescent light.
And why would "IRC junkies" want big screens
Several BitchX windows open in separate xterms, perhaps.
On a side note, I've noticed that I can actually see the CRT screen flickering at 72Hz when I am looking at it from the side, on the edge of my peripheral vision, but not straight on. Does anyone know why that is?
Do their heads hurt when they watch tv? Or when they watch fluroescent light tubes? Or when they drive on a flood lighted road by night?
Don't be a stupid geek. Don't invent silly "I'm more sensitive than you and need more expensive equipment" mindsets which ultimately drives up the price for the rest of us.
Now, now, he may be misguided, but there's no need to flame him. 75Hz and below is indeed bad (and immediately painful for some) for the eyes on a CRT; on an LCD there is no flicker even at 60Hz, as another poster pointed out, of course, but he may be making judgements based on CRT experience.
Also, I do get a slight headache after looking directly at a fluorescent light.
And why would "IRC junkies" want big screens
Several BitchX windows open in separate xterms, perhaps.
On a side note, I've noticed that I can actually see the CRT screen flickering at 72Hz when I am looking at it from the side, on the edge of my peripheral vision, but not straight on. Does anyone know why that is?
Actually, my for-college lineup is as follows:
-Ultrasparc 4 (custom case, rackmounted)
-Cisco 2900 x2
-iMac (custom case, rackmounted, just for the hell of it)
-2x 3U x86 servers
All in a nice 10U rolling case. Paper is the medium of choice for in-class notes, but geeks stuff deserves a nice rackmount mini-farm.
I really don't find debian install to be such a pain. Autodetection for the NIC driver and complete removal of dselect are pretty much the only changes I could wish for.
I am not denying that first-time setup may involve a *bit* more thought than RH/SuSE/MD, but once operational (~1.5hr process for me, usually; most of that is downloading) the system is much easier to maintain. You know exactly what modules are compiled, what packages are installed, where everything lives, and how to fix it if it breaks. I initially switched to linux seeking a greater degree of control of my system, and I can say that Debian install is a perfect example.
Re:OK, most are ugly, but fvwm is the fug-ugliest
on
fvwm Turns Ten
·
· Score: 1
You should try aewm, my favorite window manager. The cool thing about it is that an uninitiated user will not be able to do *anything* with it:)
This was done by placing the keys in such a configuration, such that no two successive keys were right beside eachother.
Do you not think that would reduce typing speed?
Slashdot Mirror
You're snipping out the context:
Any review, reproduction, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited.
(emphasis mine)
I believe posting it on a publically-accessible website qualifies as making it availible for review by "by persons or entities other than the intended recipient".
Heh, there's of course the infinitely slim chance that the 286 in the corner will stumble upon the key at 2 o'clock this sunday afternoon ;)
Once again, the story has been posted on physicsweb two days ago.
bush_assassination_plan.doc
The Department Of Homeland Security is pleased to inform you that the enemy of freedom known as "Octagon Most" in online terrorist circles has been eliminated.
Are you trying to say that the vast majority of the human race has the intellegence of the bugblatter beast because geeks can't get laid? ;)
It's "Rosaviakosmos", not "Rosoviakosmos".
Posted previously on slashdot; head overehere for the discussion.
I blame the new, undocumented "Make /. critics appear hypocritical" feature of slashcode.
Whether or not slashdot editors will ever startproofreading their stories or not.
Because you usually want *control* of where and how the kernel goes. install just puts it into the default path and (AFAIR, I haven't used it in a bit) updates lilo accordingly. I name my kernels according to version and specific features I compiled in. A naming scheme allows me to roll back to a specific older kernel that I know to be working if something goes wrong. It's possible to modify the makefile to do that for me, to an extent, but I just don't compile kernels often enough to bother.
BT checks file integrity by SHA1 hashing; MD5ing the files is redundant, unless you do not trust the original seed.
I knew some guys in high school who were really in to things like this. They hit college, promptly failed out (because they made straight As in high school without trying, they saw no need to go to class) and are now working at various shit jobs. One works at a gas station, one works at a grocery store, etc. "LAN Gamer" is not a skill that will serve you any good in the near or distant future. And how exactly "going out and living a little" would have remedied their troubles?
I honestly don't see any connection between attending LAN parties semi-freqently and being an utter failure. LAN parties and gaming are about as beneficial as any hobby- small advantages (improved reflexes, better logical thinking- to an extent), minute possibilities for gigantic success (i.e. starting your own game studio and writing the next DooM), a stimulus for socializing, but generally an unproductive use of one's time.
The section doesn't really seem appropriate, unless someone builds a web-controlled robot that plays these things, of course.
You are correct. However, posting the full text has become a gesture welcome by most readers, it seems. I will refrain from doing so in the future, however, and I aplogize to the author in this case.
Erm. I did not realize a quick cut'n'paste aimed at alleviating the slashdot effect would be considered a reprint. Please pardon me, normally it isn't a problem.
Palmtop NetBSD
/usr/src/sys/arch/hpc/stand/binary/ARM/hpcboot.exe .uu. If you have trouble with uudecode, Google led me to a variety of places from which it could be downloaded. Get the boot loader hpcboot.exe and save it for later. Don't worry about the kernel linked from that page; we'll build our own kernel.
/usr/src ./build.sh -m hpcarm -T /
by Michael Lucas
06/05/2003
In my previous article, I discussed building the latest NetBSD-current and installing it on your system. Today, we take things a little further and use NetBSD's cross-building abilities as a tool to install it on a rather unusual platform â" specifically, the HP Jornada 728 palmtop, which comes with Windows CE (WinCE) embedded. While HP no longer makes this device, you can pick them up used or on auction sites. The process discussed here uses examples from the Jornada 728, but with some tweaking will work on many other types of hardware. You could even install onto standard PC hardware in this manner, if you wanted to be masochistic about it.
Setup
This method requires that you already have a NetBSD machine that can physically accept the disk device you want to install onto, and that has the same sort of disklabel(8) as the Jornada, which means that you need the same endian hardware. You're probably best off running standard X86 hardware for this type of installation on this type of palmtop. In this example, I use a Toshiba laptop running NetBSD-current 1.6P to install NetBSD-current 1.6P on my Jornada. I'm using a 512MB flash card to run NetBSD, and am using a PCMCIA adapter to attach the flash card to the laptop during the installation phase. If you're using a desktop, you could use a USB-to-Flash adapter.
Running NetBSD on your Jornada will erase all data from the WinCE operating system. That's OK, because you'll never boot back to Windows once you discover the joys of palmtop UNIX, right? Still, you might want the WinCE data some day, so be certain to back up your device before starting this install! Some people who switch boots between WinCE and NetBSD use the backup tool that comes with WinCE to back up their data to the FAT partition on their flash card. If you do this, be sure to use only the backup tool that came with the Jornada, not a newer version.
NetBSD runs on a whole bunch of hardware that was never intended to run UNIX, so this install isn't really anything special. Each of these unusual platforms has its own unique requirements, which are generally documented on the appropriate port page for that architecture. Check the port page for an instructions document, which in this case is the Using NetBSD/hpcarm page. The directions may be partially obsolete, as code development frequently outpaces the web documentation. Still, it's a good place to start. Also search the mailing list archives for your chosen platform for other people's experiences installing and running NetBSD on that system. Lastly, you'll want to be certain that NetBSD runs on your system â" for example, while the Jornada 720 and 728 are well-supported, the Jornada 820 isn't yet.
Bootstrapping
The how-to-use page for hpcarm shows that you need a kernel and a boot loader that runs in the WinCE environment. At this time the page also mentions a root filesystem image, which is not yet available. The only piece you really need to get at this point is the hpcarm boot loader, which is available as a uuencoded file in the NetBSD source tree at
Now go to your existing NetBSD system. We covered the basics of building NetBSD in the last article, including getting the source code and using the build.sh building system. As each platform has its own compiler requirements, make(1), and so on, we need to start by building these tools for the hpcarm architecture. Here, we use the -T flag to specify where to put these tools, and the -m flag to specify the type of machine for which you're building.
# cd
#
No, it's like suing ford because the doors in your car don't lock factory-standard, and fixing them requires a professional mechanic and a pile of manuals, and any further repairs to the car might break the door again. And did I mention the gigantic neon sign on the roof stating "ROB ME PLEASE!"?
Reformatted properly, accidentally selected the incorrect formating option and didn't hit preview: Do their heads hurt when they watch tv? Or when they watch fluroescent light tubes? Or when they drive on a flood lighted road by night? Don't be a stupid geek. Don't invent silly "I'm more sensitive than you and need more expensive equipment" mindsets which ultimately drives up the price for the rest of us.
Now, now, he may be misguided, but there's no need to flame him. 75Hz and below is indeed bad (and immediately painful for some) for the eyes on a CRT; on an LCD there is no flicker even at 60Hz, as another poster pointed out, of course, but he may be making judgements based on CRT experience.
Also, I do get a slight headache after looking directly at a fluorescent light.
And why would "IRC junkies" want big screens
Several BitchX windows open in separate xterms, perhaps.
On a side note, I've noticed that I can actually see the CRT screen flickering at 72Hz when I am looking at it from the side, on the edge of my peripheral vision, but not straight on. Does anyone know why that is?
Do their heads hurt when they watch tv? Or when they watch fluroescent light tubes? Or when they drive on a flood lighted road by night? Don't be a stupid geek. Don't invent silly "I'm more sensitive than you and need more expensive equipment" mindsets which ultimately drives up the price for the rest of us.
Now, now, he may be misguided, but there's no need to flame him. 75Hz and below is indeed bad (and immediately painful for some) for the eyes on a CRT; on an LCD there is no flicker even at 60Hz, as another poster pointed out, of course, but he may be making judgements based on CRT experience. Also, I do get a slight headache after looking directly at a fluorescent light. And why would "IRC junkies" want big screens Several BitchX windows open in separate xterms, perhaps. On a side note, I've noticed that I can actually see the CRT screen flickering at 72Hz when I am looking at it from the side, on the edge of my peripheral vision, but not straight on. Does anyone know why that is?
Actually, my for-college lineup is as follows: -Ultrasparc 4 (custom case, rackmounted) -Cisco 2900 x2 -iMac (custom case, rackmounted, just for the hell of it) -2x 3U x86 servers All in a nice 10U rolling case. Paper is the medium of choice for in-class notes, but geeks stuff deserves a nice rackmount mini-farm.
Couldn't the same task be accomplished via a script that calls scp foo bob@fred:~/ssh bob@fred -t "rm foo"/etc?
Why can't they just hit ctrl-alt-backspace?
I really don't find debian install to be such a pain. Autodetection for the NIC driver and complete removal of dselect are pretty much the only changes I could wish for. I am not denying that first-time setup may involve a *bit* more thought than RH/SuSE/MD, but once operational (~1.5hr process for me, usually; most of that is downloading) the system is much easier to maintain. You know exactly what modules are compiled, what packages are installed, where everything lives, and how to fix it if it breaks. I initially switched to linux seeking a greater degree of control of my system, and I can say that Debian install is a perfect example.
You should try aewm, my favorite window manager. The cool thing about it is that an uninitiated user will not be able to do *anything* with it :)
This was done by placing the keys in such a configuration, such that no two successive keys were right beside eachother. Do you not think that would reduce typing speed?