Re: [Leaf-devel] MTD/DOC2000 question
Hi Conrad What kernel are you booting off? As far as I know, the stock bering kernel doesn't have DOC support built in, so even though you have the device files, you won't be able to access ntfla1 unless you build your own kernel with DOC support.. When I last setup a DOC based system, I booted it off an IDE drive running DOS, formatted the DOC with a FAT filesystem (in fact installed DOS), copied all the Bering stuff over, along with a customer kernel with DOC support, ran syslinux on the DOC as boot loader. Seemed to work fine. Cheers Si On Tue, Jul 23, 2002 at 09:37:16AM -0700, Conrad Steenberg said: Hi Jacques Thanks for your reply. I think my question was a little unclear, though: Making the devices works fine, whether by hand or using root.dev.mk. What has me stumped is formatting the partition (using either mke2fs of mkfs.minix from busybox) which gives me the errors described below. The Netier doesn't have a hard drive, so it has to be booted using PXE/dhcp/tftp until I can get the DOC formatted. And I'd very much like to keep it HD-less since it is blissfully quiet :-) Cheers! Conrad On Tue, 2002-07-23 at 01:27, Jacques Nilo wrote: I'm new to LEAF and embedded devices, so please bear with me :-) I trying to create a filesystem on a 72M DOC2000 (Netier XL1000), and get up to creating a partition (/dev/nftla1). This is with Bering-rc3. When I try mke2fs /dev/nftla1, the following gets reported: NFTL_writeblock(): Cannot find block to write to end_request; I/O error, dev 5d:01 (unknown) sector X Argh! No free blocks found LastFreeEUN = 4603, FirstEUN = 3 No Virtual Unit Chains available for folding. Failing request This gets repeated lots of times with different values for X. (I _think_ that the utility nftl_format might be able to free the blocks on the DOC, but I don't know where to get one that's been compiled for Bering.) Does anybody have an idea why the error mesages happen, and maybe what to do about it? Or better yet, have copies of the nftl utilities compiled with the right libc(+kernel?) to work with Bering? From Bering rc3 Changelog: root.dev.mk updated to create mtd, nftla1-4, lp0, lp1 devices for DoC and parallel printer support The relevant devices are created automatically at boot time (check the /dev directory). Jacques -- Profitez de l'offre exceptionnelle Tiscali ! Internet Gratuit le Jour Cliquez ici, http://register.tiscali.fr/forfaits_ls/ Offre soumise à conditions. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel -- --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel --- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[Leaf-devel] leaf-announce ML
Subject was: Re: [Leaf-devel] Re: [leaf-user] Bering: PPTP server updated (pptpd.lrp) On Mon, 2002-07-29 at 23:08, Dan Harkless wrote: Mike Noyes [EMAIL PROTECTED] writes: Everyone, Announcements should be posted on our leaf-announce list, and/or posted ^^ on our phpWebSite. Please don't cross post announcements to leaf-user. Um, that and/or worries me a bit. I hope important things like security advisories, bugfix updates, and the like are always posted to leaf-announce. Not _or_ posted on our phpWebSite. Dan, I didn't say anything about posting security advisories on our phpWebSite. I said announcements are and/or. Right. And security advisories are a subcategory of announcements, are they not? That's announcements as in leaf-announce. Dan, Security advisories are not a subset of announcements. They are permitted on leaf-announce because we don't have a security list. Larger projects usually have separate lists for security advisories and announcements. Example: http://www.debian.org/MailingLists/subscribe debian-announce debian-security-announce I suspect what you had in mind when you said and/or was that important stuff, including, but not limited to, security advisories, should go to leaf-announce, and less important stuff, like announcements of interesting potential LEAF hardware platforms, should be website posts. That is not what I had in mind. The person making the announcement needs to decide the target audience. Our mailing lists reach a different set of users than our web site. Note: our web site provides an RDF news feed, and it's syndicated. http://syndic8.com/feedinfo.php?FeedID=7207 That just wasn't clear from your statement, I hope this message clarifies matters. and I was hoping people wouldn't get the wrong idea, since we're trying to correct the underuse of leaf-announce for its intended purpose. I understand your desire to have a functional announce list. I created it in the hope it would be useful. It hasn't to date, but not for lack of trying on my part. I was redirecting posts from our other lists to leaf-announce, and rewriting web site announcements for a while. Thanks for your feedback. BTW, regarding bugs: Bugs are reported on leaf-user or in our SF project bug tracker. Then corrected in cvs, and noted in a changlog of each release. You can monitor all steps of this process if you want to. -- Mike Noyes [EMAIL PROTECTED] http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ --- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] MTD/DOC2000 question
Hi Simon I used the installer's ability to load modules at startup to get the DOC to work (after doing it a couple of times by hand to get it to work ;-) The kernel that Bering ships with has all the right modules available (go to the Bering download page, which links to http://sourceforge.net/project/showfiles.php?group_id=13751 and get Bering_1.0-rc3_modules_2.4.18.tar.gz) I was trying to hack the installer to be able to install on the DOC so that I could distribute the result, but it seems the installer wants to load packages and modules from a mounted device, and install the system on a ramdisk, while I want to load packages and modules from a directory and install on a mounted device and make the device bootable. So it seems like just making a custom install like yu did would be a lot less trouble. Cheers! Conrad On Tue, 2002-07-30 at 02:05, Simon Blake wrote: Hi Conrad What kernel are you booting off? As far as I know, the stock bering kernel doesn't have DOC support built in, so even though you have the device files, you won't be able to access ntfla1 unless you build your own kernel with DOC support.. When I last setup a DOC based system, I booted it off an IDE drive running DOS, formatted the DOC with a FAT filesystem (in fact installed DOS), copied all the Bering stuff over, along with a customer kernel with DOC support, ran syslinux on the DOC as boot loader. Seemed to work fine. Cheers Si On Tue, Jul 23, 2002 at 09:37:16AM -0700, Conrad Steenberg said: Hi Jacques Thanks for your reply. I think my question was a little unclear, though: Making the devices works fine, whether by hand or using root.dev.mk. What has me stumped is formatting the partition (using either mke2fs of mkfs.minix from busybox) which gives me the errors described below. The Netier doesn't have a hard drive, so it has to be booted using PXE/dhcp/tftp until I can get the DOC formatted. And I'd very much like to keep it HD-less since it is blissfully quiet :-) Cheers! Conrad On Tue, 2002-07-23 at 01:27, Jacques Nilo wrote: I'm new to LEAF and embedded devices, so please bear with me :-) I trying to create a filesystem on a 72M DOC2000 (Netier XL1000), and get up to creating a partition (/dev/nftla1). This is with Bering-rc3. When I try mke2fs /dev/nftla1, the following gets reported: NFTL_writeblock(): Cannot find block to write to end_request; I/O error, dev 5d:01 (unknown) sector X Argh! No free blocks found LastFreeEUN = 4603, FirstEUN = 3 No Virtual Unit Chains available for folding. Failing request This gets repeated lots of times with different values for X. (I _think_ that the utility nftl_format might be able to free the blocks on the DOC, but I don't know where to get one that's been compiled for Bering.) Does anybody have an idea why the error mesages happen, and maybe what to do about it? Or better yet, have copies of the nftl utilities compiled with the right libc(+kernel?) to work with Bering? From Bering rc3 Changelog: root.dev.mk updated to create mtd, nftla1-4, lp0, lp1 devices for DoC and parallel printer support The relevant devices are created automatically at boot time (check the /dev directory). Jacques -- Profitez de l'offre exceptionnelle Tiscali ! Internet Gratuit le Jour Cliquez ici, http://register.tiscali.fr/forfaits_ls/ Offre soumise à conditions. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel -- --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel -- *-* | Conrad Steenberg| | Caltech, Mail Code 356-48 | | Pasadena, CA, 91125 | | e-mail: [EMAIL PROTECTED] | | Tel: (626) 395-8758 | *-* --- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code1 ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[Leaf-devel] Is there a lawyer in the house? (long)
Hi all Hoping that the mail-snafu has blown over, I hope to resume the licensing discussion WRT my blinder.lrp (and licensing issues in general): Since I got the responses on the 'Speaking of Licensing' thread, I've done a fair amount of reading, and have been reminded why I *loathe* paperwork :-P I think it might be practical to split this thread in two 'separate' subthreads; [legal] About the copyrights/-lefts/legalese. What may/must I (not) do and, [practical] on how/where to put notices, source locations etc. and so: [legal] I'm almost finished reviewing the code, and thus far the only piece that remains unchanged since I found it, is the bit that does the actual writes to the parport. I put the src at http://bund.dk/blinder/lptout.c.html It does contain a copyright notice, but as I understand it, as long as I make sure that's kept in place, then it's o.k. use/post the code(?) I've contacted the author, and am awaiting his reply. What I'm more uncertain of however, is how this plays out if I decide to release my work under the GPL? The only other thing that bears significant resemblance to any 'original' is the main part of the webinterface. As such it is, in fact, a complete rewrite of Justins index.html. But I feel that I owe it to him to give him credits, so I'm going to put an Original design by Justin Ribeiro (C) bladablada in that. The rest is so far removed, that I don't think I'll be stepping on anybody's toes if I declare it my own. Evenso, I will try to compile a list of references to the material that I used as guides. As for choice of license... Much as I like the idea of releasing under the GPL, it sure looks like there's a lot of 'overhead' involved, what with section 2(a,b,c)'s requierements that You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change. etc. So that in the (likely) event that I make changes/updates to the software at a later time, I could spend as much time fulfilling the above requirements, as I do coding... How do you guys deal with that? The MIT-license, otoh, (appealing as it is in it's brevity) does it (legally) do anything other than make sure you get ongoing credit? [/legal] [practical] The software can be seen as divided between the 'runtime' stuff and the configuration stuff (cgi-scripts mostly) Both 'groups' are made up of a main script, and a number of 'support' scripts/programs. so for the .lrp -can I get away with only quoting the full copyright notice in the 'main' parts, and then make an abbreviated notice in the 'subscripts' pointing to the full quote in the main? (to save space) Also I don't see any LICENSE files in other .lrps that I've looked at. Is there a geenral concensus towards Mike's quote that Embedded releases can't practically include full license text, so I think linking is acceptable.? As for source: Until I get around to learning how to use CVS, this software will only be available from the download area that I'm about to set up at bund.dk/blinder/download/ From this location I will make available the blinder.lrp itself and a tarball of src/everything. Am I to understand that what Ray meant by I never see the full text of licenses included in the actual source code files themselves, though an accompanying LICENSE file is fairly common with the source packages. is that said LICENSE file should hold a *full* quote of whichever license? [/practical] PHEW!!! -sorry, this got somewhat longer than I intended, but I hope it's not too much... TIA Jon Clausen --- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] MTD/DOC2000 question
Conrad, SImon: I would really like to add a new chapter in the Bering user's guide about Booting Bering from DoC. Would you be ready to draft something ? Jacques --- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [Leaf-devel] MTD/DOC2000 question
Hi Jacques I'll gladly write something, but let me first get it to boot from the DoC ;-) The hold-up is that the leaf install script is heavily geared towards booting from a floppy and then installing on a ramdisk. Anyway, I'm still trying to hack the install script to install to the DoC. Cheers! Conrad On Tue, 2002-07-30 at 13:37, Jacques Nilo wrote: Conrad, SImon: I would really like to add a new chapter in the Bering user's guide about Booting Bering from DoC. Would you be ready to draft something ? Jacques -- *-* | Conrad Steenberg| | Caltech, Mail Code 356-48 | | Pasadena, CA, 91125 | | e-mail: [EMAIL PROTECTED] | | Tel: (626) 395-8758 | *-* --- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[Leaf-devel] Re: leaf-announce ML
Mike Noyes [EMAIL PROTECTED] writes: Right. And security advisories are a subcategory of announcements, are they not? That's announcements as in leaf-announce. Dan, Security advisories are not a subset of announcements. They are in most people's minds. That's why I wanted to clarify your statement. They are permitted on leaf-announce because we don't have a security list. Larger projects usually have separate lists for security advisories and announcements. Example: http://www.debian.org/MailingLists/subscribe debian-announce debian-security-announce Sure, if you go up to the level of a whole OS, there will often be separate announce and security mailing lists, but 99+% of open source projects have a single project-announce list, which covers both general and security announcements. I suspect what you had in mind when you said and/or was that important stuff, including, but not limited to, security advisories, should go to leaf-announce, and less important stuff, like announcements of interesting potential LEAF hardware platforms, should be website posts. That is not what I had in mind. The person making the announcement needs to decide the target audience. Our mailing lists reach a different set of users than our web site. I think you're making the criteria more vague and complicated than need be. Bottom-line, stuff that's important for most or all LEAF users to hear, including, but not limited to, security advisories, should definitely be posted to leaf-announce. That just wasn't clear from your statement, I hope this message clarifies matters. Well, since you've redirected the thread off of leaf-user, it's partially a moot point. It wasn't clarification for me personally that I was driving for, but for others. But I suppose most of the people who are likely to have posts worthy of leaf-announce subscribe to leaf-devel. BTW, regarding bugs: Bugs are reported on leaf-user or in our SF project bug tracker. Then corrected in cvs, and noted in a changlog of each release. You can monitor all steps of this process if you want to. Okay. That conflicts with what Jacques said -- he said to use leaf-devel rather than leaf-user. But you both said to use the bug tracker, so as that's the most targeted path for bug reports, that's what I'll use in the future. You probably should update the Bering install and user's guides to say to use that, rather than saying to email you guys directly. -- Dan Harkless [EMAIL PROTECTED] http://harkless.org/dan/ --- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ___ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
