Hacker Newsnew | past | comments | ask | show | jobs | submit | SingletonIface's commentslogin

Oh look, it's Google Ultron!

Nope, guess it's not :(


> But speaking as a former FreeBSD user, this is pretty easy to figure out after your first time seeing the flood of syntax errors.

I seem to be about the only person that makes use of the following feature, but FreeBSD and GNU make will in addition to looking for a file named Makefile, also look for BSDmakefile or GNUmakefile respectively.

So when I write a makefile with GNU make specific contents, I name it GNUmakefile, and when I write one that is specific to FreeBSD make, I name it BSDmakefile.

The user has to do absolutely nothing different; they simply write

    make
and if their make is GNU make and my makefile is a GNUmakefile then it builds. Likewise with FreeBSD make and a file named BSDmakefile.

The big win is when someone then has the wrong make. Instead of beginning to build and then failing at some point kicking and screaming, they will simply be told

    make: no target to make.

    make: stopped in (path)
by FreeBSD make, or

    make: *** No targets specified and no makefile found.  Stop.
by GNU make.

And at that point they will consult the README I have written for the project in question and they will learn that they need the other make than what they are using if they want to build this software.


Nowadays I write a GNUmakefile, then add a Makefile with a message telling people to use gmake. Same idea.


i have this in a (hand-written) configure script:

    case "$(uname -s)" in
    Darvin|Linux)
      MAKE=make
      GMAKE=$MAKE
    ;;
    DragonFly|*BSD)
      MAKE=make
      GMAKE=gmake
    ;;
    *)
      MAKE=gmake
      GMAKE=$MAKE
    ;;
    esac

    ...

    if test "$MAKE" != "$GMAKE"; then
      case "$(uname -s)" in
      DragonFly|*BSD)
        populate $rootdir/Makefile.in Makefile
      ;;
      esac
    fi

    cat <<EOF

    to build the programs from their sources:

      $MAKE

    to test their correctness:

      $MAKE check

    EOF
$rootdir/Makefile.in contains

    all .DEFAULT:
      @@GMAKE@ --no-print-directory "$@"


People keep saying that but is it true? There are some problems;

1. The seller would like to keep their identity secret so that they aren't prosecuted or attacked.

2. The buyer would also like to keep their identity secret.

3. The seller wants money. How do they know that the buyer will send them the money if they hand over the exploit before getting paid? Normally you'd report theft to the police but you're not going to go to the police and admit to selling exploits. Also you don't know who the seller is.

4. The seller wants the exploit. If they pay first then how do they know they will get the exploit.

If you contact some agency directly then surely they will not want to pay you out of fear that you will inform either the public or another government or agency about the transaction?

If there was a darknet marketplace for exploits (maybe there already is, maybe there already are several ones?) then that might solve it. There you can have both some degree of anonymity, you can have reputations for sellers and buyers and the DNM can offer escrow of funds.


But then since it was from xp and not win7 and you didn't know that, does that mean that your calc.exe is something you downloaded off some random site on the net trusting that it didn't contain malware?


Nope. I just have a crap memory.


Nice work, both with the music and the video.


> Taking control of a command and control server, however, had another unexpected outcome: Around 400 victims infected with FruitFly started connecting to it.

"Unexpected"? How? This would have been obvious to Wardle. Maybe the journalist added this to "inject some suspense"? Thanks but no thanks, I won't bother reading the rest of this article.


Maybe he wasn't expecting to see 400 infected victims.


Same here. I've talked with multiple untechnical people who have managed to tether their iPads to their iPhones without problems.


Plug in your phone to your laptop and it works, no need to fiddle with wifi.


You're replying to someone talking about tethering their tablet onto their phone by wifi access point ... and suggesting they plug their phone into their computer.

I have experimented - in both Debian and Windows 7 - using plugged-in / USB connectivity, but a) it's a bit spotty, b) it means I need a cable connection and that's often not ideal when on the go, c) it doesn't (as noted) work with tablets, and d) it doesn't solve the underlying issue of slave devices thinking they have non-mobile(3g,4g,lte,etc) network connectivity and sucking down lots of data.


I hadn't heard of CFront.

https://en.wikipedia.org/wiki/Cfront

Interesting.


> I wish I could run a water heater, heating or fridge off this system to use the excess 270Wh of the daily energy production.

Or better yet, be able to sell the excess power. In the future power grid this will be possible.


It's possible today, almost everywhere in the USA. In fact, the power company will usually buy it from you at the same rate that they are charging. My house is turning the meter backwards as we speak.

To do this, you need extra components to protect your house, the power grid, and the electricians who work on it.


Web browser: Firefox, Chromium. Comment: It is important that neither Chrome nor Chromium eat too much market share in order for the web to remain healthy.

Email client: ??? Comment: I use mutt but I'm wishing for something better. mutt is too limited

Terminal: Terminology, urxvt

IDE: None; neo-vim is sufficient for programming tasks, don't need most IDE features.

File manager: What ever is the default for the selected DE.

Basic Text Editor: neo-vim

IRC/Messaging Client: irssi and Pidgin

PDF Reader: Evince

Office Suite: LibreOffice

Calendar: Don't know

Video player: VLC

Music player: Tomahawk

Photo Viewer: What ever is default for the selected DE

Screen recording: Open Broadcast Studio


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: