Tomahawk Desktop 2.0 Beta1 Released

2009-12-14 Thread Sagara Wijetunga
if the FreeBSD developers could help us to diagnose this issue. Tomahawk Desktop download: http://www.tomahawkcomputers.com/download.html Kind regards Sagara Wijetunga ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd

Re: Avahi compilation help needed

2009-09-11 Thread Sagara Wijetunga
John Baldwin wrote: The avahi ports can still be useful to look at as they contain patches that you will probably need. For example, net/avahi-app has a patch against the configure script in files/patch-configure. In total it seems that net/avahi-app has 21 different patches to the avahi

Avahi compilation help needed

2009-09-10 Thread Sagara Wijetunga
Dear FreeBSD community I'm trying to compile Avahi-0.6.25 (http://avahi.org/) on FreeBSD 7.2 (i386) [in fact, on Tomahawk Desktop]. It develops compilation errors. Is it possible someone to help us by compile Avahi and identify the compilations issues and propose relevant fixes. We use

Re: Avahi compilation help needed

2009-09-10 Thread Sagara Wijetunga
Dimitry Andric wrote: On 2009-09-10 14:06, Sagara Wijetunga wrote: I'm trying to compile Avahi-0.6.25 (http://avahi.org/) on FreeBSD 7.2 (i386) [in fact, on Tomahawk Desktop]. It develops compilation errors. Any reason why you don't use the net/avahi port instead? This will save you

Re: Avahi compilation help needed

2009-09-10 Thread Sagara Wijetunga
Dimitry Andric wrote: On 2009-09-10 16:39, Sagara Wijetunga wrote: Tomahawk Desktop uses FreeBSD sources, it is not based on the FreeBSD distribution. Please contact the Tomahawk Desktop mailing lists then. :) We are Tomahawk Desktop

Now doesn't unmount on time

2009-07-31 Thread Sagara Wijetunga
Hi FreeBSD community We are Tomahawk Desktop, trying to make a working desktop OS based on FreeBSD! We use FreeBSD 7.2 on i386. We earlier discussed two crucial issues regarding a desktop OS: 1.http://lists.freebsd.org/pipermail/freebsd-stable/2009-July/051231.html

Re: SCSI device not created upon a CF card plug in

2009-07-22 Thread Sagara Wijetunga
Milan Obuch writes: On Wednesday 22 July 2009 04:20:27 Sagara Wijetunga wrote: Hi FreeBSD community The SCSI device (eg. da1s1) is not created automatically upon a CF card plug in on an USB multi-card reader on FreeBSD 7.2 (i386) but the SCSI device (eg. da1s1) is created automatically if I

Re: SCSI device not created upon a CF card plug in

2009-07-22 Thread Sagara Wijetunga
Milan Obuch writes: On Wednesday 22 July 2009 08:11:23 Sagara Wijetunga wrote: Milan Obuch writes: On Wednesday 22 July 2009 04:20:27 Sagara Wijetunga wrote: Hi FreeBSD community The SCSI device (eg. da1s1) is not created automatically upon a CF card plug in on an USB multi-card reader

Re: SCSI device not created upon a CF card plug in

2009-07-22 Thread Sagara Wijetunga
Ivan Voras writes: Milan Obuch wrote: On Wednesday 22 July 2009 09:38:50 Ivan Voras wrote: [ snip ] After the CF card is plugged in: $ ls -l /dev/ | grep da crw-r- 1 rootoperator0, 105 Jul 22 13:18 da0 crw-r- 1 rootoperator0, 106 Jul 22 13:18 da1 crw-r- 1

Re: SCSI device not created upon a CF card plug in

2009-07-22 Thread Sagara Wijetunga
Pete French writes: I have earlier posted my tests with Linux. All tests were done with same CF cards and the very same multi-card reader on the same computer. They work on Linux. That is, nothing wrong with the multi-card reader, it does it's job of signaling well. What makes you sure

Re: SCSI device not created upon a CF card plug in

2009-07-22 Thread Sagara Wijetunga
Eugene Grosbein writes: On Wed, Jul 22, 2009 at 10:20:27AM +0800, Sagara Wijetunga wrote: My questions in this regards are: 1. Is this an error/bug in FreeBSD 7.2? This is regression from pre-5.x days. In 4.x and earlier, you can have static device nodes and access them just fine. 2

Re: SCSI device not created upon a CF card plug in

2009-07-22 Thread Sagara Wijetunga
Eugene Grosbein writes: On Thu, Jul 23, 2009 at 08:13:38AM +0800, Sagara Wijetunga wrote: Hi Eugene, thanks for the reply. The issue we discussed is about internal multi-card readers. For internal multi-card readers, the umassX created at boot time. If there is media inside at boot time

SCSI device not created upon a CF card plug in

2009-07-21 Thread Sagara Wijetunga
Hi FreeBSD community The SCSI device (eg. da1s1) is not created automatically upon a CF card plug in on an USB multi-card reader on FreeBSD 7.2 (i386) but the SCSI device (eg. da1s1) is created automatically if I reboot the computer while the CF card is plug in. Here are detail: $

FreeBSD 7.2 USB stack info needed

2009-07-13 Thread Sagara Wijetunga
Hi FreeBSD community After an USB thumb drive id pluged in, the devd prints following line: +umass0 vendor=0x0781 product=0x5406 devclass=0x00 devsubclass=0x00 release=0x0200 sernum=087663165D8139E6 intclass=0x08 intsubclass=0x06 at port=0 interface=0 vendor=0x0781 product=0x5406

Re: FreeBSD 7.2 USB stack info needed

2009-07-13 Thread Sagara Wijetunga
Sagara Wijetunga writes: Hi FreeBSD community After an USB thumb drive id pluged in, the devd prints following line: +umass0 vendor=0x0781 product=0x5406 devclass=0x00 devsubclass=0x00 release=0x0200 sernum=087663165D8139E6 intclass=0x08 intsubclass=0x06 at port=0 interface=0 vendor

Re: FreeBSD 8.0-BETA1 Available

2009-07-07 Thread Sagara Wijetunga
Ken Smith writes: The first public test build of the FreeBSD 8.0-RELEASE test cycle is now available, 8.0-BETA1. Through the next week or so more information about the release will be posted but here is the current target schedule for the other 'major events': BETA2: July 13, 2009

Re: FreeBSD child process die for root [SOLVED]

2009-07-04 Thread Sagara Wijetunga
Dear all The issue was solved. It was a our side mistake. On a modification we made to libutils, we execute following line without checking whether the group is empty or not. In our case, it was empty, therefore, crashes: running = strdup(*(grp-gr_mem)); So that now login, su

Re: FreeBSD child process die for root

2009-07-03 Thread Sagara Wijetunga
Carlos A. M. dos Santos writes: Try to debug the login program: (become root) # cd /usr/src/usr.bin/login # make clean # make CFLAGS=-g # gdb /usr/obj/usr/src/usr.bin/login/login (supposing that sagara is your user name) #run sagara (fill-in the password name, if requested) If the signal

Re: FreeBSD child process die for root

2009-07-03 Thread Sagara Wijetunga
Roland Smith writes: Is there anything else from su in the logfiles? That might help narrow down where it crashes. No, other than the same “uid 0: exited on signal 11” for login, su and cron. What we see is after the fork, child process run for some time and crashes. Are you using the

Re: FreeBSD child process die for root

2009-07-02 Thread Sagara Wijetunga
Roland Smith writes: I have tested with bash, sh and csh. It seems the child process forked simply die irrespective of the shell. Ok, so it's probably not a shell problem There is no change in the dot files for root: [r...@tds sagara]# diff /root/.cshrc /usr/src/etc/root/dot.cshrc

FreeBSD child process die for root

2009-07-01 Thread Sagara Wijetunga
Hi I'm Sagara Wijetunga from Tomahawk Computers from Singapore, makers of the Tomahawk Desktop, a FreeBSD based desktop operating system (http://www.tomahawkcomputers.com/) which is free for personal use. Ever since we upgraded our Tomahawk Core OS to the FreeBSD 7.2 sources, we experienced

Re: FreeBSD child process die for root

2009-07-01 Thread Sagara Wijetunga
Roland Smith writes: On Wed, Jul 01, 2009 at 02:04:09AM -0500, Sagara Wijetunga wrote: Hi I'm Sagara Wijetunga from Tomahawk Computers from Singapore, makers of the Tomahawk Desktop, a FreeBSD based desktop operating system (http://www.tomahawkcomputers.com/) which is free for personal use