Rush vickie (35 risultati)

Paperback. Condizione: Good.

Paperback. Condizione: Very Good.

Condizione: Good. Pages intact with minimal writing/highlighting. The binding may be loose and creased. Dust jackets/supplements are not included. Stock photo provided. Product includes identifying sticker. Better World Books: Buy Books. Do Good.

Paperback. Condizione: Good.

Paperback. Condizione: Very Good.

Paperback. Condizione: new. Paperback. Ever installed a Linux server, got it "working," and then quietly hoped nothing would ever go wrong with it? If that sounds familiar, this book was written with you in mind.Debian has quietly powered a huge share of the internet's infrastructure for over three decades, and its latest release brings real, practical improvements that matter to anyone running production systems. But here's the problem: most guides either treat you like a total beginner clicking through an installer, or they assume you already know everything and just want a syntax reference. Neither approach actually teaches you how to run a server you'd trust with real data, real users, and real consequences if something breaks.So let me ask you a few questions. Do you know the difference between a firewall rule that looks correct and one that's actually enforced? Could you explain, right now, why your backup strategy might still fail you during an actual disaster, even if the backups themselves complete without error? Have you ever wondered what separates someone who can install software from someone organizations trust to run their infrastructure unsupervised?This book exists to close that gap.Written for system administrators, DevOps engineers, computer science students, and self-taught tinkerers who are ready to stop guessing and start understanding, this guide walks through the complete lifecycle of running Debian in the real world. Not just installation and basic commands, but the reasoning behind every decision: why you'd choose one partitioning scheme over another, why a firewall policy needs to be layered rather than a single list of allowed ports, and why "it works on my machine" is never good enough for production.Inside, you'll work through: Installation and initial hardening done correctly from the first boot, not patched together after the fact.Networking and firewall architecture that actually holds up under scrutiny, including modern packet filtering, segmentation, and secure remote access.User, identity, and privilege management built around the principle that nobody, including you, should have more access than the job requires.Shell scripting and automation that behaves reliably even when nobody's watching it run at three in the morning.Configuration management and infrastructure-as-code practices that let you manage dozens or hundreds of servers without losing your mind or your job security.Containers, virtualization, and orchestration concepts explained in a way that connects to what you already know, rather than treating them as an entirely separate universe.Database administration, web services, file sharing, and mail infrastructure, the unglamorous services that most businesses actually depend on every single day.Backup architecture and disaster recovery planning that gets tested, not just configured and forgotten.Monitoring, logging, and performance tuning grounded in actual measurement, not folklore copied from a forum post that solved a completely different problem.Enterprise-scale practices including patch management, compliance readiness, and documentation standards that keep infrastructure maintainable long after you've moved on to your next role.Every chapter is built around practical workflows and realistic scenarios, not abstract theory disconnected from what you'll actually face. Whether you're preparing for a systems administration role, migrating your organization's infrastructure, or simply tired of feeling one misconfiguration away from disaster, this book gives you the depth to actually understand what you're doing and why.Because there's a real difference between a server that happens to be running, and a server you actually understand. This book is here to help you build the second kind. This Shipping may be from multiple locations in the US or from the UK, depending on stock availability.…

Paperback. Condizione: new. Paperback. Ever installed a Linux server, got it "working," and then quietly hoped nothing would ever go wrong with it? If that sounds familiar, this book was written with you in mind.Debian has quietly powered a huge share of the internet's infrastructure for over three decades, and its latest release brings real, practical improvements that matter to anyone running production systems. But here's the problem: most guides either treat you like a total beginner clicking through an installer, or they assume you already know everything and just want a syntax reference. Neither approach actually teaches you how to run a server you'd trust with real data, real users, and real consequences if something breaks.So let me ask you a few questions. Do you know the difference between a firewall rule that looks correct and one that's actually enforced? Could you explain, right now, why your backup strategy might still fail you during an actual disaster, even if the backups themselves complete without error? Have you ever wondered what separates someone who can install software from someone organizations trust to run their infrastructure unsupervised?This book exists to close that gap.Written for system administrators, DevOps engineers, computer science students, and self-taught tinkerers who are ready to stop guessing and start understanding, this guide walks through the complete lifecycle of running Debian in the real world. Not just installation and basic commands, but the reasoning behind every decision: why you'd choose one partitioning scheme over another, why a firewall policy needs to be layered rather than a single list of allowed ports, and why "it works on my machine" is never good enough for production.Inside, you'll work through: Installation and initial hardening done correctly from the first boot, not patched together after the fact.Networking and firewall architecture that actually holds up under scrutiny, including modern packet filtering, segmentation, and secure remote access.User, identity, and privilege management built around the principle that nobody, including you, should have more access than the job requires.Shell scripting and automation that behaves reliably even when nobody's watching it run at three in the morning.Configuration management and infrastructure-as-code practices that let you manage dozens or hundreds of servers without losing your mind or your job security.Containers, virtualization, and orchestration concepts explained in a way that connects to what you already know, rather than treating them as an entirely separate universe.Database administration, web services, file sharing, and mail infrastructure, the unglamorous services that most businesses actually depend on every single day.Backup architecture and disaster recovery planning that gets tested, not just configured and forgotten.Monitoring, logging, and performance tuning grounded in actual measurement, not folklore copied from a forum post that solved a completely different problem.Enterprise-scale practices including patch management, compliance readiness, and documentation standards that keep infrastructure maintainable long after you've moved on to your next role.Every chapter is built around practical workflows and realistic scenarios, not abstract theory disconnected from what you'll actually face. Whether you're preparing for a systems administration role, migrating your organization's infrastructure, or simply tired of feeling one misconfiguration away from disaster, this book gives you the depth to actually understand what you're doing and why.Because there's a real difference between a server that happens to be running, and a server you actually understand. This book is here to help you build the second k Shipping may be from our UK warehouse or from our Australian or US warehouses, depending on stock availability.…

Taschenbuch. Condizione: Neu. Neuware.

Taschenbuch. Condizione: Neu. Neuware.

Taschenbuch. Condizione: Neu. Neuware.

Taschenbuch. Condizione: Neu. Neuware.

Taschenbuch. Condizione: Neu. Neuware.

Paperback. Condizione: new. Paperback. Have you ever stared at a microcontroller reference manual and felt like it was written in a different language?You are not alone. Most engineers learn embedded programming by copying example code, tweaking a few lines, and hoping it works. It usually does, eventually. But somewhere along the way, a question creeps in: what is actually happening inside that chip when my code runs? What does a register really do? Why does my interrupt fire late sometimes? Why does the processor jump into a fault handler for no obvious reason?This book was written to answer exactly those questions, directly and without the fluff.Arm Cortex-M Architecture and System Design takes you inside the 32-bit processor core that powers an enormous share of the microcontrollers used in consumer electronics, industrial equipment, medical devices, and automotive systems today. Rather than treating the processor as a black box you configure through a vendor library, this book opens it up and walks you through how it actually works, one layer at a time.Do you want to understand how a single line of C code becomes a sequence of machine instructions moving through the pipeline? This book shows you. Curious why the stack pointer matters so much, or what really happens in the microseconds after an interrupt fires? You will find clear, worked explanations here, not hand-waving.Here is what you can expect to actually learn: You will build a genuine mental model of the processor core itself, covering registers, the instruction execution cycle, and how the CPU moves data between memory and the arithmetic logic unit. You will understand memory organization in real depth, including how flash and RAM are mapped, how the linker actually places your program in memory, and why a mismatched startup file can produce mysterious, hard to reproduce bugs.You will learn how interrupts and exceptions genuinely work under the hood, including priority handling, nested interrupts, and the kind of timing pitfalls that cause intermittent, maddening failures in real products. You will get a practical, no-nonsense introduction to debugging using industry standard tools and techniques, so that when something goes wrong, and something always eventually goes wrong, you know how to find out why instead of guessing.Security gets serious treatment as well. As connected devices multiply, understanding memory protection, privilege separation, and secure boot concepts is no longer optional for a working embedded engineer, and this book treats those topics as core material rather than an afterthought.Who is this book actually for? If you are a computer engineering or electrical engineering student trying to connect what you learned in a computer architecture course to the chips you actually work with, this book bridges that gap. If you are a self-taught developer who has built a few projects and now wants to understand what is really going on beneath your code, you will find the depth you have been missing. And if you are a working engineer who has used vendor supplied libraries for years and wants to finally understand the register level details you have been quietly avoiding, this book was written with you specifically in mind.Every explanation in this book is paired with practical, realistic code examples and workflow guidance, not abstract theory disconnected from anything you would actually build. You will not just read about how processors work. You will come away able to read a reference manual confidently, debug a real hardware problem methodically, and design firmware that is efficient, reliable, and genuinely understood, not just copied and hoped for.If you are ready to stop guessing and start understanding, this book is where you begin. This item is printed on demand. Shipping may be from multiple locations in the US or from the UK, depending on stock availability. …

PAP. Condizione: New. New Book. Shipped from UK. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000.

Paperback. Condizione: new. Paperback. Have you ever stared at a linker error message that made absolutely no sense, copied a linker script from an old project just to get your build working, and quietly hoped you'd never have to touch it again?If that sounds familiar, you're not alone, and you're exactly who this book was written for.Most firmware engineers can write solid C code, configure peripherals, and debug a tricky timing issue without breaking a sweat. But ask them to explain why a variable's initial value needs to live in one address and run from another, or why an interrupt suddenly stops firing after a bootloader hands off control, and the confidence disappears. That gap isn't a knowledge problem you can Google your way out of in five minutes. It's a blind spot that most embedded courses and tutorials skip entirely, because it sits in the uncomfortable space between the compiler and the hardware, where the linker quietly makes every decision about where your program actually lives in memory.This book closes that gap, deliberately and thoroughly.Inside, you'll build a real, working understanding of how a linker script controls memory regions, organizes sections, separates load addresses from execution addresses, manages symbols, and ultimately decides whether your firmware boots cleanly or fails in ways that are maddening to trace. You won't just learn syntax. You'll learn why each command exists, what problem it was designed to solve, and how experienced engineers actually use it on production hardware.So what will you walk away with?You'll be able to read an unfamiliar linker script and understand its intent within minutes, instead of guessing. You'll know exactly how to structure memory regions for a new microcontroller, how to place startup code, interrupt tables, and custom sections with full control, and how to separate a variable's storage location from where it actually runs, a distinction that trips up even experienced developers. You'll understand how bootloaders hand off execution to an application, how dual bank update schemes protect a device from a failed firmware update, and how memory layout choices contribute directly to a device's security posture rather than existing as an afterthought.You'll also find a full set of real world case studies, walking through the design decisions behind a battery powered sensor node, a multitasking control system, a safety conscious device with redundant memory zones, and a field updatable product with a dual bank bootloader, so you can see these techniques applied to problems that actually resemble what you're working on.Who is this for? If you're an embedded software engineer who wants to stop treating the linker script as a mysterious file you inherit rather than something you understand, this book is for you. If you're preparing to design firmware for a new microcontroller and don't want to discover memory layout mistakes after the hardware has already shipped, this book is for you. If you've ever been the person on your team who gets handed the "why won't this link correctly" problem and had to figure it out under pressure, this book will make that job considerably easier the next time it comes up.You don't need to be a linker expert to start. You do need some familiarity with C and a basic sense of how compiled programs work. Everything else, the memory maps, the address arithmetic, the startup sequencing, the security considerations, is built up carefully, one concept at a time, with working examples throughout.Firmware that boots reliably, updates safely, and behaves predictably in the field doesn't happen by accident. It happens because someone understood exactly where every piece of that firmware lives in memory, and why. This book will make sure that someone is you. This item is printed on demand. Shipping may be from multiple locations in the US or from the UK, depending on stock availability.…

PAP. Condizione: New. New Book. Shipped from UK. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000.

Paperback. Condizione: new. Paperback. Have you ever wondered what actually stands between the device you're designing and the person trying to break into it?If you build firmware for a living, or you're responsible for the security of a connected product, you already know the uncomfortable truth: most attackers don't bother with your cloud infrastructure or your mobile app. They go straight for the firmware, because it's the layer everyone assumes is safe simply because it's hard to see. Is your boot process actually verifying what it thinks it's verifying? Do you know exactly what happens to your cryptographic keys if someone gets physical access to a single unit in the field? If you're not confident in your answers, this book was written for you.Architecting Secure Embedded Firmware is a complete, practical guide to building embedded systems that can genuinely defend themselves, not just systems that look secure on a datasheet. It starts from first principles and walks through the entire discipline: how a hardware root of trust actually establishes confidence in a device from the moment power is applied, how a properly designed boot chain prevents unauthorized code from ever executing, and how to structure cryptographic keys so that a single compromised unit doesn't take down your entire fleet.Along the way, you'll work through real engineering questions that most books skip over. How do you decide which physical attacks are actually worth defending against for your specific product, rather than defending against everything and blowing your budget? How do you keep a firmware update mechanism from becoming the very backdoor an attacker uses to compromise every device you've ever shipped? How do you design access control boundaries so that one vulnerable component doesn't automatically hand over control of the whole system?This book covers: Hardware based trust anchors, secure boot design, and how to build a chain of trust that actually holds up under scrutinyPractical, disciplined approaches to memory safety, code integrity, and hardening your build and signing pipeline against supply chain compromiseCryptographic key hierarchies built for constrained devices, including guidance on preparing for a post quantum futureSecure communication protocol design for constrained networks, mutual authentication, and update delivery that can't be silently hijackedAccess control architecture, privilege isolation, and debug interface lockdown that closes the doors attackers rely on mostDefense against power analysis, electromagnetic leakage, and fault injection, for anyone building devices that face determined physical attackersVerification and testing methodology, including fuzzing, formal methods, and a clear path through the certification landscapeHow real industries, consumer products, industrial control systems, automotive electronics, medical devices, and critical infrastructure, actually apply these principles under their own specific constraintsWhether you're an embedded engineer trying to level up your security thinking, a technical lead responsible for a product that regulators are starting to scrutinize, or someone simply trying to understand why firmware security has become such an urgent topic, this book gives you something you can actually use. Not vague principles borrowed from enterprise software security, but engineering guidance built specifically for the constraints, the hardware, and the adversaries that embedded systems actually face.Your device is going to be in the field for years. The question is whether it's still going to be trustworthy when it gets there. This book will help you make sure it is. This item is printed on demand. Shipping may be from multiple locations in the US or from the UK, depending on stock availability. …

PAP. Condizione: New. New Book. Shipped from UK. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000.

PAP. Condizione: New. New Book. Shipped from UK. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000.

Condizione: New. Print on Demand.

Condizione: New. Print on Demand.

Condizione: New. Print on Demand.

Condizione: New. Print on Demand.

PAP. Condizione: New. New Book. Delivered from our UK warehouse in 4 to 14 business days. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000.

PAP. Condizione: New. New Book. Delivered from our UK warehouse in 4 to 14 business days. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000.

PAP. Condizione: New. New Book. Delivered from our UK warehouse in 4 to 14 business days. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000.

PAP. Condizione: New. New Book. Delivered from our UK warehouse in 4 to 14 business days. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000.

Paperback. Condizione: new. Paperback. Have you ever stared at a HardFault handler at two in the morning, with no idea what actually went wrong?Have you configured an interrupt priority, watched it behave exactly the opposite of what you expected, and had no real explanation why?Have you copied a vendor's example project, gotten it running, and realized you don't actually understand why it works?If any of that sounds familiar, you're not alone, and you're not missing some secret talent other engineers have. You're missing the underlying architecture, the part that never gets properly explained in a datasheet, a forum post, or a thirty minute YouTube tutorial.This book exists to fix that.It's written for engineers, students, and hobbyists working with 32 bit microcontrollers built around the Cortex-M processor family, the small, efficient cores that run inside everything from wearables and medical devices to industrial sensors and automotive control modules. Rather than teaching you to copy and paste working code, it teaches you to understand the processor itself: how it fetches and executes instructions, how memory is actually organized, how interrupts are prioritized and dispatched, and what's really happening when something goes wrong.So what will you actually walk away with?You'll understand the pipeline, register set, and instruction execution model well enough to read disassembly with confidence instead of dread. You'll know exactly how the memory map, bus architecture, and protection unit fit together, and how to use that knowledge to catch bugs before they become mysteries. You'll be able to configure interrupts correctly, reason about worst case timing, and diagnose a fault using the actual status registers instead of guessing. You'll learn how modern security extensions isolate trusted code from untrusted code at the hardware level, how secure boot and firmware updates are supposed to work, and how to design a memory map that keeps one buggy task from corrupting another. And you'll get a clear, honest look at where machine learning inference fits on a microcontroller, without the hype.Is this a beginner's book?Not exactly, but it doesn't assume you're already an expert either. If you can write C and you understand basic digital logic, you have everything you need to start. The early chapters build the foundation carefully, and the later chapters, covering real-time scheduling, functional safety, security architecture, and edge AI, will still be genuinely useful once you've moved well past the basics.What makes this different from the documentation you already have access to?Official reference manuals tell you what a register does. They rarely tell you why it matters, how it connects to everything else, or what mistake you're likely to make with it. This book fills that gap. It's built around real engineering scenarios: a fault that only appears under specific compiler settings, an interrupt that misses its timing budget, a memory corruption bug that takes hours to track down. You'll see how an experienced engineer actually reasons through problems like these, step by step, rather than just being handed a final answer.Whether you're a working engineer trying to go beyond the vendor's HAL library, a student trying to connect your coursework to real hardware, or a hobbyist tired of firmware that works by accident, this book is meant to be the resource that finally makes the processor make sense.Ready to actually understand the hardware you've been programming? This item is printed on demand. Shipping may be from multiple locations in the US or from the UK, depending on stock availability.…

PAP. Condizione: New. New Book. Shipped from UK. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000.

Condizione: New. Print on Demand.