-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathfaq.html
127 lines (107 loc) · 5.7 KB
/
faq.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
<meta name="description" content="SquashFS.net">
<meta name="author" content="squashfs.net">
<title>SquashFS.net</title>
<!-- Bootstrap core CSS -->
<link href="/meta/bootstrap/css/bootstrap.min.css" rel="stylesheet">
<!-- IE10 viewport hack for Surface/desktop Windows 8 bug -->
<link href="/local/ie10-viewport-bug-workaround.css" rel="stylesheet">
<!-- Custom styles for this template -->
<link href="/meta/dejavu-fonts/dejavu-fonts.css" rel="stylesheet">
<link href="/meta/font-awesome/css/font-awesome.min.css" rel="stylesheet">
<link href="/local/font.css" rel="stylesheet">
<link href="/local/label.css" rel="stylesheet">
<link href="/local/margin.css" rel="stylesheet">
<link href="/local/navbar.css" rel="stylesheet">
<link href="/local/rotate.css" rel="stylesheet">
<link href="/local/table.css" rel="stylesheet">
<!-- HTML5 shim and Respond.js for IE8 support of HTML5 elements and media queries -->
<!--[if lt IE 9]>
<script src="/meta/html5shiv/html5shiv.min.js"></script>
<script src="/meta/respond/respond.min.js"></script>
<![endif]-->
</head>
<body>
<div class="container">
<!-- Static navbar -->
<nav class="navbar navbar-default">
<div class="container-fluid">
<div class="navbar-header">
<button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar" aria-expanded="false" aria-controls="navbar">
<span class="sr-only">Toggle navigation</span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
<a class="navbar-brand" href="/" style="color: black;"><b><i class="fa fa-fw fa-cogs" style="color: #03a9f4;"></i> SquashFS.net</b></a>
</div>
<div id="navbar" class="navbar-collapse collapse">
<ul class="nav navbar-nav navbar-right">
<li><a href="/topdownremaster.html"> Top Down Remaster </a></li>
<li><a href="/faq.html"> FAQ </a></li>
<li><a href="/sponsors.html"> Sponsors </a></li>
<li><a href="/about.html"> About </a></li>
</ul>
</div><!--/.nav-collapse -->
</div><!--/.container-fluid -->
</nav>
<!-- Content -->
<h1>FAQ (Under Construction)</h1>
<h3>Why Top Down Remastering and not Bottom Up?</h3>
<ul>
<li>
First let me say that building images from the Bottom Up in a pristine work environment is always a great option. It is my belief that many distributions, including Debian, build their officially released images in this manner.
However, for the average user who probably only wants a few minor adjustments to an officially released live Debian image they may be overwhelmed by one or more of the following:
<ul>
<li>The user does not build images on a regular basis and not sure where to start.</li>
<li>The user has little or no knowledge on the setup of a truly pristine build environment.</li>
<li>The user is overwhelmed with the tools and tool lexicon.</li>
<li>The user is confused as to why build attempts are failing.</li>
<li>...</li>
</ul>
Hence the user's quest for a custom live Debian image may never be achieved.
So why not provide options for the user to reach their desired goal of creating a custom live Debian image. Top Down Remastering is a very viable option allowing users to create custom images. Furthermore these custom images can be based on official live Debian images.
</li>
</ul>
<h3>Why are official live Debian images mentioned frequently?</h3>
<ul>
<li>There are many advantages of Top Down Remastering with official live Debian images. Below are just a few (not an exhaustive list) reasons why official images are preferred:
<ul>
<li>Official images are created by a talented team of creators.</li>
<li>Official images are pristine images.</li>
<li>Official images are production ready.</li>
<li>Official images offer a stable point in time reference to remaster with.</li>
<li>...</li>
</ul>
</li>
</ul>
<h3>Why the name SquashFS.net?</h3>
<ul>
<li>One primary reason is that <a href="https://en.wikipedia.org/wiki/SquashFS">squashfs filesystem</a> is a key component of live cd's created by many popular Linux distributions.</li>
<li>Also see the <a href="/about.html"> About </a>link.</li>
</ul>
<!-- /Content -->
<hr />
<footer>
<p class="text-muted">2016-2025 SquashFS.net | <a class="text-muted" href="mailto:unixabg@gmail.com?subject=squashfs.net:%20Feedback">System Administration</a> (<a class="text-muted" href="/legal-information.html">Legal Information</a>)</p>
</footer>
</div> <!-- /container -->
<!-- Bootstrap core JavaScript
================================================== -->
<!-- Placed at the end of the document so the pages load faster -->
<script src="/meta/jquery/jquery.min.js"></script>
<script>window.jQuery || document.write('<script src="/meta/jquery/jquery/min.js"><\/script>')</script>
<script src="/meta/bootstrap/js/bootstrap.min.js"></script>
<!-- IE10 viewport hack for Surface/desktop Windows 8 bug -->
<script src="/local/ie10-viewport-bug-workaround.js"></script>
<!-- Custom scripts for this template -->
<script src="/local/headings.js"></script>
<script src="/local/table.js"></script>
</body>
</html>