From special.kevin at gmail.com Wed Aug 1 00:41:47 2007 From: special.kevin at gmail.com (Kevin Harriss) Date: Tue Jul 31 23:41:57 2007 Subject: [LUNI] Chicago Free and Open Source Conference Message-ID: <1185943308.3544.6.camel@localhost.localdomain> Hey all, I interested in setting up a Free and Open Source conference in Chicago. This conference is to focus more on the desktop/enthusiast not the business side of Free and Open Source software. If you would be interested helping out our sharing ideas please join us in our irc channel #chicon on freenode. Also if you would be interested in a conference like just please reply saying that you are interested. This will help us gage the interest. I am really hoping to show everyone that the Midwest and more specifically Chicago is a good city for conferences and Free and Open Source Software, this can be done since we are hosting PyCon and Flourish. Thanks, I. Kevin Harriss From me at heyjay.com Wed Aug 1 01:27:13 2007 From: me at heyjay.com (Jay Strauss) Date: Wed Aug 1 00:33:31 2007 Subject: [LUNI] Re: Pseudo RSS In-Reply-To: References: Message-ID: On 7/24/07, Jay Strauss wrote: > Hi, > > Does anyone know of a product/tool/script that could tell me when a > web page has changed? Sort of like RSS, but this site doesn't have > RSS. > > I need to watch this page on a bulletin board where fairly > infrequently someone posts a message that I need to know has been > posted. I hate having to remind myself to check all the time, and the > site has no provision to email. > > It'd be nice if I could have some utility do it for me. Hi, So regarding the above, I played with wget and md5sum as people suggested. The problem I'm having is that: While the page seems the same to the eye, there seems to be constantly changing content, some sort of IDs change with every page request. I'm using: wget --quiet -O - http://www.playalinda.com/members/phpBB2/viewforum.php?f=6 | md5sum If you run the command twice in a row, the checksum is different (even though I can't see any difference when I see the page on a browser). Does anyone have a suggestion to address this? (other than parsing the entire page and finding the message titles) Thanks Jay From jgd-luni at metajoe.com Wed Aug 1 08:14:28 2007 From: jgd-luni at metajoe.com (Joe Digilio) Date: Wed Aug 1 07:14:41 2007 Subject: [LUNI] Re: Pseudo RSS In-Reply-To: References: Message-ID: <8563497c0708010514p2ea03756wd92d0c770ec69a57@mail.gmail.com> On 8/1/07, Jay Strauss wrote: > Hi, > > So regarding the above, I played with wget and md5sum as people > suggested. The problem I'm having is that: While the page seems the > same to the eye, there seems to be constantly changing content, some > sort of IDs change with every page request. > > I'm using: > > wget --quiet -O - > http://www.playalinda.com/members/phpBB2/viewforum.php?f=6 | md5sum > > If you run the command twice in a row, the checksum is different (even > though I can't see any difference when I see the page on a browser). > > Does anyone have a suggestion to address this? (other than parsing > the entire page and finding the message titles) Try links or lynx instead: links -dump http://www.playalinda.com/members/phpBB2/viewforum.php?f=6 | md5sum lynx -dump http://www.playalinda.com/members/phpBB2/viewforum.php?f=6 | md5sum -Joe From aclose at gmail.com Wed Aug 1 08:44:33 2007 From: aclose at gmail.com (Andrew Close) Date: Wed Aug 1 07:44:38 2007 Subject: [LUNI] Chicago Free and Open Source Conference In-Reply-To: <1185943308.3544.6.camel@localhost.localdomain> References: <1185943308.3544.6.camel@localhost.localdomain> Message-ID: On 7/31/07, Kevin Harriss wrote: > Hey all, > > I interested in setting up a Free and Open Source conference in Chicago. > This conference is to focus more on the desktop/enthusiast not the > business side of Free and Open Source software. If you would be > interested helping out our sharing ideas please join us in our irc > channel #chicon on freenode. Also if you would be interested in a > conference like just please reply saying that you are interested. This > will help us gage the interest. I am really hoping to show everyone > that the Midwest and more specifically Chicago is a good city for > conferences and Free and Open Source Software, this can be done since we > are hosting PyCon and Flourish. i think it's a good idea, but... businesses are willing to pay to go to conferences and learn, most 'people' are not. it's definitely a worthy cause and i'd be interested in it. :) maybe organizing this conference in conjunction with another one, partially to spread the word amongst attendees and partially to help mitigate costs, would be a good idea. just my $.02 From barry at vonahsen.com Wed Aug 1 09:33:53 2007 From: barry at vonahsen.com (Barry Von Ahsen) Date: Wed Aug 1 08:53:48 2007 Subject: [LUNI] Re: Pseudo RSS In-Reply-To: References: Message-ID: <46B08BC1.8020100@vonahsen.com> Jay Strauss wrote: > On 7/24/07, Jay Strauss wrote: >> Hi, >> >> Does anyone know of a product/tool/script that could tell me when a >> web page has changed? Sort of like RSS, but this site doesn't have >> RSS. >> >> I need to watch this page on a bulletin board where fairly >> infrequently someone posts a message that I need to know has been >> posted. I hate having to remind myself to check all the time, and the >> site has no provision to email. >> >> It'd be nice if I could have some utility do it for me. > > Hi, > > So regarding the above, I played with wget and md5sum as people > suggested. The problem I'm having is that: While the page seems the > same to the eye, there seems to be constantly changing content, some > sort of IDs change with every page request. > > I'm using: > > wget --quiet -O - > http://www.playalinda.com/members/phpBB2/viewforum.php?f=6 | md5sum > > If you run the command twice in a row, the checksum is different (even > though I can't see any difference when I see the page on a browser). > > Does anyone have a suggestion to address this? (other than parsing > the entire page and finding the message titles) > debian has samidare[1] and websec[2], and the websec page shows some "competitors" (links on page) KWebWatch urlchange wrep WebReporter [1] http://a-k-r.org/samidare/ [2] http://baruch.ev-en.org/proj/websec/ -barry From me at heyjay.com Wed Aug 1 10:06:38 2007 From: me at heyjay.com (Jay Strauss) Date: Wed Aug 1 09:06:46 2007 Subject: [LUNI] Re: Pseudo RSS In-Reply-To: <8563497c0708010514p2ea03756wd92d0c770ec69a57@mail.gmail.com> References: <8563497c0708010514p2ea03756wd92d0c770ec69a57@mail.gmail.com> Message-ID: > Try links or lynx instead: > links -dump http://www.playalinda.com/members/phpBB2/viewforum.php?f=6 | md5sum > > lynx -dump http://www.playalinda.com/members/phpBB2/viewforum.php?f=6 | md5sum > > -Joe lynx suffers the same problems wget does: jstrauss@fs1:~$ lynx -dump http://www.playalinda.com/members/phpBB2/viewforum.php?f=6 | md5sum 8a41ed1ac3062e2ee9784844c734bb52 - jstrauss@fs1:~$ lynx -dump http://www.playalinda.com/members/phpBB2/viewforum.php?f=6 | md5sum 77b4bff8a5f2fad51d14ce9802cc7241 - jstrauss@fs1:~$ lynx -dump http://www.playalinda.com/members/phpBB2/viewforum.php?f=6 | md5sum d97651b0b79ee6b2117db0afe6723322 - Thanks Jay From me at heyjay.com Wed Aug 1 10:07:07 2007 From: me at heyjay.com (Jay Strauss) Date: Wed Aug 1 09:07:14 2007 Subject: [LUNI] Re: Pseudo RSS In-Reply-To: <46B08BC1.8020100@vonahsen.com> References: <46B08BC1.8020100@vonahsen.com> Message-ID: > debian has samidare[1] and websec[2], and the websec page shows some > "competitors" (links on page) > > KWebWatch > urlchange > wrep > WebReporter > > [1] http://a-k-r.org/samidare/ > [2] http://baruch.ev-en.org/proj/websec/ > > -barry Thanks Barry, I'll look at these From ohrock at gmail.com Wed Aug 1 10:07:54 2007 From: ohrock at gmail.com (Roberto Serrano) Date: Wed Aug 1 09:08:02 2007 Subject: [LUNI] Chicago Free and Open Source Conference In-Reply-To: References: <1185943308.3544.6.camel@localhost.localdomain> Message-ID: <3d76512f0708010707g5dcc07dal8c60d7dd4d5dcaf8@mail.gmail.com> Flourish might be open to have a third day we a different emphasis, and even under a different name all together. We have Friday with the view in education, and Saturday with a view in business, it might be great to have Sunday with an emphases on the desktop. We would need help from the community, because as it is putting together 14 activities/talks takes the sap out of all the resources we have. Just and idea. Roberto On 8/1/07, Andrew Close wrote: > > On 7/31/07, Kevin Harriss wrote: > > Hey all, > > > > I interested in setting up a Free and Open Source conference in Chicago. > > This conference is to focus more on the desktop/enthusiast not the > > business side of Free and Open Source software. If you would be > > interested helping out our sharing ideas please join us in our irc > > channel #chicon on freenode. Also if you would be interested in a > > conference like just please reply saying that you are interested. This > > will help us gage the interest. I am really hoping to show everyone > > that the Midwest and more specifically Chicago is a good city for > > conferences and Free and Open Source Software, this can be done since we > > are hosting PyCon and Flourish. > > i think it's a good idea, but... businesses are willing to pay to go > to conferences and learn, most 'people' are not. it's definitely a > worthy cause and i'd be interested in it. :) > maybe organizing this conference in conjunction with another one, > partially to spread the word amongst attendees and partially to help > mitigate costs, would be a good idea. > just my $.02 > -- > Linux Users Of Northern Illinois - Technical Discussion > http://luni.org/mailman/listinfo/luni > From jgd-luni at metajoe.com Wed Aug 1 10:57:43 2007 From: jgd-luni at metajoe.com (Joe Digilio) Date: Wed Aug 1 09:57:50 2007 Subject: [LUNI] Re: Pseudo RSS In-Reply-To: References: <8563497c0708010514p2ea03756wd92d0c770ec69a57@mail.gmail.com> Message-ID: <8563497c0708010757x4672f3a7n505eaa8aced34c81@mail.gmail.com> On 8/1/07, Jay Strauss wrote: > lynx suffers the same problems wget does: I just tried it with two different versions of links and it works for me. Ubuntu 6.06: 1.00pre12 DarwinPorts: 2.1pre28 You might also want to try adding this option to links, if your version supports it: -html-numbered-links 0 Eg, links -dump -html-numbered-links 0 \ "http://www.playalinda.com/members/phpBB2/viewforum.php?f=6" | md5sum -Joe From csieh at fnal.gov Wed Aug 1 11:10:01 2007 From: csieh at fnal.gov (Connie Sieh) Date: Wed Aug 1 10:10:28 2007 Subject: [LUNI] Chicago Free and Open Source Conference In-Reply-To: <1185943308.3544.6.camel@localhost.localdomain> References: <1185943308.3544.6.camel@localhost.localdomain> Message-ID: On Tue, 31 Jul 2007, Kevin Harriss wrote: > Hey all, > > I interested in setting up a Free and Open Source conference in Chicago. > This conference is to focus more on the desktop/enthusiast not the > business side of Free and Open Source software. If you would be > interested helping out our sharing ideas please join us in our irc > channel #chicon on freenode. Also if you would be interested in a > conference like just please reply saying that you are interested. This I think this is a good idea. > will help us gage the interest. I am really hoping to show everyone > that the Midwest and more specifically Chicago is a good city for > conferences and Free and Open Source Software, this can be done since we > are hosting PyCon and Flourish. > > Thanks, > > I. Kevin Harriss > > -Connie Sieh From me at heyjay.com Wed Aug 1 11:27:34 2007 From: me at heyjay.com (Jay Strauss) Date: Wed Aug 1 10:27:43 2007 Subject: [LUNI] Re: Pseudo RSS In-Reply-To: <8563497c0708010757x4672f3a7n505eaa8aced34c81@mail.gmail.com> References: <8563497c0708010514p2ea03756wd92d0c770ec69a57@mail.gmail.com> <8563497c0708010757x4672f3a7n505eaa8aced34c81@mail.gmail.com> Message-ID: Sorry, I used "lynx", I thought it was a typo. I'll try that On 8/1/07, Joe Digilio wrote: > On 8/1/07, Jay Strauss wrote: > > lynx suffers the same problems wget does: > > I just tried it with two different versions of links and it works for me. > Ubuntu 6.06: 1.00pre12 > DarwinPorts: 2.1pre28 > > You might also want to try adding this option to links, if your > version supports it: > -html-numbered-links 0 > > Eg, > links -dump -html-numbered-links 0 \ > "http://www.playalinda.com/members/phpBB2/viewforum.php?f=6" | md5sum > > -Joe > -- > Linux Users Of Northern Illinois - Technical Discussion > http://luni.org/mailman/listinfo/luni > From maney at two14.net Wed Aug 1 12:00:51 2007 From: maney at two14.net (Martin Maney) Date: Wed Aug 1 11:01:13 2007 Subject: [LUNI] Re: Pseudo RSS In-Reply-To: References: Message-ID: <20070801160051.GA8358@furrr.two14.net> On Wed, Aug 01, 2007 at 12:27:13AM -0500, Jay Strauss wrote: > suggested. The problem I'm having is that: While the page seems the > same to the eye, there seems to be constantly changing content, some > sort of IDs change with every page request. I would say I told you so, but I didn't, I only thought it. :-/ > Does anyone have a suggestion to address this? (other than parsing > the entire page and finding the message titles) No, that's basically what you have to do, if you can't convince the site to make the information more conveniently available. You scrape the info off the screen, find the bits you're interested in, and do whatever it is you want to do with it. A venerable trade of great antiquity (predates the intertubes as we know 'em, that's prehistoric) which, like mucking out stables, is not to everyone's taste. -- During almost fifteen centuries has the legal establishment of Christianity been on trial. What have been its fruits? More or less in all places, pride and indolence in the Clergy, ignorance and servility in the laity, in both, superstition, bigotry and persecution. -- James Madison From r_a_smith3530 at sbcglobal.net Wed Aug 1 16:03:13 2007 From: r_a_smith3530 at sbcglobal.net (Robert Smith) Date: Wed Aug 1 17:03:35 2007 Subject: [LUNI] IE Most Influential Tech Product of Last 25 Years? Message-ID: <720854.2723.qm@web81305.mail.mud.yahoo.com> According to a recent CompTIA survey, Micro$oft's Internet Explorer was voted the most influential technology product of the last 25 years. You can be sure that Microsoft will get every milimeter of publicity out of this that it can, even though the survey only polled the opinions of 471 people. NCSA's Mosaic should have scored the numero uno slot if web browsing was the criteria used by the voters to pick IE. Without Mosaic, there would be no IE, or FireFox for that matter. Both IE and FireFox (through Netscape Navigator) can trace their parentage back to the browser developed at NCSA. The survey listed three other M$ products in the top five, including Word, Windows 95, and Excel, which tied with Apple's iPod. The top ten included Blackberry, Adobe Photoshop, McAfee VirusScan, Netscape Navigator, and the Palm Pilot. It sure shows who voted, that Linus's kernel project didn't crack the top ten, yet the iPod made it into the top five. Makes you wonder what CompTIA is using for servers. Anyway, here's a link to the article... http://www.comptia.org/pressroom/get_pr.aspx?prid=1262 It is interesting to note that 471 respondents is probably but a fraction of a percent of the number of people walking around with CompTIA certifications. I wonder how many hold Linux+ certs? Rob Smith From fixedored at gmail.com Wed Aug 1 21:30:14 2007 From: fixedored at gmail.com (Jeff D) Date: Wed Aug 1 22:30:07 2007 Subject: [LUNI] Laptop component recommendations In-Reply-To: <27fc5523b95675df9ff5d3a73a51d1b8@localhost> References: <200707301214.54395.knura@yahoo.com> <27fc5523b95675df9ff5d3a73a51d1b8@localhost> Message-ID: On Mon, 30 Jul 2007, Larry Garfield wrote: > > On Mon, 30 Jul 2007 12:14:54 +0530, Arun Khan wrote: >> On Monday 30 July 2007 01:09, Larry Garfield wrote: >> >>> Naturally Lenovo is having a back to school sale (on Thinkpads???) >>> right now that ends tomorrow night, so I'm debating if I should jump >>> on it or wait and see what August brings. Ah, marketing... >> >>> From personal experience of last year, I'd say wait for August. The >> deals got better as it got closer to school opening but to get them you >> must read the Sunday inserts on Sat. and be at the store on Sun. AM >> before they open. > > Oh I'm looking to buy online, not at the store. I want to be able to customize it. > > --Larry Garfield > > -- Just thought I'd add an update to this. I just got my T61 yesterday. Installed Debian Lenny on it. For the most part it was pretty painless. Everything on it up and running, sound, wireless. The only thing I had to compile was some alsa bits from. Right now I have the 4965AGN working though ndiswrapper, seems to work pretty well. The other option would be to roll my own kernel and add in the modules myself. All in all, getting everything to work was pretty easy. And I have to say that I'm pretty impressed with it so far. Jeff -+- 8 out of 10 Owners who Expressed a Preference said Their Cats Preferred Techno. From sushid at voxlox.com Wed Aug 1 15:10:13 2007 From: sushid at voxlox.com (D. Wade) Date: Thu Aug 2 01:27:03 2007 Subject: [LUNI] Chicago Free and Open Source Conference In-Reply-To: <1185943308.3544.6.camel@localhost.localdomain> References: <1185943308.3544.6.camel@localhost.localdomain> Message-ID: <46B0DA95.4080301@voxlox.com> Interested! I'd hoped to see something like this grow out of the "Uber FEST" discussions of last year, but I don't know what ever happened to that. I *might* be able to get some sponsorship / cost defrayment going, if this becomes real. --Derek W. Kevin Harriss wrote: > Hey all, > > I interested in setting up a Free and Open Source conference in Chicago. > This conference is to focus more on the desktop/enthusiast not the > business side of Free and Open Source software. If you would be > interested helping out our sharing ideas please join us in our irc > channel #chicon on freenode. Also if you would be interested in a > conference like just please reply saying that you are interested. This > will help us gage the interest. I am really hoping to show everyone > that the Midwest and more specifically Chicago is a good city for > conferences and Free and Open Source Software, this can be done since we > are hosting PyCon and Flourish. > > Thanks, > > I. Kevin Harriss > From larry at garfieldtech.com Thu Aug 2 02:46:35 2007 From: larry at garfieldtech.com (Larry Garfield) Date: Thu Aug 2 01:47:04 2007 Subject: [LUNI] Laptop component recommendations In-Reply-To: References: <200707301214.54395.knura@yahoo.com> <27fc5523b95675df9ff5d3a73a51d1b8@localhost> Message-ID: <200708020146.35177.larry@garfieldtech.com> On Wednesday 01 August 2007, Jeff D wrote: > Just thought I'd add an update to this. I just got my T61 yesterday. > Installed Debian Lenny on it. For the most part it was pretty painless. > Everything on it up and running, sound, wireless. The only thing I had to > compile was some alsa bits from. Right now I have the 4965AGN working > though ndiswrapper, seems to work pretty well. The other option would be > to roll my own kernel and add in the modules myself. All in all, getting > everything to work was pretty easy. And I have to say that I'm pretty > impressed with it so far. > > Jeff Good to know, Jeff, thanks. I ordered one for myself on Monday, about 30 min before the price went up. :-) I'll report back with Feisty experiences once I've toyed with it a bit. -- Larry Garfield AIM: LOLG42 larry@garfieldtech.com ICQ: 6817012 "If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson From knura at yahoo.com Thu Aug 2 15:38:00 2007 From: knura at yahoo.com (Arun Khan) Date: Thu Aug 2 04:08:22 2007 Subject: [LUNI] IE Most Influential Tech Product of Last 25 Years? In-Reply-To: <720854.2723.qm@web81305.mail.mud.yahoo.com> References: <720854.2723.qm@web81305.mail.mud.yahoo.com> Message-ID: <200708021438.01112.knura@yahoo.com> On Thursday 02 August 2007 03:33, Robert Smith wrote: > According to a recent CompTIA survey, Micro$oft's Internet Explorer ... snip ... A) CompTIA's sponsors are the industry heavy weights including M$. > The survey listed three other M$ products in the top five, > including Word, Windows 95, and Excel, which tied with Apple's iPod. B) Please see item A) above :) ... snip ... > It is interesting to note that 471 respondents is probably but a > fraction of a percent of the number of people walking around with > CompTIA certifications. I wonder how many hold Linux+ certs? I am willing to bet - none. As far as Linux cert. go, I think RHC[TEA] and LPI Level 1 and Level 2 have more global value; I wonder what is the value of their Linux+ cert. Personally, I have come across more RHCT/E and LPI level 1 than Linux+ (0). -- Arun Khan "They alone live who live for others, rest are more dead than alive." - Swami Vivekanada From ohrock at gmail.com Thu Aug 2 06:54:03 2007 From: ohrock at gmail.com (Roberto Serrano) Date: Thu Aug 2 05:54:07 2007 Subject: [LUNI] Chicago Free and Open Source Conference In-Reply-To: <46B0DA95.4080301@voxlox.com> References: <1185943308.3544.6.camel@localhost.localdomain> <46B0DA95.4080301@voxlox.com> Message-ID: <3d76512f0708020354u65ebd9c0yabb8ffd4c94c0510@mail.gmail.com> The "Uber" discussion became Flourish.... Most of the people that where pushing for that where UIC LUG members - as you know - so when the interest from most of the community was not materializing, we took it upon ourselves to make something happen. Flourish was the result. We are going for another run this coming April. We are hoping to have a bigger audience and go from 180 overall to about 300. But, we are not increasing the scope of the event because we lack man-power - we are planing to have around 14 activities for 2 days, same as this year. If we get more help, like I suggested, maybe we could do a third day with a focus on the desktop. Roberto On 8/1/07, D. Wade wrote: > > Interested! > > I'd hoped to see something like this grow out of the "Uber FEST" > discussions of last year, but I don't know what ever happened to that. > > I *might* be able to get some sponsorship / cost defrayment going, if > this becomes real. > > --Derek W. > From aclose at gmail.com Thu Aug 2 09:29:59 2007 From: aclose at gmail.com (Andrew Close) Date: Thu Aug 2 08:30:06 2007 Subject: [LUNI] Chicago Free and Open Source Conference In-Reply-To: <3d76512f0708020354u65ebd9c0yabb8ffd4c94c0510@mail.gmail.com> References: <1185943308.3544.6.camel@localhost.localdomain> <46B0DA95.4080301@voxlox.com> <3d76512f0708020354u65ebd9c0yabb8ffd4c94c0510@mail.gmail.com> Message-ID: On 8/2/07, Roberto Serrano wrote: > The "Uber" discussion became Flourish.... > > Most of the people that where pushing for that where UIC LUG members - as > you know - so when the interest from most of the community was not > materializing, we took it upon ourselves to make something happen. Flourish > was the result. > > We are going for another run this coming April. We are hoping to have a > bigger audience and go from 180 overall to about 300. But, we are not > increasing the scope of the event because we lack man-power - we are planing > to have around 14 activities for 2 days, same as this year. > > If we get more help, like I suggested, maybe we could do a third day with a > focus on the desktop. Roberto, i just just checked out the previous Flourish website (http://www.flourishconf.com/). have you guys already started planning for 2008? do you have a separate mailing list/wiki/etc? i don't "remember" if i saw a posting on LUNI last year regarding volunteers/donations, but i bet there are ppl on list that would be interested in helping out. From sfaci at cs.uic.edu Thu Aug 2 09:44:20 2007 From: sfaci at cs.uic.edu (Samir Faci) Date: Thu Aug 2 08:44:25 2007 Subject: [LUNI] Chicago Free and Open Source Conference In-Reply-To: References: <1185943308.3544.6.camel@localhost.localdomain> <46B0DA95.4080301@voxlox.com> <3d76512f0708020354u65ebd9c0yabb8ffd4c94c0510@mail.gmail.com> Message-ID: <9db93b0e0708020644v8703e61k10860f5475e920ef@mail.gmail.com> We really should setup those lists, though luni has kind of become the newsletter/flourish update list. At least I end up sending emails every so often about flourish as we get closer to d-day. Right now, we are still looking at the details regarding venue and where to have the event. Once we have a date and time established, I'm sure we'd appreciate any help from the community. I think the chicon or whatever it ends up being called is target more at open source enthusiasts, getting develops in, and straying far more away from the business aspect of the industry then flourish did. One of the main focuses of flourish was, hey... i can code in FLOSS and not be broke.. who knew. (minus the sarcasm) I'm not sure if we're keeping the same theme as we did last year, but flourish is going to be in April. ChiCon according to the discussion in irc is planned for november. It would be great if we could get Open Source conferences going twice a year. Talk about a revival on Conferences for chicago. -- Samir On 8/2/07, Andrew Close wrote: > On 8/2/07, Roberto Serrano wrote: > > The "Uber" discussion became Flourish.... > > > > Most of the people that where pushing for that where UIC LUG members - as > > you know - so when the interest from most of the community was not > > materializing, we took it upon ourselves to make something happen. Flourish > > was the result. > > > > We are going for another run this coming April. We are hoping to have a > > bigger audience and go from 180 overall to about 300. But, we are not > > increasing the scope of the event because we lack man-power - we are planing > > to have around 14 activities for 2 days, same as this year. > > > > If we get more help, like I suggested, maybe we could do a third day with a > > focus on the desktop. > > Roberto, > > i just just checked out the previous Flourish website > (http://www.flourishconf.com/). > have you guys already started planning for 2008? do you have a > separate mailing list/wiki/etc? > i don't "remember" if i saw a posting on LUNI last year regarding > volunteers/donations, but i bet there are ppl on list that would be > interested in helping out. > -- > Linux Users Of Northern Illinois - Technical Discussion > http://luni.org/mailman/listinfo/luni > From aclose at gmail.com Thu Aug 2 10:05:12 2007 From: aclose at gmail.com (Andrew Close) Date: Thu Aug 2 09:05:14 2007 Subject: [LUNI] Chicago Free and Open Source Conference In-Reply-To: <9db93b0e0708020644v8703e61k10860f5475e920ef@mail.gmail.com> References: <1185943308.3544.6.camel@localhost.localdomain> <46B0DA95.4080301@voxlox.com> <3d76512f0708020354u65ebd9c0yabb8ffd4c94c0510@mail.gmail.com> <9db93b0e0708020644v8703e61k10860f5475e920ef@mail.gmail.com> Message-ID: On 8/2/07, Samir Faci wrote: > We really should setup those lists, though luni has kind of become the > newsletter/flourish update list. At least I end up sending emails > every so often about flourish as we get closer to d-day. i'm sure the LUNIs won't mind the use of the list since it is linux related. if you do continue that route, it might be worthwhile to tag the subject with [Flourish] or [FLOSS Conf] or something like that, so it's easier for ppl to filter... > Right now, we are still looking at the details regarding venue and > where to have the event. Once we have a date and time established, > I'm sure we'd appreciate any help from the community. > > I think the chicon or whatever it ends up being called is target more > at open source enthusiasts, getting develops in, and straying far more > away from the business aspect of the industry then flourish did. One > of the main focuses of flourish was, hey... i can code in FLOSS and > not be broke.. who knew. (minus the sarcasm) twice a year would be cool, and sarcasm is good. ;) > I'm not sure if we're keeping the same theme as we did last year, but > flourish is going to be in April. ChiCon according to the discussion > in irc is planned for november. It would be great if we could get > Open Source conferences going twice a year. Talk about a revival on > Conferences for chicago. has anyone from 'the group' contacted anyone from the city of Chicago? if you're attempting to set up conferences that will bring in ppl from outside the city, they may be willing to help, or at least provide contacts/references, since you'd ultimately be benefiting the city. From sfaci at cs.uic.edu Thu Aug 2 15:49:49 2007 From: sfaci at cs.uic.edu (Samir Faci) Date: Thu Aug 2 09:49:57 2007 Subject: [LUNI] Chicago Free and Open Source Conference In-Reply-To: References: <1185943308.3544.6.camel@localhost.localdomain> <46B0DA95.4080301@voxlox.com> <3d76512f0708020354u65ebd9c0yabb8ffd4c94c0510@mail.gmail.com> <9db93b0e0708020644v8703e61k10860f5475e920ef@mail.gmail.com> Message-ID: <9db93b0e0708020749s1eff5b2fl21f5f065cc760e63@mail.gmail.com> That's actually a great idea, though I wouldn't know where to get started, or who I'd need to talk to. I'm sure flourish or the chicon people would love a few contact names to talk to. If the city starts supporting us a bit more, we'd definitely could make these events better and grander. -- Samir > has anyone from 'the group' contacted anyone from the city of Chicago? > if you're attempting to set up conferences that will bring in ppl > from outside the city, they may be willing to help, or at least > provide contacts/references, since you'd ultimately be benefiting the > city. > -- > Linux Users Of Northern Illinois - Technical Discussion > http://luni.org/mailman/listinfo/luni > From dbt at meat.net Thu Aug 2 11:20:32 2007 From: dbt at meat.net (David Terrell) Date: Thu Aug 2 10:20:36 2007 Subject: [LUNI] IE Most Influential Tech Product of Last 25 Years? In-Reply-To: <720854.2723.qm@web81305.mail.mud.yahoo.com> References: <720854.2723.qm@web81305.mail.mud.yahoo.com> Message-ID: <20070802152032.GB11635@sphinx.chicagopeoplez.org> On Wed, Aug 01, 2007 at 03:03:13PM -0700, Robert Smith wrote: > ... Both IE and FireFox (through Netscape Navigator) can trace their parentage back to the browser developed at NCSA. > > It sure shows who voted, that Linus's kernel project didn't crack the top ten, yet the iPod made it into the top five. Makes you wonder what CompTIA is using for servers. I find it interesting that you don't think IE or Netscape/Firefox should qualify because they're so derivative of NCSA Mosaic, yet you think Linux does. It makes you wonder.... -- David Terrell dbt@meat.net ((meatspace)) http://meat.net/ From sfaci at cs.uic.edu Thu Aug 2 11:56:45 2007 From: sfaci at cs.uic.edu (Samir Faci) Date: Thu Aug 2 10:56:51 2007 Subject: [LUNI] IE Most Influential Tech Product of Last 25 Years? In-Reply-To: <20070802152032.GB11635@sphinx.chicagopeoplez.org> References: <720854.2723.qm@web81305.mail.mud.yahoo.com> <20070802152032.GB11635@sphinx.chicagopeoplez.org> Message-ID: <9db93b0e0708020856q61b7c984n83eff2442e1d7301@mail.gmail.com> Guys, I really think you're looking at this the wrong way. IE was VERY influential in the past 25 years. It's not necessarily a good product, but the list was about being influential, not quality iirc. What person owning a computer that isn't a hardcore geek has a PC that doesn't have IE? or doesn't associate internet = big blue E on my desktop I may be looking at this the wrong way, but MSFT and IE has had a huge influence on the IT/Computer industry in the last 25 years. We may wish they would write better software or crawl in a hole and stop producing any more vista/whatever.. but they definitely have had an influence. my $0.02 -- Samir On 8/2/07, David Terrell wrote: > On Wed, Aug 01, 2007 at 03:03:13PM -0700, Robert Smith wrote: > > ... Both IE and FireFox (through Netscape Navigator) can trace their parentage back to the browser developed at NCSA. > > > > It sure shows who voted, that Linus's kernel project didn't crack the top ten, yet the iPod made it into the top five. Makes you wonder what CompTIA is using for servers. > > I find it interesting that you don't think IE or Netscape/Firefox > should qualify because they're so derivative of NCSA Mosaic, yet > you think Linux does. > > It makes you wonder.... > > -- > David Terrell > dbt@meat.net > ((meatspace)) http://meat.net/ > -- > Linux Users Of Northern Illinois - Technical Discussion > http://luni.org/mailman/listinfo/luni > From craig at codestorm.org Thu Aug 2 13:44:05 2007 From: craig at codestorm.org (Craig Van Tassle) Date: Thu Aug 2 12:44:06 2007 Subject: [LUNI] IE Most Influential Tech Product of Last 25 Years? In-Reply-To: <9db93b0e0708020856q61b7c984n83eff2442e1d7301@mail.gmail.com> References: <720854.2723.qm@web81305.mail.mud.yahoo.com> <20070802152032.GB11635@sphinx.chicagopeoplez.org> <9db93b0e0708020856q61b7c984n83eff2442e1d7301@mail.gmail.com> Message-ID: <46B217E5.7060507@codestorm.org> Actually I hope they produce a LOT more vista quality products. That will help a the F/OSS world a LOT! Samir Faci wrote: > Guys, I really think you're looking at this the wrong way. IE was > VERY influential in the past 25 years. It's not necessarily a good > product, but the list was about being influential, not quality iirc. > What person owning a computer that isn't a hardcore geek has a PC that > doesn't have IE? or doesn't associate internet = big blue E on my > desktop > > I may be looking at this the wrong way, but MSFT and IE has had a huge > influence on the IT/Computer industry in the last 25 years. We may > wish they would write better software or crawl in a hole and stop > producing any more vista/whatever.. but they definitely have had an > influence. > > > my $0.02 > -- > Samir > > On 8/2/07, David Terrell wrote: >> On Wed, Aug 01, 2007 at 03:03:13PM -0700, Robert Smith wrote: >>> ... Both IE and FireFox (through Netscape Navigator) can trace their parentage back to the browser developed at NCSA. >>> >>> It sure shows who voted, that Linus's kernel project didn't crack the top ten, yet the iPod made it into the top five. Makes you wonder what CompTIA is using for servers. >> I find it interesting that you don't think IE or Netscape/Firefox >> should qualify because they're so derivative of NCSA Mosaic, yet >> you think Linux does. >> >> It makes you wonder.... >> >> -- >> David Terrell >> dbt@meat.net >> ((meatspace)) http://meat.net/ >> -- >> Linux Users Of Northern Illinois - Technical Discussion >> http://luni.org/mailman/listinfo/luni >> From me at heyjay.com Thu Aug 2 14:33:51 2007 From: me at heyjay.com (Jay Strauss) Date: Thu Aug 2 13:33:57 2007 Subject: [LUNI] oh oh, my raid it having problems Message-ID: Hi, I have a raid1 fileserver at home, where I store all my home directories. I just noticed in my mail the messages below. I'm a bit frightened. All my files seem to be accessable, but not sure what my next steps should be. Any help, suggestions, guidence would be appreciated. Thank you Jay >U 1 root@localhost.lo Sat Jul 02 18:50 21/718 Fail event on /dev/md1:iron U 2 root@localhost.lo Sat Oct 28 20:54 21/736 DegradedArray event on /dev/md0:iron U 3 root@localhost.lo Sat Oct 28 20:54 21/736 DegradedArray event on /dev/md1:iron U 4 root@localhost.lo Sat Oct 28 21:18 21/736 DegradedArray event on /dev/md0:iron U 5 root@localhost.lo Sat Oct 28 21:18 21/736 DegradedArray event on /dev/md1:iron U 6 root@localhost.lo Sat Oct 28 21:51 21/736 DegradedArray event on /dev/md0:iron U 7 root@localhost.lo Sat Oct 28 21:51 21/736 DegradedArray event on /dev/md1:iron U 8 root@localhost.lo Sat Oct 28 22:19 21/736 DegradedArray event on /dev/md0:iron U 9 root@localhost.lo Sat Oct 28 22:19 21/736 DegradedArray event on /dev/md1:iron U 10 root@localhost.lo Sat Oct 28 22:22 21/736 DegradedArray event on /dev/md0:iron U 11 root@localhost.lo Sat Oct 28 22:22 21/736 DegradedArray event on /dev/md1:iron U 12 root@localhost.lo Sat Oct 28 22:25 21/736 DegradedArray event on /dev/md0:iron U 13 root@localhost.lo Sat Oct 28 22:25 21/736 DegradedArray event on /dev/md1:iron U 14 root@localhost.lo Sun Feb 04 23:01 21/736 DegradedArray event on /dev/md0:iron U 15 root@localhost.lo Sun Feb 04 23:01 21/736 DegradedArray event on /dev/md1:iron U 16 root@localhost.lo Sun Apr 29 20:53 21/736 DegradedArray event on /dev/md0:iron U 17 root@localhost.lo Sun Apr 29 20:53 21/736 DegradedArray event on /dev/md1:iron U 18 root@localhost.lo Sun May 13 10:18 21/736 DegradedArray event on /dev/md0:iron U 19 root@localhost.lo Sun May 13 10:18 21/736 DegradedArray event on /dev/md1:iron U 20 root@localhost.lo Thu May 17 21:06 21/736 DegradedArray event on /dev/md0:iron U 21 root@localhost.lo Thu May 17 21:06 21/736 DegradedArray event on /dev/md1:iron U 22 root@localhost.lo Thu May 17 21:15 21/736 DegradedArray event on /dev/md0:iron U 23 root@localhost.lo Thu May 17 21:15 21/736 DegradedArray event on /dev/md1:iron U 24 root@localhost.lo Fri May 18 08:17 21/736 DegradedArray event on /dev/md1:iron U 25 root@localhost.lo Fri May 18 08:17 21/736 DegradedArray event on /dev/md0:iron U 26 root@localhost.lo Mon Jul 30 21:48 21/736 DegradedArray event on /dev/md0:iron U 27 root@localhost.lo Mon Jul 30 21:48 21/736 DegradedArray event on /dev/md1:iron U 28 Mailer-Daemon@loc Thu Aug 02 13:25 38/1394 Mail delivery failed: returning message to sender U 29 Mailer-Daemon@loc Thu Aug 02 13:26 38/1394 Mail delivery failed: returning message to sender & 1 Message 1: >From root@localhost.localdomain Sat Jul 02 18:50:43 2005 Envelope-to: root@localhost.localdomain Delivery-date: Sat, 02 Jul 2005 18:50:43 -0500 From: mdadm monitoring To: root@localhost.localdomain Subject: Fail event on /dev/md1:iron Date: Sat, 02 Jul 2005 18:50:36 -0500 This is an automatically generated mail message from mdadm running on iron A Fail event had been detected on md device /dev/md1. Faithfully yours, etc. & q Saved 1 message in /home/jstrauss/mbox Held 28 messages in /var/mail/jstrauss From craig at codestorm.org Thu Aug 2 14:46:24 2007 From: craig at codestorm.org (Craig Van Tassle) Date: Thu Aug 2 13:46:24 2007 Subject: [LUNI] oh oh, my raid it having problems In-Reply-To: References: Message-ID: <46B22680.4060807@codestorm.org> I would check /proc/mdstat and if it shows one drive failed then I would replace the drive. You should be able to tell what drive is bad when you look at mdstat. I'm assuming you are only using the full drive for raid. Get a drive of the same size, remove the failed drive. Install the new drive. Partision it and then hotadd it to the array. Depending on size of the partision you should be able to sync it from any time between 10 minutes to 3 hours. watch -n 1 'cat /proc/mdstat' will show you the drive as it resyncs. It should not take that long. Then I would check RMA status and also run a badblocks on the failed drive. That should tell you what went wrong. Another thing to do is check the smart status of the drive. That should show if the drive failed and why. HTH Craig Jay Strauss wrote: > Hi, > > I have a raid1 fileserver at home, where I store all my home > directories. I just noticed in my mail the messages below. > > I'm a bit frightened. > > All my files seem to be accessable, but not sure what my next steps should be. > > Any help, suggestions, guidence would be appreciated. > > Thank you > Jay > >> U 1 root@localhost.lo Sat Jul 02 18:50 21/718 Fail event on /dev/md1:iron > U 2 root@localhost.lo Sat Oct 28 20:54 21/736 DegradedArray > event on /dev/md0:iron > U 3 root@localhost.lo Sat Oct 28 20:54 21/736 DegradedArray > event on /dev/md1:iron > U 4 root@localhost.lo Sat Oct 28 21:18 21/736 DegradedArray > event on /dev/md0:iron > U 5 root@localhost.lo Sat Oct 28 21:18 21/736 DegradedArray > event on /dev/md1:iron > U 6 root@localhost.lo Sat Oct 28 21:51 21/736 DegradedArray > event on /dev/md0:iron > U 7 root@localhost.lo Sat Oct 28 21:51 21/736 DegradedArray > event on /dev/md1:iron > U 8 root@localhost.lo Sat Oct 28 22:19 21/736 DegradedArray > event on /dev/md0:iron > U 9 root@localhost.lo Sat Oct 28 22:19 21/736 DegradedArray > event on /dev/md1:iron > U 10 root@localhost.lo Sat Oct 28 22:22 21/736 DegradedArray > event on /dev/md0:iron > U 11 root@localhost.lo Sat Oct 28 22:22 21/736 DegradedArray > event on /dev/md1:iron > U 12 root@localhost.lo Sat Oct 28 22:25 21/736 DegradedArray > event on /dev/md0:iron > U 13 root@localhost.lo Sat Oct 28 22:25 21/736 DegradedArray > event on /dev/md1:iron > U 14 root@localhost.lo Sun Feb 04 23:01 21/736 DegradedArray > event on /dev/md0:iron > U 15 root@localhost.lo Sun Feb 04 23:01 21/736 DegradedArray > event on /dev/md1:iron > U 16 root@localhost.lo Sun Apr 29 20:53 21/736 DegradedArray > event on /dev/md0:iron > U 17 root@localhost.lo Sun Apr 29 20:53 21/736 DegradedArray > event on /dev/md1:iron > U 18 root@localhost.lo Sun May 13 10:18 21/736 DegradedArray > event on /dev/md0:iron > U 19 root@localhost.lo Sun May 13 10:18 21/736 DegradedArray > event on /dev/md1:iron > U 20 root@localhost.lo Thu May 17 21:06 21/736 DegradedArray > event on /dev/md0:iron > U 21 root@localhost.lo Thu May 17 21:06 21/736 DegradedArray > event on /dev/md1:iron > U 22 root@localhost.lo Thu May 17 21:15 21/736 DegradedArray > event on /dev/md0:iron > U 23 root@localhost.lo Thu May 17 21:15 21/736 DegradedArray > event on /dev/md1:iron > U 24 root@localhost.lo Fri May 18 08:17 21/736 DegradedArray > event on /dev/md1:iron > U 25 root@localhost.lo Fri May 18 08:17 21/736 DegradedArray > event on /dev/md0:iron > U 26 root@localhost.lo Mon Jul 30 21:48 21/736 DegradedArray > event on /dev/md0:iron > U 27 root@localhost.lo Mon Jul 30 21:48 21/736 DegradedArray > event on /dev/md1:iron > U 28 Mailer-Daemon@loc Thu Aug 02 13:25 38/1394 Mail delivery > failed: returning message to sender > U 29 Mailer-Daemon@loc Thu Aug 02 13:26 38/1394 Mail delivery > failed: returning message to sender > & 1 > Message 1: >>From root@localhost.localdomain Sat Jul 02 18:50:43 2005 > Envelope-to: root@localhost.localdomain > Delivery-date: Sat, 02 Jul 2005 18:50:43 -0500 > From: mdadm monitoring > To: root@localhost.localdomain > Subject: Fail event on /dev/md1:iron > Date: Sat, 02 Jul 2005 18:50:36 -0500 > > This is an automatically generated mail message from mdadm > running on iron > > A Fail event had been detected on md device /dev/md1. > > Faithfully yours, etc. > > & q > Saved 1 message in /home/jstrauss/mbox > Held 28 messages in /var/mail/jstrauss From ramin-list at badapple.net Thu Aug 2 12:50:15 2007 From: ramin-list at badapple.net (Ramin K) Date: Thu Aug 2 14:07:31 2007 Subject: [LUNI] oh oh, my raid it having problems In-Reply-To: References: Message-ID: <46B22767.9030502@badapple.net> Jay Strauss wrote: > Hi, > > I have a raid1 fileserver at home, where I store all my home > directories. I just noticed in my mail the messages below. > > I'm a bit frightened. > > All my files seem to be accessable, but not sure what my next steps should be. > > Any help, suggestions, guidence would be appreciated. > > Thank you > Jay Step 1: Remember that RAID, any sort of RAID, is not a backup. Make a backup if you don't have one. Now. Step 2: Craig's instructions are spot on. Ramin From me at heyjay.com Thu Aug 2 16:09:24 2007 From: me at heyjay.com (Jay Strauss) Date: Thu Aug 2 15:09:28 2007 Subject: [LUNI] oh oh, my raid it having problems In-Reply-To: <46B22680.4060807@codestorm.org> References: <46B22680.4060807@codestorm.org> Message-ID: On 8/2/07, Craig Van Tassle wrote: > I would check /proc/mdstat and if it shows one drive failed then I would replace the drive. > You should be able to tell what drive is bad when you look at mdstat. I'm assuming you are only using the full drive for > raid. Get a drive of the same size, remove the failed drive. Install the new drive. Partision it and then hotadd it to > the array. Depending on size of the partision you should be able to sync it from any time between 10 minutes to 3 hours. > watch -n 1 'cat /proc/mdstat' will show you the drive as it resyncs. It should not take that long. > > Then I would check RMA status and also run a badblocks on the failed drive. That should tell you what went wrong. > Another thing to do is check the smart status of the drive. That should show if the drive failed and why. > > HTH > > Craig Hi Craig, thanks for advice. Here is the output: iron:~# cat /proc/mdstat Personalities : [raid1] md0 : active raid1 hda1[0] 1951744 blocks [2/1] [U_] md1 : active raid1 hda2[0] 115266304 blocks [2/1] [U_] unused devices: I'm guessing it's hda1 that is the problem. I don't know how to print the partition table. I have 2 disks which I broke into 2 partitions. On top of those I built two raid 1 devices. On one of the devices (the big one) I built an LVM. So how do I print the partition table? Do I power down the box, remove the drive, replace with new, power back on and try to sync OR do I do it all while the box is running? What is RMA how do I check it? Do I stick the failed drive in a different computer? Thanks Jay From me at heyjay.com Thu Aug 2 16:11:37 2007 From: me at heyjay.com (Jay Strauss) Date: Thu Aug 2 15:11:45 2007 Subject: [LUNI] oh oh, my raid it having problems In-Reply-To: <46B22767.9030502@badapple.net> References: <46B22767.9030502@badapple.net> Message-ID: > Step 1: Remember that RAID, any sort of RAID, is not a backup. Make a > backup if you don't have one. Now. > > Step 2: Craig's instructions are spot on. > > Ramin I do not have a backup. Been meaning to configure some offsite backups (for a couple of boxes), I guess I need to get on that. I'm going out of town this evening for the weekend, do you think I should power down the box, or should I let sleeping dogs lie? Thanks Jay From craig at codestorm.org Thu Aug 2 16:34:55 2007 From: craig at codestorm.org (Craig Van Tassle) Date: Thu Aug 2 15:35:02 2007 Subject: [LUNI] oh oh, my raid it having problems In-Reply-To: References: <46B22680.4060807@codestorm.org> Message-ID: <46B23FEF.5050707@codestorm.org> Ugg bottom posters.. No it looks like hda is the drive that is working. > md0 : active raid1 hda1[0] Notice it does not say anything about hdb. > 1951744 blocks [2/1] [U_] Also notice it says 2/1 That means 2 drives configured and one drive failed. the U_ means that the first drive of the array is good (Up), and the second one failed. As for copying the partision table once you get the new drive installed dd if=/dev/hda of=/dev/hdb bs=512 count=1024. That will copy your MBR and your partision table. If you dont have hot-swap drives you have to power down the box. To read the partision table use fdisk. Man fdisk will help out there. Remember IDE is NOT hot-swap! If you don't know if you have hotswap drives then you don't. To check for RMA you need to look at the drive. Go to the makers website and look up warranty status. RMA == Return Material Authorization. The SMART checks and badblocks can be done on the current system. Man smartctl and man badblocks. That will give ya all the info you need. Jay Strauss wrote: > > Hi Craig, thanks for advice. Here is the output: > > iron:~# cat /proc/mdstat > Personalities : [raid1] > md0 : active raid1 hda1[0] > 1951744 blocks [2/1] [U_] > > md1 : active raid1 hda2[0] > 115266304 blocks [2/1] [U_] > > unused devices: > > I'm guessing it's hda1 that is the problem. I don't know how to print > the partition table. I have 2 disks which I broke into 2 partitions. > On top of those I built two raid 1 devices. On one of the devices > (the big one) I built an LVM. > > So how do I print the partition table? > > Do I power down the box, remove the drive, replace with new, power > back on and try to sync OR do I do it all while the box is running? > > What is RMA how do I check it? Do I stick the failed drive in a > different computer? > > Thanks > Jay From craig at codestorm.org Thu Aug 2 16:37:09 2007 From: craig at codestorm.org (Craig Van Tassle) Date: Thu Aug 2 15:37:09 2007 Subject: [LUNI] oh oh, my raid it having problems In-Reply-To: References: <46B22767.9030502@badapple.net> Message-ID: <46B24075.2040108@codestorm.org> Now is as good a time as any. With a degraded array you are at much higher risk to lose data if the other drive fails. As for powering down the box that may help it may not. It depends if how long until you can replace the disk. Considering you dont have a backup. I would say shut it down to make sure the good drive does not go while you are away. Jay Strauss wrote: >> Step 1: Remember that RAID, any sort of RAID, is not a backup. Make a >> backup if you don't have one. Now. >> >> Step 2: Craig's instructions are spot on. >> >> Ramin > > I do not have a backup. Been meaning to configure some offsite > backups (for a couple of boxes), I guess I need to get on that. > > I'm going out of town this evening for the weekend, do you think I > should power down the box, or should I let sleeping dogs lie? > > Thanks > Jay From m.mccune at comcast.net Thu Aug 2 16:38:26 2007 From: m.mccune at comcast.net (Mike McCune) Date: Thu Aug 2 15:38:45 2007 Subject: [LUNI] ANN: State Restaurant closed for a private event. In-Reply-To: <46AF908C.8010305@comcast.net> References: <46AF908C.8010305@comcast.net> Message-ID: <46B240C2.80902@comcast.net> Looks like we need to find a new location. Any suggestions? If you need to call me, my cell phone is 773-531-6780. Maybe we could meet at Kelly's (http://www.kellyspub.com), which is directly east of State? Mike McCune wrote: > Remodling is done and they now serve booze. > > WCLUG is meeting Thursday, August 2, 7pm at State Restaurant, 935 W. > Webster Ave. > > The Web site www.wclug.org is having DNS problems but > http://hocomm.com/WCLUG/ still works. > -- Linux Users Of Northern Illinois - Announcements Mailing List http://luni.org/mailman/listinfo/luni-announce From ramin-list at badapple.net Thu Aug 2 14:57:52 2007 From: ramin-list at badapple.net (Ramin K) Date: Thu Aug 2 15:57:56 2007 Subject: [LUNI] oh oh, my raid it having problems In-Reply-To: References: <46B22767.9030502@badapple.net> Message-ID: <46B24550.2010204@badapple.net> Jay Strauss wrote: >> Step 1: Remember that RAID, any sort of RAID, is not a backup. Make a >> backup if you don't have one. Now. >> >> Step 2: Craig's instructions are spot on. >> >> Ramin > > I do not have a backup. Been meaning to configure some offsite > backups (for a couple of boxes), I guess I need to get on that. > > I'm going out of town this evening for the weekend, do you think I > should power down the box, or should I let sleeping dogs lie? > > Thanks > Jay Having a backup, even if it's a simple rsync to another machine or a quick copy to an external drive would make me feel better about the whole thing. If you leave things running the working drive could fail. If you power down the working drive might fail when it comes up again. Both may be unlikely, but only a backup protects you in both cases. Ramin, bottom poster From sqrfolkdnc at comcast.net Thu Aug 2 19:13:57 2007 From: sqrfolkdnc at comcast.net (Carey Tyler Schug) Date: Thu Aug 2 18:14:21 2007 Subject: [LUNI] ANN: NWCLUG's next meeting 7/3/07 In-Reply-To: <472758.52761.qm@web57013.mail.re3.yahoo.com> References: <472758.52761.qm@web57013.mail.re3.yahoo.com> Message-ID: <46B26535.7080209@comcast.net> Any topic for August yet? I see nothing on the web page and haven't received an email. I have promised to help somebody if the NWCLUG is not "unmissable" so need to know ASAP if I will have to cancel that offer. Mike Swier wrote: > Hi, > > NWCLUG's next meeting will be at Harper College in A238 at 7pm on Tuesday 7/3/07. > > The Freevo project will be talked about. > > For (a bit) more info see http://nwclug.org/httpd/html/meetings.html#nextmtg > > mikie > > > > -- Carey Tyler Schug From jrstark at barntowire.com Thu Aug 2 21:32:35 2007 From: jrstark at barntowire.com (Janine Starykowicz) Date: Thu Aug 2 20:32:31 2007 Subject: [LUNI] Open Office question Message-ID: <46B285B3.1090404@barntowire.com> Not a Linux question, but it is open source, please help. I'm trying to convert some rich text charts that I was emailed to tab-delimited text files. If I copy them into calc, the columns hold, I can export fine from there. The problem is the formatting of some of the data. I have dollar fields that need to keep the dollar signs and commas ($20,000). This converts to 20000. I have another field that is odds: 8-1, 5-2 etc. These get calculated. Is there any way to force text formatting on these columns aside from manually entering ' at the beginning of each cell? Thanks! Janine From mark at msbrepairs.com Thu Aug 2 22:52:02 2007 From: mark at msbrepairs.com (Mark Stuart Burge) Date: Thu Aug 2 21:48:30 2007 Subject: [LUNI] Open Office question In-Reply-To: <46B285B3.1090404@barntowire.com> References: <46B285B3.1090404@barntowire.com> Message-ID: <46B29852.6040002@msbrepairs.com> Hi Janine > > The problem is the formatting of some of the data. I have dollar > fields that need to keep the dollar signs and commas ($20,000). This > converts to 20000. You can select the column that should have $ and format the whole column as currency (there is a toolbar icon that looks like ) > I have another field that is odds: 8-1, 5-2 etc. These get > calculated. Is there any way to force text formatting on these > columns aside from manually entering ' at the beginning of each cell? If you select the columns you want left alone, then go to Format Cell and choose TEXT (it is represented with the @ format code) then paste without formatting, the cells should hold the text format and leave the - as a - and not a minus From r_a_smith3530 at sbcglobal.net Fri Aug 3 00:19:08 2007 From: r_a_smith3530 at sbcglobal.net (Robert Smith) Date: Fri Aug 3 01:19:16 2007 Subject: [LUNI] IE Most Influential Tech Product of Last 25 Years? In-Reply-To: <9db93b0e0708020856q61b7c984n83eff2442e1d7301@mail.gmail.com> Message-ID: <619785.16357.qm@web81313.mail.mud.yahoo.com> First, my intent was to point out how quickly people forget. I wonder how many of those 147 respondents were even around when Mosaic was being developed? Of those that were, did Microsoft's marketing genius and predatory practices cloud their memory? Yes, Internet Explorer had a major influence on computer use as we know it today, but how much of that is due to product excellence, and how much is due to being able to either outspend the competition or hit below the belt? Meanwhile, Linux, and Open Source software in general have made major inroads into the computing world in their short lifespan due both to technical excellence, and a solid development philosophy, yet no open source software, OS or otherwise, made it to the top ten in this survey. Things that make you go Hmm! If you want to give Gates and the Redmond folks an award, give it to them where they've earned it, savvy marketing panache, and predatory industrial practices. Gates himself admitted that he almost missed the Internet phenomenon, and if you recall, IE3 wasn't all that sexy an object to behold or work with. IE owes its existence to Mosaic, just as Win XP owes its existence to the OS2 folks that Gates was able to hire away to Microsoft. Vista? I won't blame that on any predecessor software! I just felt that the systems that power giants like Google, Pixar Studios, the Home Depot, AutoZone, and a myriad number of other businesses should have received some credit. But then hey, I'm one of those weirdos who believe that the Open Source movement is one of the most innovative ideas to come out of the past quarter century. Of course, the advertising budget is much smaller, so they certainly can't be very technically influential! Rob Smith Samir Faci wrote: Guys, I really think you're looking at this the wrong way. IE was VERY influential in the past 25 years. It's not necessarily a good product, but the list was about being influential, not quality iirc. What person owning a computer that isn't a hardcore geek has a PC that doesn't have IE? or doesn't associate internet = big blue E on my desktop I may be looking at this the wrong way, but MSFT and IE has had a huge influence on the IT/Computer industry in the last 25 years. We may wish they would write better software or crawl in a hole and stop producing any more vista/whatever.. but they definitely have had an influence. my $0.02 -- Samir On 8/2/07, David Terrell wrote: > On Wed, Aug 01, 2007 at 03:03:13PM -0700, Robert Smith wrote: > > ... Both IE and FireFox (through Netscape Navigator) can trace their parentage back to the browser developed at NCSA. > > > > It sure shows who voted, that Linus's kernel project didn't crack the top ten, yet the iPod made it into the top five. Makes you wonder what CompTIA is using for servers. > > I find it interesting that you don't think IE or Netscape/Firefox > should qualify because they're so derivative of NCSA Mosaic, yet > you think Linux does. > > It makes you wonder.... > > -- > David Terrell > dbt@meat.net > ((meatspace)) http://meat.net/ > -- > Linux Users Of Northern Illinois - Technical Discussion > http://luni.org/mailman/listinfo/luni > -- Linux Users Of Northern Illinois - Technical Discussion http://luni.org/mailman/listinfo/luni From dbt at meat.net Fri Aug 3 10:13:34 2007 From: dbt at meat.net (David Terrell) Date: Fri Aug 3 09:13:38 2007 Subject: [LUNI] IE Most Influential Tech Product of Last 25 Years? In-Reply-To: <619785.16357.qm@web81313.mail.mud.yahoo.com> References: <9db93b0e0708020856q61b7c984n83eff2442e1d7301@mail.gmail.com> <619785.16357.qm@web81313.mail.mud.yahoo.com> Message-ID: <20070803141334.GC11635@sphinx.chicagopeoplez.org> On Thu, Aug 02, 2007 at 11:19:08PM -0700, Robert Smith wrote: > But then hey, I'm one of those ... > May I suggest you be one of those people who learn to ignore foolish corporate propoganda. Or at least debate it in a forum where you're not simply preaching to (or annoying) the choir. -- David Terrell dbt@meat.net ((meatspace)) http://meat.net/ From donotreply at trm.brassring.com Fri Aug 3 15:07:32 2007 From: donotreply at trm.brassring.com (tom@yarrish.com) Date: Fri Aug 3 13:18:30 2007 Subject: [LUNI] UNIX position at my company Message-ID: <06cc01c7d5f9$296709a0$190a14ac@prod.brassring.com> Hey all, If anyone is looking for a Unix position, I just found this one at the place I work at. I don't have many specifics about the job other than what's in the listing (different group), but if you have questions about the company feel free to email me. Thanks, Tom ------------------------------------------ Your friend has found job(s) at TAP that you might find interesting. Please click the following "View jobs" button to view job(s). Best regards. From tom at yarrish.com Fri Aug 3 14:54:21 2007 From: tom at yarrish.com (Tom Yarrish) Date: Fri Aug 3 14:13:15 2007 Subject: [LUNI] UNIX position at my company In-Reply-To: <06cc01c7d5f9$296709a0$190a14ac@prod.brassring.com> References: <06cc01c7d5f9$296709a0$190a14ac@prod.brassring.com> Message-ID: <3924CFD0-FAA5-4153-A436-FC74197E6B84@yarrish.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Aug 3, 2007, at 1:07 PM, tom@yarrish.com wrote: > Hey all, > If anyone is looking for a Unix position, I just found this one at the > place I work at. I don't have many specifics about the job other than > what's in the listing (different group), but if you have questions > about > the company feel free to email me. > > Thanks, > Tom > ------------------------------------------ > Your friend has found job(s) at TAP that you might find interesting. > > Please click the following "View jobs" button to view job(s). > > > > > Best regards. > -- > Linux Users Of Northern Illinois - Technical Discussion > http://luni.org/mailman/listinfo/luni Ok, apparently we need someone at the company too that can send external links instead of buttons that don't work on systems outside of Windows..... Title Senior Unix Engineer Department IS Location Lake Forest - Home Office Position Description The Senior Unix Engineer is responsible for the following: ? Monitors UNIX server environment for problems and corrects issues by following best practices and procedures. ? Provides capacity planning and performance management for server environment. ? Assist clients in troubleshooting production system problems related to applications, as necessary. ? Provides timely project and work status updates to manager and/or clients ? Maintains documentation suitable for enterprise UNIX platform management and support (diagrams, charts, procedures, policies, technical manuals, operations manuals, position papers, etc.). ? Proactively applies patches and hot fixes to systems through approved change control processes. ? Implements system modification to hardware components, operating systems, and layered software according best practices, procedures and policies. ? Provides secure and safe configuration management practices to UNIX server systems. ? Works wit other team members to achieve company and departmental goals in a cooperative and professional manner. ? Stays current on UNIX architecture and technology. Qualifications Bachelor's Degree highly desirable in Computer Science, Information Systems, Software Engineering, Operations, or any discipline closely related to client area served. ? Minimum of 7 years of UNIX experience ? 2+ years experience providing IS support for a large system processing environment (200 servers or more). ? In depth knowledge of HP-UX and Solaris operating systems. ? Hands-on knowledge of storage arrays, NAS and SAN technology. ? In depth knowledge of Veritas file systems and volume manager. ? Strong scripting knowledge (Perl, Python, Korn, Shell, etc.). ? High availability architectures and clustering. ? Networking knowledge: NIS+, HTTP, NFS, DNS, OSI, OSPF, RIP, SMTP, SNMP. ? Hands-on LDAP directory knowledge. ? Working knowledge of client server architecture, applications, and how to support them.. ? UNIX backup and restore approaches. ? Working knowledge of database installs and operations (Oracle preferred). ? Commercial backup/restore technology knowledge (Veritas, Legato, etc.) ? In depth knowledge on vendor support mechanism to obtain external support, software, and patches. Travel Occasional Relocation Assistance No City Lake Forest State Illinois I'll be happy to pass on resumes for anyone.... -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iD8DBQFGs3ndZWzkfeDiTw4RAuBJAJ9MeUBzwftmEkYZez/bkqfHls/7igCfas4R WDn94OqgTa0Q9q3DnC5jFgM= =uYUK -----END PGP SIGNATURE----- From tom at yarrish.com Fri Aug 3 17:32:04 2007 From: tom at yarrish.com (Tom Yarrish) Date: Fri Aug 3 16:32:34 2007 Subject: [LUNI] UNIX position at my company In-Reply-To: <3924CFD0-FAA5-4153-A436-FC74197E6B84@yarrish.com> References: <06cc01c7d5f9$296709a0$190a14ac@prod.brassring.com> <3924CFD0-FAA5-4153-A436-FC74197E6B84@yarrish.com> Message-ID: <9B3DAAC7-A2CA-4644-AC5E-AE1F8CACF78D@yarrish.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Aug 3, 2007, at 1:54 PM, Tom Yarrish wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Aug 3, 2007, at 1:07 PM, tom@yarrish.com wrote: > > > Ok, apparently we need someone at the company too that can send > external links instead of buttons that don't work on systems > outside of Windows..... > And apparently I should ask the hiring manager before posting this stuff.... Sorry, the position has been filled already....they didn't pull the posting. Tom -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iD8DBQFGs57UZWzkfeDiTw4RAtfcAJ4s1WbrCiFII+8HPhQKDKI7yuvjUwCcDJbQ VkiVKrnnjAD4sIOVOTHJJhQ= =wuEN -----END PGP SIGNATURE----- From maney at two14.net Sat Aug 4 02:44:46 2007 From: maney at two14.net (Martin Maney) Date: Sat Aug 4 01:44:59 2007 Subject: [LUNI] oh oh, my raid it having problems In-Reply-To: <46B24075.2040108@codestorm.org> References: <46B22767.9030502@badapple.net> <46B24075.2040108@codestorm.org> Message-ID: <20070804064446.GA11393@furrr.two14.net> On Thu, Aug 02, 2007 at 03:37:09PM -0500, Craig Van Tassle wrote: > Now is as good a time as any. With a degraded array you are at much > higher risk to lose data if the other drive fails. As for powering > down the box that may help it may not. It depends if how long until > you can replace the disk. Considering you dont have a backup. I would > say shut it down to make sure the good drive does not go while you > are away. As sure as possible, anyway. I'm thinking of Google's analysis of many years' worth of failure data (or was it the other disk failure paper from that conference a couple months back?) that found one of the highest correlations was among same-lot drives, such as a casual raid pair very likely will be. Odds of a failure were much higher for soe time following a failure of such a sibling drive. I know I have mirrors like that; the newest & biggest has different vendor drives only by good fortune... -- You arguably have quite a few inalienable rights, but being taken seriously isn't one of them. Neither is being respected. -- Rick Moen From mswier at yahoo.com Sat Aug 4 13:22:22 2007 From: mswier at yahoo.com (Mike Swier) Date: Sat Aug 4 14:22:54 2007 Subject: [LUNI] ANN: NWCLUG's next meeting 8/7/07 Message-ID: <116813.35890.qm@web57007.mail.re3.yahoo.com> Hi, NWCLUG's next meeting will be at Harper College in A238 at 7pm on Tuesday 8/7/07. For (a bit) more info see http://nwclug.org/httpd/html/meetings.html#nextmtg mikie -------------- next part -------------- -- Linux Users Of Northern Illinois - Announcements Mailing List http://luni.org/mailman/listinfo/luni-announce From me at heyjay.com Sun Aug 5 18:28:59 2007 From: me at heyjay.com (Jay Strauss) Date: Sun Aug 5 17:29:06 2007 Subject: [LUNI] oh oh, my raid it having problems In-Reply-To: <46B23FEF.5050707@codestorm.org> References: <46B22680.4060807@codestorm.org> <46B23FEF.5050707@codestorm.org> Message-ID: (top posting for your enjoyment :) I now believe it is not my disk, but instead my IDE controller. I plugged a new drive in and the machine still does not see /dev/hdb, as in: login as: root Using keyboard-interactive authentication. Password: iron:~# fdisk /dev/hdb Unable to open /dev/hdb iron:~# Unless I'm wrong, which is a greater possibility than my being right, I guess I'll have to buy a new machine. thanks Jay On 8/2/07, Craig Van Tassle wrote: > Ugg bottom posters.. > > No it looks like hda is the drive that is working. > > > md0 : active raid1 hda1[0] > Notice it does not say anything about hdb. > > 1951744 blocks [2/1] [U_] > Also notice it says 2/1 That means 2 drives configured and one drive failed. the U_ means that the first drive of the > array is good (Up), and the second one failed. > > As for copying the partision table once you get the new drive installed dd if=/dev/hda of=/dev/hdb bs=512 count=1024. > > That will copy your MBR and your partision table. If you dont have hot-swap drives you have to power down the box. > To read the partision table use fdisk. Man fdisk will help out there. > > Remember IDE is NOT hot-swap! If you don't know if you have hotswap drives then you don't. > > To check for RMA you need to look at the drive. Go to the makers website and look up warranty status. > RMA == Return Material Authorization. > > The SMART checks and badblocks can be done on the current system. > > Man smartctl and man badblocks. That will give ya all the info you need. > > > Jay Strauss wrote: > > > > Hi Craig, thanks for advice. Here is the output: > > > > iron:~# cat /proc/mdstat > > Personalities : [raid1] > > md0 : active raid1 hda1[0] > > 1951744 blocks [2/1] [U_] > > > > md1 : active raid1 hda2[0] > > 115266304 blocks [2/1] [U_] > > > > unused devices: > > > > I'm guessing it's hda1 that is the problem. I don't know how to print > > the partition table. I have 2 disks which I broke into 2 partitions. > > On top of those I built two raid 1 devices. On one of the devices > > (the big one) I built an LVM. > > > > So how do I print the partition table? > > > > Do I power down the box, remove the drive, replace with new, power > > back on and try to sync OR do I do it all while the box is running? > > > > What is RMA how do I check it? Do I stick the failed drive in a > > different computer? > > > > Thanks > > Jay > -- > Linux Users Of Northern Illinois - Technical Discussion > http://luni.org/mailman/listinfo/luni > From craig at codestorm.org Sun Aug 5 18:35:49 2007 From: craig at codestorm.org (Craig Van Tassle) Date: Sun Aug 5 17:36:42 2007 Subject: [LUNI] oh oh, my raid it having problems In-Reply-To: References: <46B22680.4060807@codestorm.org> <46B23FEF.5050707@codestorm.org> Message-ID: <46B650C5.7030506@codestorm.org> Heh Thanks. Check your BIOS and see if it's seen in your bios. Then Check your dmesg. If it is your IDE chain you could get a PCI card to take over for the IDE controler. I recomend http://www.newegg.com/Product/Product.aspx?Item=N82E16816102027 I have been using that card in my server for several years. Also do you have any messages in your syslog about the drive going? Also have you tried moving the drive to the other IDE chain on your mother board, or tried changing the cable? Craig Jay Strauss wrote: > (top posting for your enjoyment :) > > I now believe it is not my disk, but instead my IDE controller. I > plugged a new drive in and the machine still does not see /dev/hdb, as > in: > > login as: root > Using keyboard-interactive authentication. > Password: > iron:~# fdisk /dev/hdb > > Unable to open /dev/hdb > iron:~# > > Unless I'm wrong, which is a greater possibility than my being right, > I guess I'll have to buy a new machine. > > thanks > Jay > > On 8/2/07, Craig Van Tassle wrote: >> Ugg bottom posters.. >> >> No it looks like hda is the drive that is working. >> >>> md0 : active raid1 hda1[0] >> Notice it does not say anything about hdb. >>> 1951744 blocks [2/1] [U_] >> Also notice it says 2/1 That means 2 drives configured and one drive failed. the U_ means that the first drive of the >> array is good (Up), and the second one failed. >> >> As for copying the partision table once you get the new drive installed dd if=/dev/hda of=/dev/hdb bs=512 count=1024. >> >> That will copy your MBR and your partision table. If you dont have hot-swap drives you have to power down the box. >> To read the partision table use fdisk. Man fdisk will help out there. >> >> Remember IDE is NOT hot-swap! If you don't know if you have hotswap drives then you don't. >> >> To check for RMA you need to look at the drive. Go to the makers website and look up warranty status. >> RMA == Return Material Authorization. >> >> The SMART checks and badblocks can be done on the current system. >> >> Man smartctl and man badblocks. That will give ya all the info you need. >> >> >> Jay Strauss wrote: >>> Hi Craig, thanks for advice. Here is the output: >>> >>> iron:~# cat /proc/mdstat >>> Personalities : [raid1] >>> md0 : active raid1 hda1[0] >>> 1951744 blocks [2/1] [U_] >>> >>> md1 : active raid1 hda2[0] >>> 115266304 blocks [2/1] [U_] >>> >>> unused devices: >>> >>> I'm guessing it's hda1 that is the problem. I don't know how to print >>> the partition table. I have 2 disks which I broke into 2 partitions. >>> On top of those I built two raid 1 devices. On one of the devices >>> (the big one) I built an LVM. >>> >>> So how do I print the partition table? >>> >>> Do I power down the box, remove the drive, replace with new, power >>> back on and try to sync OR do I do it all while the box is running? >>> >>> What is RMA how do I check it? Do I stick the failed drive in a >>> different computer? >>> >>> Thanks >>> Jay >> -- >> Linux Users Of Northern Illinois - Technical Discussion >> http://luni.org/mailman/listinfo/luni >> From me at heyjay.com Sun Aug 5 20:30:26 2007 From: me at heyjay.com (Jay Strauss) Date: Sun Aug 5 19:30:30 2007 Subject: [LUNI] oh oh, my raid it having problems In-Reply-To: <46B650C5.7030506@codestorm.org> References: <46B22680.4060807@codestorm.org> <46B23FEF.5050707@codestorm.org> <46B650C5.7030506@codestorm.org> Message-ID: > Check your BIOS and see if it's seen in your bios. It's seen by the BIOS > Then Check your dmesg. Below is my dmesg: for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for /disc md: md0 stopped. md: bind raid1: raid set md0 active with 1 out of 2 mirrors EXT3-fs: INFO: recovery required on readonly filesystem. EXT3-fs: write access will be enabled during recovery. kjournald starting. Commit interval 5 seconds EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. Adding 1048568k swap on /dev/mapper/vg1-swap. Priority:-1 extents:1 EXT3 FS on md0, internal journal Generic RTC Driver v1.07 Capability LSM initialized kjournald starting. Commit interval 5 seconds EXT3 FS on dm-2, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-3, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-1, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-0, internal journal EXT3-fs: mounted filesystem with ordered data mode. Linux agpgart interface v0.100 (c) Dave Jones 8139too Fast Ethernet driver 0.9.27 PCI: Enabling device 0000:00:0e.0 (0104 -> 0107) PCI: Found IRQ 11 for device 0000:00:0e.0 PCI: Sharing IRQ 11 with 0000:00:0c.0 PCI: Sharing IRQ 11 with 0000:01:00.0 eth0: RealTek RTL8139 at 0x1400, 00:e0:29:35:44:23, IRQ 11 eth0: Identified 8139 chip type 'RTL-8139A' es1371: version v0.32 time 13:45:31 Aug 16 2005 PCI: Enabling device 0000:00:0c.0 (0104 -> 0105) PCI: Found IRQ 11 for device 0000:00:0c.0 PCI: Sharing IRQ 11 with 0000:00:0e.0 PCI: Sharing IRQ 11 with 0000:01:00.0 es1371: found chip, vendor id 0x1274 device id 0x1371 revision 0x06 es1371: found es1371 rev 6 at io 0x1040 irq 11 joystick 0x0 ac97_codec: AC97 Audio codec, id: CRY3 (Cirrus Logic CS4297) usbcore: registered new driver usbfs usbcore: registered new driver hub USB Universal Host Controller Interface driver v2.2 PCI: Found IRQ 9 for device 0000:00:07.2 uhci_hcd 0000:00:07.2: Intel Corp. 82371AB/EB/MB PIIX4 USB uhci_hcd 0000:00:07.2: irq 9, io base 00001020 uhci_hcd 0000:00:07.2: new USB bus registered, assigned bus number 1 hub 1-0:1.0: USB hub found hub 1-0:1.0: 2 ports detected agpgart: Detected an Intel 440BX Chipset. agpgart: Maximum main memory to use for agp memory: 96M agpgart: AGP aperture is 64M @ 0xf8000000 cpci_hotplug: CompactPCI Hot Plug Core version: 0.2 pci_hotplug: PCI Hot Plug PCI Core version: 0.5 pciehp: acpi_pciehprm:get_device PCI ROOT HID fail=0x1001 shpchp: acpi_shpchprm:get_device PCI ROOT HID fail=0x1001 input: PC Speaker inserting floppy driver for 2.6.8-2-686 FDC 0 is a post-1991 82077 parport: PnPBIOS parport detected. parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,ECP,DMA] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 NET: Registered protocol family 10 Disabled Privacy Extensions on device c0300140(lo) IPv6 over IPv4 tunneling driver Installing knfsd (copyright (C) 1996 okir@monad.swb.de). eth0: no IPv6 routers present From craig at codestorm.org Sun Aug 5 20:34:22 2007 From: craig at codestorm.org (Craig Van Tassle) Date: Sun Aug 5 19:34:30 2007 Subject: [LUNI] oh oh, my raid it having problems In-Reply-To: References: <46B22680.4060807@codestorm.org> <46B23FEF.5050707@codestorm.org> <46B650C5.7030506@codestorm.org> Message-ID: <46B66C8E.4000700@codestorm.org> It looks like it's a problem with devfs. Why not use udev. That is the current dynamic /dev file system. Jay Strauss wrote: >> Check your BIOS and see if it's seen in your bios. > > It's seen by the BIOS > >> Then Check your dmesg. > > Below is my dmesg: > > for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > parent for /disc > md: md0 stopped. > md: bind > raid1: raid set md0 active with 1 out of 2 mirrors > EXT3-fs: INFO: recovery required on readonly filesystem. > EXT3-fs: write access will be enabled during recovery. > kjournald starting. Commit interval 5 seconds > EXT3-fs: recovery complete. > EXT3-fs: mounted filesystem with ordered data mode. > Adding 1048568k swap on /dev/mapper/vg1-swap. Priority:-1 extents:1 > EXT3 FS on md0, internal journal > Generic RTC Driver v1.07 > Capability LSM initialized > kjournald starting. Commit interval 5 seconds > EXT3 FS on dm-2, internal journal > EXT3-fs: mounted filesystem with ordered data mode. > kjournald starting. Commit interval 5 seconds > EXT3 FS on dm-3, internal journal > EXT3-fs: mounted filesystem with ordered data mode. > kjournald starting. Commit interval 5 seconds > EXT3 FS on dm-1, internal journal > EXT3-fs: mounted filesystem with ordered data mode. > kjournald starting. Commit interval 5 seconds > EXT3 FS on dm-0, internal journal > EXT3-fs: mounted filesystem with ordered data mode. > Linux agpgart interface v0.100 (c) Dave Jones > 8139too Fast Ethernet driver 0.9.27 > PCI: Enabling device 0000:00:0e.0 (0104 -> 0107) > PCI: Found IRQ 11 for device 0000:00:0e.0 > PCI: Sharing IRQ 11 with 0000:00:0c.0 > PCI: Sharing IRQ 11 with 0000:01:00.0 > eth0: RealTek RTL8139 at 0x1400, 00:e0:29:35:44:23, IRQ 11 > eth0: Identified 8139 chip type 'RTL-8139A' > es1371: version v0.32 time 13:45:31 Aug 16 2005 > PCI: Enabling device 0000:00:0c.0 (0104 -> 0105) > PCI: Found IRQ 11 for device 0000:00:0c.0 > PCI: Sharing IRQ 11 with 0000:00:0e.0 > PCI: Sharing IRQ 11 with 0000:01:00.0 > es1371: found chip, vendor id 0x1274 device id 0x1371 revision 0x06 > es1371: found es1371 rev 6 at io 0x1040 irq 11 joystick 0x0 > ac97_codec: AC97 Audio codec, id: CRY3 (Cirrus Logic CS4297) > usbcore: registered new driver usbfs > usbcore: registered new driver hub > USB Universal Host Controller Interface driver v2.2 > PCI: Found IRQ 9 for device 0000:00:07.2 > uhci_hcd 0000:00:07.2: Intel Corp. 82371AB/EB/MB PIIX4 USB > uhci_hcd 0000:00:07.2: irq 9, io base 00001020 > uhci_hcd 0000:00:07.2: new USB bus registered, assigned bus number 1 > hub 1-0:1.0: USB hub found > hub 1-0:1.0: 2 ports detected > agpgart: Detected an Intel 440BX Chipset. > agpgart: Maximum main memory to use for agp memory: 96M > agpgart: AGP aperture is 64M @ 0xf8000000 > cpci_hotplug: CompactPCI Hot Plug Core version: 0.2 > pci_hotplug: PCI Hot Plug PCI Core version: 0.5 > pciehp: acpi_pciehprm:get_device PCI ROOT HID fail=0x1001 > shpchp: acpi_shpchprm:get_device PCI ROOT HID fail=0x1001 > input: PC Speaker > inserting floppy driver for 2.6.8-2-686 > FDC 0 is a post-1991 82077 > parport: PnPBIOS parport detected. > parport0: PC-style at 0x378 (0x778), irq 7, dma 3 > [PCSPP,TRISTATE,COMPAT,ECP,DMA] > eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 > NET: Registered protocol family 10 > Disabled Privacy Extensions on device c0300140(lo) > IPv6 over IPv4 tunneling driver > Installing knfsd (copyright (C) 1996 okir@monad.swb.de). > eth0: no IPv6 routers present From me at heyjay.com Sun Aug 5 20:39:07 2007 From: me at heyjay.com (Jay Strauss) Date: Sun Aug 5 19:39:14 2007 Subject: [LUNI] oh oh, my raid it having problems In-Reply-To: <46B66C8E.4000700@codestorm.org> References: <46B22680.4060807@codestorm.org> <46B23FEF.5050707@codestorm.org> <46B650C5.7030506@codestorm.org> <46B66C8E.4000700@codestorm.org> Message-ID: I have no idea. Its an old version of debian, I don't know how to switch or how that would impact me. On 8/5/07, Craig Van Tassle wrote: > It looks like it's a problem with devfs. Why not use udev. That is the current dynamic /dev file system. > > > Jay Strauss wrote: > >> Check your BIOS and see if it's seen in your bios. > > > > It's seen by the BIOS > > > >> Then Check your dmesg. > > > > Below is my dmesg: > > > > for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to > > parent for /disc > > md: md0 stopped. > > md: bind > > raid1: raid set md0 active with 1 out of 2 mirrors > > EXT3-fs: INFO: recovery required on readonly filesystem. > > EXT3-fs: write access will be enabled during recovery. > > kjournald starting. Commit interval 5 seconds > > EXT3-fs: recovery complete. > > EXT3-fs: mounted filesystem with ordered data mode. > > Adding 1048568k swap on /dev/mapper/vg1-swap. Priority:-1 extents:1 > > EXT3 FS on md0, internal journal > > Generic RTC Driver v1.07 > > Capability LSM initialized > > kjournald starting. Commit interval 5 seconds > > EXT3 FS on dm-2, internal journal > > EXT3-fs: mounted filesystem with ordered data mode. > > kjournald starting. Commit interval 5 seconds > > EXT3 FS on dm-3, internal journal > > EXT3-fs: mounted filesystem with ordered data mode. > > kjournald starting. Commit interval 5 seconds > > EXT3 FS on dm-1, internal journal > > EXT3-fs: mounted filesystem with ordered data mode. > > kjournald starting. Commit interval 5 seconds > > EXT3 FS on dm-0, internal journal > > EXT3-fs: mounted filesystem with ordered data mode. > > Linux agpgart interface v0.100 (c) Dave Jones > > 8139too Fast Ethernet driver 0.9.27 > > PCI: Enabling device 0000:00:0e.0 (0104 -> 0107) > > PCI: Found IRQ 11 for device 0000:00:0e.0 > > PCI: Sharing IRQ 11 with 0000:00:0c.0 > > PCI: Sharing IRQ 11 with 0000:01:00.0 > > eth0: RealTek RTL8139 at 0x1400, 00:e0:29:35:44:23, IRQ 11 > > eth0: Identified 8139 chip type 'RTL-8139A' > > es1371: version v0.32 time 13:45:31 Aug 16 2005 > > PCI: Enabling device 0000:00:0c.0 (0104 -> 0105) > > PCI: Found IRQ 11 for device 0000:00:0c.0 > > PCI: Sharing IRQ 11 with 0000:00:0e.0 > > PCI: Sharing IRQ 11 with 0000:01:00.0 > > es1371: found chip, vendor id 0x1274 device id 0x1371 revision 0x06 > > es1371: found es1371 rev 6 at io 0x1040 irq 11 joystick 0x0 > > ac97_codec: AC97 Audio codec, id: CRY3 (Cirrus Logic CS4297) > > usbcore: registered new driver usbfs > > usbcore: registered new driver hub > > USB Universal Host Controller Interface driver v2.2 > > PCI: Found IRQ 9 for device 0000:00:07.2 > > uhci_hcd 0000:00:07.2: Intel Corp. 82371AB/EB/MB PIIX4 USB > > uhci_hcd 0000:00:07.2: irq 9, io base 00001020 > > uhci_hcd 0000:00:07.2: new USB bus registered, assigned bus number 1 > > hub 1-0:1.0: USB hub found > > hub 1-0:1.0: 2 ports detected > > agpgart: Detected an Intel 440BX Chipset. > > agpgart: Maximum main memory to use for agp memory: 96M > > agpgart: AGP aperture is 64M @ 0xf8000000 > > cpci_hotplug: CompactPCI Hot Plug Core version: 0.2 > > pci_hotplug: PCI Hot Plug PCI Core version: 0.5 > > pciehp: acpi_pciehprm:get_device PCI ROOT HID fail=0x1001 > > shpchp: acpi_shpchprm:get_device PCI ROOT HID fail=0x1001 > > input: PC Speaker > > inserting floppy driver for 2.6.8-2-686 > > FDC 0 is a post-1991 82077 > > parport: PnPBIOS parport detected. > > parport0: PC-style at 0x378 (0x778), irq 7, dma 3 > > [PCSPP,TRISTATE,COMPAT,ECP,DMA] > > eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 > > NET: Registered protocol family 10 > > Disabled Privacy Extensions on device c0300140(lo) > > IPv6 over IPv4 tunneling driver > > Installing knfsd (copyright (C) 1996 okir@monad.swb.de). > > eth0: no IPv6 routers present > -- > Linux Users Of Northern Illinois - Technical Discussion > http://luni.org/mailman/listinfo/luni > From craig at codestorm.org Sun Aug 5 20:44:23 2007 From: craig at codestorm.org (Craig Van Tassle) Date: Sun Aug