@# Quotes DB     useful, funny, interesting





Google
 
Web www.quotesdb.info
Undernet  |  EFnet  |  Quakenet  |  Freenode  |  Dalnet  |  Ircnet  |  Galaxynet


Comments:

<0> can anyone recommend a simple but good benchmarking package? for (temperatures and fans)
<1> symon?
<1> while sleep 60 ;do sysctl hw.sensors ;done? depends on your needs I guess..
<2> anyone knowledgeable in traffic prioritization? I was wondering if you could look at my pf.conf. thank you
<3> is there any .chf reader that runs on openbsd?
<4> good morning
<4> can you use openbsd's fsck on solaris ufs slices?
<5> no



<4> that's what I thought
<4> have to find another way then to rescue that broken slice
<6> mxpx-: fsck is not going to fix a broken disklabel
<4> tobiasu: yes, but I'm running out of options :)
<4> the disksuite metadb was installed on the wrong slice
<4> and there is no backup yet since it's a new platform
<5> if your disklabel is just toast
<5> see if solaris has a equiv to scan_ffs
<4> well there is fsdb, but that doesnt see any files
<4> but maybe there is another tool
<5> what exactly have you done? you aren't being clear enough
<5> did you wipe your disklabel? superblock? rm a file? what?
<4> NicM: I was installing a raid1 with solaris volume manager aka disksuite
<4> and usually you leave slice 3 free
<4> thats where the database for the volume manager goes
<4> unfortunatley somone else installed the os and used slice 3 for /opt
<4> so I installed the metadb on slice 3
<4> now the superblock and the inode table is gone I guess
<5> you could try fsck with an alternate superblock
<5> or sleuthkit might be able to recover some files
<5> a solaris channel might have more, better ideas
<4> I have a look for sleuthkit
<4> good idea, thank you
<7> good monring
<8> falso: hi SIR!
<7> hi
<9> hello
<9> anyone know this error?



<9> http://rafb.net/p/cadEsn98.html
<9> i have a OpenBSD on AMD64
<10> a) is there a reason you're using ports? b) that means that a patch failed; do you have a clean ports tree?
<9> i have clean the ports, yes
<9> the patch ...
<9> i see
<10> what version are you running?
<9> 4.0
<10> witha current ports tree?
<9> yep
<9> OpenBSD 4.0-current (GENERIC) #774: Tue Dec 12 20:57:03 MST 2006
<9> the ports tree is up to date
<11> can anybody here recommend a particular M68K emulator?
<9> humm lt_kije thx
<10> debugg: you shouldn't mix -release or -stable with a -current ports tree
<10> read the FAQ
<9> no no, i have a -current
<9> with a -current version
<10> ah
<10> i misread
<9> ports
<9> but
<10> that's a very old snapshot, though
<9> humm
<10> i'm not able to reproduce your problem here (eg patches apply cleanly
<10> )
<10> try pulling the ports tree again
<9> ok
<9> i'll try again
<9> many thx
<12> hmm... patches not applyied cleanly .. that's happened to me before .. and today in fact..
<12> happens when there's an error at compile time, and you try to recompile without cleaning firts
<12> patch don't work on the already patched set of files (which makes sense, really)


Name:

Comments:

Please enter the result of the sum 63 + 46 (to avoid spam):






Return to #openbsd
or
Go to some related logs:

images.trademe.co.nz//photoserver
cant delete wbsrv
#cisco
#worldcup
#nhl
nigel07
pc probe lmcontrol procedure
ubuntu dv2275ea
delphi THandleStream pipe
#linuxhelp



Home  |  disclaimer  |  contact  |  submit quotes