Zum Hauptinhalt springen
Echtzeit-Radar & Feeds
Alle RSS Feeds ➔
👥 Community & Social
IT Security DownloadsGitHub Release: ollama/ollama v0.40.0-rc0 (25.09.2026)(25.09.2026 um 04:25 Uhr)
••••
Admin & Dev ToolsGitHub Release: can1357/oh-my-pi v18.3.1 (25.09.2026)(25.09.2026 um 04:34 Uhr)
•
YouTube Security VideosMicrosoft Mechanics: How to Tell If Your Copilot Agent Is Used(25.09.2026 um 03:15 Uhr)
••
Sicherheitslücken (CVE)CVE-2025-36939 | Google Nest 3.78.518349 MLE stack-based overflow(25.09.2026 um 03:20 Uhr)
•••
IT Security DownloadsGitHub Release: ollama/ollama v0.40.0-rc0 (25.09.2026)(25.09.2026 um 04:25 Uhr)
••••
Admin & Dev ToolsGitHub Release: can1357/oh-my-pi v18.3.1 (25.09.2026)(25.09.2026 um 04:34 Uhr)
•
YouTube Security VideosMicrosoft Mechanics: How to Tell If Your Copilot Agent Is Used(25.09.2026 um 03:15 Uhr)
••
Sicherheitslücken (CVE)CVE-2025-36939 | Google Nest 3.78.518349 MLE stack-based overflow(25.09.2026 um 03:20 Uhr)
•••
Intelligence View
⚡ tsecurity.de Intelligence

Nautilus devices are not just folders: understanding mount points after moving from Windows

After moving more of my workflow from Windows to Linux (Pop!_OS 24.04), I ran into something that initially looked confusing. In Nautilus, some storage locations appeared under "Devices" while others appeared as regular folders, even…

0
↗ Quelle (reddit.com)
Reagiere als Erste:r — dein Feedback zählt!

After moving more of my workflow from Windows to Linux (Pop!_OS 24.04), I ran into something that initially looked confusing.

In Nautilus, some storage locations appeared under "Devices" while others appeared as regular folders, even though they all ultimately pointed to mounted filesystems.

At first, I assumed this was just a visual distinction. After digging deeper, I realized there is a more important difference underneath.

## What I noticed

Some disks appeared automatically in the Nautilus sidebar under Devices.

Others appeared only as directories inside the filesystem hierarchy.

Both were accessible and working correctly, but they behaved differently.

## Investigation

After looking into how Linux handles storage, I found that there were two different mechanisms involved:

- Devices managed dynamically through the desktop environment and udisks

- Filesystems mounted through traditional mount points and fstab entries

From a file access perspective they can look similar.

From a system administration perspective they are not.

## Key observation

What finally made things click for me was understanding that a mounted filesystem is not the same thing as a device entry in Nautilus.

A device shown in the sidebar is a desktop-environment representation of a storage device.

A mount point is part of the Linux filesystem hierarchy.

The two often point to the same data, but they are conceptually different.

## Why this matters

Once I understood the distinction, several things became clearer:

- why some disks appear automatically and others do not

- why permanent mounts are usually configured through fstab

- why scripts and applications often reference mount paths instead of Nautilus entries

- why Linux storage management feels different from Windows

## Result

Understanding this distinction helped me build a more predictable storage layout for my workstation.

Instead of relying on whatever appears in the file manager sidebar, I now think in terms of mount points and filesystem structure.

For long-term workflows involving GIS projects, shared storage and backups, that mental model has been much more useful.

Has anyone else had a similar "Linux storage finally clicked" moment after coming from Windows?

submitted by /u/Big-Country8915
[link] [comments]

1. Sofort-Triage & Abwehrmaßnahmen

SOC Incident Playbook: Vulnerability Remediation & Verification
Syntax validiert (0 Fehler)
title: Detect Exploitation - Nautilus devices are not just folders: understanding mount points after moving from Windows
id: d94dc0df-3ccf-44de-bec9-1b8bb7c6059e
status: experimental
description: Automatisch generierte SIEM-Erkennungsregel basierend auf CTI Intelligence
references:
  - https://tsecurity.de/
author: iShareStuff CTI Automated Detection Engine
date: 2026-09-25
logsource:
  category: network_connection
  product: any
detection:
  selection:
      CommandLine|contains:
        - 'exploit'
  condition: selection
falsepositives:
  - Legitime administrative Zugriffe oder Penetrationstests
level: high
tags:
  - attack.initial_access
Syntax validiert (0 Fehler)
rule CTI_Threat_Indicator {
    meta:
        author = "iShareStuff CTI Automated Detection Engine"
        date = "2026-09-25"
        description = "YARA Signature for "
    strings:
        $str = "Nautilus devices are not just " ascii wide
    condition:
        any of them
}
Syntax validiert (0 Fehler)
index=security sourcetype IN ("cisco:asa", "pan:traffic", "zeek_conn", "suricata", "WinEventLog:Security")
("Nautilus devices are not just folders un")
| stats count earliest(_time) as first_seen latest(_time) as last_seen by src_ip, dest_ip, dest_host, signature
| eval first_seen=strftime(first_seen, "%Y-%m-%d %H:%M:%S"), last_seen=strftime(last_seen, "%Y-%m-%d %H:%M:%S")
| sort - count
Syntax validiert (0 Fehler)
message: "*Nautilus devices are not just folders un*"
Syntax validiert (0 Fehler)
CommonSecurityLog
| where Message has "Nautilus devices are not just folders un"
| summarize EventCount = count(), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated) by SourceIP, DestinationIP, DestinationPort, Activity
| extend DetectionRule = "iShareStuff-CTI-Compiled"
| sort by EventCount desc

2. Cyber Threat Intelligence & Forensik

CTI Threat Relationship Graph2 Knoten / 1 Relationen
CVE / Incident Software MITRE ATT&CK CWE Weakness IoC
🎯
MITRE ATT&CK Matrix Navigator 14 Taktiken
Reconnaissance
-
Resource Development
-
Initial Access
Execution
Persistence
-
Privilege Escalation
Defense Evasion
Credential Access
-
Discovery
-
Lateral Movement
-
Collection
-
Command and Control
Exfiltration
-
Impact
tsecurity.de Cognitive Threat RAG
Fokus-Vektor:

Kognitive Analyse für identifizierte Bedrohung: Erhöhte Bedrohungslage im Bereich Nautilus devices are not just folders: u.... Basierend auf 368k Vektor-Korrelationen werden sofortige Isolationsmaßnahmen für betroffene Endpunkte empfohlen.

🛡️ Angriffsfläche & Exposure

Netzwerk/Remote-Zugriff ohne Vorauthentifizierung möglich.

⚡ Empfohlene Sofortmaßnahmen
  • 1. Perimeter-Inspektion: Relevante Portfreigaben und exponierte Endpunkte unverzüglich scannen.
  • 2. Patch-Applikation: Hersteller-Hotfix einspielen oder betroffene Daemons in isolierte DMZ-Segmente überführen.
  • 3. Telemetrie & EDR-Alerts: Prozessaufrufe und Child-Processes auf anomale Shell-Spawns überwachen.
🔗 Semantisch verwandte Zero-Days MariaDB 11.7 VEC
Ähnliche Beiträge
🔍 Verwandte News

Auch interessante Nachrichten Nautilus devices are not just folders: understanding mount points after moving from Windows

Thematisch verwandte Begriffe: Nautilus, devices, just, folders · 6 Treffer

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Zum Aktualisieren ziehen
ZERO-DAY CVE-2026-87722 | Uncontrolled Resource Consumption (CWE-400 / CWE-1333) in regex search q…
Advisory →
tsecurity.de Icon
Offline-Lesen, Eilmeldungen & 0ms Ladezeit

Installiere tsecurity.de direkt auf deinen Home-Bildschirm für das ultimative Vollbild-Magazinerlebnis ohne Browser-Leisten.

Nächster Beitrag
Themen-Radar & Intelligence Matrix
Echtzeit-Taxonomie nach Angriffsvektoren & Plattformen

tsecurity.de Live Threat Radar

🔴 LIVE RADAR
MONITORING
AKTIV
CVE-DATENBANK
LIVE
🔍
Community Radar & Live Chat
Sentinel Bot online • Live-Stream
Dein Cluster: Security Explorer
Match:
lädt…
Verbindung zum Community-Stream wird aufgebaut...
Bearbeitungsmodus — Senden überschreibt deine Nachricht
Community-Puls — was gerade passiert
lädt…
Aktivitäten deiner Analysten
lädt…
Neues Thema oder Eilmeldung einreichen

Reiche interessante Links, Zero-Days oder Debatten ein. Die Community entscheidet per Upvote über die Veröffentlichung.

Heiß diskutierte Einreichungen
📂 Keine gespeicherten Artikel vorhanden.
Zurück Ziehen Vor
Links: vorheriger Artikel • Rechts: nächster Artikel • unten: schließen
News NIS-2 Frühwarnung Tier-1 Intel TTP ⏱️ 3 Min vor 10 Min
Artikeldaten werden geladen...
↗ Original-Quelle