Podcasts about mmx

Lars zieht ein und es wird wild. Dann kommt noch ein anderer Lars, der Tara zum Weinen bringt. Robin macht Jermaine eifersüchtig und Sandra bekommt die große Frage gestellt: Ex or Next?#matchmyex #joyn ⚡️Die ganzen Folgen "Match My Ex" auf JOYN: https://t1p.de/MMX_trashkurs

Alle wollen Jenny, Lukas greift bei Lena an und Zoe und Barna sprechen endlich mal miteinander!#matchmyex #joyn ⚡️Die ganzen Folgen "Match My Ex" auf JOYN: https://t1p.de/MMX_trashkurs

Für Flocke und Jenny geht es in die X-Suite und dabei ist dann im anderen Schlafzimmer viel mehr los. Lena Schiwiora zieht ein und eigentlich wissen wir da ja schon, wie für sie die Show ausgeht. Barna sorgt für einen Plottwist und Zoe rastet am Ende natürlich nochmal aus.#matchmyex ⚡️Die ganzen Folgen "Match My Ex" auf JOYN: https://t1p.de/MMX_trashkurs

Zoe ist total am Ende, weil sie die Trennung von Barna immer noch nicht verkraftet hat. Da hilft auch kein Geknutsche mit Kaan. Währenddessen zieht ein neuer Bewohner ein, Lukas und Jenni zoffen sich die ganze Zeit und es geht zur ersten Match Night, wo zum ersten Mal die Männer die Couples bestimmen dürfen.#matchmyex #joyn ⚡️Die ganzen Folgen "Match My Ex" auf JOYN: https://t1p.de/MMX_trashkurs

Während die Männer noch keine Ahnung haben, was auf sie zukommt, schmieden die Frauen schon Rachepläne. Die meisten sind nämlich überhaupt nicht gut auf ihren Ex zu sprechen. Beef und Eifersucht auf jeden Fall vorprogrammiert! Wir haben so Böcke auf dieses neue Format! Wie sieht's bei euch aus?#matchmyex #joyn⚡️Die ganzen Folgen "Match My Ex" auf JOYN: https://t1p.de/MMX_trashkurs

durée : 00:55:41 - La Musique d'ici -

durée : 00:54:44 - Inun, Mikel Moreno, MMX

durée : 00:48:48 - La Musique d'ici -

durée : 00:55:05 - C la Chanson - France Bleu Pays Basque -

durée : 00:50:33 - MMX, Txiltxoko, Beietz

A NASA study using a series of supercomputer simulations reveals a potential new solution to a longstanding Martian mystery: How did Mars get its moons? The first step, the findings say, may have involved the destruction of an asteroid.  The research team, led by Jacob Kegerreis, a postdoctoral research scientist at NASA's Ames Research Center in California's Silicon Valley, found that an asteroid passing near Mars could have been disrupted – a nice way of saying “ripped apart” – by the Red Planet's strong gravitational pull. The team's simulations show the resulting rocky fragments being strewn into a variety of orbits around Mars. More than half the fragments would have escaped the Mars system, but others would've stayed in orbit. Tugged by the gravity of both Mars and the Sun, in the simulations some of the remaining asteroid pieces are set on paths to collide with one another, every encounter further grinding them down and spreading more debris.  Many collisions later, smaller chunks and debris from the former asteroid could have settled into a disk encircling the planet. Over time, some of this material is likely to have clumped together, possibly forming Mars' two small moons, Phobos and Deimos. To assess whether this was a realistic chain of events, the research team explored hundreds of different close encounter simulations, varying the asteroid's size, spin, speed, and distance at its closest approach to the planet. The team used their high-performance, open-source computing code, called SWIFT, and the advanced computing systems at Durham University in the United Kingdom to study in detail both the initial disruption and, using another code, the subsequent orbits of the debris. In a paper published Nov. 20 in the journal Icarus, the researchers report that, in many of the scenarios, enough asteroid fragments survive and collide in orbit to serve as raw material to form the moons.  “It's exciting to explore a new option for the making of Phobos and Deimos – the only moons in our solar system that orbit a rocky planet besides Earth's,” said Kegerreis. “Furthermore, this new model makes different predictions about the moons' properties that can be tested against the standard ideas for this key event in Mars' history.” Two hypotheses for the formation of the Martian moons have led the pack. One proposes that passing asteroids were captured whole by Mars' gravity, which could explain the moons' somewhat asteroid-like appearance. The other says that a giant impact on the planet blasted out enough material – a mix of Mars and impactor debris – to form a disk and, ultimately, the moons. Scientists believe a similar process formed Earth's Moon. The latter explanation better accounts for the paths the moons travel today – in near-circular orbits that closely align with Mars' equator. However, a giant impact ejects material into a disk that, mostly, stays close to the planet. And Mars' moons, especially Deimos, sit quite far away from the planet and probably formed out there, too.  “Our idea allows for a more efficient distribution of moon-making material to the outer regions of the disk,” said Jack Lissauer, a research scientist at Ames and co-author on the paper. “That means a much smaller ‘parent' asteroid could still deliver enough material to send the moons' building blocks to the right place.” Jacob Kegerreis Postdoctoral research scientist at NASA's Ames Research Center Testing different ideas for the formation of Mars' moons is the primary goal of the upcoming Martian Moons eXploration (MMX) sample return mission led by JAXA (Japan Aerospace Exploration Agency). The spacecraft will survey both moons to determine their origin and collect samples of Phobos to bring to Earth for study. A NASA instrument on board, called MEGANE – short for Mars-moon Exploration with GAmma rays and Neutrons – will identify the chemical elements Phobos is made of and help select sites for the sample collection. Some of the samples will be collected by a pneumatic sampler also provided by NASA as a technology demonstration contribution to the mission. Understanding what the moons are made of is one clue that could help distinguish between the moons having an asteroid origin or a planet-plus-impactor source. Before scientists can get their hands on a piece of Phobos to analyze, Kegerreis and his team will pick up where they left off demonstrating the formation of a disk that has enough material to make Phobos and Deimos.  “Next, we hope to build on this proof-of-concept project to simulate and study in greater detail the full timeline of formation,” said Vincent Eke, associate professor at the Institute for Computational Cosmology at Durham University and a co-author on the paper. “This will allow us to examine the structure of the disk itself and make more detailed predictions for what the MMX mission could find.”   For Kegerreis, this work is exciting because it also expands our understanding of how moons might be born – even if it turns out that Mars' own formed by a different route. The simulations offer a fascinating exploration, he says, of the possible outcomes of encounters between objects like asteroids and planets. These events were common in the early solar system, and simulations could help researchers reconstruct the story of how our cosmic backyard evolved.  It's exciting to explore a new option for the making of Phobos and Deimos – the only moons in our solar system that orbit a rocky planet besides Earth's.

「ベイヤーダイナミック、開放型のゲーミングヘッドセット「MMX 330 PRO」／エントリー完全ワイヤレス「AMIRON 100」」　かぶしきかいしゃオーディオブレインズは、同社が取り扱うドイツ・beyerdynamic（ベイヤーダイナミック）ブランドより、開放型ゲーミングヘッドセット「MMX 330 PRO」と、完全ワイヤレスイヤホン「AMIRON 100」を発売する。

durée : 00:57:12 - C la Chanson - France Bleu Pays Basque

durée : 00:54:30 - MMX, Botakantu, Katamalo

「＜IFA＞beyerdynamic、ブランド初のオープン型ゲーミングヘッドセット「MMX 330 PRO」」　ドイツ・ベルリンで世界最大級のコンシューマーエレクトロニクスショー「IFA2024」において、beyerdynamicはオープン型のゲーミングヘッドセット「MMX 330 PRO」を発表した。

「beyerdynamic、ゲーミングヘッドセットのフラグシップモデル「MMX 300 PRO」」　オーディオブレインズは、同社が取り扱うドイツ・beyerdynamic（ベイヤーダイナミック）ブランドより、ゲーミングヘッドセットのフラグシップモデル「MMX 300 PRO」を9月6日に発売する。

durée : 00:53:23 - La Musique d'Ici : Bost Axola, Gozategi, Sara Azurza, MMX...

Com o cupom MARKETMAKERS15, você garante 15% OFF na sua primeira compra no site: https://www.shop2gether.com.br/masculino?utm_source=mktinfluencia&utm_medium=ig&utm_content=marketmakers&utm_campaign=junho_mktinfluencia_ig_marketmakers Recebemos no Market Makers ninguém menos que Eike Batista, empresário responsável por uma das histórias mais surreais da história do emprendedorismo brasileiro. Eike já viveu várias vidas em uma: já foi o 7º homem mais rico do mundo, mas também foi preso por duas vezes durante a Operação Lava Jato. De tão surreal que é sua vida, ela virou livro e filme nos cinemas.Uma breve bio de Eike: nascido em Governador Valadares, Eike Fuhrken Batista da Silva mudou-se aos 12 anos para Frankfurt na Alemanha por causa da carreira profissional de seu pai, Eliezer Batista, que na época presidia a Vale do Rio Doce. Eike cursou Engenharia Metalúrgica numa universidade alemã mas não chegou a concluir o curso.Na época de estudante, começou a vender seguros de porta em porta. Voltou para o Brasil em 1981, com 24 anos, quando adquiriu sua primeira mina e atuou como intermediário de garimpeiros do Mato Grosso na venda do ouro para os grandes centros do País.Foi sua primeira de várias empreitadas no mundo das commodities e pedras preciosas. Seu ápice como empresário veio em 2012, quando alcançou mais de 30bi dólares e tornou-se o 7º homem mais rico do mundo. A fortuna vinha das empresas do Grupo EBX, que tinha atuações nos setores de petróleo, mineração, energia térmica, carvão, portos e logística.No entanto, nos anos seguintes, uma sucessão de frustrações com os projetos das empresas X fez com que o império derretesse na bolsa, sendo a mais emblemática a OGX Petróleo, que chegou a ser uma das ações mais importantes do Ibovespa. Outras companhias, como MMX, CCX e LLX também sucumbiram, enquanto a MPX Energia permanece até hoje e como uma das queridinhas da bolsa atualmente, agora sob o nome de Eneva.Esta será uma conversa sobre o passado, o presente e o futuro de uma das personalidades mais marcantes do capitalismo brasileiro.Convidado: Eike Batista (Empresário brasileiro)Apresentadores: Thiago Salomão (@_salomoney) e Josué Guedes (@josueguedes_) Become a supporter of this podcast: https://www.spreaker.com/podcast/market-makers--5613725/support.

durée : 00:52:15 - La Musique d'Ici: Pier Paul Berzaitz, Olatz Zugasti, MMX, Nogen...

Prepare for lift off as the Krewe sits down with returning guest Dr. Kate Kitagawa of JAXA to look deep into the past, present, and future of Japan's space program! From pencil rockets & SLIM landers to international collaborative efforts, discover Japan's role in exploring the far reaches of outer space.------ About the Krewe ------The Krewe of Japan Podcast is a weekly episodic podcast sponsored by the Japan Society of New Orleans. Check them out every Friday afternoon around noon CST on Apple, YouTube, Spotify, Amazon, Stitcher, or wherever you get your podcasts.  Want to share your experiences with the Krewe? Or perhaps you have ideas for episodes, feedback, comments, or questions? Let the Krewe know by e-mail at kreweofjapanpodcast@gmail.com or on social media (Twitter: @kreweofjapan, Instagram: @kreweofjapanpodcast, Facebook: Krewe of Japan Podcast Page, TikTok: @kreweofjapanpodcast, LinkedIn: Krewe of Japan LinkedIn Page, Blue Sky Social: @kreweofjapan.bsky.social, & the Krewe of Japan Youtube Channel). Until next time, enjoy!------ Support the Krewe! Offer Links for Affiliates ------Use the referral links below & our promo code from the episode (timestamps [hh:mm:ss] where you can find the code)!Zencastr Offer Link - Use my special link to save 30% off your 1st month of any Zencastr paid plan!  (00:58:25)------ Past Episodes with Dr. Kate Kitagawa ------The Age of Lady Samurai (S01E12)------ Links about JAXA & Dr. Kate Kitagawa ------JAXA (English) on TwitterJAXA (Japanese) on TwitterJAXA on InstagramJAXA (English) on FacebookJAXA (Japanese) on FacebookJAXA Website (Japanese)JAXA Website (English)ISAS (English) on TwitterISAS (Japanese) on TwitterISAS on InstagramJAXA on YouTubeJAXA Space Education Center Website (English)MMX GameLunarcraft GameSLIM The Pinpoint Moon Landing GameKate's Book "The Secret Lives of Numbers"Kate's Website------ JSNO Upcoming Events ------JSNO Event Calendar

We finally learn the true color of Neptune. Vulcan succeeds while Peregrine fails. Delays for Artemis missions. A rocket that eats itself for more thrust.

We finally learn the true color of Neptune. Vulcan succeeds while Peregrine fails. Delays for Artemis missions. A rocket that eats itself for more thrust.

Очень сбалансированный выпуск, где 3 плохие космические новости компенсируются тремя хорошими космическими новостями.

#231It's a new year and that means new science. But what (that we know so far) does 2024 hold? On the space front, agencies around the world have as many as 13 missions to Earth's moon, while Japan's MMX mission will launch to take samples from the Martian moon Phobos. NASA will finally launch the Europa Clipper mission to explore Jupiter's ocean-bearing moon. On the technology front, Europe's first ever exascale supercomputer, capable of performing billions of operations per second – only the third officially recognised such machine in the world, and an extraordinary tool for physicists, mathematicians and even AI development. Plus why we're increasingly close to the time when quantum computers may break encryption as we know it.And while 2023 was officially the hottest year on record, 2024 is poised to be even hotter, thanks to even higher concentrations of greenhouse gases and more months of El Niño conditions in the Pacific Ocean. How this combination should leave us expecting the unexpected when it comes to drought and rainfall, while nations grapple with the renewable energy and fossil fuel transition pledges they made at 2023's COP28 climate summit. And why the story isn't over for hormone-mimicking weight loss injections like Ozempic and Wegovy – or the many similar drugs that are following close on their heels.Host Christie Taylor discusses all of this and more with guests Leah Crane, Matthew Sparkes, James Dinneen and Clare Wilson. To read more about these stories, visit newscientist.com/2024preview. Hosted on Acast. See acast.com/privacy for more information.

Все главные космические события, которые стоит ждать от 2024 года в одном подкасте.

MMX for Chaos Planet 29.11 Saigon

JAXA, Japan Aerospace Exploration Agency är den Japanske motsvarigheten till NASA, ESA eller vår Svenska Rymdstyrelse. På vårt första stopp på vår Japanresa träffar vi Masaki Fujimoto, Deputy Director General på JAXAs Institute of Space and Astronautical Science. Med honom pratat vi om några av deras rymdmissioner, som alla är små steg med det långsiktiga målet att nån gång kunna landa på Mars. Och så kollar vi såklart läget med sveriges nye astronaut Marcus Wandt som bland annat berättar om sin träning på den Japanska modulen på ISS. もう 火星に 行った？   Har vi åkt till Mars än? görs på Beppo av Rundfunk Media i samarbete med Saab. Avsnittet Har Japan åkt till Mars än? är producerat med hjälp av stöd från Japanstiftelsen.

The Perseverance rover is building up a stockpile. It's collecting samples of Martian rocks, dirt, and air, and storing them in small tubes. A complex retrieval mission will gather the tubes and bring them to Earth in about a decade. By then, scientists may be analyzing another set of samples — of Mars's larger moon, Phobos. A Japanese mission, MMX, is scheduled for launch in about a year. It'll land on Phobos and gather a few grams of material. Return to Earth is scheduled for 2029. The two sets of samples will provide different details about Mars. Perseverance is inside a large crater. It's exploring the delta of an ancient river that once filled the crater with water. The sediments will tell us about conditions in the distant past, when Mars was warm and wet. And they could contain evidence of microscopic life. MMX will tell us about the formation of both Martian moons, Phobos and Deimos. They could be captured asteroids. Or they could be debris from an ancient collision that blasted some of the Martian crust into orbit. Recent observations of Deimos by another mission, from the United Arab Emirates, appear to favor the impact scenario. The samples could help scientists confirm it. Mars is quite low in the west at sunset, and sets by the time it gets dark. It's just visible from the southern latitudes of the U.S. — Miami or San Antonio — but lost in the Sun's glare for those farther north.  Script by Damond Benningfield Support McDonald Observatory

Episodio cargado de datos y curiosidades sobre la creación de Mega Man X4, joya de la saga MMX. Todo en compañía del gran amigo Pablo Naop desde Mega Mixtape.

Beyerdynamic, the world-renowned manufacturer of professional audio equipment, was at the 2023 NAMM Show in Anaheim, California showing off their line of microphones and new headphones. This included the new DT 900 PRO X studio headphones, and the MMX 106 studio microphone. The DT 900 PRO X studio headphones are the successor to the popular […] The post BeyerDynamics Microphones at NAMM appeared first on Geekazine.com.

Beyerdynamic, the world-renowned manufacturer of professional audio equipment, was at the 2023 NAMM Show in Anaheim, California showing off their line of microphones and new headphones. This included the new DT 900 PRO X studio headphones, and the MMX 106 studio microphone. The DT 900 PRO X studio headphones are the successor to the popular […] The post BeyerDynamics Microphones at NAMM appeared first on Geekazine.com.

Make a Logo on Fiverr Beyerdynamic, the world-renowned manufacturer of professional audio equipment, was at the 2023 NAMM Show in Anaheim, California showing off their line of microphones and new headphones. This included the new DT 900 PRO X studio headphones, and the MMX 106 studio microphone. The DT 900 PRO X studio headphones are […] The post BeyerDynamics Microphones at NAMM appeared first on Geekazine.

Carlos Murillo de la banda MX PunkMetal habla de su propuesta musical y el Ep Revolución MMX.Plataformas:https://mxpunkmetal.bandcamp.com/releaseshttps://www.youtube.com/user/sojaPostmelomanRedes:https://web.facebook.com/MX-Punk-Metal-168571803754938

I've been tinkering with another "bridge" device, an old Dell Latitude CP MX233XT with 128MB RAM, 2MB video, and a 233Mhz Pentium with MMX. It's been...adventurous. https://www.geektherapyradio.com/Email me: johnny@geektherapyradio.com

HOUR3 - The Cowboys have done (mostly) diddly squat during free agency and RJ let's his voice be hear through song. Plus the Mavericks take care of the Rockets, Jorge Marsvidal's UFC career is in jeopardy and breaking news ... the Cowboys have a new coach!

Charlie sits down with Heather Greenwood, Associate Director of the Memory Maker Experience department at Broad River Retail. You will learn more about Heather's personal life, her position within the organization, and the history purpose, and goals of MMx. Episode resources: Book Heather mentioned: The Purpose Path, by Dr. Nicholas Pearce - https://www.nicholaspearce.org/book  This episode on Youtube: https://youtu.be/n012RqeNtbM We hope you enjoy this episode, and subscribe to our podcast for a new story each week. Visit storiesfromtheriver.com for more episodes.

Charlie sits down with Heather Greenwood, Associate Director of the Memory Maker Experience department at Broad River Retail. You will learn more about Heather's personal life, her position within the organization, and the history purpose, and goals of MMx. Episode resources: Book Heather mentioned: The Purpose Path, by Dr. Nicholas Pearce - https://www.nicholaspearce.org/book  This episode on Youtube: https://youtu.be/n012RqeNtbM We hope you enjoy this episode, and subscribe to our podcast for a new story each week. Visit storiesfromtheriver.com for more episodes.

Marble ManiaX is in the books and let's just say CONTROVERSY is an understatement! Join us as we recap the event, read your mailbags, and get a final fantasy league update from the TransPerfect Music City Bowl Winner and Commissioner! This is The Number 1 Podcast in Marble Sports, Let it Roll!Follow us on Twitter:Dekker: @DoubleDekksHector: @HWalkerMusicTerm: @BigGetsBigTermSky: @Skyfall_707Nonagon: @Nonagon_Violet---------------------------------If you have a big take of your own you can email the show at biggetsbigtakes@gmail.com,find us on Twitter: (https://t.co/OhU31PKZw0)YouTube: (https://www.youtube.com/c/biggetsbigtakes)iTunes: (https://t.co/hLrQK71k4z)Spotify: (https://t.co/dFsujO5h5v)

Theoretical Astrophysicist Ryuki Hyodo on the Formation of Planets, the Many Ongoing Missions in Space (Hayabusa2, MMX, BepiColombo...), the Journey to JAXA from Japan and Abroad, Life on Other Planets, and much more.Institute of Space and Astronautical Science Homepage: https://www.isas.jaxa.jp/en/Hayabusa2 Asteroid Exploration Mission: https://www.hayabusa2.jaxa.jp/en/MMX (Martian Moons eXploration Mission): https://www.mmx.jaxa.jp/BepiColombo Mercurity Mission: https://mio.isas.jaxa.jp/en/

The gang is back to discuss Event 3 of #MarbleManiaX, Extreme Funnel Clash! Join us as we chat about the event, have the postman read your mailbags, get a fantasy update from the Commissioner, and make some huge predictions for Event 4 of #MMX: Extreme Obstacle Run! Follow us on Twitter:Dekker: @DoubleDekksHector: @HWalkerMusicTerm: @BigGetsBigTermSky: @Skyfall_707Nonagon: @Nonagon_Violet---------------------------------If you have a big take of your own you can email the show at biggetsbigtakes@gmail.com,find us on Twitter: (https://t.co/OhU31PKZw0)YouTube: (https://www.youtube.com/c/biggetsbigtakes)iTunes: (https://t.co/hLrQK71k4z)Spotify: (https://t.co/dFsujO5h5v)

This month the gang played Mega Man X. Was it good? Yes. Could it have been better? Yes. It's a blast from the past with a killer soundtrack and a half-assed attempt at a Blade Runner plot line. What's not to love? How about enemies respawning immediately after killing them just because the camera moved. We spend a lot of time comparing MMX to other games trying to pinpoint what about the mechanics feel so good. We also try to nail down what makes boss fights fun -- if they are ever fun. For the next Gameclub we are going to be playing Prey, so get that going: https://store.steampowered.com/app/480490/Prey/ Everywhere that you can find us: https://linktr.ee/wideflank Timestamps: 0:00 - Intro 2:38 - MMX overview 4:15 - Frame delay 5:02 - Controls/Movement 8:35 - Doom and similar games 14:16 - MMX wants to be fast paced but aint 16:45 - The game is dated 19:50 - Could this have been a Metroidvania? 22:50 - How about make it *only* boss fights 26:30 - Favorite gun 27:00 - Why do a buster only playthrough? 28:20 - Order of bosses 32:20 - Favorite boss 38:30 - Telemelt! 40:27 - Difficulty and Soulsborne 45:20 - Story 47:37 - Opening level game design 54:50 - Cup head and memorization 1:00:00 - Favorite boss…of all time? 1:03:48 - Best music Show Notes: Bo Jackson - https://en.wikipedia.org/wiki/Bo_Jackson Telemelt - https://telemelt.com/ Ego raptor (don't watch this) - https://www.youtube.com/watch?v=8FpigqfcvlM

※ 本文章发布于订阅号：百车全说，订阅号阅读更加方便，欢迎关注前不久，本年度钢炮迷们第二关心的车，也就是“领克02 Hatchback”正式上市，定价17.68-18.18万，有人问第一关心的是什么车，那当然是前不久才聊过的第八代高尔夫GTI。这次的领克02 Hatchback一共就推出了两个版本，分别是17.68万的Halo版和18.18万的Halo驾控套件版，同时，领克还给这两个版本，各提供了101台黑橙配色的首发限量版，也就是一共202台，不过对于去选择02 Hatchback的车主来说，什么颜色并不重要，重要的是能不能买到这台车。为什么这么说，因为现在的首发限量版采用直播的形式在线上发售，据说发售当天3秒售罄，抢到的车主最快将会在6月25号提车。不得不说，领克和吉利现在玩营销都是一把好手，假如你没有抢到首发限量版，那就只能等一等，看看领克之后会怎么去卖这台车，我估计大概率会像之前的领克03+那样，继续通过官网下订单，然后玩一手饥饿营销，毕竟说到底领克02Hatchback是一台小众车，如果不靠饥饿营销去提升一下调性，那不仅价格很难守住，调性也肯定会比现在低很多。我问了一下身边玩车的同好们，其中有不少人都直呼真香，毕竟一台254马力的国产小钢炮起售价只要17.68万，但是，今天我可能要给在座的很多人，尤其是钢炮迷们泼一盆冷水，虽然领克02 Hatchback官方号称“真钢炮”，但它严格意义上来看并不算是钢炮。今天我们就来好好扒一扒这款车，它和领克02有什么区别，三大件强不强？领克在有03+的情况下为什么要出这款车？它与高尔夫GTI相比怎么样，拿到手应该怎么去改？领克02 Hatchback是一款什么样的车？首先，领克02 Hatchback在我看来更像是一台紧凑型跨界车，因为它的本源还是那台紧凑型SUV，换言之这台车只是在领克02的基础上降低了车身高度，然后换装了那套254马力/350牛米的发动机，以及那套8AT变速箱。这台02 Hatchback的尺寸为4458/1890/1486mm，轴距为2702mm，相较于普通领克02，高度从1528mm降低至1486mm，轮眉和轮胎之间的距离也减少了35mm，只剩下三指距离。可能有人对于这个三指的高度没有什么概念，我就这么跟各位去说吧，对于很多普通的轿车或者SUV来说，3指的间距属于正常操作，但是对于一台主打性能的小钢炮来说，这样的车身高度就跟SUV没有什么区别，因为性能玩家想要的是那种贴地飞行的感觉，所谓的通过性其实并不在很多人的考虑范围之内。但是，相比于之前的领克02来说，这台车确实比先前在高度上降低了很多，但是由于领克02原先的车身设计就比较高大，即使再怎么进行降低，还是制约了02 Hatchback在原厂状态下的车身姿态，虽然02 Hatchback并不比高尔夫GTI这样的传统小钢炮高多少，但两台车放在一起，你还会发现02 Hatchback的发动机舱明显高出了一截。所以，领克02 Hatchback并不是传统意义上的小钢炮，现在摆在我们面前的更像是一款低重心的跨界车，如果领克有一天做出了一款真正的钢炮，那就只有一个可能，即基于03+的03+ Hatchback，因为领克03+的先天条件放在那里，明显更适合成为钢炮，或许02 Hatchback只是领克的试水之作，试探一下市场对于这种小众车型的热度，真正的重头戏还没出来。当然，为了与普通02做出更多的区分，这次02 Hatchback在外观上也动了点刀，比如更运动的前包围，整体造型偏向领克03劲版和03+，车尾自带唬人的双边四出排气，车尾也配备了更加明显的尾唇，车顶同样也有一个小尾翼，轮圈也从普通版的17寸或18寸，换成了更大更宽的19寸轮毂，轮胎尺寸也达到了和03+相同的245/40/19。此外，由于普通的02本就是一款非常像跨界车的SUV，所以02Hatchback为了弱化跨界风格并贴近钢炮，将原先前后翼子板上的黑色轮眉变为与车身同色的设计，但轮眉这个东西怎么也不应该出现在钢炮上，虽然有不少媒体在宣传的时候都说这是小宽体，但是我总觉得这就属于收了钱然后说好话的，毕竟你既然是原厂宽体，那你倒是把接缝给去了啊。最后，02 Hatchback在内饰部分全面向03+看齐，不过这次换成橙黑配色了，远比普通02运动，黑色皮质搭配部分的Alcantara面料，整体运动氛围的营造还是很到位的，而且中控饰板也采用与03+类似的黑灰相间特殊纹路，加上橙色饰条、缝线、安全带，这套内饰无论是设计还是用料，个人认为算是同级最强之一，没什么可挑剔的。在配置方面，02 Hatchback也是向着普通02的高配车型看齐，整套主动安全系统、360度全景影像、全速自适应巡航、座椅加热通风、10扬声器燕飞利仕音响……仪表和屏幕与普通02一样，10.25英寸液晶仪表搭配10.25英寸中控屏幕。至于02 Hatchback两个版本之间有什么区别，官方在版本名称里已经表达的很清楚了，这差的5000块其实就差在一套“驾控套件”上，有套件的版本轮圈是锻造的，但单颗实测重量达到了11.2公斤，对于19英寸的锻造轮圈来说实在不轻，此外还多了一个“前舱铝合金横向稳定加强杆”，也就是我们俗称的“顶巴”，理论上可以提高车身刚性，抑制过弯侧倾，但只在极限状态下才会发挥那么一丢丢的作用，对于02 Hatchback这种街道用车来说属于“心情件”，很多玩家去改这东西也是因为好看、不贵，你问他改完有什么区别，他其实也说不出来。同时，之前很多人买03+的时候去选择那个5000元的驾控套件，目的其实就是为了在合法的情况下更换19寸轮毂，因为咱们现行的法规下，不改变轮胎数据就可以随便换轮毂，而02Hatchback现在无论加不加那5000块钱，其实都是用的19寸轮毂和245/40/19的轮胎，以至于对于很多人来说，现在这个5000块的驾控套件看似不贵，但并没有什么实质性的作用。所以，如果你真想买02 Hatchback，我是真的不太推荐各位去选这个5000元的驾控套件，除非领克愿意给换装尺寸更大、宽度更宽的圈胎，否则这5000块钱还不如自己先攒着，然后换一套大品牌的锻造轮毂，数据也会比原厂的更合适，毕竟大多数性能车主，是不愿意看到车子的圈胎缩在叶子板里面的。领克02 Hatchback的三大件强不强，潜力大不大？那么，这次的领克02 Hatchback的三大件，就真的像很多人说的那样，达到性能车的标准了吗，我觉得并没有。我们都知道，领克的高性能系列都会带“+”号，尽管目前只有一款“03+”在售，但是按照这个逻辑，只有被打上“+”号的车，才可以算作各自车系的高性能版本。而到了02 Hatchback这里，无论是官方对性能的宣传力度，还是外观、内饰设计中的运动元素，又或者是这台车在自身车系中的定位，都可以看出这就是02车系的高性能版本，而02 Hatchback之于普通02，非常类似于03+之于普通03，但它为什么不叫“02+”或者“02 Hatchback+”呢？答案可能只有一个：领克自己都不认为02 Hatchback在某些性能的关键指标上可以达到标准。现在02 Hatchback的发动机与03+同款，都是254马力/350牛米的沃尔沃Drive-ET5 2.0T高功率发动机，变速箱是爱信的8AT；而普通02的最强版本，也只是190马力/300牛米的2.0T低功率发动机，匹配的是7速湿式双离合变速箱。所以，02 Hatchback在发动机和变速箱方面与03+保持一致，可以说远强于普通02，并且官方数据只需6.2秒破百，在同价位中算非常劲爆了，只是领克的车在百公里加速一项上，往往官标都非常激进，你也可以理解成虚标。比如03+官标百公里加速5.9秒，可实际上几乎跑不出这个成绩，实测基本上都在6秒多，我查了一下02 Hatchback的实测成绩，尽管这台车有超增压模式，可以把发动机扭提升到380牛米，但是实测最快也要6.85秒，而官标6.9秒的7代半高尔夫GTI实测比它还要快一些。但是，这里面有一个点很容易被人忽略，那就是02 Hatchback的轮胎数据达到了245/40/19，同样作为小钢炮的高尔夫GTI不仅在车重上更轻，而且配备的是一套225/40/18的圈胎，也就是说在百公里加速的时候，GTI所受到圈胎的限制更小，也更容易跑出亮眼的成绩，如果02 Hatchback的圈胎数据和GTI一样，是不是大概率可以跑出比GTI更好的百公里加速成绩？此外，02 Hatchback现在只有前驱版本，而03+标配适时四驱系统，理论上02 Hatchback完全可以配备四驱系统，毕竟普通02也之前推出了四驱版本，但再多一套适时四驱系统对02 Hatchback能有多大提升，我在这里要打一个问号，因为假如你也玩儿过领克03+，你会发现拖后腿的其实是那套变速箱，实在是太“买菜车”了。在底盘部分，02 Hatchback与普通02并无太大区别，根据官方的说法，这台车的悬架弹簧刚度提升50%，副车架衬套刚度提升40%，所以更多偏向细节上的加强，02 Hatchback的整体操控虽然相较于普通02会有提升，最明显的是底盘会更加硬朗，但毕竟是SUV的底子再加上车身高大，所以并不能达到传统钢炮的水准。最后，网上有02 Hatchback的声浪，大家可以去听一下，说白了就是一台家用车，无论在何种模式下，原地轰油门都只能听到发动机的运转声，并没有所谓的“声浪”，我觉得声浪可以算是评判一款车是否是足够性能的标准，有声浪的不一定是性能车，但性能车一定会有声浪。综上所述，虽然02 Hatchback在发动机和变速箱上都达到了03+的水平，但领克的初衷，也许是希望将02 Hatchback打造成一台富有驾驶乐趣的跨界车，而非03+这样比较硬核的性能车，虽然03+在性能车中一点也不硬核，如果领克会出02+ Hatchback，那必然会配备四驱系统，至于车身高度么……这就得看领克愿不愿意花时间去重新设计和匹配了。值得一提的是，现在领克02 Hatchback能用的绞牙避震，也就一些国产的品牌可以选，比如DWD、D2、SF之类的，改完之后就是硬邦邦的感觉，目前很多大牌还没有对应的产品，所以想改避震的我建议还是等一等，或者你如果想玩低趴，那就结合自己的预算，直接去买气动避震就可以了，不过即使是最入门的气动避震套装，也要一万多块钱。领克02 Hatchback与领克03+有什么区别？那么，领克02 Hatchback和领克03+有什么区别，我觉得除了两厢车和三厢车的差别之外，还有领克02 Hatchback在车辆等级划分中属于普通车型，而领克03+属于高性能车型，之前我们在聊AMG的时候就提到过性能等级这个概念，领克现在也是这样在玩，只不过领克目前也只分了普通车型和“+”系列高性能车，而且“+”系列里面也只有一台03+，同时再往上也没有性能更加夸张的车型等级和具体车型了，只能说希望领克再接再厉。由于车辆的等级放在这里，使得领克02 Hatchback只能是一台前驱车，在外观上没有特别夸张的包围，只是基于领克02进行了一些升级和调整，比如四出排气、小宽体、小尾翼等等；而03+却相当于官方改装版本的领克03，不仅动力配置大幅提升，而且做成了一台四驱车，顶配还有夸张的碳纤维包围，据说能将11KG的下压力提升到40KG下压力。同时，领克02 Hatchback的内饰也没有领克03+那么奢华，其中02 Hatchback的内饰只是用了真皮包覆，然后搭配橙色缝线，而03+的内饰规格就做的更高，整台车的内部都被Alcantara翻毛皮包裹起来。这里面有一个细节我觉得很有意思，就是领克在做内饰的时候特别喜欢和外观油漆进行呼应，之前做03+的时候，由于车辆外观颜色用的是“炫燃金”色，所以内饰的缝线、安全带和装饰件都做成黄不黄、绿不绿的颜色，现在的02 Hatchback由于外观是橙色，所以内饰也都有橙色的缝线、安全带和装饰件。在这里也是插一句题外话，我发现领克在做这些车型的时候，总是喜欢在颜色上做一些呼应，可是为啥03+的冠军定制版内饰还是照搬普通03+的配色，难道领克就不能让这个冠军定制版再“细节”一点吗，你如果真觉得灰色做出来不显眼，那弄个红色的缝线也可以啊。简单来说，领克02 Hatchback和领克03+都是基于CMA平台生产，但是领克02 Hatchback实际上是基于领克02这台紧凑型SUV进行打造，而领克03+则是基于领克03这个轿车进行打造，并且由于两台车的等级不同，使得两台车的内饰和外观以及性能配置会有一定的差距。按现在领克的套路来看，我们是不是可以推测一下，今后领克有可能就把旗下的“+”系列弄成像奥迪的系列那样，然后给这些旗下的车型都出个“+”版本，那到时候我们是不是就能看到“01+”、“02+”、“02+Hatchback”、“05+”、“06+”甚至是“09+”，甚至有可能再出现比“+”系列性能等级更高的产品，就类似于奥迪的RS系列，想想都觉得有些激动，希望领克不要让我们失望。领克为啥要做02 Hatchback？我们都知道，领克03+在2019年8月2日晚上正式上市，但是自从03+上市之后，领克已然沉寂了太久，他们需要推出一台全新的高性能车型来吸引大家的目光。这时候，就有一个问题摆在面前：用什么车来做？首先，领克01和领克05肯定要排除掉，因为这两台车实际上都有配备2.0T高功发动机+8AT变速箱+四驱的车型，要知道实际上现在的领克03+用的也是这套动力系统。哪怕我们把即将上市的领克09也算上，但是那台车实际上是对标沃尔沃XC90的SUV，动力配置据说会和XC90类似，而沃尔沃XC90的2.0T高功率版本不仅是机械+涡轮双增压，而且还有48V轻混系统，数据也达到了300马力/420牛米，即便是XC90的低功率版本，用的也是250马力/350牛米的2.0T发动机和8AT变速箱，而且XC90全系都标配的都是全时四驱。所以，对于这几台车来说，现在领克“+”系列用的动力系统反而成了鸡肋，除非能装配更牛X的动力系统，否则这些车型做不做“+”系列的意义不是很大，不过我们是不是可以猜测一下，假如以后领克去做“01+”和“05+”的时候，是不是可以用上XC90那套高功率发动机和全时四驱系统，似乎我在无意之间，就给领克指明了方向。其次，排除掉领克01和领克05之后，领克目前在售车型里只剩下02、03和06了，其中领克03已经有了03+作为性能标杆，以至于领克只能在02和06之间进行抉择，而领克06是用的BMA-evo平台打造，要知道BMA平台下的车型，只能用1.0T或者1.5T发动机，外加PHEV、HEV和MHEV这些新能源动力，除非领克愿意进行大量的重新设计，否则领克06就无法使用那套2.0T+8AT的动力系统，更不用说四驱系统了。所以，摆在领克面前的，就只剩下了领克02一台车，加上领克02之前哪怕是18.88万的2.0T DCT四驱劲PRO版本，配的也不过就是一颗190马力/300牛米的2.0T发动机，还有一套7速湿式双离合变速箱，而领克02本身是基于CMA平台打造，使得这台车在动力系统上有了可操作的空间，而且不需要去进行大量的重新设计，省时省力还省钱。再者，之前也有玩家用领克02进行改装，不仅将原车的黑色塑料板变成了和车身同色，而且还把车身高度降低，然后配上了大尺寸的轮毂和定做的包围，很多人看完改装之后的样子，发现原来领克02的身上还有一些小钢炮的味道在里面，我猜测领克的厂家应该也看到过相关的信息，从而促使他们去做了这台02 Hatchback。最后，就是市场层面的因素，目前国内市场上在售的纯种两厢掀背小钢炮，你会发现能买到的车型特别少，要么就是像奔驰AMG A45/A45S那样价格高高在上，很多地方想要买车还得加价；要么就是像本田思域TYPE-R那样没有官方正式进口，然后只能买平行进口车，价格也被炒到了天上；要么就是像高尔夫GTI或者高尔夫R这种，虽然整体性价比还算可以，而且有情怀加持，但是能跑多快完全取决于你的动手能力，属于“买车不贵改车贵”的代表。撇开车辆的价格不谈，你会发现无论是在售还是停售的两厢小钢炮车型，它们要么是日系车，比如思域TYPE-R之类的车型；要么是美系车，比如福克斯ST和福克斯RS这种；要么是德系车，比如奔驰有A45系列，宝马之前也有进口到国内的M135i和M140i，奥迪的槽点比较多，海外明明有两厢版本的S3和RS3，但是到国内只引进了三厢版；要么是法系车，比如标致308GTI、雷诺梅甘娜RS、雪铁龙DS3Racing这一类精品车型；即便是在国内江河日下的韩系车，人家现代都有i20N、i30N和飞思N等车型。换言之，在咱们的国产品牌当中，除了领克现在推出了02 Hatchback以外，没有一家做出真正的两厢高性能掀背小钢炮，之前2017年上海车展的时候，我在长安的展位上还看到他们展出的逸动R，那时候号称配备2.0T高功率发动机和6AT变速箱，而且那个外观确实能打，结果到现在已经4年过去了，长安逸动R也没正式上市。即便我们把范围放宽，仅仅是去看小钢炮车型或者说高性能车型，你会发现国内似乎也就领克在做，可能有人会说比亚迪的DM-P系列也是主打高性能，但是我这里说的前提，是纯靠燃油发动机来实现较高的功率和扭矩，而不是通过混动系统去获得较高的动力数值。所以，有的时候我自己也很矛盾，一方面我觉得02 Hatchback和03+在性能、工艺和配置上，完全可以再往前进一步，但是另一方面回头看看国内其他厂家的作品，我发现很多时候就像郭德纲在相声里说的那样，不是自己多优秀，都是靠同行的衬托。领克02 Hatchback还有什么竞争对手，高尔夫GTI？领克02 Hatchback有哪些竞争对手，我觉得以目前17.68-18.18万的价格来看，其实对手真的不多，无非就是比它贵一些的高尔夫GTI，还有比它便宜一些的思域Hatchback，如果你就认准了这种性能比较强的两厢小车，那么领克02 Hatchback在同价位中还真就没有对手。首先我们来聊一聊高尔夫GTI，之前我们其实已经聊过这台车，相比于领克02 Hatchback，我觉得高尔夫GTI的主要劣势在于几个方面。第一是价格，因为17.68-18.18万的价格确实会比高尔夫GTI要便宜不少，毕竟之前7代GTI刚出的时候要23.99万，后来7.5代的GTI也卖到了23.42万，所以现在8代GTI大概率不会比这个价格低，哪怕是价格持平，在最后的落地价上还是会远高于02 Hatchback。第二是原厂状态下的性能，我们总说GTI不改不如推下海，但是并不是说每一个去买小钢炮的人都一定会去改装，更不用说高尔夫GTI现在220马力/350牛米的动力参数，显然会比02 Hatchback原厂254马力/350牛米的数据要低一些，换言之，领克02 Hatchback其实瞄准的更多是那些不一定会去改装，但也想开小钢炮的车主，这也是为啥02 Hatchback在外观上做的就有一些改装车的味道。但是，一旦涉及到车辆改装，那么领克02 Hatchback的劣势就显现出来了，我们且不说这台车到底能不能算是一台正经的小钢炮，就车辆后期的升级潜力而言，尤其是动力上的潜力，至少在目前的情况下来看，确实不如大众的EA888系列。首先，所有领克的车辆如果想要进行动力升级，那就只能通过外挂电脑的方式来进行提升，国内现在性价比高一些的也就MAGICPRO这个牌子，受制于原车的硬件限制，提升的数据也比较有限，现在国6的车型用DYNAPACK实测，也就提升35马力/42牛米，而高尔夫GTI刷个一阶程序轻轻松松能做到300马力/440牛米的数据。其次，领克02 Hatchback的整备质量达到了1590KG，而上一代高尔夫GTI的整备质量只有1430KG，哪怕现在8代GTI稍重一些，也会比领克02Hatch轻不少，要知道在小钢炮这个领域里，够轻、够短、够快才是关键。最后，领克02 Hatchback能用的改装件实在是太少了，以至于现在想找一个性能好点的避震器都找不到，主要原因还是车辆的保有量太小了，哪怕你把领克02的改装件都算上，你会发现相比于高尔夫GTI铺天盖地的改装件，领克在改装市场里面的配套产品真的少的可怜。接着我们来聊一聊思域Hatchback，这台车目前定价14.39-16.69万。思域Hatchback这台车很有意思，你看配置表会发现15.99万的手动挡车型竟然是个高配，如果以玩车的角度去看待的话，那么我是不建议你去买CVT版本的思域Hatchback，因为变速箱确实有点不够运动，所以如果你真的想玩两厢版的思域，那就咬牙去买15.99万的手动版本，目前这台车都是平价销售，基本上没什么优惠。实际上，思域这颗代号L15B8的1.5T发动机其实潜力也不小，即使你只刷写最为基础的HONDATA一阶程序，都可以轻松做到233马力/352牛米的机头数据，而且官网明码标价，一阶程序695美金（折合人民币大约4697元），一般改装店都会报价在5000元（含刷程序的设备费和工时费）。同时，思域这台车的改装件极其丰富，常见的避震、轮毂、进气、排气、包围……不论你能想到的，甚至是你想不到的改装件，都可以买到思域专车专用的产品，而且思域这台车好歹也能满足一部分人的JDM情怀，相比于动辄加价10万销售的丰田SUPRA，你是不是觉得思域Hatchback手动版还挺有性价比的？综合而言，其实领克02 Hatchback和高尔夫GTI、思域Hatchback之间其实非常好选，如果你只是想买一台跑的快一点的车，然后也不想去费心费力的改装，那么领克02 Hatchback确实很有性价比；如果你想深入的去玩一台两厢小钢炮，那么就去选择高尔夫GTI吧；至于思域Hatchback这台车……喜欢的早就去买了，不喜欢的再怎么劝也没用。我们认为，领克02 Hatchback应该怎么改？最后，和大家聊一聊领克02 Hatchback的改装方案，为了方便大家阅读，我这里就分成入门级、进阶级和发烧级。这个改装方案只是根据我自己的喜好和经验来进行罗列的，价格和内容仅供各位交流和参考，而且实际上这些产品价格都会有一定的折扣。入门级：国产改色膜-4000元K&N高流量进气风格-700元车贴-15元进阶级：19寸MMX单片锻造轮毂-16000元K&N高流量进气风格-700元RES中尾段电子阀门排气-9400元MOTEK S400刹车皮-1280元HEL刹车钢喉-500元BREMBO DOT4刹车油-150元/瓶发烧级：20寸RAYS G025轮毂-30000元NITTO NT05轮胎（255/35/20）-1900元/条FOGIAGO进气套件-6900元AP9540刹车套装-15000元分体式后轮刹车盘-3500元MAGICPRO外挂电脑-6999元ASPEC中尾段阀门排气-15500元RES头段+前管（带三元催化）-7000元BLOX 12.9级锻造螺丝-1498元狮特底盘强化套装-4040元所以，如果你买了02 Hatchback想拿来玩，我只能说以目前的改装件配套来说，实在是可选择性太低了，而且很多厂家都不做这个车型的产品，相比于高尔夫GTI甚至是思域Hatchback来说，领克的改装市场产品确实少的有些可怜，所以如果有需求的话，还是再等一等吧。可以添加微信46415254加入我们的社群音频图文更新在订阅号： 百车全说每期抽三条留言，每人赠168元的“芥末绿”燃油添加剂一瓶点击订阅，每周三，周六更新会有提醒新听友可以搜索：百车全说2014，百车全说2015，百车全说2016，往期300多个小时的节目可供收听

※ 本文章发布于订阅号：百车全说，订阅号阅读更加方便，欢迎关注前不久，本年度钢炮迷们第二关心的车，也就是“领克02 Hatchback”正式上市，定价17.68-18.18万，有人问第一关心的是什么车，那当然是前不久才聊过的第八代高尔夫GTI。这次的领克02 Hatchback一共就推出了两个版本，分别是17.68万的Halo版和18.18万的Halo驾控套件版，同时，领克还给这两个版本，各提供了101台黑橙配色的首发限量版，也就是一共202台，不过对于去选择02 Hatchback的车主来说，什么颜色并不重要，重要的是能不能买到这台车。为什么这么说，因为现在的首发限量版采用直播的形式在线上发售，据说发售当天3秒售罄，抢到的车主最快将会在6月25号提车。不得不说，领克和吉利现在玩营销都是一把好手，假如你没有抢到首发限量版，那就只能等一等，看看领克之后会怎么去卖这台车，我估计大概率会像之前的领克03+那样，继续通过官网下订单，然后玩一手饥饿营销，毕竟说到底领克02Hatchback是一台小众车，如果不靠饥饿营销去提升一下调性，那不仅价格很难守住，调性也肯定会比现在低很多。我问了一下身边玩车的同好们，其中有不少人都直呼真香，毕竟一台254马力的国产小钢炮起售价只要17.68万，但是，今天我可能要给在座的很多人，尤其是钢炮迷们泼一盆冷水，虽然领克02 Hatchback官方号称“真钢炮”，但它严格意义上来看并不算是钢炮。今天我们就来好好扒一扒这款车，它和领克02有什么区别，三大件强不强？领克在有03+的情况下为什么要出这款车？它与高尔夫GTI相比怎么样，拿到手应该怎么去改？领克02 Hatchback是一款什么样的车？首先，领克02 Hatchback在我看来更像是一台紧凑型跨界车，因为它的本源还是那台紧凑型SUV，换言之这台车只是在领克02的基础上降低了车身高度，然后换装了那套254马力/350牛米的发动机，以及那套8AT变速箱。这台02 Hatchback的尺寸为4458/1890/1486mm，轴距为2702mm，相较于普通领克02，高度从1528mm降低至1486mm，轮眉和轮胎之间的距离也减少了35mm，只剩下三指距离。可能有人对于这个三指的高度没有什么概念，我就这么跟各位去说吧，对于很多普通的轿车或者SUV来说，3指的间距属于正常操作，但是对于一台主打性能的小钢炮来说，这样的车身高度就跟SUV没有什么区别，因为性能玩家想要的是那种贴地飞行的感觉，所谓的通过性其实并不在很多人的考虑范围之内。但是，相比于之前的领克02来说，这台车确实比先前在高度上降低了很多，但是由于领克02原先的车身设计就比较高大，即使再怎么进行降低，还是制约了02 Hatchback在原厂状态下的车身姿态，虽然02 Hatchback并不比高尔夫GTI这样的传统小钢炮高多少，但两台车放在一起，你还会发现02 Hatchback的发动机舱明显高出了一截。所以，领克02 Hatchback并不是传统意义上的小钢炮，现在摆在我们面前的更像是一款低重心的跨界车，如果领克有一天做出了一款真正的钢炮，那就只有一个可能，即基于03+的03+ Hatchback，因为领克03+的先天条件放在那里，明显更适合成为钢炮，或许02 Hatchback只是领克的试水之作，试探一下市场对于这种小众车型的热度，真正的重头戏还没出来。当然，为了与普通02做出更多的区分，这次02 Hatchback在外观上也动了点刀，比如更运动的前包围，整体造型偏向领克03劲版和03+，车尾自带唬人的双边四出排气，车尾也配备了更加明显的尾唇，车顶同样也有一个小尾翼，轮圈也从普通版的17寸或18寸，换成了更大更宽的19寸轮毂，轮胎尺寸也达到了和03+相同的245/40/19。此外，由于普通的02本就是一款非常像跨界车的SUV，所以02Hatchback为了弱化跨界风格并贴近钢炮，将原先前后翼子板上的黑色轮眉变为与车身同色的设计，但轮眉这个东西怎么也不应该出现在钢炮上，虽然有不少媒体在宣传的时候都说这是小宽体，但是我总觉得这就属于收了钱然后说好话的，毕竟你既然是原厂宽体，那你倒是把接缝给去了啊。最后，02 Hatchback在内饰部分全面向03+看齐，不过这次换成橙黑配色了，远比普通02运动，黑色皮质搭配部分的Alcantara面料，整体运动氛围的营造还是很到位的，而且中控饰板也采用与03+类似的黑灰相间特殊纹路，加上橙色饰条、缝线、安全带，这套内饰无论是设计还是用料，个人认为算是同级最强之一，没什么可挑剔的。在配置方面，02 Hatchback也是向着普通02的高配车型看齐，整套主动安全系统、360度全景影像、全速自适应巡航、座椅加热通风、10扬声器燕飞利仕音响……仪表和屏幕与普通02一样，10.25英寸液晶仪表搭配10.25英寸中控屏幕。至于02 Hatchback两个版本之间有什么区别，官方在版本名称里已经表达的很清楚了，这差的5000块其实就差在一套“驾控套件”上，有套件的版本轮圈是锻造的，但单颗实测重量达到了11.2公斤，对于19英寸的锻造轮圈来说实在不轻，此外还多了一个“前舱铝合金横向稳定加强杆”，也就是我们俗称的“顶巴”，理论上可以提高车身刚性，抑制过弯侧倾，但只在极限状态下才会发挥那么一丢丢的作用，对于02 Hatchback这种街道用车来说属于“心情件”，很多玩家去改这东西也是因为好看、不贵，你问他改完有什么区别，他其实也说不出来。同时，之前很多人买03+的时候去选择那个5000元的驾控套件，目的其实就是为了在合法的情况下更换19寸轮毂，因为咱们现行的法规下，不改变轮胎数据就可以随便换轮毂，而02Hatchback现在无论加不加那5000块钱，其实都是用的19寸轮毂和245/40/19的轮胎，以至于对于很多人来说，现在这个5000块的驾控套件看似不贵，但并没有什么实质性的作用。所以，如果你真想买02 Hatchback，我是真的不太推荐各位去选这个5000元的驾控套件，除非领克愿意给换装尺寸更大、宽度更宽的圈胎，否则这5000块钱还不如自己先攒着，然后换一套大品牌的锻造轮毂，数据也会比原厂的更合适，毕竟大多数性能车主，是不愿意看到车子的圈胎缩在叶子板里面的。领克02 Hatchback的三大件强不强，潜力大不大？那么，这次的领克02 Hatchback的三大件，就真的像很多人说的那样，达到性能车的标准了吗，我觉得并没有。我们都知道，领克的高性能系列都会带“+”号，尽管目前只有一款“03+”在售，但是按照这个逻辑，只有被打上“+”号的车，才可以算作各自车系的高性能版本。而到了02 Hatchback这里，无论是官方对性能的宣传力度，还是外观、内饰设计中的运动元素，又或者是这台车在自身车系中的定位，都可以看出这就是02车系的高性能版本，而02 Hatchback之于普通02，非常类似于03+之于普通03，但它为什么不叫“02+”或者“02 Hatchback+”呢？答案可能只有一个：领克自己都不认为02 Hatchback在某些性能的关键指标上可以达到标准。现在02 Hatchback的发动机与03+同款，都是254马力/350牛米的沃尔沃Drive-ET5 2.0T高功率发动机，变速箱是爱信的8AT；而普通02的最强版本，也只是190马力/300牛米的2.0T低功率发动机，匹配的是7速湿式双离合变速箱。所以，02 Hatchback在发动机和变速箱方面与03+保持一致，可以说远强于普通02，并且官方数据只需6.2秒破百，在同价位中算非常劲爆了，只是领克的车在百公里加速一项上，往往官标都非常激进，你也可以理解成虚标。比如03+官标百公里加速5.9秒，可实际上几乎跑不出这个成绩，实测基本上都在6秒多，我查了一下02 Hatchback的实测成绩，尽管这台车有超增压模式，可以把发动机扭提升到380牛米，但是实测最快也要6.85秒，而官标6.9秒的7代半高尔夫GTI实测比它还要快一些。但是，这里面有一个点很容易被人忽略，那就是02 Hatchback的轮胎数据达到了245/40/19，同样作为小钢炮的高尔夫GTI不仅在车重上更轻，而且配备的是一套225/40/18的圈胎，也就是说在百公里加速的时候，GTI所受到圈胎的限制更小，也更容易跑出亮眼的成绩，如果02 Hatchback的圈胎数据和GTI一样，是不是大概率可以跑出比GTI更好的百公里加速成绩？此外，02 Hatchback现在只有前驱版本，而03+标配适时四驱系统，理论上02 Hatchback完全可以配备四驱系统，毕竟普通02也之前推出了四驱版本，但再多一套适时四驱系统对02 Hatchback能有多大提升，我在这里要打一个问号，因为假如你也玩儿过领克03+，你会发现拖后腿的其实是那套变速箱，实在是太“买菜车”了。在底盘部分，02 Hatchback与普通02并无太大区别，根据官方的说法，这台车的悬架弹簧刚度提升50%，副车架衬套刚度提升40%，所以更多偏向细节上的加强，02 Hatchback的整体操控虽然相较于普通02会有提升，最明显的是底盘会更加硬朗，但毕竟是SUV的底子再加上车身高大，所以并不能达到传统钢炮的水准。最后，网上有02 Hatchback的声浪，大家可以去听一下，说白了就是一台家用车，无论在何种模式下，原地轰油门都只能听到发动机的运转声，并没有所谓的“声浪”，我觉得声浪可以算是评判一款车是否是足够性能的标准，有声浪的不一定是性能车，但性能车一定会有声浪。综上所述，虽然02 Hatchback在发动机和变速箱上都达到了03+的水平，但领克的初衷，也许是希望将02 Hatchback打造成一台富有驾驶乐趣的跨界车，而非03+这样比较硬核的性能车，虽然03+在性能车中一点也不硬核，如果领克会出02+ Hatchback，那必然会配备四驱系统，至于车身高度么……这就得看领克愿不愿意花时间去重新设计和匹配了。值得一提的是，现在领克02 Hatchback能用的绞牙避震，也就一些国产的品牌可以选，比如DWD、D2、SF之类的，改完之后就是硬邦邦的感觉，目前很多大牌还没有对应的产品，所以想改避震的我建议还是等一等，或者你如果想玩低趴，那就结合自己的预算，直接去买气动避震就可以了，不过即使是最入门的气动避震套装，也要一万多块钱。领克02 Hatchback与领克03+有什么区别？那么，领克02 Hatchback和领克03+有什么区别，我觉得除了两厢车和三厢车的差别之外，还有领克02 Hatchback在车辆等级划分中属于普通车型，而领克03+属于高性能车型，之前我们在聊AMG的时候就提到过性能等级这个概念，领克现在也是这样在玩，只不过领克目前也只分了普通车型和“+”系列高性能车，而且“+”系列里面也只有一台03+，同时再往上也没有性能更加夸张的车型等级和具体车型了，只能说希望领克再接再厉。由于车辆的等级放在这里，使得领克02 Hatchback只能是一台前驱车，在外观上没有特别夸张的包围，只是基于领克02进行了一些升级和调整，比如四出排气、小宽体、小尾翼等等；而03+却相当于官方改装版本的领克03，不仅动力配置大幅提升，而且做成了一台四驱车，顶配还有夸张的碳纤维包围，据说能将11KG的下压力提升到40KG下压力。同时，领克02 Hatchback的内饰也没有领克03+那么奢华，其中02 Hatchback的内饰只是用了真皮包覆，然后搭配橙色缝线，而03+的内饰规格就做的更高，整台车的内部都被Alcantara翻毛皮包裹起来。这里面有一个细节我觉得很有意思，就是领克在做内饰的时候特别喜欢和外观油漆进行呼应，之前做03+的时候，由于车辆外观颜色用的是“炫燃金”色，所以内饰的缝线、安全带和装饰件都做成黄不黄、绿不绿的颜色，现在的02 Hatchback由于外观是橙色，所以内饰也都有橙色的缝线、安全带和装饰件。在这里也是插一句题外话，我发现领克在做这些车型的时候，总是喜欢在颜色上做一些呼应，可是为啥03+的冠军定制版内饰还是照搬普通03+的配色，难道领克就不能让这个冠军定制版再“细节”一点吗，你如果真觉得灰色做出来不显眼，那弄个红色的缝线也可以啊。简单来说，领克02 Hatchback和领克03+都是基于CMA平台生产，但是领克02 Hatchback实际上是基于领克02这台紧凑型SUV进行打造，而领克03+则是基于领克03这个轿车进行打造，并且由于两台车的等级不同，使得两台车的内饰和外观以及性能配置会有一定的差距。按现在领克的套路来看，我们是不是可以推测一下，今后领克有可能就把旗下的“+”系列弄成像奥迪的系列那样，然后给这些旗下的车型都出个“+”版本，那到时候我们是不是就能看到“01+”、“02+”、“02+Hatchback”、“05+”、“06+”甚至是“09+”，甚至有可能再出现比“+”系列性能等级更高的产品，就类似于奥迪的RS系列，想想都觉得有些激动，希望领克不要让我们失望。领克为啥要做02 Hatchback？我们都知道，领克03+在2019年8月2日晚上正式上市，但是自从03+上市之后，领克已然沉寂了太久，他们需要推出一台全新的高性能车型来吸引大家的目光。这时候，就有一个问题摆在面前：用什么车来做？首先，领克01和领克05肯定要排除掉，因为这两台车实际上都有配备2.0T高功发动机+8AT变速箱+四驱的车型，要知道实际上现在的领克03+用的也是这套动力系统。哪怕我们把即将上市的领克09也算上，但是那台车实际上是对标沃尔沃XC90的SUV，动力配置据说会和XC90类似，而沃尔沃XC90的2.0T高功率版本不仅是机械+涡轮双增压，而且还有48V轻混系统，数据也达到了300马力/420牛米，即便是XC90的低功率版本，用的也是250马力/350牛米的2.0T发动机和8AT变速箱，而且XC90全系都标配的都是全时四驱。所以，对于这几台车来说，现在领克“+”系列用的动力系统反而成了鸡肋，除非能装配更牛X的动力系统，否则这些车型做不做“+”系列的意义不是很大，不过我们是不是可以猜测一下，假如以后领克去做“01+”和“05+”的时候，是不是可以用上XC90那套高功率发动机和全时四驱系统，似乎我在无意之间，就给领克指明了方向。其次，排除掉领克01和领克05之后，领克目前在售车型里只剩下02、03和06了，其中领克03已经有了03+作为性能标杆，以至于领克只能在02和06之间进行抉择，而领克06是用的BMA-evo平台打造，要知道BMA平台下的车型，只能用1.0T或者1.5T发动机，外加PHEV、HEV和MHEV这些新能源动力，除非领克愿意进行大量的重新设计，否则领克06就无法使用那套2.0T+8AT的动力系统，更不用说四驱系统了。所以，摆在领克面前的，就只剩下了领克02一台车，加上领克02之前哪怕是18.88万的2.0T DCT四驱劲PRO版本，配的也不过就是一颗190马力/300牛米的2.0T发动机，还有一套7速湿式双离合变速箱，而领克02本身是基于CMA平台打造，使得这台车在动力系统上有了可操作的空间，而且不需要去进行大量的重新设计，省时省力还省钱。再者，之前也有玩家用领克02进行改装，不仅将原车的黑色塑料板变成了和车身同色，而且还把车身高度降低，然后配上了大尺寸的轮毂和定做的包围，很多人看完改装之后的样子，发现原来领克02的身上还有一些小钢炮的味道在里面，我猜测领克的厂家应该也看到过相关的信息，从而促使他们去做了这台02 Hatchback。最后，就是市场层面的因素，目前国内市场上在售的纯种两厢掀背小钢炮，你会发现能买到的车型特别少，要么就是像奔驰AMG A45/A45S那样价格高高在上，很多地方想要买车还得加价；要么就是像本田思域TYPE-R那样没有官方正式进口，然后只能买平行进口车，价格也被炒到了天上；要么就是像高尔夫GTI或者高尔夫R这种，虽然整体性价比还算可以，而且有情怀加持，但是能跑多快完全取决于你的动手能力，属于“买车不贵改车贵”的代表。撇开车辆的价格不谈，你会发现无论是在售还是停售的两厢小钢炮车型，它们要么是日系车，比如思域TYPE-R之类的车型；要么是美系车，比如福克斯ST和福克斯RS这种；要么是德系车，比如奔驰有A45系列，宝马之前也有进口到国内的M135i和M140i，奥迪的槽点比较多，海外明明有两厢版本的S3和RS3，但是到国内只引进了三厢版；要么是法系车，比如标致308GTI、雷诺梅甘娜RS、雪铁龙DS3Racing这一类精品车型；即便是在国内江河日下的韩系车，人家现代都有i20N、i30N和飞思N等车型。换言之，在咱们的国产品牌当中，除了领克现在推出了02 Hatchback以外，没有一家做出真正的两厢高性能掀背小钢炮，之前2017年上海车展的时候，我在长安的展位上还看到他们展出的逸动R，那时候号称配备2.0T高功率发动机和6AT变速箱，而且那个外观确实能打，结果到现在已经4年过去了，长安逸动R也没正式上市。即便我们把范围放宽，仅仅是去看小钢炮车型或者说高性能车型，你会发现国内似乎也就领克在做，可能有人会说比亚迪的DM-P系列也是主打高性能，但是我这里说的前提，是纯靠燃油发动机来实现较高的功率和扭矩，而不是通过混动系统去获得较高的动力数值。所以，有的时候我自己也很矛盾，一方面我觉得02 Hatchback和03+在性能、工艺和配置上，完全可以再往前进一步，但是另一方面回头看看国内其他厂家的作品，我发现很多时候就像郭德纲在相声里说的那样，不是自己多优秀，都是靠同行的衬托。领克02 Hatchback还有什么竞争对手，高尔夫GTI？领克02 Hatchback有哪些竞争对手，我觉得以目前17.68-18.18万的价格来看，其实对手真的不多，无非就是比它贵一些的高尔夫GTI，还有比它便宜一些的思域Hatchback，如果你就认准了这种性能比较强的两厢小车，那么领克02 Hatchback在同价位中还真就没有对手。首先我们来聊一聊高尔夫GTI，之前我们其实已经聊过这台车，相比于领克02 Hatchback，我觉得高尔夫GTI的主要劣势在于几个方面。第一是价格，因为17.68-18.18万的价格确实会比高尔夫GTI要便宜不少，毕竟之前7代GTI刚出的时候要23.99万，后来7.5代的GTI也卖到了23.42万，所以现在8代GTI大概率不会比这个价格低，哪怕是价格持平，在最后的落地价上还是会远高于02 Hatchback。第二是原厂状态下的性能，我们总说GTI不改不如推下海，但是并不是说每一个去买小钢炮的人都一定会去改装，更不用说高尔夫GTI现在220马力/350牛米的动力参数，显然会比02 Hatchback原厂254马力/350牛米的数据要低一些，换言之，领克02 Hatchback其实瞄准的更多是那些不一定会去改装，但也想开小钢炮的车主，这也是为啥02 Hatchback在外观上做的就有一些改装车的味道。但是，一旦涉及到车辆改装，那么领克02 Hatchback的劣势就显现出来了，我们且不说这台车到底能不能算是一台正经的小钢炮，就车辆后期的升级潜力而言，尤其是动力上的潜力，至少在目前的情况下来看，确实不如大众的EA888系列。首先，所有领克的车辆如果想要进行动力升级，那就只能通过外挂电脑的方式来进行提升，国内现在性价比高一些的也就MAGICPRO这个牌子，受制于原车的硬件限制，提升的数据也比较有限，现在国6的车型用DYNAPACK实测，也就提升35马力/42牛米，而高尔夫GTI刷个一阶程序轻轻松松能做到300马力/440牛米的数据。其次，领克02 Hatchback的整备质量达到了1590KG，而上一代高尔夫GTI的整备质量只有1430KG，哪怕现在8代GTI稍重一些，也会比领克02Hatch轻不少，要知道在小钢炮这个领域里，够轻、够短、够快才是关键。最后，领克02 Hatchback能用的改装件实在是太少了，以至于现在想找一个性能好点的避震器都找不到，主要原因还是车辆的保有量太小了，哪怕你把领克02的改装件都算上，你会发现相比于高尔夫GTI铺天盖地的改装件，领克在改装市场里面的配套产品真的少的可怜。接着我们来聊一聊思域Hatchback，这台车目前定价14.39-16.69万。思域Hatchback这台车很有意思，你看配置表会发现15.99万的手动挡车型竟然是个高配，如果以玩车的角度去看待的话，那么我是不建议你去买CVT版本的思域Hatchback，因为变速箱确实有点不够运动，所以如果你真的想玩两厢版的思域，那就咬牙去买15.99万的手动版本，目前这台车都是平价销售，基本上没什么优惠。实际上，思域这颗代号L15B8的1.5T发动机其实潜力也不小，即使你只刷写最为基础的HONDATA一阶程序，都可以轻松做到233马力/352牛米的机头数据，而且官网明码标价，一阶程序695美金（折合人民币大约4697元），一般改装店都会报价在5000元（含刷程序的设备费和工时费）。同时，思域这台车的改装件极其丰富，常见的避震、轮毂、进气、排气、包围……不论你能想到的，甚至是你想不到的改装件，都可以买到思域专车专用的产品，而且思域这台车好歹也能满足一部分人的JDM情怀，相比于动辄加价10万销售的丰田SUPRA，你是不是觉得思域Hatchback手动版还挺有性价比的？综合而言，其实领克02 Hatchback和高尔夫GTI、思域Hatchback之间其实非常好选，如果你只是想买一台跑的快一点的车，然后也不想去费心费力的改装，那么领克02 Hatchback确实很有性价比；如果你想深入的去玩一台两厢小钢炮，那么就去选择高尔夫GTI吧；至于思域Hatchback这台车……喜欢的早就去买了，不喜欢的再怎么劝也没用。我们认为，领克02 Hatchback应该怎么改？最后，和大家聊一聊领克02 Hatchback的改装方案，为了方便大家阅读，我这里就分成入门级、进阶级和发烧级。这个改装方案只是根据我自己的喜好和经验来进行罗列的，价格和内容仅供各位交流和参考，而且实际上这些产品价格都会有一定的折扣。入门级：国产改色膜-4000元K&N高流量进气风格-700元车贴-15元进阶级：19寸MMX单片锻造轮毂-16000元K&N高流量进气风格-700元RES中尾段电子阀门排气-9400元MOTEK S400刹车皮-1280元HEL刹车钢喉-500元BREMBO DOT4刹车油-150元/瓶发烧级：20寸RAYS G025轮毂-30000元NITTO NT05轮胎（255/35/20）-1900元/条FOGIAGO进气套件-6900元AP9540刹车套装-15000元分体式后轮刹车盘-3500元MAGICPRO外挂电脑-6999元ASPEC中尾段阀门排气-15500元RES头段+前管（带三元催化）-7000元BLOX 12.9级锻造螺丝-1498元狮特底盘强化套装-4040元所以，如果你买了02 Hatchback想拿来玩，我只能说以目前的改装件配套来说，实在是可选择性太低了，而且很多厂家都不做这个车型的产品，相比于高尔夫GTI甚至是思域Hatchback来说，领克的改装市场产品确实少的有些可怜，所以如果有需求的话，还是再等一等吧。可以添加微信46415254加入我们的社群音频图文更新在订阅号： 百车全说每期抽三条留言，每人赠168元的“芥末绿”燃油添加剂一瓶点击订阅，每周三，周六更新会有提醒新听友可以搜索：百车全说2014，百车全说2015，百车全说2016，往期300多个小时的节目可供收听

※ 本文章发布于订阅号：百车全说，订阅号阅读更加方便，欢迎关注前不久，本年度钢炮迷们第二关心的车，也就是“领克02 Hatchback”正式上市，定价17.68-18.18万，有人问第一关心的是什么车，那当然是前不久才聊过的第八代高尔夫GTI。这次的领克02 Hatchback一共就推出了两个版本，分别是17.68万的Halo版和18.18万的Halo驾控套件版，同时，领克还给这两个版本，各提供了101台黑橙配色的首发限量版，也就是一共202台，不过对于去选择02 Hatchback的车主来说，什么颜色并不重要，重要的是能不能买到这台车。为什么这么说，因为现在的首发限量版采用直播的形式在线上发售，据说发售当天3秒售罄，抢到的车主最快将会在6月25号提车。不得不说，领克和吉利现在玩营销都是一把好手，假如你没有抢到首发限量版，那就只能等一等，看看领克之后会怎么去卖这台车，我估计大概率会像之前的领克03+那样，继续通过官网下订单，然后玩一手饥饿营销，毕竟说到底领克02Hatchback是一台小众车，如果不靠饥饿营销去提升一下调性，那不仅价格很难守住，调性也肯定会比现在低很多。我问了一下身边玩车的同好们，其中有不少人都直呼真香，毕竟一台254马力的国产小钢炮起售价只要17.68万，但是，今天我可能要给在座的很多人，尤其是钢炮迷们泼一盆冷水，虽然领克02 Hatchback官方号称“真钢炮”，但它严格意义上来看并不算是钢炮。今天我们就来好好扒一扒这款车，它和领克02有什么区别，三大件强不强？领克在有03+的情况下为什么要出这款车？它与高尔夫GTI相比怎么样，拿到手应该怎么去改？领克02 Hatchback是一款什么样的车？首先，领克02 Hatchback在我看来更像是一台紧凑型跨界车，因为它的本源还是那台紧凑型SUV，换言之这台车只是在领克02的基础上降低了车身高度，然后换装了那套254马力/350牛米的发动机，以及那套8AT变速箱。这台02 Hatchback的尺寸为4458/1890/1486mm，轴距为2702mm，相较于普通领克02，高度从1528mm降低至1486mm，轮眉和轮胎之间的距离也减少了35mm，只剩下三指距离。可能有人对于这个三指的高度没有什么概念，我就这么跟各位去说吧，对于很多普通的轿车或者SUV来说，3指的间距属于正常操作，但是对于一台主打性能的小钢炮来说，这样的车身高度就跟SUV没有什么区别，因为性能玩家想要的是那种贴地飞行的感觉，所谓的通过性其实并不在很多人的考虑范围之内。但是，相比于之前的领克02来说，这台车确实比先前在高度上降低了很多，但是由于领克02原先的车身设计就比较高大，即使再怎么进行降低，还是制约了02 Hatchback在原厂状态下的车身姿态，虽然02 Hatchback并不比高尔夫GTI这样的传统小钢炮高多少，但两台车放在一起，你还会发现02 Hatchback的发动机舱明显高出了一截。所以，领克02 Hatchback并不是传统意义上的小钢炮，现在摆在我们面前的更像是一款低重心的跨界车，如果领克有一天做出了一款真正的钢炮，那就只有一个可能，即基于03+的03+ Hatchback，因为领克03+的先天条件放在那里，明显更适合成为钢炮，或许02 Hatchback只是领克的试水之作，试探一下市场对于这种小众车型的热度，真正的重头戏还没出来。当然，为了与普通02做出更多的区分，这次02 Hatchback在外观上也动了点刀，比如更运动的前包围，整体造型偏向领克03劲版和03+，车尾自带唬人的双边四出排气，车尾也配备了更加明显的尾唇，车顶同样也有一个小尾翼，轮圈也从普通版的17寸或18寸，换成了更大更宽的19寸轮毂，轮胎尺寸也达到了和03+相同的245/40/19。此外，由于普通的02本就是一款非常像跨界车的SUV，所以02Hatchback为了弱化跨界风格并贴近钢炮，将原先前后翼子板上的黑色轮眉变为与车身同色的设计，但轮眉这个东西怎么也不应该出现在钢炮上，虽然有不少媒体在宣传的时候都说这是小宽体，但是我总觉得这就属于收了钱然后说好话的，毕竟你既然是原厂宽体，那你倒是把接缝给去了啊。最后，02 Hatchback在内饰部分全面向03+看齐，不过这次换成橙黑配色了，远比普通02运动，黑色皮质搭配部分的Alcantara面料，整体运动氛围的营造还是很到位的，而且中控饰板也采用与03+类似的黑灰相间特殊纹路，加上橙色饰条、缝线、安全带，这套内饰无论是设计还是用料，个人认为算是同级最强之一，没什么可挑剔的。在配置方面，02 Hatchback也是向着普通02的高配车型看齐，整套主动安全系统、360度全景影像、全速自适应巡航、座椅加热通风、10扬声器燕飞利仕音响……仪表和屏幕与普通02一样，10.25英寸液晶仪表搭配10.25英寸中控屏幕。至于02 Hatchback两个版本之间有什么区别，官方在版本名称里已经表达的很清楚了，这差的5000块其实就差在一套“驾控套件”上，有套件的版本轮圈是锻造的，但单颗实测重量达到了11.2公斤，对于19英寸的锻造轮圈来说实在不轻，此外还多了一个“前舱铝合金横向稳定加强杆”，也就是我们俗称的“顶巴”，理论上可以提高车身刚性，抑制过弯侧倾，但只在极限状态下才会发挥那么一丢丢的作用，对于02 Hatchback这种街道用车来说属于“心情件”，很多玩家去改这东西也是因为好看、不贵，你问他改完有什么区别，他其实也说不出来。同时，之前很多人买03+的时候去选择那个5000元的驾控套件，目的其实就是为了在合法的情况下更换19寸轮毂，因为咱们现行的法规下，不改变轮胎数据就可以随便换轮毂，而02Hatchback现在无论加不加那5000块钱，其实都是用的19寸轮毂和245/40/19的轮胎，以至于对于很多人来说，现在这个5000块的驾控套件看似不贵，但并没有什么实质性的作用。所以，如果你真想买02 Hatchback，我是真的不太推荐各位去选这个5000元的驾控套件，除非领克愿意给换装尺寸更大、宽度更宽的圈胎，否则这5000块钱还不如自己先攒着，然后换一套大品牌的锻造轮毂，数据也会比原厂的更合适，毕竟大多数性能车主，是不愿意看到车子的圈胎缩在叶子板里面的。领克02 Hatchback的三大件强不强，潜力大不大？那么，这次的领克02 Hatchback的三大件，就真的像很多人说的那样，达到性能车的标准了吗，我觉得并没有。我们都知道，领克的高性能系列都会带“+”号，尽管目前只有一款“03+”在售，但是按照这个逻辑，只有被打上“+”号的车，才可以算作各自车系的高性能版本。而到了02 Hatchback这里，无论是官方对性能的宣传力度，还是外观、内饰设计中的运动元素，又或者是这台车在自身车系中的定位，都可以看出这就是02车系的高性能版本，而02 Hatchback之于普通02，非常类似于03+之于普通03，但它为什么不叫“02+”或者“02 Hatchback+”呢？答案可能只有一个：领克自己都不认为02 Hatchback在某些性能的关键指标上可以达到标准。现在02 Hatchback的发动机与03+同款，都是254马力/350牛米的沃尔沃Drive-ET5 2.0T高功率发动机，变速箱是爱信的8AT；而普通02的最强版本，也只是190马力/300牛米的2.0T低功率发动机，匹配的是7速湿式双离合变速箱。所以，02 Hatchback在发动机和变速箱方面与03+保持一致，可以说远强于普通02，并且官方数据只需6.2秒破百，在同价位中算非常劲爆了，只是领克的车在百公里加速一项上，往往官标都非常激进，你也可以理解成虚标。比如03+官标百公里加速5.9秒，可实际上几乎跑不出这个成绩，实测基本上都在6秒多，我查了一下02 Hatchback的实测成绩，尽管这台车有超增压模式，可以把发动机扭提升到380牛米，但是实测最快也要6.85秒，而官标6.9秒的7代半高尔夫GTI实测比它还要快一些。但是，这里面有一个点很容易被人忽略，那就是02 Hatchback的轮胎数据达到了245/40/19，同样作为小钢炮的高尔夫GTI不仅在车重上更轻，而且配备的是一套225/40/18的圈胎，也就是说在百公里加速的时候，GTI所受到圈胎的限制更小，也更容易跑出亮眼的成绩，如果02 Hatchback的圈胎数据和GTI一样，是不是大概率可以跑出比GTI更好的百公里加速成绩？此外，02 Hatchback现在只有前驱版本，而03+标配适时四驱系统，理论上02 Hatchback完全可以配备四驱系统，毕竟普通02也之前推出了四驱版本，但再多一套适时四驱系统对02 Hatchback能有多大提升，我在这里要打一个问号，因为假如你也玩儿过领克03+，你会发现拖后腿的其实是那套变速箱，实在是太“买菜车”了。在底盘部分，02 Hatchback与普通02并无太大区别，根据官方的说法，这台车的悬架弹簧刚度提升50%，副车架衬套刚度提升40%，所以更多偏向细节上的加强，02 Hatchback的整体操控虽然相较于普通02会有提升，最明显的是底盘会更加硬朗，但毕竟是SUV的底子再加上车身高大，所以并不能达到传统钢炮的水准。最后，网上有02 Hatchback的声浪，大家可以去听一下，说白了就是一台家用车，无论在何种模式下，原地轰油门都只能听到发动机的运转声，并没有所谓的“声浪”，我觉得声浪可以算是评判一款车是否是足够性能的标准，有声浪的不一定是性能车，但性能车一定会有声浪。综上所述，虽然02 Hatchback在发动机和变速箱上都达到了03+的水平，但领克的初衷，也许是希望将02 Hatchback打造成一台富有驾驶乐趣的跨界车，而非03+这样比较硬核的性能车，虽然03+在性能车中一点也不硬核，如果领克会出02+ Hatchback，那必然会配备四驱系统，至于车身高度么……这就得看领克愿不愿意花时间去重新设计和匹配了。值得一提的是，现在领克02 Hatchback能用的绞牙避震，也就一些国产的品牌可以选，比如DWD、D2、SF之类的，改完之后就是硬邦邦的感觉，目前很多大牌还没有对应的产品，所以想改避震的我建议还是等一等，或者你如果想玩低趴，那就结合自己的预算，直接去买气动避震就可以了，不过即使是最入门的气动避震套装，也要一万多块钱。领克02 Hatchback与领克03+有什么区别？那么，领克02 Hatchback和领克03+有什么区别，我觉得除了两厢车和三厢车的差别之外，还有领克02 Hatchback在车辆等级划分中属于普通车型，而领克03+属于高性能车型，之前我们在聊AMG的时候就提到过性能等级这个概念，领克现在也是这样在玩，只不过领克目前也只分了普通车型和“+”系列高性能车，而且“+”系列里面也只有一台03+，同时再往上也没有性能更加夸张的车型等级和具体车型了，只能说希望领克再接再厉。由于车辆的等级放在这里，使得领克02 Hatchback只能是一台前驱车，在外观上没有特别夸张的包围，只是基于领克02进行了一些升级和调整，比如四出排气、小宽体、小尾翼等等；而03+却相当于官方改装版本的领克03，不仅动力配置大幅提升，而且做成了一台四驱车，顶配还有夸张的碳纤维包围，据说能将11KG的下压力提升到40KG下压力。同时，领克02 Hatchback的内饰也没有领克03+那么奢华，其中02 Hatchback的内饰只是用了真皮包覆，然后搭配橙色缝线，而03+的内饰规格就做的更高，整台车的内部都被Alcantara翻毛皮包裹起来。这里面有一个细节我觉得很有意思，就是领克在做内饰的时候特别喜欢和外观油漆进行呼应，之前做03+的时候，由于车辆外观颜色用的是“炫燃金”色，所以内饰的缝线、安全带和装饰件都做成黄不黄、绿不绿的颜色，现在的02 Hatchback由于外观是橙色，所以内饰也都有橙色的缝线、安全带和装饰件。在这里也是插一句题外话，我发现领克在做这些车型的时候，总是喜欢在颜色上做一些呼应，可是为啥03+的冠军定制版内饰还是照搬普通03+的配色，难道领克就不能让这个冠军定制版再“细节”一点吗，你如果真觉得灰色做出来不显眼，那弄个红色的缝线也可以啊。简单来说，领克02 Hatchback和领克03+都是基于CMA平台生产，但是领克02 Hatchback实际上是基于领克02这台紧凑型SUV进行打造，而领克03+则是基于领克03这个轿车进行打造，并且由于两台车的等级不同，使得两台车的内饰和外观以及性能配置会有一定的差距。按现在领克的套路来看，我们是不是可以推测一下，今后领克有可能就把旗下的“+”系列弄成像奥迪的系列那样，然后给这些旗下的车型都出个“+”版本，那到时候我们是不是就能看到“01+”、“02+”、“02+Hatchback”、“05+”、“06+”甚至是“09+”，甚至有可能再出现比“+”系列性能等级更高的产品，就类似于奥迪的RS系列，想想都觉得有些激动，希望领克不要让我们失望。领克为啥要做02 Hatchback？我们都知道，领克03+在2019年8月2日晚上正式上市，但是自从03+上市之后，领克已然沉寂了太久，他们需要推出一台全新的高性能车型来吸引大家的目光。这时候，就有一个问题摆在面前：用什么车来做？首先，领克01和领克05肯定要排除掉，因为这两台车实际上都有配备2.0T高功发动机+8AT变速箱+四驱的车型，要知道实际上现在的领克03+用的也是这套动力系统。哪怕我们把即将上市的领克09也算上，但是那台车实际上是对标沃尔沃XC90的SUV，动力配置据说会和XC90类似，而沃尔沃XC90的2.0T高功率版本不仅是机械+涡轮双增压，而且还有48V轻混系统，数据也达到了300马力/420牛米，即便是XC90的低功率版本，用的也是250马力/350牛米的2.0T发动机和8AT变速箱，而且XC90全系都标配的都是全时四驱。所以，对于这几台车来说，现在领克“+”系列用的动力系统反而成了鸡肋，除非能装配更牛X的动力系统，否则这些车型做不做“+”系列的意义不是很大，不过我们是不是可以猜测一下，假如以后领克去做“01+”和“05+”的时候，是不是可以用上XC90那套高功率发动机和全时四驱系统，似乎我在无意之间，就给领克指明了方向。其次，排除掉领克01和领克05之后，领克目前在售车型里只剩下02、03和06了，其中领克03已经有了03+作为性能标杆，以至于领克只能在02和06之间进行抉择，而领克06是用的BMA-evo平台打造，要知道BMA平台下的车型，只能用1.0T或者1.5T发动机，外加PHEV、HEV和MHEV这些新能源动力，除非领克愿意进行大量的重新设计，否则领克06就无法使用那套2.0T+8AT的动力系统，更不用说四驱系统了。所以，摆在领克面前的，就只剩下了领克02一台车，加上领克02之前哪怕是18.88万的2.0T DCT四驱劲PRO版本，配的也不过就是一颗190马力/300牛米的2.0T发动机，还有一套7速湿式双离合变速箱，而领克02本身是基于CMA平台打造，使得这台车在动力系统上有了可操作的空间，而且不需要去进行大量的重新设计，省时省力还省钱。再者，之前也有玩家用领克02进行改装，不仅将原车的黑色塑料板变成了和车身同色，而且还把车身高度降低，然后配上了大尺寸的轮毂和定做的包围，很多人看完改装之后的样子，发现原来领克02的身上还有一些小钢炮的味道在里面，我猜测领克的厂家应该也看到过相关的信息，从而促使他们去做了这台02 Hatchback。最后，就是市场层面的因素，目前国内市场上在售的纯种两厢掀背小钢炮，你会发现能买到的车型特别少，要么就是像奔驰AMG A45/A45S那样价格高高在上，很多地方想要买车还得加价；要么就是像本田思域TYPE-R那样没有官方正式进口，然后只能买平行进口车，价格也被炒到了天上；要么就是像高尔夫GTI或者高尔夫R这种，虽然整体性价比还算可以，而且有情怀加持，但是能跑多快完全取决于你的动手能力，属于“买车不贵改车贵”的代表。撇开车辆的价格不谈，你会发现无论是在售还是停售的两厢小钢炮车型，它们要么是日系车，比如思域TYPE-R之类的车型；要么是美系车，比如福克斯ST和福克斯RS这种；要么是德系车，比如奔驰有A45系列，宝马之前也有进口到国内的M135i和M140i，奥迪的槽点比较多，海外明明有两厢版本的S3和RS3，但是到国内只引进了三厢版；要么是法系车，比如标致308GTI、雷诺梅甘娜RS、雪铁龙DS3Racing这一类精品车型；即便是在国内江河日下的韩系车，人家现代都有i20N、i30N和飞思N等车型。换言之，在咱们的国产品牌当中，除了领克现在推出了02 Hatchback以外，没有一家做出真正的两厢高性能掀背小钢炮，之前2017年上海车展的时候，我在长安的展位上还看到他们展出的逸动R，那时候号称配备2.0T高功率发动机和6AT变速箱，而且那个外观确实能打，结果到现在已经4年过去了，长安逸动R也没正式上市。即便我们把范围放宽，仅仅是去看小钢炮车型或者说高性能车型，你会发现国内似乎也就领克在做，可能有人会说比亚迪的DM-P系列也是主打高性能，但是我这里说的前提，是纯靠燃油发动机来实现较高的功率和扭矩，而不是通过混动系统去获得较高的动力数值。所以，有的时候我自己也很矛盾，一方面我觉得02 Hatchback和03+在性能、工艺和配置上，完全可以再往前进一步，但是另一方面回头看看国内其他厂家的作品，我发现很多时候就像郭德纲在相声里说的那样，不是自己多优秀，都是靠同行的衬托。领克02 Hatchback还有什么竞争对手，高尔夫GTI？领克02 Hatchback有哪些竞争对手，我觉得以目前17.68-18.18万的价格来看，其实对手真的不多，无非就是比它贵一些的高尔夫GTI，还有比它便宜一些的思域Hatchback，如果你就认准了这种性能比较强的两厢小车，那么领克02 Hatchback在同价位中还真就没有对手。首先我们来聊一聊高尔夫GTI，之前我们其实已经聊过这台车，相比于领克02 Hatchback，我觉得高尔夫GTI的主要劣势在于几个方面。第一是价格，因为17.68-18.18万的价格确实会比高尔夫GTI要便宜不少，毕竟之前7代GTI刚出的时候要23.99万，后来7.5代的GTI也卖到了23.42万，所以现在8代GTI大概率不会比这个价格低，哪怕是价格持平，在最后的落地价上还是会远高于02 Hatchback。第二是原厂状态下的性能，我们总说GTI不改不如推下海，但是并不是说每一个去买小钢炮的人都一定会去改装，更不用说高尔夫GTI现在220马力/350牛米的动力参数，显然会比02 Hatchback原厂254马力/350牛米的数据要低一些，换言之，领克02 Hatchback其实瞄准的更多是那些不一定会去改装，但也想开小钢炮的车主，这也是为啥02 Hatchback在外观上做的就有一些改装车的味道。但是，一旦涉及到车辆改装，那么领克02 Hatchback的劣势就显现出来了，我们且不说这台车到底能不能算是一台正经的小钢炮，就车辆后期的升级潜力而言，尤其是动力上的潜力，至少在目前的情况下来看，确实不如大众的EA888系列。首先，所有领克的车辆如果想要进行动力升级，那就只能通过外挂电脑的方式来进行提升，国内现在性价比高一些的也就MAGICPRO这个牌子，受制于原车的硬件限制，提升的数据也比较有限，现在国6的车型用DYNAPACK实测，也就提升35马力/42牛米，而高尔夫GTI刷个一阶程序轻轻松松能做到300马力/440牛米的数据。其次，领克02 Hatchback的整备质量达到了1590KG，而上一代高尔夫GTI的整备质量只有1430KG，哪怕现在8代GTI稍重一些，也会比领克02Hatch轻不少，要知道在小钢炮这个领域里，够轻、够短、够快才是关键。最后，领克02 Hatchback能用的改装件实在是太少了，以至于现在想找一个性能好点的避震器都找不到，主要原因还是车辆的保有量太小了，哪怕你把领克02的改装件都算上，你会发现相比于高尔夫GTI铺天盖地的改装件，领克在改装市场里面的配套产品真的少的可怜。接着我们来聊一聊思域Hatchback，这台车目前定价14.39-16.69万。思域Hatchback这台车很有意思，你看配置表会发现15.99万的手动挡车型竟然是个高配，如果以玩车的角度去看待的话，那么我是不建议你去买CVT版本的思域Hatchback，因为变速箱确实有点不够运动，所以如果你真的想玩两厢版的思域，那就咬牙去买15.99万的手动版本，目前这台车都是平价销售，基本上没什么优惠。实际上，思域这颗代号L15B8的1.5T发动机其实潜力也不小，即使你只刷写最为基础的HONDATA一阶程序，都可以轻松做到233马力/352牛米的机头数据，而且官网明码标价，一阶程序695美金（折合人民币大约4697元），一般改装店都会报价在5000元（含刷程序的设备费和工时费）。同时，思域这台车的改装件极其丰富，常见的避震、轮毂、进气、排气、包围……不论你能想到的，甚至是你想不到的改装件，都可以买到思域专车专用的产品，而且思域这台车好歹也能满足一部分人的JDM情怀，相比于动辄加价10万销售的丰田SUPRA，你是不是觉得思域Hatchback手动版还挺有性价比的？综合而言，其实领克02 Hatchback和高尔夫GTI、思域Hatchback之间其实非常好选，如果你只是想买一台跑的快一点的车，然后也不想去费心费力的改装，那么领克02 Hatchback确实很有性价比；如果你想深入的去玩一台两厢小钢炮，那么就去选择高尔夫GTI吧；至于思域Hatchback这台车……喜欢的早就去买了，不喜欢的再怎么劝也没用。我们认为，领克02 Hatchback应该怎么改？最后，和大家聊一聊领克02 Hatchback的改装方案，为了方便大家阅读，我这里就分成入门级、进阶级和发烧级。这个改装方案只是根据我自己的喜好和经验来进行罗列的，价格和内容仅供各位交流和参考，而且实际上这些产品价格都会有一定的折扣。入门级：国产改色膜-4000元K&N高流量进气风格-700元车贴-15元进阶级：19寸MMX单片锻造轮毂-16000元K&N高流量进气风格-700元RES中尾段电子阀门排气-9400元MOTEK S400刹车皮-1280元HEL刹车钢喉-500元BREMBO DOT4刹车油-150元/瓶发烧级：20寸RAYS G025轮毂-30000元NITTO NT05轮胎（255/35/20）-1900元/条FOGIAGO进气套件-6900元AP9540刹车套装-15000元分体式后轮刹车盘-3500元MAGICPRO外挂电脑-6999元ASPEC中尾段阀门排气-15500元RES头段+前管（带三元催化）-7000元BLOX 12.9级锻造螺丝-1498元狮特底盘强化套装-4040元所以，如果你买了02 Hatchback想拿来玩，我只能说以目前的改装件配套来说，实在是可选择性太低了，而且很多厂家都不做这个车型的产品，相比于高尔夫GTI甚至是思域Hatchback来说，领克的改装市场产品确实少的有些可怜，所以如果有需求的话，还是再等一等吧。可以添加微信46415254加入我们的社群音频图文更新在订阅号： 百车全说每期抽三条留言，每人赠168元的“芥末绿”燃油添加剂一瓶点击订阅，每周三，周六更新会有提醒新听友可以搜索：百车全说2014，百车全说2015，百车全说2016，往期300多个小时的节目可供收听

Mars has been the destination for so many of our spacecraft, and for good reason, it's probably the most Earthlike place in the Solar System, with water ice on its surface and reservoirs of the liquid beneath the surface. If we're going to find life, Mars might be the place. But the tiny moons orbiting Mars, Phobos and Deimos, are scientifically fascinating on their own, and so far, a mission has never reached them. Last week, Japan announced that they've greenlit their Martian Moon eXploration mission, or MMX, which will launch an orbiter, lander and maybe even a rover to Phobos in 2024, returning samples back to Earth by the end of the decade. Our Book is out! https://www.amazon.com/Universe-Today-Ultimate-Viewing-Cosmos/dp/1624145442/ Audio Podcast version: ITunes: https://itunes.apple.com/us/podcast/universe-today-guide-to-space-audio/id794058155?mt=2 RSS: https://www.universetoday.com/audio Weekly email newsletter: https://www.universetoday.com/newsletter Weekly Space Hangout: https://www.youtube.com/channel/UC0-KklSGlCiJDwOPdR2EUcg/ Astronomy Cast: https://www.youtube.com/channel/UCUHI67dh9jEO2rvK--MdCSg Support us at https://www.patreon.com/universetoday More stories at https://www.universetoday.com/ Twitch: https://twitch.tv/fcain Twitter: https://twitter.com/universetoday Facebook: https://www.facebook.com/universetoday Instagram - https://instagram.com/universetoday Team: Fraser Cain - @fcain / frasercain@gmail.com Karla Thompson - @karlaii / https://www.youtube.com/channel/UCEItkORQYd4Wf0TpgYI_1fw Chad Weber - weber.chad@gmail.com References: http://mmx.isas.jaxa.jp/en/ http://www.hayabusa2.jaxa.jp/en/ https://www.universetoday.com/145054/japan-is-sending-a-lander-to-phobos/ https://sci.esa.int/web/rosetta https://solarsystem.nasa.gov/missions/hayabusa/in-depth/ http://mmx-news.isas.jaxa.jp/?p=1016&lang=en https://solarsystem.nasa.gov/moons/mars-moons/phobos/in-depth/ https://solarsystem.nasa.gov/missions/phobos-grunt/in-depth/ https://www.jpl.nasa.gov/spaceimages/details.php?id=PIA21837 https://www.jpl.nasa.gov/news/news.php?feature=6965 https://www.jpl.nasa.gov/spaceimages/details.php?id=PIA04746 https://www.jpl.nasa.gov/news/news.php?feaSupport Universe Today Podcast

Welcome back! This time on GameDev Breakdown we're discussing the finer points of tutorials in games, and yes, whether or not they even have a rightful place in them. That idea may surprise you, unless you spend any time talking about development on Twitter where it's become oddly commonplace. This idea comes from a well-intentioned place. As games and players have matured, we've seen a lot of games with subtler, more innovative introductions. As seen in one of the tweets above, for some reason people who like attacking game designers like bringing up the introductory stage of Mega Man X. I generally go out of my way not to criticize the work of other designers, but I would be very hesitant to set up an introductory stage like what Mega Man X features. For one thing, MMX seems to depend on the player having played previous games in the series and having some sense of what's going on. It leaves players to experiment with what amounts to an unusually easy level, mashing buttons and experimenting with enemies and mechanics along the way. Even at that, I find the level visually confusing--quick, you just started, here comes some cars! Just kidding they can't hurt you--and I don't agree that players wouldn't be better served by an optional scene with a few prompts to get newbies acclimated before dropping them into a proper stage. Meanwhile, players in favor of sensible tutorials all pointed me at the same game: Far Cry 3: Blood Dragon. https://www.youtube.com/watch?v=RVtwKiOYdzc Blood Dragon actually had the same challenge to overcome as Mega Man X: a unique game in a pre-existing series that still needs to onboard new players. To do this, Blood Dragon goes all the way in the opposite direction, interrupting players with nearly full-screen prompts every few seconds while the protagonist complains about the delay. Blood Dragon manages to roast an annoying trend in game tutorials (overdoing it) while using a tried and true method to teach players advanced FPS controls in a hurry. This comparison is too simplistic, of course, and also doesn't take into account the widely varied needs across other genres. Angry Birds doesn't need too much handholding, but have you ever designed your own card game? The resource we look at in this episode is the condensed result of a master's project study on reactions to tutorials and introductory levels featured at Gamasutra. If you enjoy GameDev Breakdown Sign up for our free game dev newsletter! Subscribe to the podcast on the platform of your choice Follow us on Twitter: @GameDevPod, @CodeWritePlay, @Mechatodzilla Check show notes and articles at CodeWritePlay.com Join us on Discord! --- This episode is sponsored by · Anchor: The easiest way to make a podcast. https://anchor.fm/app --- Send in a voice message: https://anchor.fm/gamedevbreakdown/message Support this podcast: https://anchor.fm/gamedevbreakdown/support

Is AV1 more efficient than HEVC? Dror & Mark get into the middle of a 3 against 1 standoff over whether AV1 is actually more efficient than HEVC. The following blog post first appeared on the Beamr blog at: https://blog.beamr.com/2018/11/23/codec-efficiency-is-in-the-eye-of-the-measurer-podcast/ When it comes to comparing video codecs, it's easy to get caught up in the “codec war” mentality. If analyzing and purchasing codecs was as easy as comparing fuel economy in cars, it would undoubtedly take a lot of friction out of codec comparison, but the reality is that it's not that simple. In Episode 02, The Video Insiders go head-to-head comparing two of the leading codecs in a three against one standoff over whether AV1 is more efficient than HEVC. So, which is more efficient? Listen in to this week's episode, “Codec Efficiency Is in the Eye of the Measurer,” to find out. Want to join the conversation? Reach out to TheVideoInsiders@beamr.com. TRANSCRIPTION (lightly edited to improve readability only) Mark Donnigan: 00:41 Hi everyone I am Mark Donnigan and I want to welcome you to episode two of the Video Insiders. Dror Gill: 00:48 And I am Dror Gill. Hi there. Mark Donnigan: 00:50 In every episode of the Video Insiders we bring the latest inside information about what's happening in the video technology industry from encoding, to packaging, to delivery, and playback, and even the business behind the video business. Every aspect of the video industry is covered in detail on the Video Insiders podcast. Dror Gill: 01:11 Oh yeah, we usually do cover everything from pixels, to blocks, to microblocks, to frames, to sequences. We go all the way up and down the video delivery chain and highlight the most important things you should know before you send any video bits over the wire. Mark Donnigan: 01:28 In our first episode we talked about a very hot topic which asked, “Hasn't this kind of been worn out?” The whole HEVC, AV1 discussion. But I think it was very interesting. I sure enjoyed the talk. What about you Dror? Dror Gill: 01:47 Yeah, yeah, yeah. I sure did. It was great talking about the two leading codecs. I don't want to say the word, codec war. Mark Donnigan: 01:58 No, no, we don't believe in codec wars. Dror Gill: 01:59 We believe in codec peace. Mark Donnigan: 02:00 Yeah, that's true. Why is it so complicated to compare video codecs? Why can't it be as simple as fuel economy of cars, this one gets 20 miles per gallon and that one gets 30 and then I make a decision based on that. Dror Gill: 02:15 I wish it was that simple with video codecs. In video compression you have so many parameters to consider. You have the encoding tools, tools are grouped into what's called profiles and levels, or as AV1 calls them “experiments.” Mark Donnigan: 02:31 Experiments, mm-hmm… Dror Gill: 02:35 When you compare the codecs which profiles and levels do you use. What rate control method? Which specific parameters do you set for each codec? And each codec can have hundreds, and hundreds of parameters. Then there is the question of implementation. Which software implementation of the codec do you use? Some implementations are reference implementations that are used for research, and others are highly performance optimized commercial implementations. Which one do you select for the test? And then, which operating system, what hardware do you run on, and obviously what test content? Because encoding two people talking, or encoding an action scene for a movie, is completely different. Dror Gill: 03:13 Finally, when you come to evaluate your video, what quality measure do you use? There're various objective quality measures and some people use actual human viewers and they assesses subjective quality of the video. On that front also, there're many possibilities that you need to choose from. Mark Donnigan: 03:32 Yeah, so many questions and no wonder the answers are not so clear. I was quite surprised when I recently read three different technical articles published at IBC actually, effectively comparing AV1 versus HEVC and I can assume that each of the authors did their research independently. What was surprising was they came to the exact same conclusion, AV1 has the same compression efficiency as HEVC. This is surprising because some other studies and one in particular (I think we'll talk about) out there says the contrary. So can you explain what this means exactly, Dror. Dror Gill: 04:16 By saying that they have the same compression efficiency, this means that they can reach the same quality at the same bitrate or the other way round. You need the same bitrate to reach that same quality. If you need for example, two and a half megabits per second to encode an HD video file using HEVC at a certain quality, then with AV1 you would need roughly the same bitrate to reach that same quality and this means that AV1 and HEVC provide the same compression level. In other words, this means that AV1 does not have any technical advantage over HEVC because it has the same compression efficiency. Of course that's if we put aside all the loyalty issues but we discussed that last time. Right? Mark Donnigan: 04:56 That's right. The guys who wrote the three papers that I'm referencing are really top experts in the field. It's not seminar work done by a student, not to downplay those papers, but the point is these are professionals. One was written by the BBC in cooperation with the Multimedia and Vision Group at the Queen Mary University of London. I think nobody is going to say that the BBC doesn't know a thing or two about video. The second was written by Ateme, and the third by Harmonic, leading vendors. Mark Donnigan: 05:29 I actually pulled out a couple of phrases from each that I'd like to quote. First the BBC and Queen Mary University, here is a conclusion that they wrote, “The results obtained show in general a similar performance between AV1 and the reference HEVC both objectively and subjectively.” Which is interesting because they did take the time to both do the visual assessment as well as use a quality measure. Mark Donnigan: 06:01 Ateme said, “Results demonstrate AV1 to have equivalent performance to HEVC in terms of both objective and subjective video quality test results.” Dror Gill: 06:10 Yeah, very similar. Mark Donnigan: 06:16 And then here is what Harmonic said, “The findings are that AV1 is not more advantageous today than HEVC on the compression side and much more complex to encode than HEVC.” What do you make of this? Dror Gill: 06:32 I don't know. It sounds pretty bad to me, even two of those papers also analyzed subjective quality so they used actual human viewers to check out the quality. But Mark what if I told you that researchers from the University of Klagenfurt in Austria together with Bitmovin published a paper which showed completely different results. What would you say about that? Mark Donnigan: 06:57 Tell me more. Dror Gill: 06:58 Last month in Athens I was the ICIP conference that's the IEEE International Conference on Image Compression and Image Processing. There was this paper presented by this University in Austria with Bitmovin and their conclusion was, let me quote, “When using weighted PSNR, AV1 performs consistently better for bit rate compared to AVC, HEVC, and VP9.” So they claim AV1 is better than three codecs but specifically it's better than HEVC. And then they have a table in their article that compares AV1 to HEVC for six different video clips. The table shows that with AV1 you get up to 25% lower bitrate at the same quality than HEVC. Dror Gill: 07:43 I was sitting there in Athens last month when they presented this and I was shocked. Mark Donnigan: 07:50 What are the chances that three independent papers are wrong and only this paper got it right? And by the way, the point here is not three against one because presumably there're some other papers. I'm guessing other research floating around that might side with Bitmovin. The point is that three companies who no one is going to say that any of them are not experts and not highly qualified to do a video assessment, came up with such a different result. Tell us what you think is going on here? Dror Gill: 08:28 I was thinking the same thing. How can that be. During the presentation I asked one of the authors who presented the paper a few questions and it turned out that they made some very questionable decisions in all of that sea of possibility that I talked about before. Decisions related to coding tools, codec parameters, and quality measures. Dror Gill: 08:51 First of all, in this paper they didn't show any results of subjective viewing. Only the objective metrics. Now we all know that you should always your eyes, right? Mark Donnigan: 09:03 That's right. Dror Gill: 09:04 Objective metrics, nice numbers, but obviously you need to view the video because that's how the actual viewers are going to assess the (video) quality. The second thing is that they only used the single objective metric and this was PSNR. PSNR, it stands for peak signal-to-noise ratio and basically this measure is a weighted average of the difference in peaks between pixel values of the two images. Dror Gill: 09:30 Now, we're Video Insiders, but even if you're not an insider you know that PSNR is not a very good quality measure because it does not correlate very well with human vision. This is the measure that they choose to look at but what was most surprising is that there is a flag in the HEVC open source encoder which they used that if chosen, the result is improved PNSR. What it does, it turns off some psycho-visual optimizations which make the video look better but reduce the PSNR, and that's turned on by default. So you would expect that they're measuring PSNR they would turn that flag on so you would get higher PSNR. Well, they didn't. They didn't turn the flag on! Mark Donnigan: 10:13 Amazing. Dror Gill: 10:17 Finally, even then AV1 is much slower than HEVC, and they also reported in this data that it was much, much slower than HEVC but still they did not use the slowest encoding standing of HEVC, which would provide the best quality. There's always a trade off between performance and quality. The more tools you employ the better quality you can squeeze out of the video, of course that takes you more CPU cycles but they used for HEVC, the third slowest setting which means this is the third best quality you can get with that codec and not the very best quality. When you handicap an HEVC encoder in this way, it's not surprising that you get such poor results. Dror Gill: 11:02 I think based on all these points everybody can understand why the results of this comparison were quite different than all of the other comparison that were published a month earlier at IBC (by Ateme, BBC, Harmonic). Mark Donnigan: 11:13 It's interesting. Mark Donnigan: 11:14 Another critical topic that we have to cover is performance. If you measure the CPU performance on encoding time of AV1, I believe that it's pretty universally understood that you are going to find it currently is a hundred times slower than HEVC. Is that correct? Dror Gill: 11:32 Yeah, that's right. Typically, you measure the performance of an encoder and FPS which is frames per second. For HEVC it's common to measure an FPM which is frames per minute. Mark Donnigan: 11:42 Frames per minute, (more like) frames per hour, FPH. Dror Gill: 11:45 A year and a half ago or a year ago when there were very initial implementation, it was really FPD or FPH, Frames per hour or per day and you really needed to have a lot of patience, but now after they've done some work it's only a hundred times slower than HEVC. Mark Donnigan: 12:02 Yeah, that's pretty good. They're getting there. But some people say that the open source implementation of AV1 I believe it's AOM ENC. Dror Gill: 12:11 Yeah, AOM ENC. Mark Donnigan: 12:16 ENC exactly has not been optimized for performance at all. One thing I like about speed is either your encoder produces X number of frames per second or per minute, or it doesn't. It's really simple. Here is my next question for you. Proponents of AV1 are saying, “well it's true it's slow but it hasn't been optimized, the open source implementation,” which is to imply that there's a lot of room (for improvement) and that we're just getting started, “don't worry we'll close the gap.” But if you look at the code, and by the way I may be a marketing guy but my formal education is computer science. Mark Donnigan: 13:03 You can see it already includes performance optimizations. I mean eptimizations like MMX, SSE, there's AVX instructions, there's CPU optimization, there's multithreading. It seems like they're already trying to make this thing go faster. So how are they going to close this a hundred X (time) gap? Dror Gill: 13:22 I don't think they can. I mean a hundred X, that's a lot and you know even the AV1 guys they even admit that they won't be able to close the gap. I talked to a few senior people who're involved in the Alliance for Open Media and even they told me that they expect AV1 to five to 10 times more complex than HEVC at the end of the road. In two to three years after all optimization are done, it's still going to be more complex than HEVC. Dror Gill: 13:55 Now, if you ask me why it's so complex I'll tell you my opinion. Okay, this is my personal opinion. I think it's because they invested a lot of effort in side stepping the patents (HEVC). Mark Donnigan: 14:07 Good point. I agree. Dror Gill: 14:07 They need to get that compression efficiency which is the same as HEVC but they need to use algorithms that are not patented. They have methods that use much more CPU resources than the original patent algorithms to reach the same results. You can call it kind of brute force implementation of the same thing to avoid the patent issue. That's my personal opinion, but the end result I think is clear, it's going to be five to 10 times slower than HEVC. It has the same compression efficiency so I think it's quite questionable. This whole notion of using AV1 to get better results. Mark Donnigan: 14:45 Absolutely. If you can encode let's say on a single computer with HEVC a full ABR stack, this is what people want to do. But here we're talking speeds that are so slow let's just try and do (encode) one stream. Literally what you're saying is you'll need five to 10 computers to do the same encode with AV1. I mean, that's just not viable. It doesn't make sense to me. Dror Gill: 15:14 Yeah, why would you invest so much encoding into getting the same results. If you look at another aspect of this, let's talk about hardware encode. Companies that have large data centers, companies that are encoding vast amount of video content are not looking into moving from the traditional software encoding and CPUs and GPUs, to dedicated hardware. We're hearing talks about FPGAs even ASICs … by the way this is a very interesting trend in itself that we'll probably cover in one of the next episodes. But in the context of AV1, imagine a chip that is five to 10 times larger than an HEVC chip and which is the same complexity efficiency. The question I ask again is why? Why would anybody design such a chip, and why would anybody use it when HEVC is available today? It's much easier to encode, royalty issues have been practically solved so you know? Mark Donnigan: 16:06 Yeah, it's a big mystery for sure. One thing I can say is the Alliance for Open Media has done a great service to HEVC by pushing the patent holders to finalize their licensing terms … and ultimately make them much more rational shall we say? Dror Gill: 16:23 Yeah. Mark Donnigan: 16:25 Let me say that as we're an HEVC vendor and speaking on behalf of others (in the industry), we're forever thankful to the Alliance for Open Media. Dror Gill: 16:36 Definitely, without the push from AOM and the development of AV1 we would be stuck with HEVC royalty issue until this day. Mark Donnigan: 16:44 That was not a pretty situation a few years back, wow! Dror Gill: 16:48 No, no, but as we said in the last episode we have a “happy ending” now. (reference to episode 1) Mark Donnigan: 16:52 That's right. Dror Gill: 16:52 Billions of devices support HEVC and royalty issues are pretty much solved, so that's great. I think we've covered HEVC and AV1 pretty thoroughly in two episodes but what about the other codecs? There's VP9, you could call that the predecessor of AV1, and then there's VVC, which is the successor of HEVC. It's the next codec developed by MPEG. Okay, VP9 and VVC I guess we have a topic for our next episode, right? Mark Donnigan: 17:21 It's going to be awesome. Narrator: 17:23 Thank you for listening to the Video Insider podcast a production of Beamr limited. To begin using Beamr codecs today go to beamr.com/free to receive up to 100 hours of no cost HEVC and H.264 transcoding every month.

Papers we love: ARC by Bryan Cantrill, SSD caching adventures with ZFS, OpenBSD full disk encryption setup, and a Perl5 Slack Syslog BSD daemon. This episode was brought to you by Headlines Papers We Love: ARC: A Self-Tuning, Low Overhead Replacement Cache (https://www.youtube.com/watch?v=F8sZRBdmqc0&feature=youtu.be) Ever wondered how the ZFS ARC (Adaptive Replacement Cache) works? How about if Bryan Cantrill presented the original paper on its design? Today is that day. Slides (https://www.slideshare.net/bcantrill/papers-we-love-arc-after-dark) It starts by looking back at a fundamental paper from the 40s where the architecture of general-purpose computers are first laid out The main is the description of memory hierarchies, where you have a small amount of very fast memory, then the next level is slower but larger, and on and on. As we look at the various L1, L2, and L3 caches on a CPU, then RAM, then flash, then spinning disks, this still holds true today. The paper then does a survey of the existing caching policies and tries to explain the issues with each. This includes ‘MIN', which is the theoretically optimal policy, which requires future knowledge, but is useful for setting the upper bound, what is the best we could possibly do. The paper ends up showing that the ARC can end up being better than manually trying to pick the best number for the workload, because it adapts as the workload changes At about 1:25 into the video, Bryan start talking about the practical implementation of the ARC in ZFS, and some challenges they have run into recently at Joyent. A great discussion about some of the problems when ZFS needs to shrink the ARC. Not all of it applies 1:1 to FreeBSD because the kernel and the kmem implementation are different in a number of ways There were some interesting questions asked at the end as well *** How do I use man pages to learn how to use commands? (https://unix.stackexchange.com/a/193837) nwildner on StackExchange has a very thorough answer to the question how to interpret man pages to understand complicated commands (xargs in this case, but not specifically). Have in mind what you want to do. When doing your research about xargs you did it for a purpose, right? You had a specific need that was reading standard output and executing commands based on that output. But, when I don't know which command I want? Use man -k or apropos (they are equivalent). If I don't know how to find a file: man -k file | grep search. Read the descriptions and find one that will better fit your needs. Apropos works with regular expressions by default, (man apropos, read the description and find out what -r does), and on this example I'm looking for every manpage where the description starts with "report". Always read the DESCRIPTION before starting Take a time and read the description. By just reading the description of the xargs command we will learn that: xargs reads from STDIN and executes the command needed. This also means that you will need to have some knowledge of how standard input works, and how to manipulate it through pipes to chain commands The default behavior is to act like /bin/echo. This gives you a little tip that if you need to chain more than one xargs, you don't need to use echo to print. We have also learned that unix filenames can contain blank and newlines, that this could be a problem and the argument -0 is a way to prevent things explode by using null character separators. The description warns you that the command being used as input needs to support this feature too, and that GNU find support it. Great. We use a lot of find with xargs. xargs will stop if exit status 255 is reached. Some descriptions are very short and that is generally because the software works on a very simple way. Don't even think of skipping this part of the manpage ;) Other things to pay attention... You know that you can search for files using find. There is a ton of options and if you only look at the SYNOPSIS, you will get overwhelmed by those. It's just the tip of the iceberg. Excluding NAME, SYNOPSIS, and DESCRIPTION, you will have the following sections: When this method will not work so well... + Tips that apply to all commands Some options, mnemonics and "syntax style" travel through all commands making you buy some time by not having to open the manpage at all. Those are learned by practice and the most common are: Generally, -v means verbose. -vvv is a variation "very very verbose" on some software. Following the POSIX standard, generally one dash arguments can be stacked. Example: tar -xzvf, cp -Rv. Generally -R and/or -r means recursive. Almost all commands have a brief help with the --help option. --version shows the version of a software. -p, on copy or move utilities means "preserve permissions". -y means YES, or "proceed without confirmation" in most cases. Default values of commands. At the pager chunk of this answer, we saw that less -is is the pager of man. The default behavior of commands are not always shown at a separated section on manpages, or at the section that is most top placed. You will have to read the options to find out defaults, or if you are lucky, typing /pager will lead you to that info. This also requires you to know the concept of the pager(software that scrolls the manpage), and this is a thing you will only acquire after reading lots of manpages. And what about the SYNOPSIS syntax? After getting all the information needed to execute the command, you can combine options, option-arguments and operands inline to make your job done. Overview of concepts: Options are the switches that dictates a command behavior. "Do this" "don't do this" or "act this way". Often called switches. Check out the full answer and see if it helps you better grasp the meaning of a man page and thus the command. *** My adventure into SSD caching with ZFS (Home NAS) (https://robertputt.co.uk/my-adventure-into-ssd-caching-with-zfs-home-nas.html) Robert Putt as written about his adventure using SSDs for caching with ZFS on his home NAS. Recently I decided to throw away my old defunct 2009 MacBook Pro which was rotting in my cupboard and I decided to retrieve the only useful part before doing so, the 80GB Intel SSD I had installed a few years earlier. Initially I thought about simply adding it to my desktop as a bit of extra space but in 2017 80GB really wasn't worth it and then I had a brainwave… Lets see if we can squeeze some additional performance out of my HP Microserver Gen8 NAS running ZFS by installing it as a cache disk. I installed the SSD to the cdrom tray of the Microserver using a floppy disk power to SATA power converter and a SATA cable, unfortunately it seems the CD ROM SATA port on the motherboard is only a 3gbps port although this didn't matter so much as it was an older 3gbps SSD anyway. Next I booted up the machine and to my suprise the disk was not found in my FreeBSD install, then I realised that the SATA port for the CD drive is actually provided by the RAID controller, so I rebooted into intelligent provisioning and added an additional RAID0 array with just the 1 disk to act as my cache, in fact all of the disks in this machine are individual RAID0 arrays so it looks like just a bunch of disks (JBOD) as ZFS offers additional functionality over normal RAID (mainly scrubbing, deduplication and compression). Configuration Lets have a look at the zpool before adding the cache drive to make sure there are no errors or uglyness: Now lets prep the drive for use in the zpool using gpart. I want to split the SSD into two seperate partitions, one for L2ARC (read caching) and one for ZIL (write caching). I have decided to split the disk into 20GB for ZIL and 50GB for L2ARC. Be warned using 1 SSD like this is considered unsafe because it is a single point of failure in terms of delayed writes (a redundant configuration with 2 SSDs would be more appropriate) and the heavy write cycles on the SSD from the ZIL is likely to kill it over time. Now it's time to see if adding the cache has made much of a difference. I suspect not as my Home NAS sucks, it is a HP Microserver Gen8 with the crappy Celeron CPU and only 4GB RAM, anyway, lets test it and find out. First off lets throw fio at the mount point for this zpool and see what happens both with the ZIL and L2ARC enabled and disabled. Observations Ok, so the initial result is a little dissapointing, but hardly unexpected, my NAS sucks and there are lots of bottle necks, CPU, memory and the fact only 2 of the SATA ports are 6gbps. There is no real difference performance wise in comparison between the results, the IOPS, bandwidth and latency appear very similar. However lets bare in mind fio is a pretty hardcore disk benchmark utility, how about some real world use cases? Next I decided to test a few typical file transactions that this NAS is used for, Samba shares to my workstation. For the first test I wanted to test reading a 3GB file over the network with both the cache enabled and disabled, I would run this multiple times to ensure the data is hot in the L2ARC and to ensure the test is somewhat repeatable, the network itself is an uncongested 1gbit link and I am copying onto the secondary SSD in my workstation. The dataset for these tests has compression and deduplication disabled. Samba Read Test Not bad once the data becomes hot in the L2ARC cache reads appear to gain a decent advantage compared to reading from the disk directly. How does it perform when writing the same file back accross the network using the ZIL vs no ZIL. Samba Write Test Another good result in the real world test, this certainately helps the write transfer speed however I do wonder what would happen if you filled the ZIL transferring a very large file, however this is unlikely with my use case as I typically only deal with a couple of files of several hundred megabytes at any given time so a 20GB ZIL should suit me reasonably well. Is ZIL and L2ARC worth it? I would imagine with a big beefy ZFS server running in a company somewhere with a large disk pool and lots of users with multiple enterprise level SSD ZIL and L2ARC would be well worth the investment, however at home I am not so sure. Yes I did see an increase in read speeds with cached data and a general increase in write speeds however it is use case dependant. In my use case I rarely access the same file frequently, my NAS primarily serves as a backup and for archived data, and although the write speeds are cool I am not sure its a deal breaker. If I built a new home NAS today I'd probably concentrate the budget on a better CPU, more RAM (for ARC cache) and more disks. However if I had a use case where I frequently accessed the same files and needed to do so in a faster fashion then yes, I'd probably invest in an SSD for caching. I think if you have a spare SSD lying around and you want something fun todo with it, sure chuck it in your ZFS based NAS as a cache mechanism. If you were planning on buying an SSD for caching then I'd really consider your needs and decide if the money can be spent on alternative stuff which would improve your experience with your NAS. I know my NAS would benefit more from an extra stick of RAM and a more powerful CPU, but as a quick evening project with some parts I had hanging around adding some SSD cache was worth a go. More Viewer Interview Questions for Allan News Roundup Setup OpenBSD 6.2 with Full Disk Encryption (https://blog.cagedmonster.net/setup-openbsd-with-full-disk-encryption/) Here is a quick way to setup (in 7 steps) OpenBSD 6.2 with the encryption of the filesystem. First step: Boot and start the installation: (I)nstall: I Keyboard Layout: ENTER (I'm french so in my case I took the FR layout) Leave the installer with: ! Second step: Prepare your disk for encryption. Using a SSD, my disk is named : sd0, the name may vary, for example : wd0. Initiating the disk: Configure your volume: Now we'll use bioctl to encrypt the partition we created, in this case : sd0a (disk sd0 + partition « a »). Enter your passphrase. Third step: Let's resume the OpenBSD's installer. We follow the install procedure Fourth step: Partitioning of the encrypted volume. We select our new volume, in this case: sd1 The whole disk will be used: W(hole) Let's create our partitions: NB: You are more than welcome to create multiple partitions for your system. Fifth step: System installation It's time to choose how we'll install our system (network install by http in my case) Sixth step: Finalize the installation. Last step: Reboot and start your system. Put your passphrase. Welcome to OpenBSD 6.2 with a full encrypted file system. Optional: Disable the swap encryption. The swap is actually part of the encrypted filesystem, we don't need OpenBSD to encrypt it. Sysctl is giving us this possibility. Step-by-Step FreeBSD installation with ZFS and Full Disk Encryption (https://blog.cagedmonster.net/step-by-step-freebsd-installation-with-full-disk-encryption/) 1. What do I need? For this tutorial, the installation has been made on a Intel Core i7 - AMD64 architecture. On a USB key, you would probably use this link : ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO-IMAGES/11.1/FreeBSD-11.1-RELEASE-amd64-mini-memstick.img If you can't do a network installation, you'd better use this image : ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO-IMAGES/11.1/FreeBSD-11.1-RELEASE-amd64-memstick.img You can write the image file on your USB device (replace XXXX with the name of your device) using dd : # dd if=FreeBSD-11.1-RELEASE-amd64-mini-memstick.img of=/dev/XXXX bs=1m 2. Boot and install: Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F1.png) 3. Configure your keyboard layout: Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F2.png) & Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F3.png) 4. Hostname and system components configuration : Set the name of your machine: [Screenshot](https://blog.cagedmonster.net/content/images/2017/09/F4.png_ What components do you want to install? Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F5.png) 5. Network configuration: Select the network interface you want to configure. Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F6.png) First, we configure our IPv4 network. I used a static adress so you can see how it works, but you can use DHCP for an automated configuration, it depends of what you want to do with your system (desktop/server) Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F7.png) & Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F7-1.png) & Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F8.png) IPv6 network configuration. Same as for IPv4, you can use SLAAC for an automated configuration. Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F9.png) & Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F10-1.png) & Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F10-2.png) Here, you can configure your DNS servers, I used the Google DNS servers so you can use them too if needed. Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F11.png) 6. Select the server you want to use for the installation: I always use the IPv6 mirror to ensure that my IPv6 network configuration is good.Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F12.png) 7. Disk configuration: As we want to do an easy full disk encryption, we'll use ZFS. Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F13.png) Make sure to select the disk encryption :Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F14.png) Launch the disk configuration :Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F15.png) Here everything is normal, you have to select the disk you'll use :Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F16.png) I have only one SSD disk named da0 :Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F17.png) Last chance before erasing your disk :Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F18.png) Time to choose the password you'll use to start your system : Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F19.png) & Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F20.png) & Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F21.png) 8. Last steps to finish the installation: The installer will download what you need and what you selected previously (ports, src, etc.) to create your system: Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F22.png) 8.1. Root password: Enter your root password: Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F22-1.png) 8.2. Time and date: Set your timezone, in my case: Europe/France Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F22-2.png) & Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F23.png) & Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F23-1.png) Make sure the date and time are good, or you can change them :Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F24.png) & Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F25.png) 8.3. Services: Select the services you'll use at system startup depending again of what you want to do. In many cases powerd and ntpd will be useful, sshd if you're planning on using FreeBSD as a server. Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F26.png) 8.4. Security: Security options you want to enable. You'll still be able to change them after the installation with sysctl. Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F26-1.png) 8.5. Additionnal user: Create an unprivileged system user: Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F26-2.png) Make sure your user is in the wheel group so he can use the su command. Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F26-3.png) & Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F26-4.png) 8.6. The end: End of your configuration, you can still do some modifications if you want : Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F26-5.png) & Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F26-6.png) & Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F26-7.png) 9. First boot: Enter the passphrase you have chosen previously : Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F27.png) & Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F28.png) & Screenshot (https://blog.cagedmonster.net/content/images/2017/09/F29.png) Welcome to Freebsd 11.1 with full disk encryption! *** The anatomy of ldd program on OpenBSD (http://nanxiao.me/en/the-anatomy-of-ldd-program-on-openbsd/) In the past week, I read the ldd (https://github.com/openbsd/src/blob/master/libexec/ld.so/ldd/ldd.c) source code on OpenBSD to get a better understanding of how it works. And this post should also be a reference for other*NIX OSs. The ELF (https://en.wikipedia.org/wiki/Executable_and_Linkable_Format) file is divided into 4 categories: relocatable, executable, shared, and core. Only the executable and shared object files may have dynamic object dependencies, so the ldd only check these 2 kinds of ELF file: (1) Executable. ldd leverages the LD_TRACE_LOADED_OBJECTS environment variable in fact, and the code is as following: if (setenv("LD_TRACE_LOADED_OBJECTS", "true", 1) < 0) err(1, "setenv(LD_TRACE_LOADED_OBJECTS)"); When LDTRACELOADED_OBJECTS is set to 1 or true, running executable file will show shared objects needed instead of running it, so you even not needldd to check executable file. See the following outputs: $ /usr/bin/ldd usage: ldd program ... $ LD_TRACE_LOADED_OBJECTS=1 /usr/bin/ldd Start End Type Open Ref GrpRef Name 00000b6ac6e00000 00000b6ac7003000 exe 1 0 0 /usr/bin/ldd 00000b6dbc96c000 00000b6dbcc38000 rlib 0 1 0 /usr/lib/libc.so.89.3 00000b6d6ad00000 00000b6d6ad00000 rtld 0 1 0 /usr/libexec/ld.so (2) Shared object. The code to print dependencies of shared object is as following: if (ehdr.e_type == ET_DYN && !interp) { if (realpath(name, buf) == NULL) { printf("realpath(%s): %s", name, strerror(errno)); fflush(stdout); _exit(1); } dlhandle = dlopen(buf, RTLD_TRACE); if (dlhandle == NULL) { printf("%sn", dlerror()); fflush(stdout); _exit(1); } _exit(0); } Why the condition of checking a ELF file is shared object or not is like this: if (ehdr.e_type == ET_DYN && !interp) { ...... } That's because the file type of position-independent executable (PIE) is the same as shared object, but normally PIE contains a interpreter program header since it needs dynamic linker to load it while shared object lacks (refer this article). So the above condition will filter PIE file. The dlopen(buf, RTLD_TRACE) is used to print dynamic object information. And the actual code is like this: if (_dl_traceld) { _dl_show_objects(); _dl_unload_shlib(object); _dl_exit(0); } In fact, you can also implement a simple application which outputs dynamic object information for shared object yourself: # include int main(int argc, char **argv) { dlopen(argv[1], RTLD_TRACE); return 0; } Compile and use it to analyze /usr/lib/libssl.so.43.2: $ cc lddshared.c $ ./a.out /usr/lib/libssl.so.43.2 Start End Type Open Ref GrpRef Name 000010e2df1c5000 000010e2df41a000 dlib 1 0 0 /usr/lib/libssl.so.43.2 000010e311e3f000 000010e312209000 rlib 0 1 0 /usr/lib/libcrypto.so.41.1 The same as using ldd directly: $ ldd /usr/lib/libssl.so.43.2 /usr/lib/libssl.so.43.2: Start End Type Open Ref GrpRef Name 00001d9ffef08000 00001d9fff15d000 dlib 1 0 0 /usr/lib/libssl.so.43.2 00001d9ff1431000 00001d9ff17fb000 rlib 0 1 0 /usr/lib/libcrypto.so.41.1 Through the studying of ldd source code, I also get many by-products: such as knowledge of ELF file, linking and loading, etc. So diving into code is a really good method to learn *NIX deeper! Perl5 Slack Syslog BSD daemon (https://clinetworking.wordpress.com/2017/10/13/perl5-slack-syslog-bsd-daemon/) So I have been working on my little Perl daemon for a week now. It is a simple syslog daemon that listens on port 514 for incoming messages. It listens on a port so it can process log messages from my consumer Linux router as well as the messages from my server. Messages that are above alert are sent, as are messages that match the regex of SSH or DHCP (I want to keep track of new connections to my wifi). The rest of the messages are not sent to slack but appended to a log file. This is very handy as I can get access to info like failed ssh logins, disk failures, and new devices connecting to the network all on my Android phone when I am not home. Screenshot (https://clinetworking.files.wordpress.com/2017/10/screenshot_2017-10-13-23-00-26.png) The situation arose today that the internet went down and I thought to myself what would happen to all my important syslog messages when they couldn't be sent? Before the script only ran an eval block on the botsend() function. The error was returned, handled, but nothing was done and the unsent message was discarded. So I added a function that appended unsent messengers to an array that are later sent when the server is not busy sending messages to slack. Slack has a limit of one message per second. The new addition works well and means that if the internet fails my server will store these messages in memory and resend them at a rate of one message per second when the internet connectivity returns. It currently sends the newest ones first but I am not sure if this is a bug or a feature at this point! It currently works with my Linux based WiFi router and my FreeBSD server. It is easy to scale as all you need to do is send messages to syslog to get them sent to slack. You could sent CPU temp, logged in users etc. There is a github page: https://github.com/wilyarti/slackbot Lscpu for OpenBSD/FreeBSD (http://nanxiao.me/en/lscpu-for-openbsdfreebsd/) Github Link (https://github.com/NanXiao/lscpu) There is a neat command, lscpu, which is very handy to display CPU information on GNU/Linux OS: $ lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 32 On-line CPU(s) list: 0-31 Thread(s) per core: 2 Core(s) per socket: 8 Socket(s): 2 But unfortunately, the BSD OSs lack this command, maybe one reason is lscpu relies heavily on /proc file system which BSD don't provide, :-). TakeOpenBSD as an example, if I want to know CPU information, dmesg should be one choice: $ dmesg | grep -i cpu cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 Duo CPU P8700 @ 2.53GHz, 2527.35 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM, PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,NXE,LONG,LAHF,PERF,SENSOR cpu0: 3MB 64b/line 8-way L2 cache cpu0: apic clock running at 266MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2.1.3, IBE But the output makes me feeling messy, not very clear. As for dmidecode, it used to be another option, but now can't work out-of-box because it will access /dev/mem which for security reason, OpenBSD doesn't allow by default (You can refer this discussion): $ ./dmidecode $ dmidecode 3.1 Scanning /dev/mem for entry point. /dev/mem: Operation not permitted Based on above situation, I want a specified command for showing CPU information for my BSD box. So in the past 2 weeks, I developed a lscpu program for OpenBSD/FreeBSD, or more accurately, OpenBSD/FreeBSD on x86 architecture since I only have some Intel processors at hand. The application getsCPU metrics from 2 sources: (1) sysctl functions. The BSD OSs provide sysctl interface which I can use to get general CPU particulars, such as how many CPUs the system contains, the byte-order of CPU, etc. (2) CPUID instruction. For x86 architecture, CPUID instruction can obtain very detail information of CPU. This coding work is a little tedious and error-prone, not only because I need to reference both Intel and AMD specifications since these 2 vendors have minor distinctions, but also I need to parse the bits of register values. The code is here (https://github.com/NanXiao/lscpu), and if you run OpenBSD/FreeBSD on x86 processors, please try it. It will be better you can give some feedback or report the issues, and I appreciate it very much. In the future if I have other CPUs resource, such as ARM or SPARC64, maybe I will enrich this small program. *** Beastie Bits OpenBSD Porting Workshop - Brian Callahan will be running an OpenBSD porting workshop in NYC for NYC*BUG on December 6, 2017. (http://daemonforums.org/showthread.php?t=10429) Learn to tame OpenBSD quickly (http://www.openbsdjumpstart.org/#/) Detect the operating system using UDP stack corner cases (https://gist.github.com/sortie/94b302dd383df19237d1a04969f1a42b) *** Feedback/Questions Awesome Mike - ZFS Questions (http://dpaste.com/1H22BND#wrap) Michael - Expanding a file server with only one hard drive with ZFS (http://dpaste.com/1JRJ6T9) - information based on Allan's IRC response (http://dpaste.com/36M7M3E) Brian - Optimizing ZFS for a single disk (http://dpaste.com/3X0GXJR#wrap) ***