If you get out of the house, you'll learn that the plot to "A Bug's Life" was just a re-hash of Akira Kurosawa's "Seven Samurai", as was Galaxy Quest and just about every other comedic action film on the planet.
The older BBCs (the Linuxcare era) were cut instead of moulded, so they tended to be more fragile. We've got a place in Hong Kong that burns the more sturdy variety for us.
You can burn the root.bin off of the CD onto a floppy, and boot off of that. The BBC uses the El-Torito boot standard, which basically defines a header for the location of a 1.44MB FAT volume. It's loopy, but it works on the widest set of machines.
The LNX-BBC uses the El-Torito boot standard, which actually uses a 1.44MB bootable floppy image to bootstrap into the CD at power-on. Have a look at the GAR tree, and you'll find that lnx.img and root.bin are there to make a boot floppy image you can dd to a diskette if you don't have a bootable CD-ROM.
The guy with the non-booting SCSI CD-ROM drive could even use this technique.
We actually use a compressed loopback filesystem, so our "singularity" file is pretending to be a disk drive with compressed disk blocks. Cool stuff!
The LNX-BBC boots into a fully running system. GAR is the compile tree, and we use it to track the changes we make to the LNX-BBC.
Yes, it's true that you won't fit KDE onto th 50MB media, but we ultimately hope to use the same build tree to compile for targets like 8cm and full-sized CD-ROMs.
Most browsers know how to deal with a PNG's alpha transparency natively. It seems that IE needs javurscript help. So I used the iesuckssohard.htc with some cut-and-paste IE-only javurscript and CSS to make the thing's alpha channels work.
I'm sorry that you're having trouble with it, but that's between you and Microsoft at this point. Perhaps you need to upgrade or something.
If you override the stylesheet, you should still be able to view the page. It's designed to be very lynx-friendly, among other things.
Actually, no. We were, however, neighbors for at least a year and didn't even know it. I'm actually in his new home town right now, and may drop by to see him this weekend.
I wrote the gnu make libraries that it uses, and the system is getting more and more robust as time goes on.
Of course, GAR is in itself a sort of packaging system, so the GARNOME tree is only as good as the dependencies it provides. You'll still have to install all of the other software.
GAR was designed originally with the idea that slackware users could just "make install" to upgrade to a newer tree of packages, but that was before I discovered that backing up your data and installing Debian was much quicker.
That said, GAR's main purpose is to build the complete filesystem tree for the LNX-BBC CD-ROM image. Ultimately we hope to have a complete GNU system packaged within it.
I'm not breaking these peoples' systems (as the MyParty worm does). I'm simply pre-emptively killfiling myself!
I also killfile outlook users based on the User-Agent and X-Mailer headers. It's entirely my perogative.
As for the mailing list dress code, it's MY GODDAMN LIST. If you want me to set up an open mailing list for everyone, just mail me and I'd be more than happy to set it up and host it on my machine for you! But the crackmonkey list is NOT that sort of list.
If you have something to say to me, you'll just have to make sure you get my attention, which is divided enough as it is now.
It's Scottish, actually. It was originally "Moffat", but you know how names change over time. Clan Moffat now officially recognizes some several dozen different spellings.
As you will see in my mail, the headers are irrelevant. The real bug is that the BODY OF MY MESSAGE contains a line beginning with "begin ". It's Outlook's inability to display ordinary English text that is at fault here, not some header processing GAR.
Re:Does this seem contradictory to you?
on
Borking Outlook Express
·
· Score: 5, Informative
You are confusing two different issues. One is the auto-killfile that I perform on myself, not allowing anyone using outlook to read my mails. The second is the "dress code" for posting to a mailing list I run. They're two different efforts.
The first says "I don't care if windows users can't read my mail"
The second says "I don't want windows users posting to my mailing list"
Ah, but the cost is not the end of the equation for government spending! Take this example:
Suppose that the overall cost of the operation were the same whether you used free software or a completely Microsoft-driven solution. Where does the money GO? In the Microsoft case, we know where it goes. It lines the pockets of executives in Bellevue and Mercer Island. In the case of the free software solution, the money goes to LOCAL CONTRACTORS AND CITY EMPLOYEES.
Yes, that's right folks. It makes JOBS. And it's JOBS that prop up the economy in these troubled times. Keep the money at home in Charlottesville!
One force that may work in your favor is home town pride. See if you can find any developers in your area, and find some way to brag about how you could be using software that was written "Right here in VA, and not in some Redmond office complex."
Get people on the self-reliance kick. Relate it to stories about early pioneers not relying on the support of the major cities, or to direct ancestors of people famous in the town.
Much of the Free Software advocacy kick is based on out-and-out pride. We try to push GNU, Linux and BSD into service not just because they're technically superior in many ways, but because we feel like it's made by Our People rather than some deranged Redmond focus group or snooty Cupertino aesthete. We can identify with the people who made it.
Remember that Red Hat is in North Carolina, too. I don't know how you folks feel about the triangle, but you may be able to work up some small regional pride there if you can't find any local developers.
Slashdot Mirror
If you get out of the house, you'll learn that the plot to "A Bug's Life" was just a re-hash of Akira Kurosawa's "Seven Samurai", as was Galaxy Quest and just about every other comedic action film on the planet.
This is a test release. Do you think you could have filed this in our bug system like we asked? Whingeing on slashdot isn't going to fix anything.
The older BBCs (the Linuxcare era) were cut instead of moulded, so they tended to be more fragile. We've got a place in Hong Kong that burns the more sturdy variety for us.
Not all business-card CDs are BBCs.
Our images will work on standard CD-Rs, so you can use it in machines with slot-loading drives if you like.
You can burn the root.bin off of the CD onto a floppy, and boot off of that. The BBC uses the El-Torito boot standard, which basically defines a header for the location of a 1.44MB FAT volume. It's loopy, but it works on the widest set of machines.
The LNX-BBC uses the El-Torito boot standard, which actually uses a 1.44MB bootable floppy image to bootstrap into the CD at power-on. Have a look at the GAR tree, and you'll find that lnx.img and root.bin are there to make a boot floppy image you can dd to a diskette if you don't have a bootable CD-ROM.
The guy with the non-booting SCSI CD-ROM drive could even use this technique.
We actually use a compressed loopback filesystem, so our "singularity" file is pretending to be a disk drive with compressed disk blocks. Cool stuff!
You are mistaken.
The LNX-BBC boots into a fully running system. GAR is the compile tree, and we use it to track the changes we make to the LNX-BBC.
Yes, it's true that you won't fit KDE onto th 50MB media, but we ultimately hope to use the same build tree to compile for targets like 8cm and full-sized CD-ROMs.
Heh.
Most browsers know how to deal with a PNG's alpha transparency natively. It seems that IE needs javurscript help. So I used the iesuckssohard.htc with some cut-and-paste IE-only javurscript and CSS to make the thing's alpha channels work.
I'm sorry that you're having trouble with it, but that's between you and Microsoft at this point. Perhaps you need to upgrade or something.
If you override the stylesheet, you should still be able to view the page. It's designed to be very lynx-friendly, among other things.
Jesux, man. Which one are you? Winkel?
I am not a role model.
I am not paid to be a role model.
But I do take paypal. Thank you.
Choose carefully, Medevo! For while one option brings sweet, sweet freedom, the other brings death!
Actually, no. We were, however, neighbors for at least a year and didn't even know it. I'm actually in his new home town right now, and may drop by to see him this weekend.
Even worse, don't say "utilization" when you mean "use" (s-sound, not z-sound). FOUR WASTED SYLLABLES.
I wrote the gnu make libraries that it uses, and the system is getting more and more robust as time goes on.
Of course, GAR is in itself a sort of packaging system, so the GARNOME tree is only as good as the dependencies it provides. You'll still have to install all of the other software.
GAR was designed originally with the idea that slackware users could just "make install" to upgrade to a newer tree of packages, but that was before I discovered that backing up your data and installing Debian was much quicker.
That said, GAR's main purpose is to build the complete filesystem tree for the LNX-BBC CD-ROM image. Ultimately we hope to have a complete GNU system packaged within it.
A RAID array, eh? Let's see, that would be a Redundant Array of Independent Disks array. Wow! You have a Redundant Matrix of Independent Disks!
How does that RMID work for you?
those headers are indistinguishable from the proprietary Netscape.
Mailing lists, McFly. Mailing lists.
Thank you, you've hit it right on the nose.
I'm not breaking these peoples' systems (as the MyParty worm does). I'm simply pre-emptively killfiling myself!
I also killfile outlook users based on the User-Agent and X-Mailer headers. It's entirely my perogative.
As for the mailing list dress code, it's MY GODDAMN LIST. If you want me to set up an open mailing list for everyone, just mail me and I'd be more than happy to set it up and host it on my machine for you! But the crackmonkey list is NOT that sort of list.
If you have something to say to me, you'll just have to make sure you get my attention, which is divided enough as it is now.
It's Scottish, actually. It was originally "Moffat", but you know how names change over time. Clan Moffat now officially recognizes some several dozen different spellings.
That might be because your exchange server is processing the attachments beforehand.
Which mailer, in particular?
You are confusing two different issues. One is the auto-killfile that I perform on myself, not allowing anyone using outlook to read my mails. The second is the "dress code" for posting to a mailing list I run. They're two different efforts.
The first says "I don't care if windows users can't read my mail"
The second says "I don't want windows users posting to my mailing list"
There is a distinction.
Ah, but the cost is not the end of the equation for government spending! Take this example:
Suppose that the overall cost of the operation were the same whether you used free software or a completely Microsoft-driven solution. Where does the money GO? In the Microsoft case, we know where it goes. It lines the pockets of executives in Bellevue and Mercer Island. In the case of the free software solution, the money goes to LOCAL CONTRACTORS AND CITY EMPLOYEES.
Yes, that's right folks. It makes JOBS. And it's JOBS that prop up the economy in these troubled times. Keep the money at home in Charlottesville!
One force that may work in your favor is home town pride. See if you can find any developers in your area, and find some way to brag about how you could be using software that was written "Right here in VA, and not in some Redmond office complex."
Get people on the self-reliance kick. Relate it to stories about early pioneers not relying on the support of the major cities, or to direct ancestors of people famous in the town.
Much of the Free Software advocacy kick is based on out-and-out pride. We try to push GNU, Linux and BSD into service not just because they're technically superior in many ways, but because we feel like it's made by Our People rather than some deranged Redmond focus group or snooty Cupertino aesthete. We can identify with the people who made it.
Remember that Red Hat is in North Carolina, too. I don't know how you folks feel about the triangle, but you may be able to work up some small regional pride there if you can't find any local developers.