[00:37]	<JoeBorn>	hey everybody
[00:58]	<GuestN125>	hows ces goin
[01:07]	<sourcerror>	yeah... I received my OSD today... and my Hack the Duck mug!
[01:10]	<sourcerror>	everything is so nicely done. I wasn't expecting gamma to look this well polished. very cool! I know the dimensions of the OSD were in the spec's but it is amazing it is so small.
[01:26]	<TankC>	its cute
[01:26]	<TankC>	I didn't know they were still selling gamma models
[01:32]	<sourcerror>	Oh. I don't know for sure it is gamma or not. I bought it last Wed.
[01:33]	<TankC>	does it have a black case?
[01:33]	<TankC>	or a clear one?
[01:33]	<sourcerror>	black.
[01:33]	<TankC>	that's the production model, I think
[01:34]	<TankC>	Gamma units are the ones with the clear cases and orange PCBs
[01:34]	<sourcerror>	ah. OK. where is the IR receiver anyway?
[01:34]	<TankC>	built-in
[01:34]	<TankC>	next to the CF slot
[01:35]	<sourcerror>	ah. Just curious in case it is partially blocked. I just opened it 30 minutes ago, but I have some work to do so I can't set it up right now. Argh.
[01:35]	<TankC>	It's fun to play with. I'm actually kind of jealous, they doubled the ram in the production models
[01:35]	<TankC>	I've got a gamma unit
[01:36]	<sourcerror>	so is it 128MB RAM?
[01:36]	<GuestN125>	yes the black one is production
[01:37]	<GuestN125>	it has more ram 64 insted of 32
[01:37]	<sourcerror>	ah. OK.
[01:37]	<sourcerror>	...I've been seeing people on the list talking about 64MB.
[01:38]	<GuestN125>	thats why i know
[01:38]	<sourcerror>	the flash is 16MB, right?
[01:38]	<TankC>	yes
[01:38]	<GuestN125>	have you loaded the .54 firmware?
[01:39]	<GuestN125>	suposivly it doesnt work with the gamma units
[01:39]	<jwu>	the gamma one is cheeper :)
[01:39]	<sourcerror>	no, I have to finish some work for my day job and I know if I plug it in I'll be up all night. I'm going to wait until tomorrow night.
[01:39]	<TankC>	GuestN125, no I haven't.. but that's unsettling news
[01:39]	<sourcerror>	... so I don't even know what firmware I have now.
[01:39]	<GuestN125>	i read it on the forum
[01:41]	<GuestN125>	i have it loaded and am recording right now with no problems except the knowen problem with some sd cards locking up during record but to hd and mem stick and flash drive not a problem
[01:41]	<sourcerror>	GuestN125: nice.
[01:41]	<GuestN125>	i have the black model
[01:42]	<GuestN125>	it even properly syncs audio and video during play back that use to pleg it!
[01:43]	<GuestN125>	it even syncs after fast forwarding for a wile! i still wish they would set up a quick finder! im sure they are coding sumthing like that as we post
[01:43]	<sourcerror>	GuestN125: yea, I've been watching the IRC off and on and it looks like they've been working pretty hard to get those issues fixed in time for CES.
[01:44]	<TankC>	GuestN125, where are you seeing in the fourms that the .54 doesn't work with gamma?
[01:45]	<GuestN125>	man what an inprovment from out of box in october to today its realy getting to be a nice unit i figure some time in march it will be very ready for prime time (wifes or mothers)
[01:47]	<GuestN125>	unless they removed it i will find it for you
[01:48]	<TankC>	Alright
[01:48]	<TankC>	I'm browsing through and I don't see any posts regarding it
[01:50]	<GuestN125>	must have been a joker its not on the forum now! it was posted on the 10th but now its gone and the last post is on the 8th
[01:50]	<TankC>	Ah
[01:50]	* TankC  wipes his brow
[01:51]	<TankC>	Alrighty, I'm off to sleep
[01:51]	<TankC>	g'nite everyone
[01:51]	<sourcerror>	TankC: nite
[01:51]	<GuestN125>	disregard the problem with gamma unit as the post has to be a hoax
[01:52]	<GuestN125>	l8r
[02:10]	<sourcerror>	searching google for news (news.google.com on Neuros OSD came up with a couple nice but short commentaries: www.geek.com ce.seekingalpha.com
[02:11]	<sourcerror>	[re-send so links work] searching google for news (news.google.com on Neuros OSD came up with a couple nice but short commentaries: www.geek.com , ce.seekingalpha.com
[02:42]	<jwu>	what is the mean "came up with a couple"
[02:42]	<jwu>	what is the meaning "came up with a couple"
[02:43]	<sourcerror>	jwu: sorry, I didn't word that very well. The search came back with a couple posts on the OSD
[02:44]	<sourcerror>	... within the last few days. All other articles are older (last year).
[04:23]	<daurn>	hi
[06:17]	<daurn>	wow, nice ascii art:
[06:17]	<daurn>	___,------,
[06:17]	<daurn>	_,--.---. __,--' /
[06:17]	<daurn>	,' _,'_`._ \ _,-' ___,|
[06:17]	<daurn>	;--' `^-. ,' __,---' ||
[06:17]	<daurn>	,' \ ,' _,-' ||
[06:18]	<daurnimator>	w2hoops
[07:17]	<allyourrejects>	TankC: I can't think of any reason your 32mb wouldn't work with the new firmware
[07:17]	<allyourrejects>	TankC: they are still limiting the kernel to 16mb, you would have to get the old codecs that are built for 32mb though
[07:17]	<allyourrejects>	the new ones are built for 64mb
[07:18]	<allyourrejects>	you can find the old ones still in the svn
[07:18]	<allyourrejects>	then again.. it very well could brick it
[07:18]	<allyourrejects>	they've messed with sdram timings and stuff
[17:24]	<JoeBorn>	hi everybody
[17:27]	<cr-tablet>	hi
[17:27]	<cr-tablet>	how was ces?
[17:32]	<JoeBorn>	good, it was a good show for us
[17:32]	<JoeBorn>	now we just need to finish the product.
[17:35]	<cr-tablet>	cool
[17:38]	<Ric>	hello 1 :-)
[17:39]	<Ric>	anyone there?
[17:41]	<Ric>	toc toc
[17:47]	<cr-tablet>	i am here
[18:51]	<daurnimator>	hi
[18:53]	<theolodian>	howdy
[20:03]	<swoag>	hello, anyone here?
[20:04]	<Ycros>	I'm here
[20:04]	<crweb>	swoag: i am here
[20:04]	<swoag>	guess CES drew lots of eyeballs away...
[20:05]	<crweb>	oh?
[20:05]	<swoag>	well, away from here at least, I meant. ;-)
[20:05]	<crweb>	ah, yes. Well, key people weren't around here
[20:06]	<crweb>	been working on my own hacks/software
[20:06]	<swoag>	crweb: any update on the XP samba support part?
[20:06]	<crweb>	mopping server rooms.. etc
[20:06]	<crweb>	swoag: yes. actually.
[20:06]	<crweb>	swoag: you have to have a wins server
[20:06]	<swoag>	on OSD?
[20:06]	<crweb>	no, in general.
[20:07]	<crweb>	you'll find that even in98 machines can't find xp machines very well
[20:07]	<crweb>	that was win98
[20:07]	<jwu>	no OSD has not support XP samba server
[20:08]	<crweb>	jwu: you mean, the osd does not support xp's smb server?
[20:08]	<jwu>	at most time
[20:08]	<crweb>	yeah, I was searching for a solution
[20:09]	<swoag>	the conclusion?
[20:09]	<jwu>	that day before CES ,I and MGAO had asked you.
[20:10]	<swoag>	jwu: crweb knew the problem, let's see his answer.
[20:10]	<crweb>	swoag: I am goign to try to run nmbd on my osd. and see if it picks up the names so the osd can use them
[20:10]	<Ycros>	my samba works fine with XP both ways, on my laptop
[20:11]	<swoag>	ok, please keep us updated, also
[20:11]	<crweb>	Ycros: do you have smbd running?
[20:11]	<Ycros>	yes
[20:11]	<crweb>	thats why
[20:11]	<Ycros>	vista is a problem as well
[20:11]	<swoag>	ah, that is exactly what I was referring to, Ycros said it.
[20:11]	<Ycros>	you'll need samba 4
[20:11]	<crweb>	swoag: I don't think we need the full smbd
[20:11]	<Ycros>	why are you not running smbd?
[20:11]	<crweb>	Ycros: because its just a client
[20:12]	<crweb>	Ycros: what does the OSD have to share?
[20:12]	<crweb>	and if you are sharing
[20:12]	<Ycros>	erm
[20:12]	<Ycros>	doesn't it handle other things
[20:12]	<crweb>	you need all the security tools installed
[20:12]	<Ycros>	related to the client
[20:12]	<swoag>	crweb: maybe OSD can share its USB HDD?
[20:12]	<crweb>	Ycros: no it doesn't
[20:12]	<Ycros>	the client doesn't work very well if you don't have it running
[20:13]	<crweb>	swoag: its not practical. you can plug the usb drive into the computer you are sharing too. and its only usb 12mb/s
[20:13]	<Ycros>	I'd find sharing useful
[20:13]	<crweb>	Ycros: yes, it works fine
[20:13]	* swoag  agreed.
[20:13]	<crweb>	Ycros: your smbd is becoming the network master
[20:13]	<Ycros>	so I can record stuff, and then play it over the network
[20:14]	<crweb>	Ycros: 600k/s isn't fast enough
[20:14]	<swoag>	but that is still one use-case, you record to it, but you don't want to unplug and bring it to your computer room.
[20:14]	<crweb>	you still have to go to the computer room
[20:14]	<crweb>	and wait longer than if you would if you just unplugged it
[20:15]	<crweb>	i'm not saying its not possible
[20:15]	<crweb>	nor that nobody would do it.
[20:15]	<crweb>	but flashrom worthy?
[20:15]	<swoag>	hehe, some people still walks to work although they have a car in their garage. ;-)
[20:15]	<crweb>	Let me see if running nmbd will give us xp browsing
[20:15]	<crweb>	if it does, they can just send video's to the xp machine
[20:15]	<jwu>	wheather support samba master in OSD is depend on JOE
[20:16]	<swoag>	crweb: sure, I agree that is the right approach before we pulling in _lots of_ code to _just_ support XP samba.
[20:16]	<swoag>	jwu: hmm, what does that mean?
[20:17]	<jwu>	I said wheather support samba master in OSD is rest with JOE
[20:17]	<jwu>	I said whether support samba master in OSD is rest with JOE
[20:17]	<crweb>	swoag: this is one of those instances where a nice rootfs.tgz and uImage would come in handy
[20:17]	<crweb>	swoag: i need to boot my osd, rw, NOW
[20:17]	<crweb>	;)
[20:18]	<swoag>	crweb: although I don't know how big the smbd is going to be, it is up to your call, as you know what we
[20:18]	<swoag>	want:
[20:18]	<swoag>	we _need_ samba access to XP. ;-)
[20:19]	<crweb>	anyway you can get me just 1 uImage/rootfs?
[20:20]	<swoag>	crweb: of course. I'll ask the build engineer to send you that one for .54.
[20:20]	<crweb>	thank you
[20:20]	<crweb>	how long are you going to be in here?
[20:20]	<crweb>	i could come up with an answer within the hour probably
[20:21]	<jwu>	crweb: I can send .54 upk to you
[20:21]	<crweb>	jwu: i need seperate rootfs uImage not upk
[20:22]	<jwu>	upk also contain rootfs uimage
[20:22]	<crweb>	yes, but how do you get it out?
[20:22]	<swoag>	jwu: read the google ML, you'll know what crweb was asking for.
[20:23]	<swoag>	anyway, I've got Peter take care of that.
[20:24]	<swoag>	crweb: I'll hang around for about 30 more minutes, just email me if you don't see me here any more.
[20:24]	<crweb>	ok
[20:25]	<crweb>	i need to work on my own stability. I can't remember the last time I had a readily available to boot osd. heh
[20:27]	<swoag>	crweb: speaking of that, I see the need of finalizing the build system ASAP, I've put that on top of my priority list.
[20:27]	<crweb>	we had a big irc discussion about that
[20:27]	<crweb>	Ycros: is building what we all decided we need
[20:28]	<crweb>	swoag: it doesn't involve anything with neuros-bsp
[20:28]	* swoag  has lots of "super priority" though, so top priority naturally got blown off... sigh.
[20:28]	<crweb>	swoag: neuros's toolchain, setup for scratchbox is what we need and are doing
[20:29]	<Ycros>	poking at it. :)
[20:29]	<Ycros>	I'm pressed for time at the moment, so I haven't looked at it much
[20:29]	<crweb>	swoag: I felt strongly that the "build system" and "development enviroment" were being clouded
[20:29]	<crweb>	swoag: what do you mean, when you say build system?
[20:29]	<swoag>	Someone sent me a patch, it still sits in my to-do list.
[20:30]	<crweb>	if you mean building the base system in neuros-bsp (which is called bootstrapping) then that shouldn't be in scratchbox
[20:30]	<swoag>	crweb: I meant the _system_ to build the whole thing hassle free, just svn co, and make all.
[20:30]	<crweb>	thats something entirely different that what others were talking about
[20:30]	<swoag>	oh?
[20:30]	<crweb>	swoag: yes, the problem is, what you consider "building everything" isn't the same as developers
[20:31]	<swoag>	haven't got a chance to read that lengthy ML 'build system' discussion yet.
[20:31]	<crweb>	swoag: developers don't need to build ncooler, or nanox, or even the kernel and busybox
[20:31]	<crweb>	swoag: they just need an enviroment where they can build applications hassle free
[20:32]	<crweb>	having to build the OS, and everything from the ground up, just to develop for the OSD is just silly
[20:32]	<swoag>	what if the application depends on ncooler/nanox?
[20:32]	<crweb>	then you link to the libs
[20:32]	<crweb>	the libs are on the OSD
[20:32]	<crweb>	you don't have to build it, to link to it
[20:33]	<crweb>	unless the developer is working on the kernel, on busybox, or on cooler, they don't need all the cruft
[20:33]	<crweb>	swoag: linux users don't compile their whole linux system everytime they want to write an app. is what im getting at
[20:33]	<crweb>	swoag: so there are 2 seperate processes here
[20:34]	<crweb>	swoag: theres your side where everything you do is system development
[20:34]	<swoag>	well, we removed them out of the bsp area and decided to let people all of them (at least ncooler) from scratch,
[20:34]	<crweb>	swoag: which is excellent
[20:34]	<swoag>	now we are talking the other way around?
[20:34]	<crweb>	no no
[20:34]	<crweb>	whats nice about your setup now and what I didn't understand before:
[20:35]	<crweb>	neuros-bsp is the base OS. it boots, its console, its rootfs, it is the basic of what you need to have a system run
[20:35]	<crweb>	for the most part, it is "constant"
[20:35]	<crweb>	it will be much more constant once development slows down on the base OS
[20:35]	<swoag>	yep
[20:36]	<crweb>	so, why do we as developers have to build it every time we want to use it? all we need out of is is the uImage and the rootfs
[20:36]	<crweb>	so hold onto that thought
[20:36]	<crweb>	next:
[20:36]	<crweb>	basically all your other stuff, ncooler, nmsd, osdmain, etc. Those things are just applications
[20:37]	<crweb>	I don't have to have then to use the osd.
[20:37]	<crweb>	you want me to have them cause you feel they are the basis, but really, they are just applications that run on neuros-bsp
[20:38]	<crweb>	developers don't need to build them. unless they are working on them
[20:38]	<crweb>	you need to build them, cause you do work on them
[20:38]	<crweb>	theres nothing wrong with just putting headers in scratbox and using that to build
[20:39]	<crweb>	since the libs will be on the rootfs anyway
[20:39]	<crweb>	why build them?
[20:40]	<crweb>	for you an me, we want to build them. but people compiling wget, samba, apache, a firefox, etc, they don't need to compile the full system to get their application built
[20:40]	<crweb>	swoag: you are an OS developer, most developers that come to the OSD, are application developers they just want to build their app
[20:40]	<crweb>	am i making sense?
[20:41]	<swoag>	yes, got you.
[20:41]	<crweb>	so, for the full build system. yes good. we could use a system that fully builds. and I think what exists inside of neuros-bsp right now is perfect
[20:42]	<crweb>	it was a very good design.
[20:42]	<crweb>	i didn't think so at first, but now that i understand that neuros-bsp was just meant to give us a base OS, its totally perfect.
[20:42]	<swoag>	so what would you draw the line for "build system" and "development system"?
[20:42]	<swoag>	*where
[20:42]	<crweb>	I personally think that neuros-bsp is the "build system"
[20:43]	<crweb>	everything else is a 3rd party application
[20:43]	<crweb>	and should be built as such
[20:43]	<crweb>	the only thing I see needing changed in neuros-bsp/* is, rootfs generation
[20:43]	<GuestN082>	Hi, am I interrupting anything?
[20:43]	<crweb>	it has to go. gone, rip it out, and just have a premade rootfs, theres no reason to generate it
[20:44]	<crweb>	it causes make file madness just to add 1 file to the rootfs
[20:44]	<crweb>	have neuros-bsp/rootfs be the filesystem, and just use it.
[20:45]	<crweb>	none of us here can come up with a reason asto why make generates the rootfs
[20:46]	<swoag>	"make generates the rootfs", what did you mean by that?
[20:47]	<crweb>	you have a blank rootfs/default/*, and make copies ALL the files into it
[20:47]	<crweb>	the same files over and over
[20:47]	<crweb>	when, you could just have the files already in rootfs/default/*
[20:47]	<swoag>	shouldn't 'make' install to the rootfs and thus "generate" the rootfs?
[20:48]	<crweb>	not like this
[20:48]	<crweb>	think this way. /etc/init.d/telnetd always exists
[20:48]	<crweb>	it is always copied
[20:48]	<crweb>	why not have it be in rootfs/default/etc/init.d already?
[20:49]	<crweb>	why does it have to be copied?
[20:49]	<crweb>	for the most part its a constant filesystem
[20:50]	<swoag>	the reason ( I can think of at this moment):
[20:50]	<crweb>	wait wait
[20:50]	<crweb>	make install makes an image of neuros-bsp/rootfs thats not what i'm talking about
[20:50]	<crweb>	i'm talking make rootfs
[20:50]	<swoag>	waiting...
[20:51]	<crweb>	make rootfs runs the make files that copy stuff in scripts/*
[20:51]	<crweb>	ok, i'm done
[20:51]	<crweb>	heh
[20:51]	<swoag>	;-)
[20:51]	<crweb>	"wait wait" was a vocal expression
[20:52]	<swoag>	make rootfs copies things out of scripts area because
[20:53]	<swoag>	we can not svn the rootfs as it is changing everytime you re-create it. Thus we separate those that will likely
[20:53]	<swoag>	not change (like telnetd) to a different dir.
[20:53]	<crweb>	well, my solution was a little more easy
[20:54]	<crweb>	what we do is, have a base rootfs
[20:54]	<crweb>	2 directories
[20:54]	<crweb>	bsp/rootfs/base and bsp/rootfs/root ( or whatever)
[20:55]	<crweb>	on make rootfs, bsp/rootfs/base/* is copied to bsp/rootfs/root/*
[20:55]	<crweb>	the kernel installs to bsp/rootfs/root/*
[20:55]	<crweb>	busybox installs to bsp/rootfs/root/*
[20:55]	<crweb>	then done
[20:56]	<swoag>	hmm? isn't your /base equal to /scripts?
[20:56]	<crweb>	we just merge base/* into the rootfs that way files such as /etc/network/* doesn't have to be added to make files
[20:56]	<crweb>	no
[20:56]	<crweb>	inorder to have things added to rootfs/defaults/* we ahve to put them in make files
[20:57]	<crweb>	you have targetetc, which is copied to rootfs/defaults/etc/*
[20:57]	<swoag>	well, you don't have to touch make files if you don't want to,
[20:57]	<swoag>	ya.
[20:58]	<crweb>	i'm saying do that with the whole rootfs
[20:58]	<swoag>	isn't that the same idea?
[20:58]	<crweb>	yes, but it only does /etc
[20:58]	<crweb>	say i want to add the file /usr/share/udhcp/default.sh
[20:58]	<crweb>	i have to put it in /scripts
[20:58]	<crweb>	then edit a make file to copy it to /usr/share/udhcp
[20:59]	<crweb>	thats not right. it doesn't have to be generated, its always at /usr/sahre/udhcp
[20:59]	<crweb>	generated = make system copies into place
[20:59]	<crweb>	same with mount.cifs and umount.cifs
[21:00]	<crweb>	and smbclient
[21:00]	<swoag>	got it.
[21:00]	<crweb>	we could just put everything in base/* and copy the base/* put base/usr base/etc base/var etc
[21:01]	<crweb>	to rootfs/default
[21:01]	<crweb>	would make our lives easier when we want to expand the base OS
[21:01]	<crweb>	making dev nodes, install of kernel, install of busybox, stay the same
[21:02]	<crweb>	but base/ has the full file system, and is just copied to rootfs/default/
[21:02]	<swoag>	ok, probably we can svn the base and you don't even need a rootfs.zip?
[21:02]	<crweb>	i'm sorry rephrase that please
[21:03]	<swoag>	never mind, I took that back, that is not good anyway. soory.
[21:03]	<swoag>	*sorry.
[21:03]	<crweb>	what i'd like to see happen is
[21:03]	<crweb>	run ./setup-rootfs
[21:03]	<crweb>	rm -rf /rootfs/default/dev/*
[21:04]	<crweb>	cp -R /rootfs/default/* /rootfs/base/
[21:04]	<crweb>	edit make rootfs
[21:05]	<crweb>	(this is the make rootfs steps as if /rootfs/default/* was empty)
[21:05]	<crweb>	step 1: cp -R /rootfs/base/* /rootfs/default
[21:05]	<crweb>	step 2: create dev nodes in /rootfs/default/dev/*
[21:06]	<crweb>	then done.
[21:06]	<crweb>	kernel make install installes to /rootfs/default
[21:06]	<crweb>	busybox make install installs to /rootfs/default
[21:06]	<crweb>	then make install in neuros-bsp makes the image of /rootfs/default just like it does now
[21:07]	<crweb>	then done.
[21:07]	<swoag>	hmm? when does /base get used?
[21:07]	<crweb>	step 1: cp -R /rootfs/base/* /rootfs/default
[21:08]	<crweb>	that would give us rootfs/default/usr rootfs/default/etc etc
[21:09]	<swoag>	ok, sounds good. not sure there is any other caveats though.
[21:09]	<crweb>	basically base is the directory structure /usr/* /usr/local/* /usr/share/* /etc/* /etc/networking/* /etc/init.d/* etc
[21:09]	<swoag>	like when we re-sync the default back to base?
[21:10]	<crweb>	re-sync?
[21:10]	<crweb>	you mean rebuild?
[21:10]	<swoag>	no, re-sync.
[21:10]	<swoag>	guess you never.
[21:10]	<swoag>	because you'll maintain the base directly.
[21:10]	<crweb>	yeah, sorry those first 3 lines where just for the svn
[21:10]	<crweb>	to create the base
[21:11]	<crweb>	then we just edit base directly. want a file added? put it in base
[21:11]	<crweb>	want it removed, del from base
[21:11]	<crweb>	so, this would be the only thing I would change in neuros-bsp
[21:12]	<crweb>	cause like the guy from ingenient said, the bsp is constant. it is the bootstrap of a OS to make it build
[21:12]	<crweb>	when the OS is stable, the only thing that you guys will be working on, is the applications that run on the bsp
[21:13]	<daurnimator>	wow
[21:13]	<daurnimator>	swoag
[21:13]	<swoag>	ironically, we took this rootfs structure from ingenient. ;-)
[21:13]	<daurnimator>	you're unexpected... to me
[21:13]	<crweb>	yeah
[21:13]	<crweb>	i saw that, i've been working with cowon
[21:13]	<crweb>	this is a much better system that i perpose
[21:14]	<swoag>	good, will make this change when I review the 'build system' thing if I don't see oops if any.
[21:14]	<swoag>	daurnimator: hi.
[21:14]	<crweb>	when you make clean, all you have to do is rm -rf rootfs/default/*
[21:14]	<crweb>	so even going back to a "clean" state is easy
[21:14]	<crweb>	swoag: this is something I already do
[21:15]	<crweb>	i didn't wait :) lol
[21:15]	<swoag>	great, patch/script?
[21:15]	<crweb>	is abosolutely huge
[21:15]	<crweb>	and I'm not that comfortable with svn
[21:15]	<daurnimator>	anything new in last few days/2 weeks?
[21:15]	<crweb>	swoag: between the osdmain network settings, and my own apps, i dunno where to put this
[21:16]	<crweb>	swoag: i'm having a hard time adding the network setting setup to osdmain
[21:16]	<crweb>	swoag: i dont' think im going to beable to produce
[21:16]	<swoag>	crweb: I'll probably just follow what you suggested and clean the bsp up.
[21:16]	<crweb>	swoag: the linux networking is ready to go
[21:17]	<crweb>	swoag: all osdmain has to do is edit /mnt/OSD/networking/interfaces and run /etc/init.d/networking restart
[21:17]	<swoag>	crweb: for the networking setup for osdmain, you probably can command jwu to help, just tell him what you need him to change.
[21:17]	<swoag>	and linux networking part, please submit the patch if any.
[21:18]	<crweb>	they are already in
[21:18]	<swoag>	when was that?
[21:18]	<crweb>	i just can't figure out how to get the make rootfs to put them in.