This list is closed, nobody may subscribe to it.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
(69) |
May
(6) |
Jun
(27) |
Jul
(6) |
Aug
(22) |
Sep
(13) |
Oct
(11) |
Nov
(1) |
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
|
Feb
(3) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <pn...@ut...> - 2005-03-12 03:52:32
|
Unfortunately, I am still alive and so is WCLP. Surprise! What have I been up to for the past few months? I have been making half-hearted attempts at getting a release ready, and as part of that effort I have been writing some user documentation. The documentation is still fairly incomplete (it is missing most of the user application information, and I only included one token screenshot) and is already out of date but I am hoping that it is a start towards getting real documentation. You can take a look at the HTML and PDF versions of the userguide from http://wclp.sourceforge.net/documentation.html http://wclp.sourceforge.net/documentation/userguide/index.html In other news, the FreeGeek guys have a new release, and a Subversion repository for their packages. At some point we might want to look at this. As well, the Ubuntu team has been working on good user documentation as well. That's what I got. Does anybody else have anything to report? - Paul |
|
From: Mark B. <ma...@wa...> - 2005-02-14 22:54:55
|
Message: 1 ## Date: Fri, 11 Feb 2005 13:39:13 -0500 (EST) ## From: Paul Nijjar <pn...@ut...> ## To: wcl...@li... ## Subject: Re: [Wclp-admin] WCLP Installation Notes I - ## Display Problems - ## February 7, 2005 ## Reply-To: wcl...@li... ## ## On Mon, 7 Feb 2005, Mark Bellinger wrote: ## ## > The resolution was to include 'vga=0x0300' in the boot ## command/kernel ## > paramters under grub. (btw, I really like grub...) ## I looked this up. It sets the VGA display to a ## particular mode. Is ## it 24x80 mode? Specifically, 0x300 is 8bit, 640x400. I think 0x303 would be fine as well (8bit, 640x480). My reference is the Framebuffer HOWTO (p. 6) found at faqs.org. ## Is there anything special about the monitors ## in question? ## Are they only capable of 640x480 or anything like that? I think that is the problem. Thanks. Mark |
|
From: Paul N. <pn...@ut...> - 2005-02-11 18:39:22
|
On Mon, 7 Feb 2005, Mark Bellinger wrote: > The resolution was to include 'vga=0x0300' in the boot command/kernel > paramters under grub. (btw, I really like grub...) I looked this up. It sets the VGA display to a particular mode. Is it 24x80 mode? Is there anything special about the monitors in question? Are they only capable of 640x480 or anything like that? I will look into patching the GRUB options, and let you know how it turns out. Thanks for the bug report. We always appreciate your notes from the field. - Paul |
|
From: Mark B. <mbe...@wa...> - 2005-02-07 15:59:35
|
I have been doing a number of installs using the WCLP 0.7.1. I found the following problem... After loading WCLP and rebooting, the text screen (prior to going to X) flashes on and off. This makes it hard to troubleshoot and is confusing to others. Once it goes into X, all is good. =20 The resolution was to include 'vga=3D0x0300' in the boot command/kernel paramters under grub. (btw, I really like grub...) I would suggest including this as a default for all setups, as old monitors are common. Mark Bellinger |
|
From: Paul N. <pn...@ut...> - 2004-12-18 04:26:44
|
This mailing list has been kind of dead lately, so I thought I would post some drivel for you: - Inspired by Charles's hard work in translating the admin guide, I have been writing some user documentation in Mockbook. Now that I have jinxed the project by telling you about it there's no danger it will ever get finished, and maybe that's a good thing. I meant it to be a short and sweet introduction to the mysticism of Linux. Instead it has bloated like a government-funded project. None of it compiles yet (because I have to fix up some of the tags) and it is not yet in Sourceforge CVS, but I will post whatever I have just before going AWOL in January. - On the technical side, writing the documentation has shown me all kinds of problems with the software selection on the machines. Other than that, I have put in a bit of work to make the menus cleaner and improve the package selection. It would be nice if I could get my act together enough to get a new release out for January, but I doubt that will happen. Today is likely the last day I will be able to work on the project at the Working Centre. - If you have been itching to help out the project but haven't known what to do, here are some projects you could take on in January (or, if you are as pathetic as me, over the holidays): 0. Compiling a new kernel. At the very least it would be nice to have a 2.6 series kernel with the "supermount" patches installed. We need supermount to mount floppies and CD-ROMs. I have been building kernels with the same modules available as ship in standard Debian kernels. Also, I compile for the i486 processor. I would also like to investigate the "tiny" kernel patches available from http://www.selenic.com/tiny-about/ . I would like to know which patches could help us improve memory performance, and whether they will compile cleanly in the kernel. If you want to take on this project, you should read up on "make-kpkg". 1. Compile the "kdrive" X-servers, and get them working with out distribution. Making a Debian package would be nice, but I think that is out of scope for the project. Even figuring out how to compile these x-servers from the source shipped with Debian would be a great asset. 2. Find or write some nice graphical backup utility that our users could use. There are a bunch of command-line tools available; my hope would be that we could get a nice user-friendly frontend. Backup mechanisms I would like to support are: Internet backups (with encryption), CD/DVD backups, USB key backups, Zip drive backups, hard drive backups, and floppy backups. Users should be able to select their backup method, choose the personal files they want to backup, and provide as little other information as we can get away with. The backups should run on a regular schedule once configured, preferably with a minimum of user intervention. I care less about archiving and more about disaster recovery. This is a big project, but from my surfing tonight I think there is no good candidate that meets all of these requirements. 3. There are some big holes in our application support: - We have no good web browser - We have no good spreadsheet (Gnumeric doesn't run at all anymore) - We have no good printer system Finding lightweight tools to address any of these needs would be greatly useful. 4. If anybody wants to do some C++ hacking, it would be lovely to investigate the possibility of building desktop icon support into xfe (our current file manager). This may not be as hard as it sounds -- there are already programs (such as idesk) which create desktop icons. 5. I need an mean editor who will whip all of my bad writing habits out of me, but I am afraid to ask for one (which is why I am reluctant to release the userguide to sourceforge). There. That's my drivel. Now yell at me or something. - Paul |
|
From: Paul N. <pn...@ut...> - 2004-11-13 06:35:12
|
Instead of working on something useful, I have been wasting my time with the following things: - I made Gnumeric's save facilities better. In fact this doesn't matter, as Gnumeric appears to be broken anyways. Grr. - I messed up the access.html page in an attempt to document that we have the entire installer on CVS now. - I got some feedback from our beta tester. He has managed to successfully print his resume (which he edited on his Linux box) on some foreign printer. This is shocking. - I created a temporary server, downloaded the CVS installer to it, and successfully used it to install a machine. Does anybody else notice a glaring lack of documentation in those tasks? - Paul |
|
From: Paul N. <pn...@ut...> - 2004-10-31 06:21:44
|
Well, I finally managed to get something into Sourceforge's CVS. It is not pretty and it required changing the directory structure somewhat, but it is done. If you want to get the sources and you are a developer, try cvs -d:ext:<username>@cvs.sf.net:/cvsroot/wclp checkout wclp and if you are not a developer (or don't want write access), try cvd -d:pserver:ano...@cv...:/cvsroot/wclp checkout wclp A few notes: - The kernels are not included on CVS, because they are huge. You have to put them in manually. - There are symlinks in the installer, but CVS doesn't deal with symlinks well, so I threw together a stupid script to recreate the symlinks. You can read about how to use this in the README.cvs file. - I managed to get one install working off the CVS sources, but I don't know how well things work. Also, in local news I broke the installer somehow. The installer itself works but I can no longer make boot floppies that actually mount the NFS partition. It's really crazy. The craziest thing is that floppies I made before the transition do work. Currently I think there is one old floppy that does work: wc_195. I think I messed up all of the other floppies with assorted upgrades. - Paul |
|
From: Charles M. <ch...@po...> - 2004-10-28 20:13:47
|
A very rough version of the book is on at: http://members.porchlight.ca/charm/wclp/book1.html There are some major problems. Chapter 11 has a bunch of nested lists that I have to debug, as a result most of the content doesn't show. The icons for the items are not showing...problems. They should be fixed soon. |
|
From: Charles M. <ch...@po...> - 2004-10-28 18:48:15
|
On Wednesday 27 October 2004 1:31 pm, Paul Nijjar wrote: > Keep in mind two things: > - The current manuals are not building (and won't until I fix the > scripts) > - The manual sources are on Sourceforge already (as part of the > 0.6 release, I think). No problem Paul. I'm almost done debugging all the problems with the DocBook v4.2 version of the WCLP Admin guide. I've debugged it to the point that 11 out of the 15 chapters are compiling successfully. Most of the work now is just cleaning out cobwebs from my SGML (DocBook V3.1) version - a couple of tags are no longer supported. 4.2 is an XML-compliant version of DocBook. > Could you put all of these aliases into one file which other books > could include? I think so, but I've never set up a "set" of books. As it is, I'm creating a single file for each chapter: i.e. chap1.docbook, chap2.docbook. At the top level is a file I called index.docbook. In it I have entities like &wclp; which chap1.docbook and chap2.docbook replace with "The Working Centre Linux Project" in each instance it exists in the text. Given this, I'm almost sure it'll work with Sets, which are the highest level (above Book). If we set it in a Set file I'm sure it will filter down to the books. > I don't care too much which tags are used so long as I know what > they are. I ran into a bit of a snag last night while debugging some of the chapters. For user input I'm using the tag <userinput>User input goes here</userinput>. Unfortunately this tag does not seem to accept <quote></quote> as a child, what this means is that if we need to instruct a user to type something with quotations we have to use a different tag like <programlisting>. Since DocBook is a page description language it defeats a bit of the purpose using programlisting... I think I'm going to join a DocBook list and see if I can't get <quote> as an accepted child of <userinput>. Cheers |
|
From: Paul N. <pn...@ut...> - 2004-10-27 17:32:07
|
On Wed, 27 Oct 2004, Charles McColm wrote: > On Monday 25 October 2004 5:49 pm, Paul Nijjar wrote: > > Are you going to use the sourceforge servers for this? I want to > > synchronize the directory structure for the entire project, so maybe we > > should discuss what you will call this directory tree. We already have a > > "manuals" directory -- maybe you could put the docbook admin guide in > > > > wclp/manuals/adminguide ? > > Or I could add a subdirectory: wclp/manuals/docbook/adminguide Maybe this would work, but the old manuals will disappear soon (as soon as they are replaced by the docbook versions). I don't care too much, provided that the overall structure stays sane. Unfortunately I have to look at the directory structure on our server on Friday -- I may be changing things around then (because CVS doesn't handle symlinks). > > This would wipe out our existing admin guide, but that should be > > okay. > > Let's not wipe out the existing guide. We can always remove it later. There > are still problems with the DocBook version. Keep in mind two things: - The current manuals are not building (and won't until I fix the scripts) - The manual sources are on Sourceforge already (as part of the 0.6 release, I think). > > At some point we will have to come up with a guide to writing documentation > with tips on what DocBook tags to use where. DocBook has hundreds of tags, > finding the proper one can be a bit daunting. If we have a guide we'll ensure > that documentation stays uniform among books. One of the nice things about > DocBook is that we can books into sets of books. Uniformity would be critical > for this. And content can be reusable. So, at the top level (Set) we could > have something like &twc; stand for "The Working Centre." Every book below > the set need only type &twc; instead of The Working Centre. Could you put all of these aliases into one file which other books could include? I don't care too much which tags are used so long as I know what they are. > > I can explain the partitioning part, but I don't know why the > > This can be turned off if you wish. Maybe I will put a message > > saying that the installer is checking for bad blocks, which will take a > > Keeping it on is probably a good idea until we start dealing with 10GB+ > drives, but I wondered why it took so long - I imagine others would too - I > was tempted to shut the machine off, someone with less patience might. I will add a "this could take a long time" message. - Paul |
|
From: Charles M. <ch...@po...> - 2004-10-27 14:08:56
|
On Monday 25 October 2004 5:49 pm, Paul Nijjar wrote: > Are you going to use the sourceforge servers for this? I want to > synchronize the directory structure for the entire project, so maybe we > should discuss what you will call this directory tree. We already have a > "manuals" directory -- maybe you could put the docbook admin guide in > > wclp/manuals/adminguide ? Or I could add a subdirectory: wclp/manuals/docbook/adminguide > This would wipe out our existing admin guide, but that should be > okay. Let's not wipe out the existing guide. We can always remove it later. There are still problems with the DocBook version. At some point we will have to come up with a guide to writing documentation with tips on what DocBook tags to use where. DocBook has hundreds of tags, finding the proper one can be a bit daunting. If we have a guide we'll ensure that documentation stays uniform among books. One of the nice things about DocBook is that we can books into sets of books. Uniformity would be critical for this. And content can be reusable. So, at the top level (Set) we could have something like &twc; stand for "The Working Centre." Every book below the set need only type &twc; instead of The Working Centre. > I can explain the partitioning part, but I don't know why the > This can be turned off if you wish. Maybe I will put a message > saying that the installer is checking for bad blocks, which will take a Keeping it on is probably a good idea until we start dealing with 10GB+ drives, but I wondered why it took so long - I imagine others would too - I was tempted to shut the machine off, someone with less patience might. |
|
From: Paul N. <pn...@ut...> - 2004-10-25 21:50:22
|
On Mon, 25 Oct 2004, Charles McColm wrote: > On Saturday 23 October 2004 1:18 am, Paul Nijjar wrote: > > My big project for tonight was going to be getting the installer > > files on sourceforge's CVS. Daniel had been bugging me to do this for a > > I've pretty much finished moving the WCLP Admin guide to DocBook v4.2 with an > abundance of comments. There's still quite a bit to debug, but it's > essentially done. I'm going to move it to CVS next. Are you going to use the sourceforge servers for this? I want to synchronize the directory structure for the entire project, so maybe we should discuss what you will call this directory tree. We already have a "manuals" directory -- maybe you could put the docbook admin guide in wclp/manuals/adminguide ? This would wipe out our existing admin guide, but that should be okay. > In a semi-related matter, I recently bought one of those removable drive kits, > and I used it to install the WCLP distribution on a 3GB hard drive. > Partitioning took almost 20 minutes and the distribution loaded very slow and > ran slow. I can explain the partitioning part, but I don't know why the distribution ran slowly. By default, the partitioning program scans the drive for bad blocks before partitioning anything. I think this is wise given the context of the installer. This can be turned off if you wish. Maybe I will put a message saying that the installer is checking for bad blocks, which will take a while. - Paul |
|
From: Charles M. <ch...@po...> - 2004-10-25 16:51:15
|
On Saturday 23 October 2004 1:18 am, Paul Nijjar wrote: > My big project for tonight was going to be getting the installer > files on sourceforge's CVS. Daniel had been bugging me to do this for a I've pretty much finished moving the WCLP Admin guide to DocBook v4.2 with an abundance of comments. There's still quite a bit to debug, but it's essentially done. I'm going to move it to CVS next. My problem with CVS has always been knowing where and what tags to insert into documents so they show the correct revision, date, author, etc. In a semi-related matter, I recently bought one of those removable drive kits, and I used it to install the WCLP distribution on a 3GB hard drive. Partitioning took almost 20 minutes and the distribution loaded very slow and ran slow. I don't think this is the fault of the removable kit because my other hard drive runs very fast. The 3GB drive may be faulty, but even so, we should perhaps have more information during the partitioning process, it seems more is going on than just partitioning. Cheers, Charles |
|
From: Paul N. <pn...@ut...> - 2004-10-23 05:19:12
|
My big project for tonight was going to be getting the installer files on sourceforge's CVS. Daniel had been bugging me to do this for a while, but as usual I was being lazy. Given that I am now maintaining an elaborate "obsolete" directory for old versions, it's probably time to turn to source control. For a while I toyed with the idea of using Subversion or arch or something else, but these tools are (apparently) not supported on Sourceforge, and unless we get server space someplace else, we are stuck with Sourceforge for a while. In any case, I flunked at carrying out the big project. Or rather, I chickened out, because I was frightened away by two things: 0. Symlinks 1. Binary files Symlinks worry me more. The FAI configuration contains a small symlink farm (a symlink garden?), and I honestly don't understand whether CVS supports these symlinks and/or what I have to do to work around the situation. The version of CVS on Sourceforge appears to be 1.11.15, if that means anything. I am going to fiddle around with this at home, but if you have any tips or can point me to documentation, it would be much appreciated. - Paul |
|
From: Paul N. <pn...@ut...> - 2004-10-02 07:43:30
|
(This post is basically meaningless to non-locals. It's mostly meaningless to the locals, too. Sorry.) I did basically nothing on the actual WCLP distro today. Instead, I sat around and played with some new toys Bill gave me: a 9GB hard drive and a CD-burner for our old 233MHz server. I also was allowed to put in some extra RAM, but one of the slots in the server is damaged, so I stuck with 64MB. (64MB ought to be enough for anybody.) I allocated 3MB of the server to use as a local mirror, and the remaing 6GB as storage space for ISO images. I managed to download a bunch of ISOs for the LUG meeting just in case anybody needs them (Ubuntu, Fedora Core 2 (which is not done yet), Knoppix, and Mepis). In unrelated news, I also learned how to use Bittorrent... Instead of wiping out everything and starting fresh, I did a dist-upgrade to sarge. This took hours and hours. I now need to get rid of a bunch of programs we don't need, and I have to set up our old server as a FAI server. Either that, or we can continue using the new server as a text-only development machine, and use the old server as a fileserver/CD-burning machine/desktop environment. Maybe I will actually do some work next week. - Paul |
|
From: Paul N. <pn...@ut...> - 2004-10-01 18:02:41
|
On Fri, 1 Oct 2004, Mark Bellinger wrote: > I didn't do the all the installations myself, but the folks doing it did > not mention any problems. So, good to go... Fair enough. > I work on a project that administers to 72 primary (elementary) schools. > I also support other PCVs at other sites. The issue as I see it is > pretty basic. They have nothing or very little, and the wclp gives them > a chance to use a product that is legal and robust. What is a PCV? > Regarding documentations, we need basic how-to docs. Maybe someone has > already done this for Ice but I could not find it on thru google. IceWM does come with a manual but it is more geared towards configuring the window manager and less geared towards actually using it. > > The documentation would be at the level of your setting-up-the-hardware > document you already have, but would focus on using ice to start > applications and games. It would not necessarily need to be long or > complicated, but something we can give folks that would give them a > fighting chance. This is a good place to start. What I will try to do is get some Docbook template set up on CVS. We can put in some sections and fill the sections out in a very basic way. Charles: would you be willing to help with this? > At present, the computers we will be recycling will have a PCV onsite, > but in the future, I like the idea that we could give a PC w/ wclp, > provide a one or two hour training, and hand the enduser the > documentation and the installation cd. In my experience you need some kind of followup support. The support need not be formal or sophisticated, but some friendly, patient person (or group of people) must be available to answer questions. I personally have correspondences with a couple of people via e-mail. LUGs (Linux User Groups) can be a good resource for this as well. > Also, I hope to use local high school kids to recycle these computers. > We will use wclp and this will be an excellent platform for the kids to > learn linux, as well as repair > > I'd like to work on a beginners guide to wclp -- from an enduser > perspective. It would have basic screenshots of what the default > installation looks like, how to open applications, manage windows, > shutdown the system. We could use (hopefully) existing documentation > for abiword and gnumeric and so on to provide support for the installed > apps. This was our hope as well. A good comprehensive guide would be nice. Actually, the freegeek.org people already have written some documentation that might be useful for us. Check out: http://web.freegeek.org/groups/ed/manual/ Tell me what kinds of additional information you are looking for. Maybe I will ask whether the manual is distributed under some liberal licence. If not we can write our own documentation, but I expect this will take some time. > I need guidance on how to do this. I am not familiar with the 'woody' > nor how to access. I would like to contribute... The easiest way to get started is as follows: 0. Start with any Debian box (a WCLP box will be fine) and become the root user. Then type apt-get update apt-get install woody This will install the woody editor. 1. You may need CVS on your computer as well, which we do not provide by default: apt-get install cvs 2. Now follow the instructions on http://wclp.sourceforge.net/access.html export CVS_RSH=ssh cvs -d:pserver:ano...@cv...:/cvsroot/wclp checkout todolist 3. To start learning about woody, type woody help.tree 4. To see our current todo list, type woody todo-wclp.tree 5. You cannot actually contribute anything to these files unless you have an account on www.sourceforge.net. You can visit sourceforge.net and become a developer by clicking the "new user via SSL" link and following the instructions. Once you have generated this account write back and tell us the userID you have chosen. We can then add your account to the WCLP project as a developer, and you will be able to check in changes. At some point we will set up some documentation CVS repositories as well. Maybe that can happen as early as today, if I get my act together. - Paul |
|
From: Mark B. <mbe...@wa...> - 2004-10-01 14:39:32
|
I didn't do the all the installations myself, but the folks doing it did = not mention any problems. So, good to go... I work on a project that administers to 72 primary (elementary) schools. = I also support other PCVs at other sites. The issue as I see it is = pretty basic. They have nothing or very little, and the wclp gives them = a chance to use a product that is legal and robust. =20 Regarding bootable CD, I was thinking ala Knoppix. I see your point = though; maybe something in the future... Regarding documentations, we need basic how-to docs. Maybe someone has = already done this for Ice but I could not find it on thru google. The documentation would be at the level of your setting-up-the-hardware = document you already have, but would focus on using ice to start = applications and games. It would not necessarily need to be long or = complicated, but something we can give folks that would give them a = fighting chance. At present, the computers we will be recycling will have a PCV onsite, = but in the future, I like the idea that we could give a PC w/ wclp, = provide a one or two hour training, and hand the enduser the = documentation and the installation cd. Also, I hope to use local high school kids to recycle these computers. = We will use wclp and this will be an excellent platform for the kids to = learn linux, as well as repair=20 I'd like to work on a beginners guide to wclp -- from an enduser = perspective. It would have basic screenshots of what the default = installation looks like, how to open applications, manage windows, = shutdown the system. We could use (hopefully) existing documentation = for abiword and gnumeric and so on to provide support for the installed = apps. =20 I need guidance on how to do this. I am not familiar with the 'woody' = nor how to access. I would like to contribute... Thanks. Mark=20 |
|
From: Paul N. <pn...@ut...> - 2004-09-30 21:21:22
|
On Wed, 29 Sep 2004, Mark Bellinger wrote: Dear Mark, I see that you are on the wclp-admin list, so I will not CC mails to you. > We have loaded up four PCs with the 0.7 product. No problem in > installation using boot floppy/cd. Excellent. Is mouse detection working now? > > Is the CD bootable? If not, any plans to do so...? I have PCs without > harddrives and am curious if this solution wouldn't work for diskless > workstations...? If by bootable you mean that the install CD is bootable (so you don't need a floppy) then the answer is "yes". If your BIOS/CD-Drive support booting from CD-ROM, then you can install from CD without a floppy. If by bootable you mean that we have a LiveCD version of the distro (a la Knoppix or MEPIS) the answer is "no". At some point it would be nice to have a LiveCD, but it is not a priority yet (unless you would like it to be). Here are the problems: - Without a hard drive swapping becomes deadly (because we have no hard drive for swap space). - Distros like Knoppix use "compressed loopback" filesystems, which means that they take the entire filesystem, smoosh it up, and uncompress it on the fly to load programs. The big advantage of this is that you can fit much more software in the distro (about 2GB of software on a 700MB CD-ROM). The big disadvantage is that such systems require a lot of memory to run, because you have to make a ramdisk to uncompress the filesystem. For this reason running Knoppix really is not feasible without 64 or 128MB of RAM. Having said that, some distros (notably DamnSmallLinux and Feather Linux) do work with 32 MB of RAM, but they require some swap space. If you are interested in diskless workstations maybe you should look into Skolelinux. They are a Debian-based distro designed for schools (which also addresses your next point below). They support LTSP -- the Linux Terminal Server Project, which allows a lot of low-end computers to be used as dumb workstations so long as they have a relatively powerful central server. Their installer is also geared towards asking only non-technical questions. In theory you could use our distro to support LTSP as well, but I have not looked into this. Our target right now is standalone workstations with limited resources. Here is the Skolelinux URL: http://www.skolelinux.org/portal/index_html > > Also, we want to distribute these to schools, etc, and need > documentation. I see the first-time-setup guide and like this, but > would like something for using icewm. What in particular would you like to see? If you could give us a list of topics or questions to answer, we could write those sections first. A question about schools (and your work in general): are you responsible for doing the administration of these machines? Are you training others to do administration when your term with the Peace Corps ends? Every school probably needs at least one administrator who can fix problems when they crop up. > I see that something may be in development. Can I see what you have? > How do I get a screenshot under ice? At this point we don't have anything more than what is on the website in the Documentation section or on the Todolist. This is a great big fault in our project, and is one of the big priorities for us to get right within the next couple of releases. I was thinking of setting up another todolist-type thing that would contain documentation we would like to see. Do you have access to the "woody" editor? If so, you could contribute to the list -- we could make you a Sourceforge developer. I should note that Charles is currently working hard to translate our (moderately but hopefully not totally obsolete) Adminstrator's guide to Docbook. We will be writing user documentation in Docbook as well, probably. - Paul |
|
From: Mark B. <mbe...@wa...> - 2004-09-29 16:47:26
|
We have loaded up four PCs with the 0.7 product. No problem in = installation using boot floppy/cd. Is the CD bootable? If not, any plans to do so...? I have PCs without = harddrives and am curious if this solution wouldn't work for diskless = workstations...? Also, we want to distribute these to schools, etc, and need = documentation. I see the first-time-setup guide and like this, but = would like something for using icewm. I see that something may be in development. Can I see what you have? = How do I get a screenshot under ice? Thanks. Mark |
|
From: Charles M. <ch...@po...> - 2004-09-26 12:07:33
|
=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday 25 September 2004 03:23, Paul Nijjar wrote: > The old server is sitting around doing little. I would like to > reinstall it and maybe put in a bigger hard drive, then use that server as > our installation server. I have everything I need from the server. I think Daniel had some work on t= he=20 server, but I'm pretty sure I backed up wclp-feedback to my ftp space on=20 porchlight. =46YI: The DocBook conversion of the wclp-admin-guide is going well, but it= 's=20 slow going. I have all the work on my new notebook. > Our new server has a better processor but less > disk space (6GB). This is a problem because I am running out of room for > the Debian mirror, and I get cramped for space when trying to build ISO > images. I may be able to solve this, I have a larger hard drive (20GB), but it's=20 suppose to be a dud. I'm not sure it was tested properly. If it works we=20 could probably use it in the new server. > Thoughts? I am willing to preserve home directories and such, but > I don't know what else of importance is on the old server. I'm not as fond of the new setup as the old, simply because of the GDM issu= e -=20 I think it's too easy for someone to get into trouble and end up at a comma= nd=20 prompt. For example: in the wclp-admin-guide we recommend people installing= =20 press Ctrl+Alt+Backspace to exit X-Windows . The guide needs updating, whic= h=20 I plan on doing after I'm done the whole thing, but I still miss GDM, or ev= en=20 XDM. I'm not sure there isn't an option in the XDM configuration file that= =20 would let us enable auto-logins. If there's no GUI tool to configure=20 auto-logins it shouldn't be too difficult to create one. Anyway, here's where I am: * The entire outline of the wclp-admin-guide is done. * Chapters 1-4 are completely done. * Chapter 5 is about half done. The process would be quicker (quicker because I can copy and paste the onli= ne=20 version but not the pdf version) if I had cable here. I'm going to see what= I=20 can do about getting Wi-Fi to work under SuSE (what I'm running on my=20 notebook). There's a cafe downtown I can work at. > All of this is probably moot, since (according to the new price > list I saw) the Working Centre is selling Pentium IIs and IIIs with 128MB > of RAM. That means that our project is kind of obsolete -- why not just > put on a real Linux distro with OpenOffice and other nice things? Well, when I went looking for a notebook I took along a Knoppix 3.6 CD with= me=20 =2D - it recognized everything except the Winmodem (which has drivers). I r= eally=20 love how it runs, but it's a bit of a pain to install to hard drive.=20 Actually, it's a subject I wouldn't mind seeing presented at the kwlug=20 meeting. =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBVrDja8T+7n+/FpkRAkEeAKC0pzlIVXV4IshiQ8ro+bb6Bn/DQgCePi2v QxO12ghURure2UcQ60VfjOQ=3D =3DdKe0 =2D----END PGP SIGNATURE----- |
|
From: Bill R. <bi...@th...> - 2004-09-25 14:46:35
|
The pricelist does not reflect what is actually available (its the price, if available). We have only had about 2 P III's ever, to sell. The range is still from 133 to 450 Mhz, although 64 MB of ram is the standard and 128 is getting more common for what we can offer. Bill. > > All of this is probably moot, since (according to the new price > list I saw) the Working Centre is selling Pentium IIs and IIIs with 128MB > of RAM. That means that our project is kind of obsolete -- why not just > put on a real Linux distro with OpenOffice and other nice things? > > - Paul |
|
From: Paul N. <pn...@ut...> - 2004-09-25 07:24:47
|
The old server is sitting around doing little. I would like to reinstall it and maybe put in a bigger hard drive, then use that server as our installation server. Our new server has a better processor but less disk space (6GB). This is a problem because I am running out of room for the Debian mirror, and I get cramped for space when trying to build ISO images. Thoughts? I am willing to preserve home directories and such, but I don't know what else of importance is on the old server. All of this is probably moot, since (according to the new price list I saw) the Working Centre is selling Pentium IIs and IIIs with 128MB of RAM. That means that our project is kind of obsolete -- why not just put on a real Linux distro with OpenOffice and other nice things? - Paul |
|
From: Rudolf A. <am...@ed...> - 2004-09-11 05:31:11
|
Paul Nijjar wrote: > our webspace completely baffles me. Is it actually > the case that in order to change one link in our menu we have to all of > our pages? Oy. Yes, that would be the idea. Happily, you'll only need to run a single Seearch and Replace routine on the directory that holds the pages. Alternatives include: 01 Burying the whole place in a frameset. Vetoed straight off the bat. 02 Databasing the pages and publishing them through a content management system. Viable but hardly worth the effort. > for those who > are interested in blowing their computers up. BOOM! Yay! Undocumented feature! R. |
|
From: Paul N. <pn...@ut...> - 2004-09-11 05:13:44
|
Hello loonies and toonies, I'm forwarding Marco Fioretti's response to my announcement about the latest release. I will get working on a webpage for the RULE site Real Soon Now. In other news, our webspace completely baffles me. Is it actually the case that in order to change one link in our menu we have to all of our pages? Oy. I think the link we want for the "Download" page is http://sourceforge.net/project/showfiles.php?group_id=49610&package_id=48359 This shows all releases we have. In other news, I am a lazy bum. I fixed a few small things Mark raised in his e-mail but did not get much done today. In other news, I am squandering a few of Charles's CDs with the ISO image. I plan to give them away during the LUG meeting, for those who are interested in blowing their computers up. BOOM! - Paul ---------- Forwarded message ---------- Date: Sat, 4 Sep 2004 09:11:46 +0200 From: M. Fioretti <mfi...@mc...> To: rul...@ru... Subject: Re: [RULE] WCLP 0.7.1 Released ("RULE for Debian") On Sat, Sep 04, 2004 02:12:27 AM -0400, Paul Nijjar (pn...@ut...) wrote: > We are not trying to replace the Slinky installer, nor are we > asserting that RULE should give up its goal of getting Fedora > installed on older computers. Rather, I am thinking of our project > as a Debian-based approach to the problems RULE is trying to solve. ... > I am also totally willing to help (on this list if Marco allows it, > on wcl...@li... otherwise) with any problems you > are facing. Paul, first of all, congratulations. Please consider putting together a WCLP page that we can put on the RULE website, pointing at your site. As for supporting here, YES!!! See what I wrote on the home page about RULE becoming a general centre for all willing to Run Up to date Linux Everywhere, with whatever distro. Also check the slides I sent to the Debian-NP on this. The only thing to remember on this list is to specify since the subject or the very beginning of the message if you are talking about RULE-Fedora or RULE-WCLP (if you allow me saying so, just joking). > I am hoping to be able to do a RULE Network-type mailout service, > but I have not set that up yet. No need to duplicate the RULE network, just point to it from your website. Several of its registered members, if you check their webpages, already offer lots of other Free SW cds, and other Linux distros. Let's just ask them to give out your CD too. I can take care of this if you wish. On a related note, please document the common denominator, ie what you offer for SOHO application, which versions and how you trimmed it down. Thanks Marco -- Marco Fioretti mfioretti, at the server mclink.it Red Hat & Fedora for low memory http://www.rule-project.org/ Whatever you do will be insignificant, but it is very important that you do it. -- Gandhi _______________________________________________ Rule Project HOME PAGE: http://www.rule-project.org/en/ Rul...@ru... http://rita.choice-secure.com/mailman/listinfo/rule-list_rule-project.org |
|
From: Paul N. <pn...@ut...> - 2004-09-08 03:31:43
|
On Tue, 7 Sep 2004, Mark Bellinger wrote: Dear Mark, Thanks so much for writing! This is very exciting. You may be the first person we know of who has downloaded the CD and successfully used it. > Any other Linux distros with similar goals that you might know of...? There are a bunch of them. The "todolist" link has the ones that we have found. Look in "Arbitrary Lists --> The competition". Probably the main contenders at this point are DamnSmallLinux and its derivatives, and the RULE project. > All went pretty well. It did take me a while to figure out to use the > proper img file to boot to the CD. Okay. Where should I document this? Would it have helped if I put it in README.bootcd? In the main README? > And, I had to manually edit > X86Config-4 file to recognize PS2 mouse. Oh dear. This should Just Work. Was the mouse plugged into the computer during installation? Could you try this again and send me (maybe via personal mail) the log directory? You can find this in /var/log/fai/localhost/last/ , I think. > > I tried all the programs in the Start menu. The apps listed below did > not work from the menu. Some 'worked, but just needed to be run from > the shell. Others 'disappeared', but still had a process showing. Some of these are installed by Debian. Some of them are our fault. You are correct that they should all be working, at least in theory. I can test this on a local machine and we can file bugs for the Debian-related problems. > gnumeric (seen using ps -ef but never seen on desktop) I found that this does work, but that gnumeric itself takes a long time to boot, for some reason. Does it come up after 5-10 minutes for you? Gnumeric is getting really big, and it may be a candidate for removal from standard installs. > printer tool This is a problem. > math/bc (text based and not seen from ice) > math/dc > math/xcalc These are Debian-generated. > net/gaim (seen using ps -ef but never seen on desktop) This should be working. I will check this. > net/links > net/links2 (text based and not seen from ice) > net/mutt (text based and not seen from ice) > net/sylpheed > net/w3m (text based and not seen from ice) > net/Xbiff These are also Debian. I wonder why they are not working? I will check this out. > Help > TKInfo These are also Debian's, but they should work. > WCLP Help This is our fault. I will look into this. The help page we have is stale anyways. > BTW, when you click on 'downloads' from the > wclp.sourceforge.net site, you only see the 0.6 downloads. We should fix this. Could you handle this, Ruedi? It would be nice if the link did not go bad every time we made a release. Is this possible? > So, perhaps we can collaborate as we move on. In any case, I will give > you feedback on my experience. Please keep providing the feedback. Are you subscribed to wclp-admin? You may subscribe if you wish, or we can keep CCing you in our responses. > PS I posted to wclp-admin cause it seemed more active and germane to > this email. Maybe I should post to the other list? Personally, I think this is the better list, but it probably does not matter a whole lot. "wclp-user" was originally intended more for end-users of the installed machines. Do you find that the selection of software we install is appropriate for your needs? What changes would you like to see? - Paul |