Le 02/08/2016 à 02:28, Stephen Powell a écrit :
On Mon, Aug 1, 2016, at 19:30, Pascal Hambourg wrote:
This is really surprising because, according to
<https://en.wikipedia.org/wiki/Pentium_M>, Pentium M models which
support PAE also support the NX bit. Actually, PAE support was added
j
Le 01/08/2016 à 04:02, Stephen Powell a écrit :
On Sun, Jul 31, 2016, at 19:07, Pascal Hambourg wrote:
PAE allows to use the NX/XD bit on CPU which support it to prevent
execution of data memory areas.
To the best of my knowledge, there are no 32-bit-only processors which
support the NX bit
Le 01/08/2016 à 00:00, Stephen Powell a écrit :
one's processor supports PAE, but the motherboard only supports a maximum of
2 GiB of RAM, what does a PAE kernel buy one? Nothing, as far as I can see.
PAE allows to use the NX/XD bit on CPU which support it to prevent
execution of data memory
Le 28/07/2016 à 20:47, Ric Moore a écrit :
On 07/28/2016 04:44 AM, Steve Matzura wrote:
ifconfig -a
eth0 Link encap:Ethernet HWaddr bc:5f:f4:5b:80:09
inet addr:192.168.1.130 Bcast:192.168.1.255
You might be caught up in an "improvement"
ric@iam:~$ sudo ifconfig
[sudo] pas
Le 28/07/2016 à 20:13, Pascal Hambourg a écrit :
Le 28/07/2016 à 11:26, Reco a écrit :
Check your Ethernet cable. NO-CARRIER either means that the cable is
unplugged from your NIC, or from whenever other end of the cable should
be plugged to, or the cable itself is damaged.
Or the internet
Le 28/07/2016 à 11:26, Reco a écrit :
Check your Ethernet cable. NO-CARRIER either means that the cable is
unplugged from your NIC, or from whenever other end of the cable should
be plugged to, or the cable itself is damaged.
Or the internet port is damaged, or the remote port is damaged or di
Le 27/07/2016 à 22:16, deloptes a écrit :
Pascal Hambourg wrote:
Le 26/07/2016 à 23:38, deloptes a écrit :
Did you check mdadm.conf - you usually regenerate it and recreate/update
initrd
Irrelevant. GRUB does not use mdadm.conf for booting.
I understood OP has problem with assembling MD
Le 27/07/2016 à 15:43, Steve Matzura a écrit :
My 8.0 system has been running great up until Monday evening when
users started reporting they were unable to connect. Sure enough, I
couldn't even connect from my LAN. I rebooted, looked at messages from
dmesg, and saw nothing unusual--nothing that
Le 26/07/2016 à 23:38, deloptes a écrit :
Daniel Guillermo Bareiro wrote:
(...)
The idea was to re-install without losing the containers I had
created. After finishing the installation process, GRUB failed
to boot with this message:
Did you check mdadm.conf - you usually regenerate it and
Le 24/07/2016 à 15:47, Hans a écrit :
Am Sonntag, 24. Juli 2016, 09:30:12 schrieb S. P. Molnar:
How do I force the re-installation of a file and all of it's dependencies?
A file or a package ?
1. I would deinstall the package (aptitude purge packagename), then maybe all
orphaned libs
Dein
Le 23/07/2016 à 03:19, Daniel Guillermo Bareiro a écrit :
The idea was to re-install without losing the containers I had
created. After finishing the installation process, GRUB failed
to boot with this message:
error: fail
Le 22/07/2016 à 23:21, Pascal Hambourg a écrit :
Can you write into a snapshot ?
I assumed that a snapshot was just an immutable image of the original
volume taken at a given moment.
Never mind, I just found out that LVM2 snapshots are read/write.
Thanks for the tip.
Le 22/07/2016 à 22:22, Stefan Monnier a écrit :
Use LVM, of course (and you can use LVM snapshots to speed up the
cloning).
Sounds like a nice idea, but how do you use snapshots to clone a logical
volume and then use the clone as a regular volume ?
Not sure what you mean by "regular volume".
Le 22/07/2016 à 20:29, Stefan Monnier a écrit :
Use LVM, of course (and you can use LVM snapshots to speed up the
cloning).
Sounds like a nice idea, but how do you use snapshots to clone a logical
volume and then use the clone as a regular volume ?
Le 22/07/2016 à 20:07, Richard Owlett a écrit :
The partition will be marked "read only" *AFTER* install.
May I ask how you intend to do this ?
AFAIK, there is no persistent way to mark a partition or filesystem
read-only. GPT partition table entries have a read-only flag but it
seems to be
Le 22/07/2016 à 18:04, Richard Owlett a écrit :
That base install *SHALL BE* on a read-only partition (e.g. sda5).
I wish to "almost clone" it to sda5, (e.g. sda6, sda7, sda8).
(...)
Does that make sense?
Not really.
1) You cannot install on a read-only partition.
2) It does not make sense
Le 19/07/2016 à 16:01, Urs Thuermann a écrit :
Shouldn't the device nodes and entries in /proc/partitions
disappear when the drive is pulled? Or does the BIOS or the SATA
controller have to support this?
2. Can I hotplug the new drive and rebuild the RAID array?
As others replied, t
Le 17/07/2016 à 09:36, Andre Majorel a écrit :
For a shell to type the ping command in, try [ctrl]-[alt]-[f2],
[ctrl]-[alt]-[f3] and so on. To go back to the Debian installer,
[ctrl]-[alt]-[f1], if memory serves.
Or Alt+F5 if the installer is in graphic mode.
Note that you don't need to press
Le 11/07/2016 à 08:21, Miroslav Zaťko a écrit :
Same error here. First boot after fresh installation of Debian 8.5.0
from netinst CD finished with:
-BEGIN
error: invalid arch-independent ELF magic.
Entering rescue mode...
grub rescue>
-
Le 09/07/2016 à 22:41, Stephen Powell a écrit :
So I'm not concerned about it's maintenance status. As long as there are
PCs with a BIOS, or a CSM, lilo will remain usable. If the BIOS/CSM goes,
lilo goes with it. lilo can't function without a BIOS/CSM. But for UEFI-only
systems, there's elil
Le 09/07/2016 à 22:00, Brian a écrit :
All well and good but the installer inexplicably offers a choice between
GRUB and LILO. The installer manual is unhelpful on which to choose. A
newcomer wouldn't have a clue. We do them no service with this retrograde
offering. Get rid of it.
What is the p
Le 29/06/2016 à 10:30, deloptes a écrit :
rhkra...@gmail.com wrote:
My system has had several linux-images updated, but, the last one ("linux-
image-3.2.0-4-amd64 Linux 3.2 for 64-bit PCs) failed to install.
What is the failure reason?
Any printed message may be relevant.
If you keep your
Le 18/06/2016 18:19, Dan Purgert a écrit :
Pascal Hambourg wrote:
Le 17/06/2016 21:52, Jochen Spieker a écrit :
Pascal Hambourg:
Hmm. I don't know how SSL works, but HTTPS runs on top of TCP so I doubt
that it cares about IP packet size. The task of splitting the TCP payload
stream in
Le 17/06/2016 21:52, Jochen Spieker a écrit :
Pascal Hambourg:
Hmm. I don't know how SSL works, but HTTPS runs on top of TCP so I doubt
that it cares about IP packet size. The task of splitting the TCP payload
stream into IP packets is done by the TCP layer.
Sure, but if your encry
Le 16/06/2016 22:13, Dan Purgert a écrit :
Pascal Hambourg wrote:
Le 16/06/2016 18:18, Dan Purgert a écrit :
1)
So, the fact that HTTPS doesn't ~actually~ provide you with any security
when a "malicious party" has root accesss to the webserver,
AND that it
adds overhead to t
Le 16/06/2016 18:18, Dan Purgert a écrit :
1)
So, the fact that HTTPS doesn't ~actually~ provide you with any security
when a "malicious party" has root accesss to the webserver,
AND that it
adds overhead to the transmission
Does it really add network overhead of just CPU overhead on the se
Le 11/06/2016 12:28, Shailesh Pundlik a écrit :
recently I downloaded a copy of Debian 8 dvd
I liked it and I wanted to download Debian cd alos.
But while the dvd works ok the cds do not.
"Available data insufficient. Unable to compute."
Le 19/05/2016 00:58, Felix Miata a écrit :
Lisi Reisz composed on 2016-05-18 23:40 (UTC+0100):
Can one still use grub-legacy with modern kernels?
It's what I'm using for launching all my Debians, Fedoras, openSUSEs,
Mageias and more. Distros that no longer offer grub-legacy get installed
here
Le 19/05/2016 07:46, deloptes a écrit :
Haha, that's fair enough. It took me about 1h to reverse the setup to paper,
that I have done few years ago on one server with 12disks
Not only uuid, but crypt and lvm on top. I finally draw a map with this.
Tip : lsblk comes in handy to print the relati
Le 17/05/2016 17:41, Peter Hillier-Brook a écrit :
I recently re-formatted and re-partitioned a second disk that I use for
experimenting with various distributions. A consequence is that previous
UUIDs have disappeared into the bit bucket but, during booting of my
main system a script somewhere i
Le 05/05/2016 21:05, ken a écrit :
Working on the Pi just from the bash prompt as root, how do I set the
routing table (etc.) to connect directly to the DSL modem? The routing
table on my router currently shows:
# route -n
Kernel IP routing table
Destination Gateway Genmask
Stefan Monnier a écrit :
>> How can I set up a machine to boot in UEFI mode when the running kernel was
>> booted in legacy mode?
>
> AFAIK it goes something like this:
> - Use a GPT partition table, rather than MBR (you can usually convert
> from one to the other without reformatting, but that
Thomas Schmitt a écrit :
>
> The Debian ISOs for i386 and amd64 are supposed to boot via EFI.
As outlined by someone else, this is correct for installation images.
Live images lack a UEFI boot capability.
However be aware that UEFI comes in two flavours on x86 platforms :
32-bit or 64-bits. Even
Le 30/03/2016 17:17, Alan McConnell a écrit :
I have two further requests: 1. does anyone know how to proceed
from the prompt 'grub>' There are all kinds of commands available
from that point; will any lead me to the goal of getting a kernel
to boot?
It is
Alan McConnell a écrit :
>
> I am running wheezy, and would like to upgrade to jessie. To
> that end I've bought a CD and a USB stick from LinuxCollections.
> My problem: when booting I can't get into my bios to change the
> boot order. No matter what key I press, the system continues
> on with
Gene Heskett a écrit :
> On Friday 25 March 2016 15:48:56 Pascal Hambourg wrote:
>
>> Le 20/03/2016 19:58, Gene Heskett a écrit :
>>> On Sunday 20 March 2016 14:39:41 Pascal Hambourg wrote:
>>>> Le 20/03/2016 17:56, Gene Heskett a écrit :
>>>>> N
Le 20/03/2016 19:58, Gene Heskett a écrit :
On Sunday 20 March 2016 14:39:41 Pascal Hambourg wrote:
Le 20/03/2016 17:56, Gene Heskett a écrit :
Now, I do note that sdb has a re-allocated sector count of 25, but
no clue as to how many spares are left
You can estimate it from the initial and
Adam Wilson a écrit :
> On Sun, 20 Mar 2016 12:51:56 +0100
> Pascal Hambourg wrote:
>> Adam Wilson a écrit :
>
>>> USB can still
>>> only be booted from UEFI, but newer d-i means that installation now
>>> proceeds as normal until the point at which
Le 20/03/2016 17:56, Gene Heskett a écrit :
Now, I do note that sdb has a re-allocated sector count of 25, but no
clue as to how many spares are left
You can estimate it from the initial and current normalized values of
the attribute.
Remaining = raw value * norm. value / (init. norm. value
Adam Wilson a écrit :
> On Sun, 20 Mar 2016 12:51:56 +0100
> Pascal Hambourg wrote:
>
>> Did you try to boot a non-EFI capable USB boot media, such as a Debian
>> live image or a Debian installation image with the EFI partition
>> deleted ?
(I guess that just changin
Frank McCormick a écrit :
> Installed 64 bit version of Stretch yesterday and noticed this morning
> I am apparently missing some firmware.
>
> update-initramfs: Generating /boot/initrd.img-4.4.0-1-amd64
> W: Possible missing firmware /lib/firmware/tigon/tg3_tso5.bin for module tg3
> W: Possible m
Adam Wilson a écrit :
>
> There is a potential problem also where modern machines (with UEFI
> boot) fail to install off USB without UEFI, meaning that if you want a
> UEFI-free install, you have to use optical media.
I have a rather old (~2007) UEFI motherboard which does the opposite :
its UEFI
Kynn Jones a écrit :
>
> It turns out that I backed up the hard disk (HD) to the external drive
> (XD) twice. The first backup went well, as far as I can tell. I
> spot-checked individual files, etc. Everything looked normal.
>
> This first backup would have sufficed, but after I had done it I
supersonicsnow a écrit :
>
> *I expect that dhcpcd should not be involved at all with**my STATIC
> wlan0, is that correct?*
IIUC, not any more if you have dhcpcd5 (the only version available in
the current stable Jessie). It is an autonomous daemon which detects
when an interface is up and tries
Brian a écrit :
>
> Why should the installer ask for firmware if it knows it is present in
> /lib/firmware? Your problem is that the firmware is not transferred to
> the device. The consequence is that the wireless interface wlan0 is not
> detected. The syslog should confirm this.
Or not. It does
Le 08/03/2016 18:59, Dan Ritter a écrit :
https://wiki.debian.org/BridgeNetworkConnections
There are special instructions for wireless bridges.
Interesting, but it won't be of much help if the kernel itself prohibits
bridging of a wireless interface.
Andy Smith a écrit :
>
> On Mon, Mar 07, 2016 at 03:39:26AM +, Andy Smith wrote:
>> As per
>> http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/
>> I wrote an ISO of the current amd64 netinst including non-free
>> firmware to a USB and booted from it.
>>
>> At no poin
David Wright a écrit :
> On Sat 05 Mar 2016 at 21:18:55 (+0100), Pascal Hambourg wrote:
>> David Wright a écrit :
>>> You can't create files on an unmounted filesystem.
>> Of course you can, with the adequate tools. For instance mtools for FAT,
>> e2tools for
Hello,
timothy.marion@marion.systems a écrit :
>
> I am to stupid to figure out how to setup a bridge using wlan0.
No, you're not. You're just ignorant of an important fact : bridging of
a wireless interface in managed (asociated) or adhoc mode has been
disabled for some time now, because, by de
David Wright a écrit :
>
> You can't create files on an unmounted filesystem.
Of course you can, with the adequate tools. For instance mtools for FAT,
e2tools for ext2, ntfs-3g (previoulsy ntfsprogs) for NTFS.
to...@tuxteam.de a écrit :
>
> It was perceived as an artificial limitation which has no place in
> the kernel. Actually, I can conceive use cases for mount shadowing
> the content of a directory.
Typically : /dev
> On 02/03/16 08:42 AM, Albin Otterhäll wrote:
>> When doing a guided partition when installing debian, the
>> debian-installer creates a EFI (/boot/efi) partition with approximately
>> 500MB, and a /boot partition with around 250MB. Why this weird ratio
>> between them?
There is no ratio. 500 MB
Disclaimer : I do not use mutt nor any SSD yet.
Joel Roth a écrit :
>
> I have debian installed on a single SSD partition,
> with ordinary desktop use.
>
> When I set the strictatime option, mutt accurately shows new
> mails arriving. (I'm using mbox format.)
Doesn't mutt work with relatime, w
Felix Miata a écrit :
> Pascal Hambourg composed on 2016-02-15 20:52 (UTC+0100):
>
>>> be warned, if you use the partition table edit solution, uuid changes
>>> each time you touch a partition.
>
>> No, UUID don't change unless you change the contents
Frank McCormick a écrit :
> I have deleted a partition from my HD containing a distro I no longer use.
> As a result, my partitions on /dev/sda are numbered sda1. sda2 (windows)
> and sda4. sda3 contained the distro I dumped.
>
> Can I just use fdisk or fsdisk to dump the existing partition recor
jdd a écrit :
>
> be warned, if you use the partition table edit solution, uuid changes
> each time you touch a partition.
No, UUID don't change unless you change the contents of a partition.
They are not in the partition table. Same with labels.
Gary Dale a écrit :
> I have a Jessie/64 server that seems to have lost a lot of disk space.
> It boots from a 55G SSD (mounted as /) with a RAID6 array for /home. df
> shows that the SSD is full but I can't find out where the space has
> gone. When I add up all the space in the various director
Fabrizio Carrai a écrit :
> Yes! The GRUB_TERMINAL=console setting works...at least I moved forward.Now
> I can access and edit the GRUB menu.
Note that it may still be possible to use the graphic terminal but with
specific graphics mode selected in /etc/default/grub.
> Now the last messages visi
Brian a écrit :
> On Fri 05 Feb 2016 at 15:05:27 +0100, Fabrizio Carrai wrote:
>
>> Then, at the boot time, nothing happen. After the BIOS messages the screen
>> remain black (no messages at all).
>>
>> I temporary move the disk to another computer and then I was able to boot
>> the fresh Debian i
(Resent)
Hello,
Mike Gabriel a écrit :
>
> I did not meet that issue on my test rig. I will check the recently
> upload package and report back.
FWIW, I just upgraded the isc-dhcp-server package on my i386 Squeeze
server and did not meet that issue. It only has /etc/dhcp/dhcpd.conf, no
/etc/dh
Thilo Six a écrit :
>
> today DSA-3436-1 for openssl was released. According to the DSA the new
> version
> for jessie is 1.0.1f-1, but current openssl version in jessie is
> 1.0.1k-3+deb8u2.
Quote from the announce :
=
For the stable distribution (jessie), the testing distribution (stretch)
Christian Seiler a écrit :
> On 01/08/2016 02:51 AM, Pascal Hambourg wrote:
>> Current tools won't align for compatibility purpose any more. The
>> default 1-MiB alignment is only for performance purpose, not compatibility.
>
> This is new to me - I always thought
Christian Seiler a écrit :
>
> Well sure, but MBR also has all the CHS baggage - and while it isn't
> used anymore on modern systems, there still is the de-factor standard
> of aligning the first partition with the first CHS-sector that is so
> ingrained historically that the gap between MBR and t
Christian Seiler a écrit :
>
> Ok, if you use MBR, only the first 512 bytes are used for the MBR
> partition table, so that the gap between those bytes and the first
> partition (and there is *always* a gap, the size depends on the
> details of the logical geometry of the disk) has traditionally
>
W. Martin Borgert a écrit :
>
> I try to install Jessie with a soft RAID6 of four disks, 1 TB each.
> The idea is to use the complete disk for RAID and then only on top
> separate swap and root.
>
> The installation worked fine on one machine, but for some reason,
> grub does not install on the f
Petter Adsen a écrit :
> Gene Heskett wrote:
>
>> I made the mistake of trying to install a wheezy derivitive on a 2T
>> drive that had been prepared using GPT partitions. The installer
>> could not see them at all, so after 2 tries, I just let it go ahead
>> and do its own partitioning and form
Sven Hartge a écrit :
> Pascal Hambourg wrote:
>>> Le duodi 2 nivôse, an CCXXIV, Sven Hartge a écrit :
>
>>>> And this is why I love the GPT. There is a defined space for the
>>>> bootloader to be and no nether region of swirly unknowness between
>>&g
Nicolas George a écrit :
>
> In the meantime, I can tell what I saw in the code, and this is: GRUB makes
> no difference between MBR-style partitions (that it calls internally
> "msdos") and GPT.
I repeat : the point is not MBR/MSDOS vs GPT. It is that the GRUB
installer handles *specially* one t
Nicolas George a écrit :
> Le septidi 7 nivôse, an CCXXIV, Pascal Hambourg a écrit :
>> There was nothing confusing in Sven's message until you mentionned UEFI
>> in response to "I love the GPT". Why did you start talking about UEFI ?
>
> For the early stag
Nicolas George a écrit :
> Le septidi 7 nivôse, an CCXXIV, Pascal Hambourg a écrit :
>> You are confusing GPT (partition table format) and UEFI (firmware and
>> boot interface).
>
> Quite the contrary, I am trying to de-confuse by using exactly the correct
> terms.
There
to...@tuxteam.de a écrit :
>
> On Wed, Dec 23, 2015 at 07:41:00AM -0300, Renaud OLGIATI wrote:
>
>> Or do I have to first create a (failed) array with mdadm ?
>
> For RAID 1 it shouldn't be necessary, AFAIR
You cannot mount directly a RAID 1 partition with format 1.1 or 1.2
because the RAID sup
Felix Miata a écrit :
>
> A RAID1 partition normally cannot be mounted as an sdX# device.
It can if the RAID superblock is located at the end of the partition.
I.e. the superblock format is 0.9 (obsolete) or 1.0.
However if the format is 1.1 or 1.2 (default), the superblock is located
at or near
Nicolas George a écrit :
> Le duodi 2 nivôse, an CCXXIV, Sven Hartge a écrit :
>> And this is why I love the GPT. There is a defined space for the
>> bootloader to be and no nether region of swirly unknowness between the
>> MBR and the start of the first partition.
Note that current partition tool
David Christensen a écrit :
>
> A good defense against an attacker with physical access is LUKS
> encryption on all partitions except /boot.
Ecryption alone does not protect agains attack scenarios involving /boot
tampering.
Kynn Jones a écrit :
>
> I don't understand why the ffmpeg version from stretch comes out as
> the best (and only remaining) candidate.
>
> How can I find out why the ffmpeg version from jessie (whatever that
> is) is not a candidate?
It appears that there is no ffmpeg package in Jessie.
Kent West a écrit :
>
> One thing I did notice in the auth logs is that the connection port
> seems to change every connection attempt; is that normal?
Yes. The client source port used by a typical TCP connection is ephemeral.
BAGI Ákos a écrit :
>
> Should it be the first or the only entry?
The only one. So it must be recursive if you need to resolve external
domains too. If it is not recursive and you need to resolve external
domains, then you should not list it in resolv.conf. Instead you should
set up and list a re
Aman Nangia a écrit :
> Can i format that usb as ext4 in win?
No, unless you install program which can do it.
> Or how do i format it as ext4 in ununtu in rescue mode?
mkfs.ext4 /dev/sdx1
(replace sdx1 with the actual partition device name on the USB disk)
Aman Nangia a écrit :
>
> 146gb sas (2.5" drive). There were 2 empty slots in the hp gen7 system
> in the front. I inserted this spare new disk in one of the slots.
Sorry, I know nothing about SAS.
>> USB has nothing to do with file size limits. It all depends on the
>> filesystem. FAT limits fi
aman nangia a écrit :
> hi,
>
> can hot-add of new disk be recognized under rescue mode when booted
> from linux dvd by any chance? (bcz we were able to see the data from the
> boot drive after mounting it to /b, thought to back up the data. The
> data is ~80-90gb and thought to insert a new disk
Neal P. Murphy a écrit :
> I think the last linux-image update broke my CPU fan.
It may help to mention which are the previous and current versions.
Renaud (Ron) OLGIATI a écrit :
> On Thu, 26 Nov 2015 12:41:27 -0500
> Felix Miata wrote:
>
>>> /dev/sd6 noneswapsw 0 0
>>
>> If you try to boot without removing that USB stick or powering down that USB
>> HD you forgot was connected, /dev/sda6 may get you a
Pascal Hambourg a écrit :
> Andrew McGlashan a écrit :
>> On 22/11/2015 8:01 PM, Pascal Hambourg wrote:
>>> How would a flaw in the motherboard BIOS/UEFI firmware allow to bypass
>>> the disk password ?
>> If it is able to snoop on your keyboard input.
>
>
Andrew McGlashan a écrit :
>
> On 22/11/2015 8:01 PM, Pascal Hambourg wrote:
>> How would a flaw in the motherboard BIOS/UEFI firmware allow to bypass
>> the disk password ?
>
> If it is able to snoop on your keyboard input.
I would not call this a flaw but actual malware.
Andrew McGlashan a écrit :
>
> On 22/11/2015 6:11 AM, Pascal Hambourg wrote:
>> Andrew McGlashan a écrit :
>>>> Assuming the vendor firmware has no backdoor or flaw allowing to bypass
>>>> the user-defined password.
>>> Ditto for the drive's own
Andrew McGlashan a écrit :
>
> On 22/11/2015 6:17 AM, Pascal Hambourg wrote:
>> I do not see how this "solution" protects against tampering of the
>> unencrypted boot part.
>
> True, physical access and you are still toast.
The only solution I have read abo
Andrew McGlashan a écrit :
>
> On 21/11/2015 1:59 PM, David Christensen wrote:
>> On 11/20/2015 01:04 AM, Pascal Hambourg wrote:
>>> Anyone with physical access can do whatever they want. You can
>>> set up restrictions in the BIOS or set restrictions in the boot
Andrew McGlashan a écrit :
>
> On 21/11/2015 8:17 PM, Pascal Hambourg wrote:
>> David Christensen a écrit :
>>> As I understand it, self-encrypting drives (SED) encrypt everything
>>> (including the boot partition). To use this feature, you need a
>>> co
David Christensen a écrit :
>
> As I understand it, self-encrypting drives (SED) encrypt everything
> (including the boot partition). To use this feature, you need a
> computer with BIOS/ UEFI that supports it -- e.g. the BIOS will prompt
> you for the password during POST; if you don't enter t
Joel Rees a écrit :
>
> Thinking in terms of partitions as the things you mount in /etc/fstab.
Err, no. The things you mount in /etc/fstab are filesystems, not
partitions. A filesystem may not even lie in a partition or volume
(think about tmpfs, nfs...).
Ross Boylan a écrit :
> So the operations are simply setting up an environment for doing the
> rescue, not overwriting the existing system?
Even in installer mode, nothing is written on the disks until you
validate the changes in partman, the partitioning tool.
Ross Boylan a écrit :
> After booting the Debian 8.2 netinst iso I noticed a couple of oddities.
>
> First, I selected advanced and rescue, but this seemed to end up walking me
> through the installer.
Indeed, the first steps are identical to an installation.
> I was expecting to be dropped into
Himanshu Shekhar a écrit :
> This reminds of an outcome that makes your system vulnerable to data theft.
> Following the above steps, anyone having physical access to the device by
> any means (which is more likely in case of mobile devices), could gain root
> access and do whatever one wants to do
Chris Bannister a écrit :
> On Thu, Nov 19, 2015 at 06:41:50AM +0100, Jochen Spieker wrote:
>> Brian:
>>> To remove every package and the package lists in apt/archives:
>>>
>>> apt-get clean.
>> The package lists are unaffected by the clean operation. You do not need
>> to run an update afterward
Joel Rees a écrit :
>
> I think I have heard of people booting straight out of LVM partitions,
> but that takes more gum tape than I like to use. I do believe grub is
> able to look into LVM partitions somewhat these days,
Indeed. And Linux software RAID.
> so you may want
> to play with having
Gary Dale a écrit :
>
> modprobe r8169
> ifup eth1
>
> For some reason the kernel module isn't loading at startup.
Didn't you install the r8168 driver from Realtek for the previous kernel
and blacklist the r8169 module (check /etc/modprobe.d/) ?
Richard Owlett a écrit :
> In some of my reading I came across a page recommending LVM for
> ease of adjusting space.
>
> When searching for more information all I'm finding are
> essentially HOWTO's with only a couple of paragraphs on "Whats"
> and "Whys". Essentially nothing on "Why not".
>
rlhar...@oplink.net a écrit :
> On Fri, November 13, 2015 7:52 pm, Dennis Wicks wrote:
>>
>> My hosting has changed servers and I have to move all my
>> stuff pretty soon. I need a ftp program that will do site-to-site transfers
>> without having to download to my PC first then upload to the destin
Patrick Schleizer a écrit :
>
> as I just learned on the mailing list, that at least the packages
> fail2ban and miniupnpd [and most likely arno-iptables-firewall also]
> modify iptables rules...
Firewall managers such as ufw, shorewall, firestarter...
Custom iptables scripts.
IDS such as portsen
rlhar...@oplink.net a écrit :
> On Sun, November 8, 2015 6:54 pm, Pascal Hambourg wrote:
>> Now you can try to set the interface up, run a DHCP client on it
>> (dhclient, pump, dhcpcd, udhcpc...) and check what happens.
>
> IPCop responds only to dhcpcd; but I do not know wh
701 - 800 of 1182 matches
Mail list logo
