[05:15:03] *** peda__ has joined #JNode.org
[05:21:59] *** peda_ has quit IRC
[10:42:07] *** lsantha has joined #JNode.org
[10:45:46] *** lsantha1 has joined #JNode.org
[10:50:11] *** lsantha has quit IRC
[11:36:34] *** lsantha has joined #JNode.org
[11:41:17] *** lsantha1 has quit IRC
[12:56:41] *** lsantha1 has joined #JNode.org
[12:59:37] *** lsantha has quit IRC
[13:00:19] *** lsantha has joined #JNode.org
[13:04:42] *** lsantha1 has quit IRC
[13:29:37] *** galatnm has joined #JNode.org
[14:30:42] *** lsantha1 has joined #JNode.org
[14:35:52] *** lsantha has quit IRC
[14:40:38] *** lsantha has joined #JNode.org
[14:45:17] *** lsantha1 has quit IRC
[14:57:07] *** lsantha1 has joined #JNode.org
[15:02:12] *** lsantha has quit IRC
[15:05:12] *** lsantha has joined #JNode.org
[15:09:40] *** lsantha1 has quit IRC
[15:41:12] *** galatnm has quit IRC
[17:35:48] *** hagar_jnode has joined #JNode.org
[17:39:45] *** hagar_jnode has quit IRC
[20:45:52] *** BenB has joined #JNode.org
[20:46:17] <BenB> lsantha: hey
[20:49:44] <lsantha> hey BenB
[20:49:56] <lsantha> hey peda_
[20:50:32] <lsantha> BenB, peda_ is one of the guys who is using kvm
[20:51:20] <BenB> ah, cool
[20:51:28] <BenB> lsantha: what needs to be done for the test tool?
[20:53:15] * BenB boots jnode 0.2.7 in KVM
[20:54:37] <BenB> lsantha: to manually test whether it works, what shall I do? which grub option, which commands after boot?
[20:57:53] <lsantha> one minute I have to check some stuff
[20:58:04] <lsantha> at the moment we can start manually the mauve tests
[20:58:33] <lsantha> the tool under development can start them automatically over the network
[20:58:58] <lsantha> I think if you make sure that the 'all plugins' option works
[20:59:10] <lsantha> and the network works with it that would be a pretty good start
[20:59:11] * BenB starts via kvm -m 512 -std-vga -net nic,model=rtl8139,macaddr=... -net tap -vnc myhostname:4 -cdrom jnode-x86-0.2.7.iso
[20:59:28] <BenB> ok
[21:00:17] <BenB> lsantha: what would be which grub option?
[21:00:52] <BenB> "all plugins"? "all plugins VESA"? "via dhcp all plugins with MP"? "tests"?
[21:04:12] <BenB> an eth-pci interface comes up, quite some time after I see the console prompt (5-15s).
[21:04:29] <BenB> I can set an ip address and do ifconfig, but I can't ping.
[21:04:41] <BenB> "Exception in command"
[21:04:50] <BenB> is all I get
[21:06:48] <BenB> telnet (client) says "Command class not found". Does that mean "command not found", i.e. telnet does not exist?
[21:07:54] <BenB> I started telnetd per FAQ. when I telnet to it from another machine, I see lots of exceptions on the JNode console. so, at least the network is working to some degree, otherwise jnode would not know that I tried to contact it over the network.
[21:08:22] * BenB installs ubuntu 8.10 server amd64 on the test server.
[21:14:11] <lsantha> grub option: "all plugins" - for now
[21:17:17] <lsantha> you will need some hard disk space under kvm too available for jnode
[21:17:23] <BenB> and how do I start mauve afterwards, and does it set up the network automatically?
[21:17:36] <BenB> lsantha: ok.
[21:18:31] <lsantha> under vmware the LanceDriver is in use
[21:18:43] <lsantha> and this is teh most used nic driver
[21:19:08] <BenB> qemu/kvm also supports that, I'll use that
[21:19:13] <lsantha> is there such option for kvm?
[21:19:14] <lsantha> ok
[21:20:59] <BenB> lsantha: hm, the kvm-qemu man page says that "lance" is suppored, but running kvm, I get:
[21:21:07] <BenB> qemu: Unsupported NIC: lance
[21:21:28] <BenB> so, is rtl 8139 also OK? that seems to work (see above)
[21:21:54] <lsantha> maybe, but needs testing
[21:22:01] <BenB> options per man page are:
[21:22:26] <BenB> Valid values for type are
[21:22:27] <BenB>            "i82551", "i82557b", "i82559er", "ne2k_pci", "ne2k_isa", "pcnet",
[21:22:27] <BenB>            "rtl8139", "e1000", "smc91c111", "lance", "mcf_fec" and "usb"
[21:23:12] <BenB> my runtime kvm -net,model=? says: qemu: Supported PCI NICs: i82551 i82557b i82559er ne2k_pci pcnet rtl8139 e1000 virtio
[21:23:39] <lsantha> and these are the devices supported by JNode: http://www.jnode.org/devices
[21:24:02] * BenB tries ne2k_pci
[21:24:20] <lsantha> I hope something will work
[21:24:39] <BenB> lsantha: so, how do I test "work"?
[21:24:44] <lsantha> I think peda__, said that he managed to set up networking in jnode under kvm
[21:24:56] <BenB> lsantha: see above for what I tried.
[21:25:22] * BenB runs kvm -m 512 -std-vga -no-acpi -no-kvm-irqchip -net nic,model=ne2k_pci,macaddr=
[21:25:36] <lsantha> ok, just try it
[21:25:44] <lsantha> under vm I use bridged networking
[21:25:55] <BenB> lsantha: what shall I try *in* jnode?
[21:26:11] <lsantha> this allows to set up a IP addrss under jnode
[21:26:43] <lsantha> from the domain where the ip of the host interface is
[21:26:51] <BenB> hm, jnode hangs with "waiting for plugins..." with 100% cpu.
[21:27:19] <lsantha> so, under jnode you hsould make sure that everything works what is needed to run the nongui tests
[21:27:48] <lsantha> the two most important things are
[21:27:57] <lsantha> disk access and netaccess
[21:28:00] <lsantha> in this order
[21:29:18] <BenB> lsantha: please tell me *how* exactly to test that
[21:29:24] <lsantha> jnode, is still waiting there?
[21:29:29] <lsantha> ok, for teh network
[21:29:55] <BenB> just checked: with ne2k_pci, it's freezing.
[21:29:59] <BenB> with rtl8139, it boots
[21:30:17] <lsantha> are you sure it's the tetcard?
[21:30:27] <lsantha> the nic ?
[21:31:25] <lsantha> ok, here is an example for manual network configuration
[21:31:48] <BenB> lsantha: yes. I leave all other parameters the same, in with and without acpi etc.. with rtl8139, it boots, with ne2k, it hangs when loading plugins.
[21:32:11] <lsantha> ifconfig eth-pci(0,17,0) 192.168.1.5
[21:32:27] <lsantha> route --add 192.168.1.0 eth-pci(0,17,0)
[21:32:55] <BenB> "device startup took 1230582694094ms: eth-pci(0,3,0)" (with rtl8139). although it's slow (after commandline apparance), it's not *that* slow! :)
[21:33:09] <BenB> ah, I even have to add routes for local nics manually?
[21:33:22] <BenB> usually, ifconfig does that, at least on linux
[21:33:23] <lsantha> route --add 0.0.0.0 eth-pci(0,17,0) 192.168.1.10 (<--- the gateway)
[21:33:56] <lsantha> resolver --add 208.67.222.222   this is the DNS
[21:34:25] <lsantha> the first time, everything is a bit slow
[21:34:33] <lsantha> becaue the bytecode compiles to machine code
[21:34:33] <BenB> lsantha: the first ifconfig gives me "set to null". only the second works. (?!)
[21:34:42] <lsantha> no wories
[21:34:51] <lsantha> that's only a misleading message I think
[21:35:33] <BenB> lsantha: can you file bugs for the things i mention here? (liek the ne2k freeze, the ifconig message, ifconfig should set up routes automatically etc.)?
[21:36:17] <lsantha> that's a good idea, to file bugs for this
[21:36:57] <lsantha> BenB, the best thing is to file a bug as you find it, and with your comments
[21:37:09] <BenB> the first route command you gave me gives me "command arguments don't match syntax"
[21:37:22] <lsantha> then we can review it and see if is s bug or feature request or whatever
[21:37:44] <BenB> ok, but that will take me ages, as 1) I learn to use jnode, 2) i file bugs, 3) i set up the server.
[21:38:03] <BenB> but yeah.
[21:38:43] <lsantha> well, fortunatly you don't have to do it all and not all alone :-)
[21:39:23] <BenB> lsantha: bugs about ifconfig go to "Shell" project?
[21:39:41] <lsantha> this conversation is logged and readable on the website too
[21:40:15] <lsantha> shell or net
[21:41:24] <lsantha> if it's more about the network then the command syntax, parsing etc, then the net is better
[21:41:55] <lsantha> I wonder why the first route command gives an error
[21:42:24] <BenB> "set to null": http://www.jnode.org/node/2839
[21:43:30] <lsantha> that's good enough!
[21:43:52] <lsantha> actaully you can see that only teh message is misleading
[21:44:09] <lsantha> you can check the effect of the command with ifconfig (no args)
[21:44:25] <lsantha> but you are correct, it's a bug
[21:46:04] <BenB> for ifconfig adding routes: http://www.jnode.org/node/2840
[21:46:11] <lsantha> BenB, I can see no reason why "route --add 192.168.1.0 eth-pci(0,17,0)" would give an error
[21:46:31] <lsantha> as long as eth-pci(0,17,0) is a valid device id
[21:47:01] <BenB> I use eth-pci(0,3,0), of  course, because that's what the msg on the console told me, and ifconfig works for that.
[21:47:18] <BenB> and I use other IP addresses
[21:47:45] <lsantha> what version of jnode are you using?
[21:47:46] <BenB> lsantha: did you try this exact command on your jnode?
[21:47:49] <BenB> 0.2.7
[21:48:05] <lsantha> yes, I'm using it all the time
[21:48:18] <lsantha> in a startup script
[21:48:44] <lsantha> in principle it should work in 0.2.7 too
[21:49:08] <lsantha> what exception do you get?
[21:51:34] <BenB> "Command arguments don't match syntax", as said
[21:52:02] <lsantha> hm, sorry
[21:52:20] <lsantha> help route will give you some guiding
[21:54:12] <BenB> NE2000 PCI freeze: http://www.jnode.org/node/2841 - I found that NE2000 ISA works.
[21:54:49] <lsantha> at least you can check if the command you issues matches what the help says
[21:54:51] <BenB> correction: NE2000 ISA produces no hang, but no network card either
[21:56:38] <lsantha> BenB, if the problem with route persists then you better try the svn trunk
[21:57:25] <lsantha> but this command should work in 0.2.7 too
[21:59:16] <lsantha> regarding the nic drivers, apart from lance they werenot tested for quite some time
[21:59:26] <lsantha> so there can be bugs
[22:00:34] <BenB> lsantha: well, a test suite with virtual machine is now a good chance to test them, right?
[22:00:42] <BenB> :)
[22:01:34] <lsantha> SURE! :-)
[22:02:57] <BenB> lsantha: you are correct about bug 2839: "set to null" is an output error only, the iface is configured correctly even the first time.
[22:03:39] <BenB> ah, I see it: if I reconfigure it, it shows "set to (old address)". that's definitely very confusing.
[22:03:53] <lsantha> definitely
[22:04:00] <BenB> it shows the output with state *before* the iface is reconfigured
[22:04:21] *** galatnm has joined #JNode.org
[22:05:25] <lsantha> hi galatnm
[22:07:27] <galatnm> hi levente ^^
[22:07:42] * BenB changed http://www.jnode.org/node/2839 to reflect the findings
[22:07:54] <galatnm> merry christmas
[22:08:18] <lsantha> galatnm, thank you ;-)
[22:08:27] <BenB> lsantha: now, route works. strange.
[22:08:48] <lsantha> ok :-)
[22:08:58] <lsantha> now if all four commands worked
[22:09:07] <lsantha> you can start pinging around
[22:09:15] <lsantha> the local addr in jnode
[22:09:16] <BenB> lsantha: not really - a bug that you can't reproduce is even harder to fix
[22:09:37] <galatnm> Ben you run on virtual machine ?
[22:09:38] <lsantha> the local addr of linux
[22:09:42] <lsantha> the gateway
[22:09:52] <lsantha> yahoo.com and so on
[22:11:01] <BenB> galatnm: yes, KVM
[22:11:13] <galatnm> ah ok, like me ^^
[22:11:33] <lsantha> if networking works which was the second step,  then it's time to do the first step too :-)
[22:12:02] <lsantha> galatnm: http://echelog.matzon.dk/logs/browse/jnode.org/1230505200
[22:12:09] <lsantha> for more info
[22:12:12] <BenB> resolving via DNS is very slow
[22:12:16] <BenB> (5s)
[22:12:30] <BenB> lsantha: I can ping local hosts and yahoo
[22:12:39] <lsantha> great
[22:12:53] <BenB> lsantha: what was the first step?
[22:12:59] <lsantha> the disk
[22:13:17] <lsantha> to have a persistent file system under jnode
[22:13:33] <lsantha> unlike your current in memory file system
[22:14:10] <lsantha> then you can set up the network and other things in startup scripts too
[22:14:48] <BenB> ok, tell me how=
[22:14:49] <BenB> ?
[22:14:54] <lsantha> also saving the mauve results to a disk for later review or comparision is a good idea
[22:14:55] * BenB creates the disk in the meantime
[22:15:08] <lsantha> hm, that's what I don't know exactly in kvm
[22:15:09] <BenB> 100MB shoudl suffice, right?
[22:15:15] <lsantha> that's ok
[22:15:29] <lsantha> you will need a partition on it too
[22:15:32] <BenB> lsantha: I mean what to do in jnode once it has a disk
[22:15:39] <lsantha> and fat32 fs for instance
[22:15:51] <lsantha> if you have all these
[22:15:58] <lsantha> jnode will do the rest for you
[22:16:07] <galatnm> at most ^^
[22:16:38] <lsantha> there is some extra stuff to do to change the system directories
[22:17:00] <lsantha> so that they use the on-disk fs
[22:17:04] <BenB> lsantha: I don't follow... you want me to create the partition and FAT32 formatting outside of jnode?
[22:17:22] <lsantha> yes, since jnode doesn't have these tools yet
[22:17:26] <BenB> ok
[22:17:46] <BenB> lsantha: will do. in the meantime, please tell me how to set stuff up within jnode once I have this done.
[22:17:51] <lsantha> bug if all goes well, soon jnode will have a tool for formatting a hfs+ partition
[22:17:53] <galatnm> formatter doesn't worl anymore ?
[22:18:12] <lsantha> there was no fat32 formatter
[22:18:42] <galatnm> jfat ?
[22:18:45] <lsantha> BenB, I'm affraid you will need the sources too
[22:18:52] <lsantha> jfat has no formatter
[22:19:06] <galatnm> ah ok ^^
[22:19:44] <lsantha> BenB, for the rest you can read this: http://www.jnode.org/node/2812
[22:20:27] <BenB> lsantha: "will need the sources too" how where?
[22:20:29] <lsantha> there I describ how to reconfigure jnode so that it's system folders reside at a custom location
[22:21:07] <lsantha> I think you better start right with the svn trunk
[22:21:18] <lsantha> mno need to go back to the 0.2.7 sources
[22:22:22] <BenB> lsantha: could you just give me an image that is configured for using the first harddrive?
[22:22:25] <BenB> I think that's easier.
[22:22:29] <lsantha> http://sourceforge.net/svn/?group_id=80882
[22:22:43] <lsantha> that for the svn checkout
[22:23:10] <lsantha> hm, mine is using the second right now
[22:23:19] <BenB> lsantha: main problem is:
[22:23:37] <BenB> how do I get the sources into the partition? via jnode or via other OS?
[22:24:07] <lsantha> oh, sorry
[22:24:16] <lsantha> you need the source sonly to create a new image
[22:24:33] <lsantha> the partition and the fs on it will be empty
[22:24:47] <BenB> what do you mean with "new image"? I assume you mean the harddrive image.
[22:24:57] <lsantha> jnode image
[22:25:01] <lsantha> jnode cd image
[22:25:07] <lsantha> for booting jnode
[22:25:21] <BenB> lsantha: please be gentle on me. I know nothing about jnode, I have no idea what you refer to, most of the time.
[22:25:49] <lsantha> hm, sorry BenB, but you figure out so much
[22:26:12] <lsantha> so, but I will explain
[22:26:25] <BenB> yeah, I know a bit or two about computers, but nothing about jnode and your customs and terminology.
[22:26:32] <BenB> ok, so when I build the source, I get an ISO as result?
[22:26:39] <lsantha> yes
[22:26:45] <BenB> and you want me to mount that r/w and modify that?
[22:27:22] <BenB> (Can Linux mount ISO r/w?)
[22:27:41] <lsantha> no
[22:27:45] <lsantha> wait
[22:27:46] <galatnm> you don't need to mount the iso
[22:27:58] <lsantha> how ae you booting jnode with kvm right now?
[22:27:59] <galatnm> get the sources, compile it, and run the iso with kvm
[22:28:25] <lsantha> you should be using an iso image
[22:28:38] <BenB> galatnm: but lsantha wanted me to modify something to use a HD
[22:29:20] <BenB> lsantha: I currently run: kvm -m 512 -std-vga -no-acpi -no-kvm-irqchip -hda jnode.img -net nic,model=rtl8139,macaddr=... -net tap -vnc ... -cdrom jnode-x86-0.2.7.iso
[22:29:27] <lsantha> BenB, actually you can use a HD with the iso image that you are using right now
[22:29:48] <galatnm> juste create a disk image withe qemu-image
[22:29:50] * BenB fetches svn source in the meantime
[22:30:08] <lsantha> but you need a newly built jnode iso image if you want jnode to have the system directories and files on the hard disk
[22:30:12] <galatnm> and next when you run kvm add -hda 'your_image.img' as parameter
[22:30:15] <BenB> galatnm: I did, and partioned and formatted it as FAT32, that's the jnode.img in the command
[22:30:23] <lsantha> and not in their default location which is an imemory partition
[22:30:30] <lsantha> or in meory file system
[22:30:32] <galatnm> ok it's fine then
[22:31:11] <BenB> lsantha: well, it doesn't matter what I want, it matters what you want for your test suite :)
[22:31:36] <lsantha> yep, this would be good for the testsuite too
[22:32:02] <lsantha> because then when jnode boots the network and other things will be configured on startup
[22:32:15] <BenB> lsantha: do you expect the test suite to continuously run within a single booted jnode instance, or reboot all the time, or get rebuilt all the time?
[22:32:35] <lsantha> there are several options
[22:32:37] <BenB> lsantha: because if you want the latest source to be built, there's no point for me to hand-craft an image, right?
[22:34:08] <lsantha> handcrafting the image is done by customizing your build env
[22:34:13] <lsantha> as you will see here
[22:34:21] <BenB> ah, ok.
[22:34:38] <lsantha> http://www.jnode.org/node/2812
[22:35:07] <BenB> yeah, I am looking at it. it starts to get clearer.
[22:35:24] <lsantha> so, if you set it up, you will get the custom jnode env too as the result on every build
[22:36:04] <lsantha> BenB, at svn co, take care to get only the trunk
[22:36:17] <BenB> oh, rats.
[22:36:37] <BenB> so, the command at http://sourceforge.net/svn/?group_id=80882 is wrong
[22:37:02] * BenB starts over again
[22:37:10] <lsantha> http://jnode.svn.sourceforge.net/viewvc/jnode/
[22:37:12] <BenB> boy, the source is huge
[22:37:28] <lsantha> that the contents of jnode
[22:37:32] <lsantha> yep :(
[22:37:55] <lsantha> and will all the tabgs and branches it would be multiplied
[22:38:08] <lsantha> but, I have plans to factor out the openjdk classlib
[22:38:18] <lsantha> that's in the works now
[22:38:32] <BenB> I have a fast line (20MBit/s), and it had not even finished trunk (first branch) after 5 or so minutes.
[22:38:52] <BenB> yeah, no problem, it's one time only. I just need to wait.
[22:39:29] <BenB> in the meantime, I'll see what is on the existing harddrive of the test machine. it's some windows. or I add a new hd.
[22:40:43] <lsantha> ok
[22:41:46] <lsantha> BenB, it would be nice to have a demo jnode server too
[22:42:02] <lsantha> since running tests will not be a constant activity
[22:42:30] <lsantha> maybe in a separate custom jnode instance could run simething like that
[22:42:47] <BenB> lsantha: you mean available to everybody?+
[22:43:02] <lsantha> I mean only a webserver
[22:43:18] <lsantha> like jetty with some demo webapp
[22:43:28] <lsantha> no shell access
[22:43:28] <BenB> I'm not sure i want sth like that on my private network, not even in the dmz
[22:43:47] <BenB> maybe on my public server
[22:44:09] <lsantha> no problem, it was just an idea
[22:44:45] <BenB> it's a nice idea - if security is no problem
[22:45:10] <lsantha> the point of this idea is to demonstrate that jnode can actually do useful work
[22:45:19] <lsantha> like running a not so busy website
[22:45:54] <BenB> yes, it's very good to convince
[22:46:12] <lsantha> the setup would be something like this:
[22:46:34] <lsantha> you have a linux, in it a kvm, in it a jnode, in it a jetty
[22:46:50] <lsantha> an in it a webapp
[22:47:24] <lsantha> you map the jetty port to a public ip
[22:47:48] <lsantha> where people can access it
[22:49:00] <lsantha> where do you think this setup has the weakest point, security -wise
[22:50:39] <lsantha> in principle it should be hard to get to the underlying linux system
[22:51:10] <lsantha> since they shold break jetty, then jnode, to get the kvm, and then out of kvm to linux
[22:51:18] <lsantha> it might be possible but not easy
[22:51:36] <lsantha> and it's a quite unusual stack for teh hackers
[22:55:00] <lsantha> but if there will be more hw available from various people then will can find a place for this too
[23:04:07] <lsantha> BenB, so, I think FabienD, who is working on the test server code will read this and will give more details about how would it work with kvm
[23:05:04] <lsantha> but I think it's good to have these preliminary steps done in any case
[23:05:40] <BenB> ok, ubuntu is installing on the test server.
[23:05:48] <BenB> svn trunk finished checkout
[23:06:30] <lsantha> so, it's going well ...
[23:07:01] <BenB> yes, the Windows on the old machine had nothing important apparently (and wasn't used since 2 years)
[23:07:12] <lsantha> ok
[23:07:43] <lsantha> you might want to check the disk, you created, with the jnode iso you had
[23:07:56] <lsantha> jnode should detect it
[23:08:18] <lsantha> and mount it under /deveces/hdXY
[23:09:07] <lsantha> if that works, you can all create the directory as described in the site and the startup files
[23:10:38] <BenB> lsantha: security: yes, it's possible to break out of virtual machines. VMWare, for example, for a long time explicitly said they don't guaratee that it's not possible. maybe they now do, but there are always holes. a bug in the network stack of jnode is already to gain control of the (virtual) machine, independent of the webapp.
[23:11:03] <BenB> lsantha: also, there can be other weaknesses. e.g. my dsl router assumes that the local network is to be trusted.
[23:11:21] <BenB> (there is a password, but it's really a joke)
[23:11:43] <BenB> s/my/most/
[23:12:35] * BenB continues the ubuntu install, verifies the hdd detection in jnode, and follows 2812
[23:15:38] <lsantha> the security under jnode definetly needs a lot of improvements
[23:16:30] <lsantha> I figure though that since the network stack of jnode is java code certain kind of attacks should be close to impossible
[23:16:46] <lsantha> when jnode will get to a most advanced state
[23:17:01] <lsantha> like attacks based on buffer overruns
[23:18:26] <lsantha> and arrayindexoutofbound exception or outofmemoryexception would need to be the response of jnode to that, instead of some other unpredictable behaviour and gain of control
[23:19:03] <lsantha> I personally expect a higher level of reliablity and safety from jnode than from other systems currently in wide use
[23:19:30] <lsantha> and this is due to the inherent properties of teh java code
[23:20:18] <lsantha> but I agree for Java code under JNode to be as safe and reliable as that we need a bit more work and more focused work on this particualr domain
[23:35:32] <lsantha> BenB, I have to go soon
[23:35:49] <lsantha> any more questions?
[23:40:38] <BenB> lsantha: I am still trying to get ubuntu installed. the silly installer is unable to install the grub boot loader
[23:41:13] <lsantha> oh...
[23:41:30] <BenB> also, a cable was blocking the CPU fan. the CPu reached 100°C (!). I only noticed by coincidence when I browsed through the BIOS.
[23:41:50] <lsantha> oh, man that, was hot
[23:41:56] <BenB> lsantha: yes.... I am still unclear about how the test suite should run.
[23:43:15] <BenB> (the CPU usually has 46°C, and the fan 550 RPM - which is why I had to disable the BIOS CPU fan warning, because the lowest settings is 800 RPM, and it stops booting when it goes lower than that. stupid - the warnign is for exactly situations like this.)
[23:43:30] <BenB> lsantha: if I followed the steps on doc 2812, what then?
[23:44:09] <lsantha> can you boot jnode ?
[23:44:32] <lsantha> after booting
[23:44:51] <lsantha> cd (no arg) should get you to the directory on the hd
[23:45:41] <lsantha> if you are using the new built jnode from trunk
[23:45:54] <BenB> no, as said, I am still installing ubuntu, but you said you have to go soon.
[23:46:06] <BenB> I want to know what to do afterwards.
[23:46:59] <BenB> (well, of course I can boot jnode in KVM on another machine, with the standard iso)
[23:48:17] <lsantha> ok, so you will have the jnode image from trunk
[23:48:48] <BenB> lsantha: JFAT says something about devision by zerp
[23:48:51] <BenB> zero
[23:49:11] <BenB> "no filesystem found for hda0"
[23:49:34] <BenB> ls /devices/ has only sg0 (the CDROM)
[23:49:38] <lsantha> you boot jnode with "JNode tests ..." grub option
[23:50:05] <lsantha> hm
[23:51:05] <lsantha> ok I will continue this now:
[23:52:12] <lsantha> after jnode boots, you go to a persistent dir and use the mauve command
[23:52:37] <lsantha> this commands needs a list of tests to run
[23:52:39] <BenB> i.e. type "mauve" on the command prompt?
[23:52:53] <lsantha> yes with some args
[23:52:53] <BenB> "mauve all"? :)
[23:53:37] <lsantha> I send you a preliminary list of tests that I have here
[23:53:49] <lsantha> mauve testlistfile
[23:54:12] <lsantha> or mauve -o results1 list
[23:54:17] <lsantha> are the usages
[23:54:27] <lsantha> see mauve --help too
[23:58:21] <lsantha> sent
[23:58:59] <lsantha> this will be included in the testing framework later
[23:59:31] <lsantha> or maybe a cleaned up version of it since the current test list is a bit uggly

   December 29, 2008  
< | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | >