Re: [osol-discuss] [desktop-discuss] Patches to hald and gvfs to work with USB disks on SunRay
BTW, I did attempt to contact Artem separately during the last week but no response yet Your email must have been caught by a spam filter, sorry about that. Regarding HAL and Sun Ray... Two years ago I've moved to a different group and stopped working on HAL altogether. Some time later, the open source developers of HAL announced its demise and the start of DeviceKit development as a replacement - which rendered any future HAL-based work obsolete. As GNOME is slowly switching from HAL to DeviceKit, some folks at Sun have been planning a DeviceKit port for some time, but it hasn't been a high priority, from what I can tell. Any future work on supporting Sun Ray would have to be based either on DeviceKit or the GNOME I/O layer. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] OpenSolaris and 3G HSDPA USB-modems
Jussi Nieminen wrote: Hi, I'm very interested in switching from Linux to OpenSolaris, but there seems to be only one obstacle that is preventing me from doing the jump. I installed the most recent official OpenSolaris release (released in June, 2009) but I am unable to establish an internet connection because I do not have traditional cable-ethernet any more - now I'm solely using Option ICON 225 USB-stick (it's a 3G HSDPA modem) to connect to the internet and this works great in linux (out-of-the-box in Ubuntu). The problem is - OpenSolaris does not seem to support 3G HSDPA USB modems out-of-the-box. Network manager seems to recognize only traditional ethernet cable connections. I suppose there is a possibility to get this device working with OpenSolaris however. Is there anyone else who is having similar problem? Does anyone know whether the newest developer release (that is going to be released officially in february/march) supports 3G HSDPA USB-modems? It would be so great to be able to make the jump so I hope I can find a way to get this working. Google 'usbsacm' and see this (somewhat outdated) page: http://hub.opensolaris.org/bin/view/Project+wwan/ -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Automount without Gnome?
On 01/13/10 12:17 PM, Johann "Myrkraverk" Oskarsson wrote: rmvolmgr should do the automounting when Nautilus is not present. Make sure this service is online: Thank you. Both hal and rmvolmgr were offline. Something had caused hal to maintenance. Just clearing it removed the issue and now automounting a DVD works -- right now I don't want to unmount the USB disk. I'll be back if the issue persists. Johann PS: I'm using # uname -a SunOS asuka 5.11 snv_115 i86pc i386 i86pc It is possible that hal was in maintenance due to a known crash: http://bugs.opensolaris.org/view_bug.do?bug_id=6850995 This bug was fixed in build 128. -Artm ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Automount without Gnome?
On 01/13/10 11:07 AM, Johann "Myrkraverk" Oskarsson wrote: Hi all, I just switch (or tested, if you will) using fvmw instead fo Gnome. Now my external usb (with UFS) does not automount anymore. Is the automount feature tied to Gnome? Is there a way to get it without Gnome? rmvolmgr should do the automounting when Nautilus is not present. Make sure this service is online: $ svcs rmvolmgr STATE STIMEFMRI online Dec_03 svc:/system/filesystem/rmvolmgr:default What build/release of OpenSolaris are you running? If you insert a CD or DVD, does it get automounted? How about pcfs-formatted USB disks? -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] netperf not working in snv_127 ?
r...@osol:/# netserver -h -bash: /usr/bin/netserver: Invalid argument r...@osol:/# uname -a SunOS osol 5.11 snv_127 sun4v sparc SUNW,T5440 Solaris Any chance you're trying to run an x86 executable on sparc? What does 'file /usr/bin/netserver' say? -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] 1394 pci card recognized, how to capture video
The tool shows the 1394 hub, but `hci1394' as driver pkg search on both av1394 and hci1394 shows them in different packages. (both installed here) Do you know if that driver (hci1394) should be capable of video capture? No, hci1394 is a host controller driver, not a target driver. If you're familiar with USB, hci1394 is functionally similar to ehci or uhci, i.e. they are not for application use, but rather provide generic bus services for other drivers. When you plug a device into a port, the host controller driver will enumerate it and try to find a driver that matches that device. In case of DV camcorders, that driver is av1394. av1394 provides an API for capturing audio/video streams. The API is described in the iec61883(7I) man page. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] 1394 pci card recognized, how to capture video
On 11/ 5/09 01:14 PM, Harry Putnam wrote: I'd forgotten I had a pci ohci 1394 firewire card on this opensolaris box, from before it was an opensolaris box. I'm in a bind with with my video editing box (winXP) have serious trouble with usb and firewire ports. Before just tranferring the card over, I wondered if it is even a remote possibility to capture video on osol box? Can anyone here give some guidance, like would that be a whole lot of tinkering and experimentation or are there known options to do this. If you're really persistent, you can make it work. Google for 'av1394' on opensolaris.org and blogs.sun.com. But I wouldn't recommend it. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] 128 bit technology
Peter Jones wrote: Microsoft has announced No it hasn't. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] core dump on gnome-session (gvfsd?) in snv121...
> BAD TRAP: type=d (#gp General protection) rp=ff00046138f0 addr=0 unix:die+10f () unix:trap+43e () unix:_cmntrap+e6 () fuse:get_filehandle+48f () fuse:fuse_open+5a () genunix:fop_open+bf () genunix:vn_openat+65d () genunix:copen+418 () genunix:openat32+1f () genunix:fsat32+10b () unix:brand_sys_sysenter+1e3 () The kernel should not crash under no circumstance, so don't blame userland apps. Your stack trace looks similar (though not quite the same) to this bug: http://defect.opensolaris.org/bz/show_bug.cgi?id=10447 and is most likely a FUSE bug, in which case the workaround would be not to mount filesystems via FUSE. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] No VirtualBox guest graphical login
Ron Halstead wrote: Guest: OS2009.06 snv_117 (Indiana) Virtual Box: 3.0.0 r49315 Host: SXCE snv_117 (Nevada) VB 3.0 Guest Additions are installed. All services are online, both host and guest. I get a text login prompt. I logged in and checked to see if gdm is running, it is. This has been the case for the last release of VB, OS2008 and SXCE - no graphical login, text only. Any ideas? I ran into a similar issue the other day. X server failed to start (check /var/log/X*). I did Xorg -configure, verified the generated xorg.conf, copied it to /etc/X11, rebooted, and everything's fine now. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] how tolerant is osol of base hardware changes?
do i have to get ahold of an exactly identical mobo, or will osol tolerate a mobo by a different manufacturer, but with the same chipset... or would it refuse to even boot? should i just bear the pain of buying an identical spare mobo, cpu, ram, psu, so that i'm ready should the worst happen? The answer is, as usual, it depends. Even though OpenSolaris is generally pretty tolerant of hardware changes, it won't help _you_ if you happen to be an outlier. For an average user, I would say "don't do it", but it is nothing an experienced system administrator couldn't handle, IMO. The question boils down to knowing what persistent information the OS stores about hardware, and whether it is capable of automatically detecting the change and regenerating that persistent information. Swapping CPUs, RAM and power supplies should be painless, as long as they are compatible hardware-wise. Swapping disks is a well-documented procedure. Swapping the motherboard can potentially change the topology (and therefore the physical device tree), disk controllers and NICs, and might require booting off a LiveCD, mounting your root disk and doing minor surgery on some of the plain-text files. Start with path_to_inst(4) and devfsadm(1M) man pages. Explore the relationship between /devices and /dev namespaces, and where /dev paths are stored persistently (e.g. vfstab). How disks are enumerated by BIOS and GRUB. Booting and mounting also differs between ZFS and UFS. See how device instance numbers are used in network link naming, and where those names are used persistently - unless you're using NWAM, manual reconfiguration may be required. And the mantra that never gets out of fashion: back up your data :) -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] KVM-switch rebooting system
Harry Putnam wrote: Sean Bushby writes: unplugged USB stick and seems ok now? Weird?? From a machine or from a USB port on KVM unit? I'm having mysterious reboots too, and use a kvm. But don't have any usb sticks plugged in anywhere. You're unlikely to receive any response unless you enable crash dumps and provide the panic message and backtrace. http://docs.sun.com/app/docs/doc/817-0403/tscrashdumps-31 -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] SXCE 109 kernel panic
Mar 11 12:48:14 cl1 genunix: [ID 335743 kern.notice] BAD TRAP: type=e (#pf Page fault) rp=ff001fb94870 addr=0 occurred in module "ip" due to a NULL pointer dereference Mar 11 12:48:14 cl1 unix: [ID 10 kern.notice] Mar 11 12:48:14 cl1 genunix: [ID 655072 kern.notice] ff001fb94750 unix:die+dd () Mar 11 12:48:14 cl1 genunix: [ID 655072 kern.notice] ff001fb94860 unix:trap+1752 () Mar 11 12:48:14 cl1 genunix: [ID 655072 kern.notice] ff001fb94870 unix:cmntrap+e9 () Mar 11 12:48:14 cl1 genunix: [ID 655072 kern.notice] ff001fb94a00 ip:ip_tcp_input+6a () Mar 11 12:48:14 cl1 genunix: [ID 655072 kern.notice] ff001fb94bb0 ip:ip_accept_tcp+7cf () Mar 11 12:48:14 cl1 genunix: [ID 655072 kern.notice] ff001fb94c40 ip:squeue_polling_thread+13f () Mar 11 12:48:14 cl1 genunix: [ID 655072 kern.notice] ff001fb94c50 unix:thread_start+8 () Looks very similar to: 6791062 System panic in ip_tcp_input when a rule is added to ipfilter http://bugs.opensolaris.org/view_bug.do?bug_id=6791062 Bug state is "5-Cause Known", which means an engineer is working on a fix. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] eject broken in snv_106, fixed in 107
If you upgrade to build 106 and use eject(1) to eject optical media, it might fail with this message: A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.freedesktop.Hal.Device.Storage" member "Eject" error name "(unset)" destination "org.freedesktop.Hal") The bug is fixed in build 107; workaround is included in the bug report: 6791982 hal.conf policy flaws exposed by DBus 1.2.8 http://bugs.opensolaris.org/view_bug.do?bug_id=6791982 http://lists.freedesktop.org/archives/dbus/2008-December/010769.html DBus was bumped in the Desktop consolidation without testing its dependents in the ON consolidation, and the bug was discovered late. Apologies for the inconvenience. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [desktop-discuss] Patches to hald and gvfs to work with USB disks on SunRay
We have a different architecture in mind for Sun Ray support, see: http://opensolaris.org/os/project/tamarack/proposal.txt It involves changes to HAL, DBus and Sun Ray software, with no changes to GNOME. There is really no way to do this today without modifying DBus, because signals are broadcast and visible to all users, so people on different terminals can potentially eavesdrop on each others' device events. dbus-daemon needs a feature to route signals to users. Sun Ray software also needs modifications to emit disk insert/remove sysevents similar to native Solaris disks. Polling on folders is really not the way want to design the system that can host hundreds of sessions on a single Sun Ray server. With HAL support added, the Sun Ray mounting daemon would also need to be removed. Unfortunately, the work is stalled at the moment due to lack of resources. Perhaps we can put out some prototype code on opensolaris.org. The problem is that Sun Ray software is not open source (yet) afaik, so that part would be missing. -Artem > This is really cool stuff! > I have cc; desktop-discuss as well since the gvfs code are in the > desktop consolidation, so your patch should go there. > the HAL code is in ON, but I don't really know where you may put your > SUNWut changes to. Hope someone from the Sun Ray team will response when > your patches are ready :) > > -Ghe > > Alexander wrote: >> Hello. >> I have made some work to make USB disks work on SunRay terminals. I had to >> modify hald (so it spawns child monitoring every 10 seconds >> /tmp/SUNWut/units//dev/dsk folders and watching for appearing and >> disappearing of sunray usb disks. Also there is special reaction on mnttab >> changes for this events. Some parts of gvfs should be changed - only owners >> of the devices should see them, gvfs should look for new mount points in >> /tmp/SUNWut/mnt and shouldn't try mount SunRay devices itself (SUNWut soft >> will do it). I'm going to test this patches and to improve them (including >> code style)/ >> -- >> This message posted from opensolaris.org >> ___ >> opensolaris-discuss mailing list >> opensolaris-discuss@opensolaris.org >> > > ___ > desktop-discuss mailing list > [EMAIL PROTECTED] ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Is Solaris Real Time OS?
On 09/29/08 13:47, Orvar Korvar wrote: > This pdf talks a lot about Solaris beeing RT. But I thought RT OS were very > specialized, and not used in common OS? You can not have the cake and eat it? There are various degrees of "real-timeness", depending on a number of benchmarks: response, jitter, etc. You can configure a Solaris system to meet the specific needs of your application, e.g. create a processor set dedicated to RT tasks, while directing interrupt handling and TS tasks to other processors, which could produce very deterministic RT performance. Also don't confuse real time OS with embedded OS. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] CD & DVD burning - cdrecord not cutting it for me.
> Why is "cdrecord" chosen for the nautilus burning tool? It just doesn't work > for me, neither loose files nor iso's. "cdrw" works great for CD's and DVD's, > however I have to use "mkisofs" to make an iso first. Currently I have to > use command line to burn stuff. I think at some point, nautilus was modified to use cdrw in case it didn't find cdrecord. I don't know if that's still the case, but you can try moving /usr/bin/cdrecord somewhere else and see what happens. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] How can I tell what kind of blank media is in a CD/DVD recorder before I burn it?
> Why used second class information from HAL while cdrecord gives you complete > and correct information? As always, you are absolutely right, Joerg! -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] How can I tell what kind of blank media is in a CD/DVD recorder before I burn it?
I'm sure there's some way to do it with cdrecord, though I don't know which options to use. You can also parse output of 'cdrw -MV'. A more structured approach (on Nevada) is using HAL: $ for udi in `hal-find-by-capability --capability volume.disc`; do > hal-get-property --udi $udi --key volume.disc.is_blank > hal-get-property --udi $udi --key volume.disc.type > done true dvd_plus_r (same functionality is easy to program in C, Python and Java, using respective DBus bindings). Current media detection code can be flaky on some drives though, see if it works for you. Works fine on my Lite-On LH-18A1P, but has problems with writable DVDs on Sony DRU-830 (bug needs fixing). -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] How can I tell what kind of blank media is in a CD/DVD recorder before I burn it?
> Current media detection code can be flaky on some drives though, see if
> it works for you. Works fine on my Lite-On LH-18A1P, but has problems
> with writable DVDs on Sony DRU-830 (bug needs fixing).
Ah, found the bug. The fix is:
+++ usr/src/cmd/hal/utils/cdutils.c Wed Apr 16 13:01:04 2008
@@ -375,8 +375,9 @@
/*
* According to MMC-5 6.22.3.2, the Disc Information Length
should be
* 32+8*(Number of OPC Tables). Some devices, like U3 sticks,
return 0.
+* Yet some drives can return less than 32. We only need the
first 22.
*/
- if (GET16(&buf[0]) < 32) {
+ if (GET16(&buf[0]) < 22) {
return (B_FALSE);
}
I filed: 6689694 HAL fails to detect blank DVD on certain drives
-Artem
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Re: [osol-discuss] USB drive unusable (with snv_85)
> In the contrary, it is VERY slow on opensolaris. 1. Check if it's in USB 2.0 mode, see question 13: http://www.sun.com/io_technologies/usb/USB-Faq.html#General 2. How much RAM does your system have? 3. Try enabling reduced command set, see question 19: http://www.sun.com/io_technologies/usb/USB-Faq.html#Storage -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] File recovery on Solaris
> I accidently deleted some files on Solaris. > > I'd like to know if is there any way to recover deleted files as I > didn't have a backup for them. :( To the best of my knowledge, there isn't an easy way and no user-friendly tool for this. There is a range of methods that require deep understanding of the system, from The Coroner's Toolkit to grepping /dev/rdsk: depending on how valuable your data is, you could pay for recovery (google for "data recovery") or seek favor from your local unix guru. For the future, if you tend to be rm happy (and even if you don't), consider using ZFS and snapshots, automatic periodic or/and manual occasional. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Storage driver developer
Steve Chang wrote: > I am new to Solaris. I am looking for some information of how to develop a > company's SATA RAID product driver for Solair. Is there any one acn point out > where can I find those documents - compile, driver model, driver update ..? It's quite simple, you'll only need three things: 1. Study the "Writing Device Drivers" book: http://docs.sun.com/app/docs/doc/816-4854 2. Inspect code for similar drivers: http://src.opensolaris.org/source/ 3. Take your time doing 1 & 2. If you still have questions after that, send them to [EMAIL PROTECTED] -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] IP over IEEE 1394
> Please help! How do I configure my firewire adapter to act as network device. > Corresponding thing in linux is possible from eth1394 module. > Is this possible to do in OpenSolaris AFAIK IP over 1394 driver has not been written for OpenSolaris yet. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] ON source incomplete
> Where is the source for libdbus-1.so.3, libdbus-glib-1.so.2 & > libglib-2.0.so.0 http://opensolaris.org/os/project/jds/contributing/building/ describes how to install JDS CBE, pull spec files with SVN and build with pkgbuild/pkgtool. During build, source tarballs are downloaded from the web, unpacked, patched and built. It's easy to find URLs in the spec files. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] common ( Win64/Linux/SNV/UNIX ) filesystem du jour ?
> As long as your media is less than 32GB FAT32 should be ok. You can go much higher than that (even though the Windows GUI might refuse to create > 32GB, it will happily mount them). The main problem with huge FAT32 volumes on Solaris is performance: pcfs loads the entire allocation table into kernel memory and e.g. for a 2TB volume with 32KB clusters it's 256MB. 2GB file size limit is also annoying as heck. And the larger the clusters, the more disk space is wasted at the tail of an average file. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Fatal problem with "new" /usr/lib/rmvolmgr
> - Insert two different media with the same ISO-9660 > Volume name, one after the other into different drives. This will be fixed when this one's fixed: 6503408 HAL mounts multiple unlabeled optical devices under the same physical directory Patches are welcome, -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] "Next" Search in Firefox
W. Wayne Liauh wrote:
> In Firefox, I can press the slash key ("/") to bring up the search box.
> However, there does not appear to be any option to do next (forward or
> backward) search.
I always enable "search as you type" (so no need for slash or ctrl-f)
and then use ctrl-g and shift-ctrl-g to jump forward and backward.
-Artem
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Re: [osol-discuss] opensolaris build 58
> Which particular quality is "build 58" supposed to posses that makes it > required for something? ... and if that something is in the ON consolidation, one possible workaround, I think, would be to retrieve and build the source snapshot from the ON mercurial repository (hg clone -r onnv_58). -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] cdda2wav problem in build 76
This issue will be tracked under: 6633003 USCSICMD sometimes returns EINVAL while ripping audio with cdda2wav -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] cdda2wav problem in build 76
>> D 1.564 07/09/20 11:57:19 >> backout 4046204/6603211: causes 6607084 >> >> D 1.563 07/09/19 19:42:10 >> PSARC/2001/252 Recovering SCSI Sense Data >> 4046204 USCSICMD fails to pass back more than 20 bytes ARQ Sense DATA; > > I would carefully check this diff. Nope, it was backed out the next day, it's not in any build. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] cdda2wav problem in build 76
> It used to work in build 70. > Then somebody introduced a bug in the USCSI code from sd.c I prefer to say "a bug was introduced", subtler grammar with a softer attitude and leading to a more constructive discussion :) sd SCCS history between build 70 and 76: D 1.564 07/09/20 11:57:19 backout 4046204/6603211: causes 6607084 D 1.563 07/09/19 19:42:10 PSARC/2001/252 Recovering SCSI Sense Data 4046204 USCSICMD fails to pass back more than 20 bytes ARQ Sense DATA; D 1.562 07/09/17 23:27:34 <=== first appeared in build 74 PSARC 2007/053 Per-Disk-Device support of non-volatile cache 6462690 sd driver should set SYNC_NV bit when issuing SYNCHRONIZE CACHE to SBC-2 devices D 1.561 07/08/15 10:04:10 <=== first appeared in build 72 PSARC/2007/100 Device Id Extensions 6296435 native sata driver needed for nVIDIA mcp04 and mcp55 controllers D 1.560 07/08/01 15:42:01 <=== first appeared in build 71 6426973 Transport rejected fatal error occurred during Volume Copy/SnapShot and sysReboot test - LPE1100x 6459489 (TD_IOP210) (AM3-QLA2342) I/O fails after the host side cable is pulled. So in case somebody were to use elimination method, *if* the problem is indeed caused by changes in sd, then: - if CD ripping stopped working in 71, the culprit is delta 1.560 - if CD ripping stopped working in 72, the culprit is delta 1.561 - if CD ripping stopped working in 74, the culprit is delta 1.562 From a quick look at the code, I would rate 1.560 and 1.561 as low risk changes, and 1.562 as moderate risk - based on which I'd first verify whether build 72 or 73 are okay and build 74 has the problem. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Using SPARC formated disks on X86?
> The only two Solaris file systems that are endian-neutral are ISO > 9660 (High Sierra), which is read-only, and of course ZFS. UDF and FAT are also endian neutral, aren't they. -artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Using SPARC formated disks on X86?
> Really, Will it be ok with no FDisk partition? and will it be able to > use the SPARC vtoc to find the UFS partition? Not sure, what I would do is boot up a livecd and try mounting various /dev/sd* devices. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Using SPARC formated disks on X86?
>>> I just thought there might be a compatibility mode where the driver >>> or fs did the endian translation. >>> >>> Thanks for the info... I'm off to track down a SPARC machine. As another option, I think Linux UFS implementation has endian translation, 'ufstype' mount option. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Parallels vs Fusion?
> Yes, Fusion exports a network device which Solaris recognizes as pcn0. > Works just fine. It can also emulate e1000g. There used to be performance issues with pcn: http://mail.opensolaris.org/pipermail/opensolaris-discuss/2006-May/016756.html perhaps they've been fixed since then. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Potential New Developer
> What is the business potential for an entrepreneur/developer? Developers (non-zealous kind :) like to use best tools for the job. Solaris is good for some things, not good for others. So if you have a ready idea in mind, that would depend on what that idea is. If your question is open-ended, then the answer is a definite yes, Solaris provides lots of potential. If you're not allergic to marketing talk, here's a small sampler of how Solaris is used by businesses: http://www.sun.com/software/solaris/ (the "use Solaris 10 for" list) http://www.sun.com/software/solaris/success_stories.jsp (sorry for Solaris 10 links, couldn't find similar info on opensolaris.org). If you're familiar with UNIX-like OSes, I guess you could think of [Open]Solaris as the most advanced variation on the theme you can find. [I'm starting to feel this strange urge to wear dockers... I have to stop now.] Give a try to Solaris Express Developer Edition (http://developers.sun.com/sxde/faq.jsp). If you don't want to reformat your disk, it will also run well in virtual environment such as VMware. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Small experiment with "twitter.com" and /var/adm/messages ...
> Hmmm, but the only thing my mobile phone has is the charger connector and > audio out for a mic/headphone. So I guess I'd have to get a new phone for > this. > > Do you know which phones are suitable for the ugen(7D) driver in Solaris? I > presume there are no 3rd party Solaris USB drivers for mobile phones. You can use usbsacm(7D) with most phones and talk to them as if via serial line: http://www.opensolaris.org/os/community/on/flag-days/pages/2006121201/ http://opensolaris.org/os/project/wwan/ -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Java is everywhere !
> So, could someone just kindly tell me, which of my statements above is closer > to the reality? > Or, is the reality a blend of, say, 2 and 3? Yes, the reality is a non-discrete, non-uniform n-cube with n->inf. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Java is everywhere !
> The blog comments say it all...The dislike about the move is *huge*. http://rollerweblogger.org/roller/entry/blogs_on_sun_s_new -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] snv_70 odd behavior
> A smarter player would offer the option of analog, digital+analog, or > digital only playback; in the latter case, it could read in a manner that > allowed >1x, so on a faster than 1x drive, it should be possible to have > concurrent audio/data access that way. Better if the player buffered > a lot, maybe 8MiB or so, on each read, did async I/O to the audio and > drive, and scheduled another read a few seconds before the audio buffer > was due to be empty; the rest of the time, it would just be updating its > offset feedback, or would be available for the GUI event loop to use. > > An audiofs filesystem for audio CD sessions could hide all that, giving > digital-only access to a pseudo directory of files; probably just with > track numbers and a suffix indicating them as raw CD audio files. Getting > fancy, it could give another version of each file, encapsulated in > something common like .WAV format. By being data-only, and handling > buffering and read-ahead, it would ensure performance. By providing > an easy interface, it would ease portability (esp. if it resembled such > audio filesystems on other platforms). No doubt this amount of cleverness would give provide gratification to so many geeks, but the reality is such that a) people are used to not accessing data files while playing audio tracks and if they do they don't expect audio to be smooth; b) CD-A is dead, digital downloads are the only future; c) did I say CD-A is dead. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [Fwd: Re: snv_70 odd behavior]
> Well, lets start up the conversation again. It might be a good time to move the discussion to a more appropriate forum, perhaps desktop-discuss. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [Fwd: Re: snv_70 odd behavior]
> Artem, did you implement your replacement code the way I did propose (by > calling > cdda2wav)? > > If you did not. cdda2wav is full of tricks that allow it to work around > typical bugs (deviations from the CD standard) and to play or extract audio > in as many cases as possible. As we discussed before, that wasn't appropriate in the context of GStreamer plugin, we can't fork a new process every time we need to extract a sector. The idea is that Rhythmbox provides "good enough" basic functionality. Those who want advanced features is free to use cdda2wav and its secret sauce, it ships with Solaris. Let's not go back there. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [Fwd: Re: snv_70 odd behavior]
> Question: with the loss of paranoia support, are we going to see a > release in the future which will provide support for error correction? > with ripping and Soundjuicer, will it be possible to keep ripping even > after an artifact is found in the ripping - aka an error due to a small > scratch, for instance. Someone from our GNOME multimedia group should be able to answer. The new code I was helping Brian with was pretty basic, but it shouldn't be hard to add libparanoia support to it - provided there are no licensing issues. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [Fwd: Re: snv_70 odd behavior]
> The issue is that it doesn't occur with Grip - if it doesn't occur with > grip, which uses cdda2wav, and yet, occurs with Soundjuicer, then > something isn't quite kosher as to how soundjuicer interacts with the cd > drive. > > It occurs with all hybrid cds when ripping with Soundjuicer and yet, > doesn't occur with Grip. Good info. Irene, the first place I'd look is the libcdio replacement Brian Cameron and I coded up in March (he mentioned it in http://www.opensolaris.org/jive/thread.jspa?threadID=37801). -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [Fwd: Re: snv_70 odd behavior]
> We tried with a couple of CDs, and could not reproduce the bug. We > suspect that this bug can only be reproduced with the specific CD. Were your couple of CDs hybrid data and audio? Matthew claims it happens on every hybrid he tried. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] snv_70 odd behavior
> Actually I have submitted a bug - and waiting for it to be fixed. Great. > http://bugs.opensolaris.org/view_bug.do?bug_id=6580744 Hmm, the responsible engineer marked it "Incomplete:Need More Info", which means he won't look at it until someone provides the missing info. Unfortunately the b.o.o crap does not show their comments, which are: - Only one track has this problem? or every track in your cd, or every CD has this bug also? if only exists for one tracker, I guess that there is some data error on your cd's track info. Entry 1 jerry.tan [2007-07-20 03:48] Comments Can you reproduce the bug with other CDs? Thanks Entry 1 irene.huang [2007-07-17 07:31] - I will reopen the bug and try to prod Jerry and Irene - they should try to reproduce it with the CDs they have access to. Otherwise just buy the Ben Harper CD in question. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] snv_70 odd behavior
> Even I'm sure you've put some special meaning in this word, but it's not obvious what it is, given the context of this conversation. > with Data/Audio, it doens't work properly on Solaris - for > instance, one of the cd's I have, it doesn't properly detect the size of > the data side of the cd resulting when ripping the last track there is > either an error or a huge silence after the song has finished. Did you file a bug? Things like these shouldn't be hard to fix, but it will never happen if we don't know about them. Please contribute to the success of OpenSolaris to the extent of your abilities. thanks, -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] snv_70 odd behavior
> Can anyone actually come up with reasons why HAL should not simply mount > all filesystem types found on such a medium, onto different mountpoints > (/media/hsfsmnt, /media/udfsmnt, ... ?) ? I think that's been explained (more than once) earlier: it's not the "least surprise" behavior and will confuse both the inexperienced users and the GUI. We seem to be running in circles. I'm putting this on my todo list and going to stop monitoring this thread now. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Adobe Acrobat for Solaris x86
Hey Aaron, Don't take it personally and remember that Sun engineers are just like any other engineers, human. The Acrobat issue has been a source of frustration for a long time. Different folks are just in different phases of grief (http://en.wikipedia.org/wiki/Kubler-Ross_model) ;) -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] snv_70 odd behavior
> What will happen in 2-3 years when the problem hits again? We'll fix it again. With the combined cost (including this discussion) still less than if we try to architect something out of nothing right now. -Artem. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] snv_70 odd behavior
> But the second approach is based on the wrong asumption that UDF is always > the > best choice. Yes, it's a tradeoff. I know, it's a foreign concept over here, but sometimes things have to be done that way in the competitive, resource-limited environment. If the wrong assumption is consistent with any other major OS on the planet, it's the right assumption in the eyes of a casual user, which is the kind of person the default behavior is designed for. For the expert minority, some handles can be provided. But as I said earlier, if someone is prepared to donate time and resources to pursue the perfect solution, noone can stop them. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] snv_70 odd behavior
> Well ultimately one has to ask the opensource community whether they're > willing to accept the change 'globally' to address the problem. If all > the distros and opensource developers get on board with the change, the > transition might go alot smoother. Nice general statement, but the concrete problem discussed in this thread is not worth it. OTOH if you wish to pursue it, you're welcome to start a discussion on [EMAIL PROTECTED] > One might argue that if one is going to break compatibility, one might > as well fix the laundry list of problems with HAL currently - like when > putting in a device such as a mp3 player with a built in flash and > removable flash chip, it doesn't crash nautilus. Windows 3.1? In UNIX, for one process to crash another it has to be a debugger. If Nautilus crashes, fix Nautilus and stop talking crazy :) -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] snv_70 odd behavior
> As cringe worthy as it sounds - how about an ncurses dialogue that > appears on the screen when the cd is inserted, requesting the end user, > on detection of a hybrid cd/storage, as to which file system driver to > use? That's pretty much the first of the two options I suggestion earlier: > One fix would be to treat these in the same fashion we treat hybrid > data+audio media, i.e. pop a dialog asking for user's preference. A > simpler but less generic fix would be in HAL: if libfstyp returns hsfs, > call it again to check for udfs. The difference it cost. The first option requires changes in the HAL specification (to remove one fs per block device assumption), HAL code and gnome-volume-manager code. A few weeks of work. The second option is about 10 lines of code in HAL. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] snv_70 odd behavior
> This would be a good way to prevent new ideas and progress. Right... Just yesterday I heard Burt Reynolds say in a movie: "Two things we've always had here: our dignity and our illusions." > The questions: do you have a solution for the problem that different > filesystems from a hybrid disk show different files? IMO there is a problem with those who create such media. I wouldn't bend over backwards and change system architecture to accomodate them. But I could live with a few ugly lines of code to work around the problem. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] snv_70 odd behavior
> No, but do you have a better idea for a solution that also works on > systems without GUI and server systems? My idea is to be consistent with others as a default behavior. Add advanced mount options, in some form, as a bonus. > IIRC, you are able to tell MS-WIN what to mount from the GUI. If someone could stick that Vista disc in Linux, OSX and Windows and report back to us, it would be helpful. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] snv_70 odd behavior
> The mountable filesystem types might not all show the same content. > This is why it makes sense to mount everything. Is that what the other three dominating OSes do? -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] snv_70 odd behavior
> And there should definitely be no assumptions that magneto-optical or optical > media can only have UDFS, or some form of ISO-9660 just because these are the > most common formats found on optical media today. You're mistaken, no such assumption is made. If you put UFS on optical media, it will be automounted. The assumption that is made is that there is one filesystem per block device. For sliced or partitioned media, sd(7D) will create separate block devices, so all filesystems on such media will be automounted. The discussed case is different in that multiple filesystems occupy the same block device, with more than one superblock pointing to the same physical blocks on the media. Mounting all of them might technically be safe for read-only media, but I am not sure that it's the right thing from the user experience point of view. I do not believe other OSes do so, and we in Solaris are trying to be consistent. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] snv_70 odd behavior
> # fstyp -v /dev/dsk/c1t0d0s2 | more > hsfs Some DVDs contain two filesystems [1], hence mountable as either hsfs and udfs. fstyp returns the first match, and that's what HAL will use. One fix would be to treat these in the same fashion we treat hybrid data+audio media, i.e. pop a dialog asking for user's preference. A simpler but less generic fix would be in HAL: if libfstyp returns hsfs, call it again to check for udfs [2]. If anyone is willing to contribute code [3], I'll happily sponsor. -Artem [1] http://en.wikipedia.org/wiki/Universal_Disk_Format#Media [2] http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/cmd/hal/probing/volume/probe-volume.c#635 [3] http://opensolaris.org/os/communities/participation/ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] This is not a Solaris helpdesk
> as a result we no longer have any good way to reach those people. Then maybe those people don't want to be reached. > Off-topic posts on *any* mailing list aren't a > good idea, and just because we haven't been good housekeepers in the > past it doesn't follow that we should continue. IMVHO that ship has sailed and if this list is becoming the new comp.unix.solaris, so be it. The founding fathers mights have had a different vision three years ago, but the community is the driving force now. (crawling back under my rock) -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] This is not a Solaris helpdesk
I think it's a bit too late, just go with the flow and leave -discuss alone. Lobbies are always crowded and noisy, and those arriving in Hotel Solaris need to feel welcome in order to want to say. Who cares what version of Solaris they happened to try first, give them a chance to figure stuff out. Gently directing questions to -help or another more appropriate list should be preferred, but if someone decides to answer a questions here and now, I don't see why not. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] How to mount a volume under HAL?
> hate > CDE > GNOME Dunno about others, but I still care about my afterlife. So, for the record, I did not initiate this discussion, that is the truth, I swear to Lucifer. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] How to mount a volume under HAL?
>> From the command line, I can unmount and remount >> an usb flash memory stick using "volrmmount -e >> rmdisk6" >> & "volrmmount -i rmdisk6" > > Ahhh, so that's how it's done! rmmount/rmumount are preferred to volrmmount, less typing too. The only reason volrmmount was not removed together with vold is because CDE uses it and I did not want to touch that pile of history. Once CDE is gone, volrmmount should also go - so don't burn it into your nvram. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] How to mount a volume under HAL?
> But, with `volcheck` not working any more, doesn't that imply that the > backward compatibility is broken? It does sound like a bug. Feel free to fix it, I find it hard to care about floppies anymore :) -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] How to mount a volume under HAL?
> Apparently not. So how do I mount a removable media again, after "unmounting" > it? 'rmmount floppy' 'rmmount -l' or 'eject -l' are generally useful for finding out device nicknames. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] mounting NTFS
> Hello, how do i mount a windows NTFS partition? Thanks a lot! http://www.opensolaris.org/jive/search.jspa?objID=f13&q=ntfs -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] SYN Cookies for Solaris 10
> :D I don't know, maybe useful sometime. > > But, what I'm looking for is underlying things, for example how to know > that feature is on or off and how to bring it back to work. How to > monitor/How to enable again/and also what(which parts of the system) is > responsible for such thing(I'm just curious) In general, what makes something a "feature" is a documented interface. Without one, it's merely an implementation artifact. The grey area in between is where developers and experienced users may hang around, but it's a slippery ground for everyone else. Think cars: steering is a feature because there's a steering wheel; increasing engine displacement is not a feature, even though you can bore pistons and cylinders if you're motivated enough. With that in mind, you'll find stuff here if you really want it: http://docs.sun.com/app/docs/doc/817-0404 http://src.opensolaris.org/source/ -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] An Open Letter to the Solaris Community.
> You don't like reading documentation, or what? What do you think, that > development and/or engineering is a partisan, guerilla coding process? > > Sun documentation has always been one of the biggest incentives to take and > implement Sun technology. What good is an "awesome" technology that there is > just no documentation for? And, I have to ask myself how awesome is it really > if the documentation is nonexistant, boils down to a couple of READMEs or > HOWTOs, or just plain sucks. Awesome products start with (often just as > awesome) documentation. Some of your heroes would tell you, perhaps self-indulgently, if anything, that code is documentation. Never underestimate the power of power. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] An Open Letter to the Solaris Community.
> This is hugely unfair. Sun created the accessibility infrastructure that > is used in GNOME based (and compatible with) the accessibility infrastructure > used by Java. Sun has contributed a great deal back to the GNOME community > and delivers well received value add products on top of GNOME including > Trusted > JDS and APOC. I have nothing but admiration for Sun's desktop developers, but it's hard to care for Sun's desktop strategy. The fearless leadership is just not serious about it. If it was, HCI designers would be revered and given as much credit as kernel hackers; instead they are exposed to a huge cultural dissonance from engineering community and little support from management. If it was, the more aggressive, result-oriented steps would be taken (don't ask me what... bribe key gnome developers? license aqua? dance around the fire naked? half of the answers lie within correctly asked questions). -Artem (the kernel guy who loves his xterms) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] An Open Letter to the Solaris Community.
> Solaris is uniquely situated to make this dream a reality. > With the support of Sun Microsystems, resources Solaris is not very well positioned in the UI competition. Sun, it appears, has consciously chosen not to actively develop a desktop, but to patiently swallow whatever gnome.org is producing. Hire a few more GNOME polishers - and you get another Ubuntu, why bother. That's the real frustrating part: most people see the problems (except those in denial), yet very little can be done about that. Cheerleading only makes it more bitter. -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Opensolaris.org is back up
> geez .. I think I looked at one of them once .. maybe. > > as for residential areas, I have 6000 VA worth of UPS here at my desk ( at > home ) and even my X-Box has a UPS. Never lose a game to power outage! The Warlock: Why did you bring a cop to my command center? John McClane: It's a basement! The Warlock: Who is this man? ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Opensolaris.org is back up
> Wow, I was under the impression it only affected residential areas... I'm guessing netflix, craigslist, typepad and livejournal are not among your favorite sites :) -Artem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] maxtor onetouch III 1TB USB storage snv_b64a
> - USB: I will try to add reduced-cmd-support=true, reboot my system and see > whats going on. Don't forget the semicolon at the end, or it won't take effect. -Artem. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] maxtor onetouch III 1TB USB storage snv_b64a
> - FireWire: I was not able at all to access the disk, the storage is not > detected. That's peculiar. Nothing at all in /var/adm/messages? -Artem. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] maxtor onetouch III 1TB USB storage snv_b64a
> Jul 19 21:16:27 earth usba: [ID 349649 kern.info] Maxtor OneTouch III > 2CAD0L5P > Jul 19 21:16:27 earth genunix: [ID 936769 kern.info] scsa2usb0 is /[EMAIL > PROTECTED],0/pci1043,[EMAIL PROTECTED],1/[EMAIL PROTECTED] > Jul 19 21:16:27 earth genunix: [ID 408114 kern.info] /[EMAIL > PROTECTED],0/pci1043,[EMAIL PROTECTED],1/[EMAIL PROTECTED] (scsa2usb0) online This means the scsa2usb(7D) driver attached to your device. > Jul 19 21:16:27 earth scsi: [ID 193665 kern.info] sd1 at scsa2usb0: target 0 > lun 0 > Jul 19 21:16:27 earth genunix: [ID 936769 kern.info] sd1 is /[EMAIL > PROTECTED],0/pci1043,[EMAIL PROTECTED],1/[EMAIL PROTECTED]/[EMAIL PROTECTED],0 > Jul 19 21:16:28 earth genunix: [ID 408114 kern.info] /[EMAIL > PROTECTED],0/pci1043,[EMAIL PROTECTED],1/[EMAIL PROTECTED]/[EMAIL > PROTECTED],0 (sd1) online > Jul 19 21:18:48 earth scsi: [ID 107833 kern.warning] WARNING: /[EMAIL > PROTECTED],0/pci1043,[EMAIL PROTECTED],1/[EMAIL PROTECTED]/[EMAIL > PROTECTED],0 (sd1): > Jul 19 21:18:48 earth SCSI transport failed: reason 'timeout': retrying > command This mean one or more commands the aforementioned driver sent to the device have timed out. That's why none of the userland programs "see" the device. The problem is in the kernel. When our USB team comes online later today (they are in China) they should be able to make a few suggestions. Perhaps one of those suggestions will be to try the reduced-cmd-support property, see http://www.sun.com/io_technologies/usb/USB-Faq.html#Storage , question 20. You can also try connecting via FireWire interface (after power cycling the disk) and see whether the scsa1394(7D) driver has similar problems. -Artem. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] snv_66 sparc boot fails
Sun Ultra 2 UPA/SBus (2 X UltraSPARC-II 296MHz), No Keyboard 6563746 snv_65, Ultra-2 and E4500 systems unable to install and boot I think. -Artem. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] What *is* OpenSolaris about?
Darren, I feel like you covered the floor with little metal balls - one would slip no matter where he steps. I think that extensive discussions here and on indiana-discuss have established beyond reasonable doubt that opensolaris.org is indeed in a bit of an identity crisis. I would argue, however, that we have exhausted the healing potential of introspection and it is time for some bazaar-style action. I don't see any other viable way of approaching the questions you raised. humbly, -Artem. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: [desktop-discuss] Project Proposal: Fingerprint Authentication
I don't think my design has much overlap. The fingerprint drivers are required whether bioapi is used or not. The fingerprint tool is based on PAM, independent on bioapi. I'll post my detailed design document after the inception review or the opensolaris project page is built. Thanks. PSARC 2007/286 OnePager Fingerprint Authentication inception scheduled 06/20/2007 Given the apparent support of BioAPI by various organizations including NIST and the existence of a bunch of code including PAM support (http://www.bioapi.org/devtools.asp), the issue will inevitably come up during inception review. I think you'll need to provide some detailed analysis and an articulate explanation. -Artem. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: [desktop-discuss] Project Proposal: Fingerprint Authentication
Now it just focuses on the fingerprint. The design is required to be able to easily extended to other biometrics. If the resources in opensolaris are enough, the bioAPI may be considered to be imported to cover all the biometrics. Thanks. So perhaps it should use something more generic than "fpr". +1 on the project. -Artem. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: [desktop-discuss] Project Proposal: Fingerprint Authentication
Is this project limited to just fingerprints? If so, would it make sense to still make the new subsystem easily extensible to future types of biometrics? -Artem. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: valgrind for solaris?
Which new packaging system? You know, the one with multicolor ribbons, a flower-covered basket and a ladybug bell. -Artem. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] valgrind for solaris?
It was probably not a good idea to mix a perfectly fine proposal with a flamebatish personal opinion. Two very different topics. Regarding the former, I see no reason not to include valgrind in the Solaris multiverse, once the new packaging system kicks in. There's more than one way to itch an itch. -Artem. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Project Proposal - (what is/was Indiana)
I am royally confused and not sure if seconds matter anymore, but here's one just in case: +1 There are people willing to invest their time/resources on an OpenSolaris project. Please do and thank you. We desperately need to improve on the walker-to-talkers ratio. (Wouldn't that be great if everyone was allowed just 61 lines to write about a project, but each line over that allowance would have to be repayed with a line of code contributed to that project). -Artem. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [SVOSUG] Project Indiana, get the skinny direct from the source!
Taking a step back, though, I see that the Local User Group concept is showing its age in the tiny digital flat world we live in. It's ever more relevant, a necessary counterpoint to the unidimensional, almost autistic digital universe. I know I am going to drag my asocial butt to Santa Clara this Thursday. Surely some attendees will blog about it and pass on the most interesting bits. No need to bug Alan, he's doing a heck of a job. -Artem. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Project Indiana - let's talk APIs
The general wishlist kinds of discussions can easily get out of hand unless they are part of requirements analysis, which is in turn part of a project. Would probably be a good idea to wait until the Indiana project is announced, gets its own mailing list, goals are clearly stated and boundaries defined. 2c, -Artem. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Sun to make Solaris more Linux like
And we can also make the utilities behave "human friendly" when the output is a terminal and not in ohtercases, although that has the problem of making "ls -l" and "ls -l | less" behave completely differently. Another crazy idea would be to make utilities sensitive to a certain environment variable that defines the default "flavor". It doesn't work out of the box exactly, but it could be made almost OOB if the choice of flavor is offered when the user account is created - and for most newbies that would also be install time, since the new installer will create the default non-root account - and automatically add that environment variable to ~/.profile. -Artem. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Java Mobile FX & Sun's jPhone
I'd like to see some head-to-head comparisons of the jPhone versus the iPhone. "jPhone" seems like a word some irrelevant person came up with. There is no such thing. JavaFX Mobile (http://www.sun.com/software/javafx/mobile/) is a software product that can be used by anyone to build any kind of phone. -Artem. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Re: Sun to make Solaris more Linux like
Oh crappity, Solaris users aren't all "old beards". My bad, I guess I'm just looking at the world through too small a hole. Here in Menlo Park 17 we all wear beards, so I just assumed... But don't tell me not all Mac users are young and hip, and not all Windows users look like Steve Ballmer. This thread reminded me of another true story. An actor is hired to play the gravedigger in Hamlet. "What's it about?" his wife asks. "It's about a gravedigger who meets a prince," he says. -Artem. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] I'm a little sad that this post didn't get any responses. (was) Re: Lets take a moment to reflect on Solaris' strengths.
Before we rush headlong into changing Solaris, I think it is worth at least a moment to reflect on what makes Solaris our choice of OS. Who is trying to change Solaris in a way that removes/affects the good stuff you listed? -Artem. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Sun to make Solaris more Linux like
As for a "better shell experience", my stomach turns when I see people executing `bash`. It's disgusting. `tcsh` is light years ahead in user friendliness and features as compared to `bash`, but rest assured, every user that I saw execute `bash` did so because THEY HAD NO CLUE what `tcsh` is and that it was right there, bundled with Solaris. Wakes the Charlie Kaufmann in me. (Artem takes out the dusty Underwood, replaces the ribbon...) White background. Two men enter the view: a young, stylish man with a smile on his face, an older man with orange crumbs in his beard. YOUNG MAN Hi, I'm a Mac. BEARDED MAN And I'm a Solaris. YOUNG MAN What you been up to last night? BEARDED MAN The usual. Y'know, bfued, rotated backups, resilvered pools. I also discovered that I can swallow three Twinkies at a time. What about you? YOUNG MAN Me and my new boyfriend went to a beach bash! BEARDED MAN You people are ignorant. Bash is disgusting. YOUNG MAN What are you talking about, it was a blast. The lights, the waves... BEARDED MAN What do you need blastwave for?! Don't you know pkgadd(1M) accepts http URLs? Geez, get a clue. YOUNG MAN (Looks ashamed, blushes) BEARDED MAN (Pats the other on the back) Sorry man. Wanna split the last Twix? Please forgive me, -Artem. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Sun to make Solaris more Linux like
One thing to keep in mind is that most folks reading a high volume, general purpose mailing list on opensolaris.org are probably already interested in OpenSolaris. My wild guess is that's not the kind of audience the "making Solaris more Linux like" pitch is targeted at. Also, at least from the limited information in these articles, this doesn't sound like a massive strategic shift. "Embrace some Linux elements", "Sun needs to have a better experience for developer workstations, which means laptops" - nothing we haven't heard already from each other, http://www.opensolaris.org/os/project/jds/documents/desktop_gaps/ or Marc Andreessen. -Artem (speaking for myself) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] blogs.sun.com invaded by marketing ?
Right... and I don't disagree with that... but somehow the idea that "products" start to have their own "blogs" ... sounds... uhm... weired. I think you're reading it too literally. It is common for groups in organizations to be named after the product they are working on. So perhaps when they call the blog "olympus", they really mean "group_of_people_working_on_the_olympus_product_line", it'd just be more typing. You can actually see names of people under each posting. But again, it's really the contents and style of the postings that matter. Nothing prevents group blog contributors from sharing personal views and experiences. If they start mirrorig dump press releases there, then that would be a problem, though not with group blogging as a whole, but with some people not understanding the concept of blogging. -Artem. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] blogs.sun.com invaded by marketing ?
somehow this feels not good that "products" start to have blogs It can be interesting to meet real people behind a product share their views from the other side of the fence. For instance, Microsoft's IEBlog is quite popular. The concept of "group blogs" is okay, though some implementation are good and some are bad. In fact, personal blogs sometimes sound not-so-personal as well. -Artem. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Sparc Dissassembler
Perhaps stating the obvious, but Ultra 5 can be had for $40 on ebay. -Artem. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: to find logical drives in solaris 10
Am I alone in finding this scheme of naming convoluted? Can't this be made simpler? Are there any plans to do so? Many people find it convoluted and someday it should be fixed (or hope that the PC industry catches up on EFI/GPT). Next time Frank Hofmann is in the U.S., buy him a drink and he'll tell you all about it :) Today, Solaris can be installed only on a primary partition. Are there plans to change this? AFAIK it is being worked on. From the ARC caselog http://opensolaris.org/os/community/arc/caselog/2006/ : PSARC 2006/379 Solaris on Extended partition inception held 08/02/2006 It's been a while since the inception, not sure what's the latest status of this project. -Artem. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: to find logical drives in solaris 10
What is the proper command to show other fdisk partitions? fdisk(1M) Further, is there any way to show (& even mount) a "logical" (i.e., extended fdisk) partition? One step back, how do I mount a primary fdisk partition? p1-p4 are primary partitions, p0:N are logical drives. pcfs(7FS) http://faq.solaris-x86.org/9.html#9.10 -Artem. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: GPL in BusinessWeek article
How about we open license-discuss and direct all such discussions there. -Artem. P.S. And when it's abandoned 5 years from now, we give it to the creative kids, and they'd use it for a super-trendy underground club named like "The Sewer", playing robo-electronica and projecting the works of Matthew Barney onto eye-screens %) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Micro-optimizing for the wrong thing - coding efficiencies -vs- processor speeds
It is all about costs. You don't say. One would think it is all about fashion. The number of folks wearing boss of the plains, leather chaps and lariats is dwindling exponentially. -Artem. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] CD burning in Solaris
Most OS vendors are prepared to invest in basic media recording support. Advanced applications is the space where 3rd parties like Roxio and Nero compete. These companies let burner vendors to include dumbed down versions of their software in hopes that users will buy a full version. That's how things are. We also need to distinguish two parts of a media recording solution: the engine and the user interface. Most well-designed applications, regardless of the OS, have the engine separated and "abstracted out". That includes Nero (it is perfectly usable from command line in Windows). The engine defines core features, such as supported media types, drive types, write modes, etc. The user interface provides easy access to the core features, but also provides supplemental features such as file management. Then there's the third, the fun and creative part: authoring, making home movies on DVD, making mix tapes^H^H^H^H^H CDs, designing labels, etc. That, IMO, is the only thing that should differentiate 3rd party solutions and is worth paying money for. It's a real shame that evolution of optical media has been such a mess that simply putting bits on a disc requires a know-how. With respect to OpenSolaris, cdrtools/cdrecord is the engine we prefer to invest in. Missing features (Blu-Ray, HD-DVD, LightScribe, Thingmabob...) should be added to cdrtools, hopefully with the help from the community. The basic GUI we currently ship is Nautilus CD burner, which appears to provide similar experience to Windows explorer (not that it's ideal, but an example of "basic") - again, it is open to improvements, patches are always welcome. It can be tempting to "just rewrite everything", but it is more expensive than incremental improvements and does not guarantee better results. That said, it is always great to see new commercial applications for Solaris. If Nero see a business opportunity, as they apparently see with Linux, they will no doubt pursue it. -Artem. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-mktg] RE: [osol-discuss] Solaris on Intel's Classmate PC?
Just as others have talked about during the "GPL driver debate", if Solaris were suddenly under the GPLv2, it wouldn't magically make thousands of drivers available for instant use. Porting drivers is hard work, and many times its easier to write a new one with well documented specs than to try to port one that is poorly documented, Amen to that, coming from 10 years of driver-writing experience (Solaris, Linux, Windows, VxWorks, ...) -Artem. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
