On 07/09/2016 08:22, gevisz wrote:
> 3) changing hd1 and ahci1 throughout the entry to hd3 and ahci3
> (currently I am not sure about the last number but will find it
> out in the next boots)
> wich is strange as BIOS reports that the boot disk sits on the
> 0th IDE chanel and
> the
2016-09-07 1:03 GMT+03:00 gevisz :
> 2016-09-07 0:32 GMT+03:00 Neil Bothwick :
>> On Wed, 7 Sep 2016 00:05:32 +0300, gevisz wrote:
>>
>>> >> But it seems that GRUB does not read fstab... :(
>>> >
>>> > It does not, because it has not loaded the kernel yet, so it cannot do
>>> > anything on the syst
On 07/09/2016 01:57, Volker Armin Hemmann wrote:
> Am 01.09.2016 um 11:01 schrieb Alan McKinnon:
>> On 01/09/2016 09:18, gevisz wrote:
>>> 2016-09-01 9:13 GMT+03:00 Alan McKinnon :
On 01/09/2016 08:04, gevisz wrote:
>> [snip]
>>
it will take about 5 seconds to partition it.
And a few
On September 6, 2016 10:57:54 PM GMT+02:00, Grant wrote:
>> Hi, my site is being ravaged by an IP but dropping the IP via
>> shorewall is seeming to have no effect. I'm using his IP from nginx
>> logs. IP blocking in shorewall has always worked before. What could
>> be happening?
>
>
>I'm block
On September 6, 2016 10:17:53 PM GMT+02:00, Grant wrote:
>Hi, my site is being ravaged by an IP but dropping the IP via
>shorewall is seeming to have no effect. I'm using his IP from nginx
>logs. IP blocking in shorewall has always worked before. What could
>be happening?
>
>- Grant
Grant,
Wi
On Tue, Sep 6, 2016 at 6:03 PM, gevisz wrote:
> 2016-09-07 0:32 GMT+03:00 Neil Bothwick :
>> On Wed, 7 Sep 2016 00:05:32 +0300, gevisz wrote:
>>
>>> >> But it seems that GRUB does not read fstab... :(
>>> >
>>> > It does not, because it has not loaded the kernel yet, so it cannot do
>>> > anything
On Wed, Sep 07, 2016 at 12:38:40AM +0100, Neil Bothwick wrote:
> On Tue, 6 Sep 2016 18:22:54 -0500, Dutch Ingraham wrote:
>
> > > grub-mkconfig doesn't care about the fstab of the running distro
> > > since it scans your drives for all operating systems it can boot.
> > >
> > Sorry if I missed
Am 01.09.2016 um 11:01 schrieb Alan McKinnon:
> On 01/09/2016 09:18, gevisz wrote:
>> 2016-09-01 9:13 GMT+03:00 Alan McKinnon :
>>> On 01/09/2016 08:04, gevisz wrote:
> [snip]
>
>>> it will take about 5 seconds to partition it.
>>> And a few more to mkfs it.
>> Just to partition - may be, but I ver
On Tue, 6 Sep 2016 18:22:54 -0500, Dutch Ingraham wrote:
> > grub-mkconfig doesn't care about the fstab of the running distro
> > since it scans your drives for all operating systems it can boot.
> >
> Sorry if I missed something in this tome, but I was under the
> impression that a seperate ut
On Tue, Sep 06, 2016 at 10:32:35PM +0100, Neil Bothwick wrote:
> On Wed, 7 Sep 2016 00:05:32 +0300, gevisz wrote:
>
>
> grub-mkconfig doesn't care about the fstab of the running distro since it
> scans your drives for all operating systems it can boot.
>
Sorry if I missed something in this tome,
On Wed, 7 Sep 2016 01:03:19 +0300, gevisz wrote:
> > grub-mkconfig doesn't care about the fstab of the running distro
> > since it scans your drives for all operating systems it can boot.
> >
> > Either look in grub.cfg to see what it going on or post it here along
> > with the exact error message
2016-09-07 0:32 GMT+03:00 Neil Bothwick :
> On Wed, 7 Sep 2016 00:05:32 +0300, gevisz wrote:
>
>> >> But it seems that GRUB does not read fstab... :(
>> >
>> > It does not, because it has not loaded the kernel yet, so it cannot do
>> > anything on the system.
>>
>> Oh, poor little Grand Unified Boo
On Wed, 7 Sep 2016 00:05:32 +0300, gevisz wrote:
> >> But it seems that GRUB does not read fstab... :(
> >
> > It does not, because it has not loaded the kernel yet, so it cannot do
> > anything on the system.
>
> Oh, poor little Grand Unified Boot Loader!
>
> It cannot do anything! Even to
2016-09-07 0:07 GMT+03:00 Rich Freeman :
> On Tue, Sep 6, 2016 at 4:57 PM, gevisz wrote:
>>
>> It seems that now I should edit /boot/grub/grub.cfg directly
>> without even knowing its commands.
>>
>
> Well, if nothing else you can certainly read it and see what it is
> putting in there. If you pa
On 06/09/2016 22:57, Grant wrote:
>> Hi, my site is being ravaged by an IP but dropping the IP via
>> shorewall is seeming to have no effect. I'm using his IP from nginx
>> logs. IP blocking in shorewall has always worked before. What could
>> be happening?
>
>
> I'm blocking like this with th
On 06/09/2016 23:05, gevisz wrote:
> 2016-09-06 22:54 GMT+03:00 Neil Bothwick :
>> On Tue, 6 Sep 2016 21:38:07 +0300, gevisz wrote:
>> grub-mkconfig should use UUIDs by default, unless you have uncommented
>>
>> #GRUB_DISABLE_LINUX_UUID=true
>
> I did not. So, it is a bug in a almighty Grand Uni
On Tue, Sep 06, 2016 at 01:57:54PM -0700, Grant wrote:
> > Hi, my site is being ravaged by an IP but dropping the IP via
> > shorewall is seeming to have no effect. I'm using his IP from nginx
> > logs.
What you really need is to set up net-anlyzer/fail2ban and not do this
kind of stuff manually.
On Tue, Sep 6, 2016 at 4:57 PM, gevisz wrote:
>
> It seems that now I should edit /boot/grub/grub.cfg directly
> without even knowing its commands.
>
Well, if nothing else you can certainly read it and see what it is
putting in there. If you page down you'll hit the actual menus which
are readab
2016-09-06 22:54 GMT+03:00 Neil Bothwick :
> On Tue, 6 Sep 2016 21:38:07 +0300, gevisz wrote:
>
>> > It sounds like you are specifying the root device by device node and
>> > those have changed with the addition of a new drive. Using UUID or
>> > LABEL will avoid this problem.
>>
>> Thank you for t
> Hi, my site is being ravaged by an IP but dropping the IP via
> shorewall is seeming to have no effect. I'm using his IP from nginx
> logs. IP blocking in shorewall has always worked before. What could
> be happening?
I'm blocking like this with the firewall running on the web server:
/etc/
2016-09-06 22:48 GMT+03:00 Daniel Frey :
> On 09/06/2016 12:39 PM, gevisz wrote:
>> 2016-09-06 22:08 GMT+03:00 Rich Freeman :
>>> On Tue, Sep 6, 2016 at 3:01 PM, gevisz wrote:
I have already looked into this file but did not find where to set the
UUID of the root partion.
>>>
>
Hi, my site is being ravaged by an IP but dropping the IP via
shorewall is seeming to have no effect. I'm using his IP from nginx
logs. IP blocking in shorewall has always worked before. What could
be happening?
- Grant
On Tue, Sep 6, 2016 at 4:10 PM, Alan McKinnon wrote:
> On 06/09/2016 21:39, gevisz wrote:
>>
>> 2016-09-06 22:08 GMT+03:00 Rich Freeman :
>>>
>>> On Tue, Sep 6, 2016 at 3:01 PM, gevisz wrote:
I have already looked into this file but did not find where to set the
UUID of the ro
On 06/09/2016 21:39, gevisz wrote:
2016-09-06 22:08 GMT+03:00 Rich Freeman :
On Tue, Sep 6, 2016 at 3:01 PM, gevisz wrote:
I have already looked into this file but did not find where to set the
UUID of the root partion.
It depends. :)
Usually you end up with root=UUID=abc on your kernel
On Tue, 6 Sep 2016 21:38:07 +0300, gevisz wrote:
> > It sounds like you are specifying the root device by device node and
> > those have changed with the addition of a new drive. Using UUID or
> > LABEL will avoid this problem.
>
> Thank you for the prompt reply!
>
> In my fstab, all the old d
On 09/06/2016 12:39 PM, gevisz wrote:
> 2016-09-06 22:08 GMT+03:00 Rich Freeman :
>> On Tue, Sep 6, 2016 at 3:01 PM, gevisz wrote:
>>>
>>> I have already looked into this file but did not find where to set the
>>> UUID of the root partion.
>>>
>>
>> It depends. :)
>>
>> Usually you end up with ro
2016-09-06 22:08 GMT+03:00 Rich Freeman :
> On Tue, Sep 6, 2016 at 3:01 PM, gevisz wrote:
>>
>> I have already looked into this file but did not find where to set the
>> UUID of the root partion.
>>
>
> It depends. :)
>
> Usually you end up with root=UUID=abc on your kernel command line. It
> lo
On Tue, Sep 6, 2016 at 3:01 PM, gevisz wrote:
>
> I have already looked into this file but did not find where to set the
> UUID of the root partion.
>
It depends. :)
Usually you end up with root=UUID=abc on your kernel command line. It
looks like grub-mkconfig is supposed to do this automatica
2016-09-06 21:45 GMT+03:00 Willie M :
> On 09/06/2016 11:38 AM, gevisz wrote:
>> 2016-09-06 21:21 GMT+03:00 Neil Bothwick :
>>> On Tue, 6 Sep 2016 21:16:12 +0300, gevisz wrote:
>>>
I had one IDE hard drive for /
and one SATA hard drive for /home
After adding another (yet non-for
On 09/06/2016 11:38 AM, gevisz wrote:
> 2016-09-06 21:21 GMT+03:00 Neil Bothwick :
>> On Tue, 6 Sep 2016 21:16:12 +0300, gevisz wrote:
>>
>>> I had one IDE hard drive for /
>>> and one SATA hard drive for /home
>>>
>>> After adding another (yet non-formatted) SATA hard drive
>>> the system panics a
2016-09-06 21:24 GMT+03:00 Willie M :
> On 09/06/2016 11:20 AM, gevisz wrote:
>> 2016-09-06 21:16 GMT+03:00 gevisz :
>>> I had one IDE hard drive for /
>>> and one SATA hard drive for /home
>>>
>>> After adding another (yet non-formatted) SATA hard drive
>>> the system panics and complains that it
2016-09-06 21:21 GMT+03:00 Neil Bothwick :
> On Tue, 6 Sep 2016 21:16:12 +0300, gevisz wrote:
>
>> I had one IDE hard drive for /
>> and one SATA hard drive for /home
>>
>> After adding another (yet non-formatted) SATA hard drive
>> the system panics and complains that it cannot find kernel
>> (if
On 09/06/2016 11:20 AM, gevisz wrote:
> 2016-09-06 21:16 GMT+03:00 gevisz :
>> I had one IDE hard drive for /
>> and one SATA hard drive for /home
>>
>> After adding another (yet non-formatted) SATA hard drive
>> the system panics and complains that it cannot find kernel
>> (if I understood it corr
On Tue, 6 Sep 2016 21:16:12 +0300, gevisz wrote:
> I had one IDE hard drive for /
> and one SATA hard drive for /home
>
> After adding another (yet non-formatted) SATA hard drive
> the system panics and complains that it cannot find kernel
> (if I understood it correctly :).
>
> As it happens af
2016-09-06 21:16 GMT+03:00 gevisz :
> I had one IDE hard drive for /
> and one SATA hard drive for /home
>
> After adding another (yet non-formatted) SATA hard drive
> the system panics and complains that it cannot find kernel
> (if I understood it correctly :).
>
> As it happens after the GRUB(2)
I had one IDE hard drive for /
and one SATA hard drive for /home
After adding another (yet non-formatted) SATA hard drive
the system panics and complains that it cannot find kernel
(if I understood it correctly :).
As it happens after the GRUB(2) menu, I suspect GRUB(2).
Just executed
# grub-mkc
36 matches
Mail list logo
