| |
| |
| |
|
Page: 1 2
Comments:
<0> anyone know how using sed to get the last word of a line
<1> motion: TEST="this is a test"; echo ${TEST##* }
<0> ahh and it works on sh
<0> thnx lt_kije
<1> sure
<0> or not
<2> motion: :)
<1> it does work on sh/pdksh
<0> lt_kije; dont work on these peice of **** solaris machines
<1> ah
<1> that's solaris
<0> ...
<1> solaris sh is trash
<0> and i cant depend on bash
<1> with sed, echo "this is a test" | sed -e 's/.* //'
<1> then read sh(1) and sed(1) ;)
<0> heh
<1> and probably regex(3)
<0> ahh
<0> i tried /.* / in perl but didnt work
<0> and sed is just kind of wierd
<0> err my question prolly shoulda pointed toward awk
<0> the original question thatis :x
<1> depends on whether the regex is greedy or not
<0> yeah
<0> lt_kije; thnx again
<1> sure
<2> :)
<2> sed is just a pain in the ***
<3> anyone used the pptp port?
<3> i can't get my ppp side of things going
<4> Has anybody gotten pureftpd to run with the sql backend successfully?
<0> `spike; id honestly be surprised if its never been done
<5> odd with all these folks i never see anyone type
<6> mm.
<6> sup.
<5> it allways this quiet here these days
<5> used to be rockin, hard to keep up
<7> it's because of all the morons on the internet
<7> less intelligent chatter, more people being morons
<5> maybe it was cause obsd was new and lots of questions
<5> and idiots
<5> drove theo outta here I remember it
<5> hehe
<5> said he'd never come back and he didn't, bugged me out
<8> does anybody know if there's a way to un-brick an extreme networks summit84si from having loaded it with a corrupt systems image?
<8> a guy did it here at work (it was a guy, not me this time, honest), and they're throwing it out, so...
<8> when I boot it I get nothing
<9> reinstall it over a serial line
<2> hey (no havnt checked the website yet) but is it possible to donate money via neteller?
<2> yes, to the openbsd project
<8> beepbeep: I would, except I don't know where to start. we've tried holding down spacebar, soemone suggested pressing "b", we've tried sending breaks, nothing happens
<10> you get nothing on serial? sure the serial settings on the terminal are correct?
<8> I get nothing on the serial. we've tried the settings on another indentical switch. 9600, 8N2
<8> they work fine there, we get nothign on this one
<8> apparently, the guy had tried to flash it with a system image that was missing 2 bytes, and because if this, it's now just a purple desk ornament
<8> and extreme wants a hojillion dollars to even look at it
<10> try different serial settings, 8N1, 38.4, etc.
<10> i doubt you can re-flash the boot loader itself, which should already print to serial
<8> you think they are different between machines? my initial reaction was 8n1, but it proved to be 8n2 on the other one, but sure, I'll try
<8> you'd think that something like the loader wouldn't itself be re-flashable
<10> especially if it's the boot loader saying "Uncompressing primary image from flash..." over serial already ;)
<8> my co-workes has apparently been trying other emulations in the other room. emulation, I should say, jsut the one, 8N1
<8> =)
<8> no dice, I'm affraid
<8> we've even opened the thing up, hoping to find a removable rom thatwe can flash
<10> hook up one of those rs232 adapters with leds, see if anything is going on (like dtr/dsr going on/off)
<8> it just hurts to see expensive equipment get thrown out over something like this
<10> you'd think it checksums flash images
<8> hmm, dunno if we have one of those, btu I'm sure we can make one. what, just signal to one pin and another to ground? for each pin
<10> download to ram, check sum, reflash
<8> really
<10> like any decent vendor
<8> indeed
<8> or have a fallback thing, so that you could reflash in case something like this happens
<10> sometimes people lie, like you drop the thing onto the floor, hear stuff break and crunch, then make up a story about a flash gone wrong ;)
<11> Some 'gadget' I built a couple of years ago write-protected the low part of the flash, containing only simple boot-stuff and a serial flash client
<11> Thus you could always re-flash even if you pulled the plug halfway through programming
<11> Worked great :)
<8> physical gadget, or software?
<8> we'be been trying other configs now, nothing. the "management" led on the switch comes on though
<11> I only did the software
<11> Others did the hardware
<8> ok
<10> check the manual and see if there are any jumpers on the board, sometimes you can set one to boot with an alternate rom or such
<10> otherwise it might just be fried
<8> the manual(s) that we've been over tell us nothing. we opened it up, looking for jsut such a jumper, and none exists
<8> there are, what seem like, twoexpansion slots, but we don't knwo what they are for
<8> the first left in one of the slots are marked JP01, but the only way to short those tould be with a screwdriver, and I doubt that's the official way to do it
<8> besides, the manuals don't mention anything like that
<1> touching things with screwdrivers is actually rather common
<8> common, yes, intended, unlikely
<1> you don't seem to have much to lose at this point, it seems ;)
<8> hell, I've used screwdrivers as powerbuttons for ATX boards tons of times
<8> haha, I suppose you are right =)
<1> i've read manuals that said 'jump with screwdriver' before
<8> really? hehe, =)
<12> there must be a way to reset it
<12> surely nobody is stupid enough to make something completely unrecoverable
<8> you'd think, huh =(
<8> aparently, this guy had re-flashed the BootROM =(
<8> time to leave now, I'll try more inthe morning, you've all been most helpful =)
<10> let him demonstrate what he did, precisely, on a second box. if it really bricks the box, demand two free replacements from the vendor, or publish a story ;)
<8> hahaha =)
<10> i doubt he just reflashed the thing
<12> if it was that easy, the vendor would be used to dealing with it
<8> or they would learn from their misstke and put in some kind of safeguards
<12> they would either have a solution or docs saying "here is what to do" or "you are ****ed"
<13> hello, i know this is not a openbsd specific question, but is there anyway to ping or get information about a computer on the network by just having its mac address?
<10> you can send IP packets to its ethernet address and see if it replies...
<13> hmm how could i do this? i am unsure
<10> ports/net/libdnet, dnet eth ...
<10> what kind of information do you want to gather about it?
<13> its weird cuase i see in our dhcp logs, this one computer trying to to BOOTREQUEST a bunch of t imes and the the dhcp server crashes
<13> {{ gHg t }}
<13> sorry colors
<13> Ummm i want to find this stinking machine, hopefully it exists
<10> look up the mac address in the vendor table, might give a hint
<13> eh what is the vendor table
<10> something like http://www.cavebear.com/CaveBear/Ethernet/vendor.html
<1> bryckwynd: MAC addresses are determined in part by the vendor
<13> ok
<13> Oh thank you both
<1> a vendor's cards all start with the same pattern
<10> i guess fixing the dhcp server would be too reasonable as solution :)
<13> thats odd this one starts like this 00:14
<13> well i will do that too
<13> {{ gHg t }}
<14> sudo nmap -sP -PR yournet works as well
<13> but who said i was reasonable
<14> it will show you all mac adresses
<13> Oh cool
<13> thanks
<10> http://standards.ieee.org/regauth/oui/index.shtml
<10> more complete list
<10> given that it's doing DHCP queries, it likely hasn't got an IP address yet
<14> hmm
<13> true
<13> it has stoped since tho
<13> ***king that is
<10> you can send it an IP packet (to its mac address, but a random IP address), it might send back an ICMP error (to the source IP address you used), revealing its IP address
<10> what's the third byte of its mac address?
<13> hmm hang on
<13> third from left is 22
<13> third from right is 70
<10> Dell :)
<13> dell lol
<13> thanks man
<13> Yeah we have a lot of those
<13> well more than any other kind anyway
Return to
#openbsd
or
Go to some related
logs:
#winxp
#nhl
#hardware
calls consitution quaint
skb->magic whatis
#computers
#unix
#sex
#flash
#firebird
|
|