when you extract the tzdata archive, is it okay to leave all the packaged
files all separate in the /sources folder? or do theyhave to be in their
own dedicated folder like all the other packages
On Fri, Oct 28, 2016 at 6:03 PM, Ken Moffat wrote:
> On Fri, Oct 28, 2016
On Sat, 2016-10-29 at 22:44 -0400, jacob wrote:
> On 2016-10-29 22:04, Wayne Blaszczyk wrote:
> > On Sat, 2016-10-29 at 15:28 -0400, jacob wrote:
> > > Hello, I've recently completed an LFS build using GRUB-2.03~beta, and
> > > I've installed this using UEFI. When I boot linux however, I'm
> > >
Apologies for creating any sort of confusion.
My machine has x86_64 architecture. Earlier I was not sure of, it but now
I'm.
On Oct 29, 2016 11:53 PM, "Ken Moffat" wrote:
> On Sat, Oct 29, 2016 at 08:07:44PM +0530, Aditya Dixit wrote:
> > Hey William,
> >
> > Thanks
Hello, I've recently completed an LFS build using GRUB-2.03~beta, and
I've installed this using UEFI. When I boot linux however, I'm greeted
with a black screen. I'm unsure how to debug this as the kernel doesn't
even panic, it just sits.
Here are some configuration files
.config:
On Sat, Oct 29, 2016 at 08:07:44PM +0530, Aditya Dixit wrote:
> Hey William,
>
> Thanks for response.
>
> After hours of research I could figure out the significance of 139 but I
> still need to interpret the reason.
>
> And, as far as I know, my machine doesn't support x86_64 architecture.
>
On Sat, 29 Oct 2016 20:07:44 +0530
Aditya Dixit wrote:
> So what should I do regarding the architecture (if there is any, if my
> machine doesn't support x86_64 architecture)??
You would want to build for x86 and not x86_64.
Run "uname -m" to be certain of your host
Hey William,
Thanks for response.
After hours of research I could figure out the significance of 139 but I
still need to interpret the reason.
And, as far as I know, my machine doesn't support x86_64 architecture.
So what should I do regarding the architecture (if there is any, if my
machine