The collected works of duck - Page 8

hamei wrote: Seriously, if you guys can make those things get as far as drawing three lines without crashing, I'm impressed. Especially Scribbles

This was drawn with inkscape from nekoware on IRIX, gzipped because I am not allowed to upload .svg. It's the launcher icon to one of my apps.

I have found a LTO-3 drive now, so this is no longer pertinent. If you have a LTO-4 (or greater! but I can't afford a reasonable price for those drive--SCSI or SAS--I might be interested, autoloaders or just rackmounted get bonus points.

Keep in mind though, I have all the backup I need now, so any additional drive would be for future needs.

I just woke up, but I think that the ld argument list is actually reversed, objects you need symbols from should come AFTER the object that needs them.

Libpng has traditional C function names, i.e. png_foo, so those aren't from libpng, they're likely internal to the program (does ld need objects in an archive to be in order?) and basename is found in libc unless they're clobbering the standard names.

Appropriate video?



Check out the rest of the channel as well.

Wow, I totally missed a whole page of inane twaddle (cj & hamei's replies excluded) before trying to be informative. Makes me wonder if jimmer wasn't on to something with exile.

tomvos wrote:

duck wrote: Check out the rest of the channel as well.

Thanks for the link. These guys are quite good at explaining topics. I never thought about the fact that humanity might end by the means of a stamp collector and his overambitious AI.

Quite a few of Brady Haran's channels (he's got videos on lots of subjects) are funny/serious like that. I recommend checking out his other stuff as well; the podcast he does with CGP Gray is a weekly highlight for me.

Happy to help, for what it's worth. Ooh, I'm purple!

mia wrote: didn't they even port ccc to linux?

Yes, ISTR running ccc on FreeBSD in linux emulation at one point

Out of curiosity, do you have any figures on what level of bandwidth the forum takes?

editres?

vishnu wrote: Silly duck

As usual, I point to my sig disclaimer...

hamei wrote: Am I correct that if the application does not specify a color, that's when you get the default blue-meanies look ? So if there is no call to set a color, then there is nothing to find ?

Pretty much, the blue backgrounds come from the app using resources, but there isn't a resource value set. I see you have enabled sgiMode, perhaps you could just blanked *background: #cccccc to make it less blue.

Nevermind this post, it seems I've twiddled with the file in question.

Being the lazy guy I am I just extruded a nurbs tube. Your curves are pretty darn nice though, props.

The power output socket on the back of the Octane is AFAIR for the speakers, I wouldn't try using it for anything else. Also, SGI wouldn't have expected you to sit next to an octane and record any quality audio; That would be done in the sound insulated recording booth, probably to DAT (or perhaps some XLR-ADAT bridge, but I know nothing about studio recording). The mic port on the back is there for videoconferencing and such things.

As far as I know, any mic that has a 3.5mm jack can be used, however I'm pretty sure that a microphone that specifically would not pick up the pleasant-but-loud hum of the green beast does not exist. My suggestion would be to record to something less noisy, in another room.

Why is the noisy octane in the picture in the first place?

Other than answering this post?-) Unifying all my tripod heads to Arca-swiss (a grand total of two). I also just finished moving my on-line photo collection to iSCSI rather than NFS because windows (which runs the raw developer) is shit at NFS. The iSCSI target is a file (on a level 5 raid), mounted RO locally on the host machine via (vnd and fuse and) ntfs-3g so the photos can be fed individually to backup tape rather than pulling the entire filesystem image every time (bacula doesn't do block-level differentials AFAIK). Works great.

My octane started pausing every time I shut it down until I pressed enter and I narrowed it down to the init.d scripts neko_pgsql-8.3.1 installs; even if you're not running the server, it will still try to shut it down using su - $PGUSER -c [...] and the unprivileged user that it also sets up does have a password (*LK*, lock?) causing su to prompt for input.

I would suggest something like



To prevent trying to shut down a server that isn't running at least.

Got bored with the old ones and made some new wallpapers

http://duck.at.shangtai.net/files/pegboard/

Damn it, I'm jealous now.

I sense much confusion in the questioneer. My apologies if this seems patronising, but it seems like these concepts could use a bit of a firming up.

A link is a file that points to the same data as another file in a given file system. The files are exactly the same, except for there being two of them. Since the link and the file are the same, the file cannot be of another filesystem as the link. Sometimes these are called hard links.

A symbolic link (soft as I think you call them) is a file that points to the path of another file or even a directory. This file is NOT the same as the other file, it merely points to the other file. Because of this it can point to anything, even itself (which doesn't make any sense, but there you go). Some operating systems allow wildcards in the path it points to so that the link may dynamically change depending on e.g. who opens it.

Filesystems are the logical structure of files and directories on a storage medium, these may be on a partition, an entire disk or in a file in another filesystem. It's the organisation of data on a medium.

Mounting is the act of attaching the filesystem (wherever it is) to a path in a directory structure. (IRIX does not, as far as I know, support mounting files.)

On unix and unix-like systems, there is only ever one directory structure, and to access files on another filesystem than the root filesystem that was mounted when the system started (nfs, memory filesystem, whatever) you mount these filesystems to a path in the directory structure. The contents of the filesystem the become part of the directory structure until you unmount it.

NFS acts as a filesystem. The server part provides a means for sharing the directory structure and files of a filesystem (not the filesystem itself!) to NFS clients, that in turn have the ability to emulate a filesystem but the structure and data is actually fetched from the server.

Thus you are able to mount these like filesystems but across the network.

NFS doesn't need to know about links, it just exports them like any other file. (hard) links are exactly the same as any other file it exports and thus work just like normal. Symbolic links on the other hand point to a path and thus is dependent on the layout of the client directory structure (if symbolic links are supported).

So a symbolic link that points outside the filesystem that has been exported via NFS, would still work on the client system that mounts it, but you couldn't access the data from the file on the server because the path points to a location in the client's directory structure as the symbolic link is being resolved on the client machine.

I hope that reduces the confusion?

itsvince725 wrote: Chatting on IRC.

As to imply, there's a time when you're not?

The Saint finally returns to heaven. RIP.