IRC Logs

Network: freenode Channel: #macosx

	Enter your search terms Submit search form
	Web www.irclog.org

[00:00]<sxzzcxzv> /quit job
[00:00]<fnavzyac>sharkhat: lol
[00:00]<sxzzcxzv> /kill boss
[00:00]<sxzzcxzv>lol
[00:01]<zjzw>lectrick: look for a tool named "play"
[00:01]<fnavzyac>k
[00:01]<zjzw>It uses NSSound to play any file supported by QuickTime I believe.
[00:02]<ajgnscjj>sharkhat: another trick that would be nice: ALAC to FLAC
[00:02]<fnavzyac>aha! http://www.versiontracker.com/dyn/moreinfo/macosx/27808
[00:02]<ajgnscjj>so far I've done that with a perl script that's a bit .. well, it's not stable ;P
[00:03]<ajgnscjj>sometimes it doesn't encode a file and fails to report it completely
[00:05]<yzzjjg>the file or directory ipod/contro/itunes/itunes playlist is corrupt
[00:05]<yzzjjg>How do we fix that?
[00:06]<yzzjjg>OK, is fixed...
[00:06]<rvdrv>Yaroon: I did it
[00:06]<rrfygw>Yaroon: cool :)
[00:06]<rvdrv>it's called "voodoo"
[00:06]<yzzjjg>lol
[00:06]<rvdrv>:P
[00:06]<rvdrv>haha
[00:06]<rrfygw>Yaroon: so how did you fix it ?
[00:09]<2zyrgscy>weird. if your IP address is 1.2.3.4, and you have an entry "1.2.3.4 some_hostname" in /etc/hosts, terminal.app will use that instead of your machine name in PS1
[00:10]<zzzjgp0>thats the point of that file...
[00:10]<zjzw>brianski: as expected
[00:11]<2zyrgscy>rorx: why is that expected?
[00:12]<zjzw>brianski: the system first tries to resolve the IP address that it's assigned, at boot time. If it receives a result, it uses that for the hostname.
[00:12]<zjzw>brianski: so if you're using the IP address it's assigned on boot, in hosts(5), it will use naturally resolve to that name.
[00:13]<2zyrgscy>rorx: seems to me it should always use the entry for 127.0.0.1
[00:13]<2zyrgscy>but then again, it seems mac os x doesn't put the machine name there
[00:13]<zjzw>brianski: nope, it doesn't that's localhost anyhow.
[00:13]<2zyrgscy>so, i'd argue that's two bugs
[00:13]<zjzw>no, not a bug, it's definitely intentional behavior. B)
[00:14]<2zyrgscy>on unix systems typically you have 127.0.0.1 localhost your_name
[00:14]<zjzw>brianski: not necessarily.
[00:14]<2zyrgscy>anyway, not important and easy to "fix"
[00:14]<zjzw>there's nothing that states it needs be that way.
[00:14]<zjzw>127.0.0.1 is really just for localhost.
[00:15]<zjzw>The idea with the OSX behavior is that if you're on a network where you are given a static address that has your name, you don't need to set the hostname, it's auto configured.
[00:17]<rgmygyus>My OSX machines pick up their names from reverse dns
[00:17]<rgmygyus>for example, right now this laptop is panna.local
[00:17]<agp>http://www.ronpatrickstuff.com/
[00:17]<agp>daddy, can i have one?
[00:17]<rgmygyus>When it gets home it'll pick up the rdns entry and change the hostname to panna.galaxy.local
[00:17]<gdj>panna.local == mdns ;o
[00:17]<zjzw>aedinius: exactly, that's the reason for the behavior.
[00:17]<rgmygyus>rorx: Yep
[00:17]<2zyrgscy>ah
[00:17]<rgmygyus>nmo: Aye.
[00:17]<2zyrgscy>i don't want that :)
[00:17]<rgmygyus>What do you want?
[00:20]<zjzw>brianski: if you instead want a static hostname, set the HOSTNAME knob in hostconfig
[00:20]<zjzw>at least, that's the recommended method.
[00:21]<rgmygyus>panna:~ drew$ hostname
[00:21]<rgmygyus>panna.local
[00:21]<rgmygyus>I set "panna" in SysPrefs/Sharing
[00:21]<rgmygyus>That's how that works
[00:22]<zjzw>aedinius: yes, but it only will use the Bonjour name (that's what that's called) if it cannot resolve the IP address. If you define HOSTNAME in hostconfig it uses that value, no matter what.
[00:22]<rgmygyus>Ah.
[00:22]<wjgcgu>yep hostconfig overrides
[00:22]<rgmygyus>I don't like that.
[00:22]<zjzw>wonknu: exactly, a static setting.
[00:23]<rgmygyus>That sucks.
[00:23]<wjgcgu>perhaps (i don't remember) though it isn't recommanded, you can edit /etc/rc*
[00:23]<zjzw>aedinius: yeah, for people using the system as a desktop, the default makes sense.
[00:23]<wjgcgu>somwhere there is probably a hostname command
[00:23]<wjgcgu>in order to set localhost
[00:23]<wjgcgu>and other things
[00:23]<rgmygyus>you can set the hostname with `hostname`
[00:23]<zjzw>wonknu: no reason to if there's a knob for it.
[00:23]<wjgcgu>yep
[00:24]<wjgcgu>yep rorx
[00:24]<wjgcgu>'though it isn't recommanded' :p with my bad english
[00:24]<zjzw>aedinius: It's not persistent though.
[00:24]<rgmygyus>Of course not.
[00:24]<rgmygyus>technically neither is hostconfig
[00:24]<zjzw>oh ok, thought you were thinking it was.
[00:24]<rgmygyus>=]
[00:25]<zjzw>yes it is, on boot that file is used quite a bit. It's similar to BSD's rc.conf(5)
[00:25]<rgmygyus>Wow, my point just flew right by you.
[00:25]<rgmygyus>rc.conf and hostconfig and all that get parsed and then set on boot
[00:26]<zjzw>aedinius: exactly, that's what I mean by "persistent"
[00:26]<rgmygyus>Not what I meant!
[00:27]<zjzw>hmm, I'm not following you I guess.
[00:27]<rgmygyus>Before it gets parsed and taken care of, the hostname isn't set to that.
[00:27]<zjzw>Sure
[00:27]<zjzw>in single user
[00:27]<zjzw>or maybe not even then, I'm not sure.
[00:28]<zjzw>probably is set by single user actually.
[00:29]<zjzw>aedinius: so that's not persistent to you, eh? B)
[00:31]<rgmygyus>Never.
[00:32]<rgmygyus>Change it so the kernel sets it immediately, well, then it's persistent =]
[00:33]<zjzw>oh boy..
[00:33]<rgmygyus>=]
[00:35]<wjgcgu>you can
[00:35]<wjgcgu>with a .kext per example
[00:36]<zjzw>I'd call that a compile time setting, which is a different level, but anyhow.
[00:39]<czugc->anyone here use imagemagick?
[00:39]<rgmygyus>krunk-: sure.
[00:39]<rvdrv>krunk-: aedinius
[00:39]<rgmygyus>krunk-: Don't ask if anyone uses something.

Back to #macosx
Or go to some related logs:
#gentoo
#gentoo
#gentoo
#cisco
#gentoo