On Fri, Nov 15, 2019 at 8:31 AM Hongyi Zhao via arch-general <
arch-general@archlinux.org> wrote:
> Hongyi Zhao 于2019年11月15日周五 下午9:13写道：
> >
> > Ralph Corderoy 于2019年11月15日周五 下午8:57写道：
> >
> > >
> > > Hi Hongyi,
> > >
> > > > I noticed that for many distro's install iso, there are some efi
>
> I will go through the links guys, thanks a lot..
>
> And Yi Zheng, me neither like UEFI, but what to do, nowadays all laptops
> comes as UEFI.. and to change it to MBR i have to wipe the entire drive :(
>
It's actually much easier to dual boot with UEFI once you become familiar
with it. If your
If you're going to use automatic login, why not cut out the middle man and
ditch the display manager entirely?
Relevant wiki articles/sections:
Getty#Automatic_login_to_virtual_console
Xinit#Autostart_X_at_login
KDE#Manual
On Tue, Jul 18, 2017 at 10:08 AM, Junayeed Ahnaf via arch-general <
>
> So what? Is linux now about restricting user choice?
>
Arch is a pragmatic distribution, both for the users and developers.
Upstream decided to make pulseaudio a hard dependency specifically to
reduce maintenance costs on their end. Arch devs really aren't in the
business of adopting such
>
> Not about systemd, but about your request. This is the wrong list for
> such a request and apart from this, it's the wrong time to ask those
> questions. You are years too late with those questions.
>
I agree. This would be better suited for the Arch forums. We have a section
for general
>
> How can I get rid of this annoying flashing line.
>
> This is the currently used xorg.conf:
>
Does the problem persist if you remove your X config so it just runs the
defaults? In my experience Intel generally requires little to no
configuration to work well with X.
>
> All those distros, everyone except arch has decided at some point to no
> longer restrict the use of unprivileged user namespaces.
>
In no way whatsoever does Arch restrict the use of unprivileged user
namespaces. Rebuilding your kernel with them enabled is a trivial task for
any user
>
> I get an error about a conflict between .SRCINFO and PKGBUILD - how can I
> resolve this problem?
>
I'm not getting that error, have you tried cloning a fresh copy from AUR?
Regardless, you don't need to care about .SRCINFO unless you're the
maintainer. Just delete it.
Max
>
> CVE / ASA logging or however you call it is now officially hosted on
> https://security.archlinux.org
>
> The wiki is dead, long live the new awesome tracker :)
>
I will archive the old wiki articles in about a week. Get your arguments in
now if you want them to stick around.
>
> Allan has already declared that he will not change the default
> makepkg.conf, on the grounds that #2 is the most likely scenario for
> people getting malicious packages.
> He also wants everyone to know that updpkgsums and makepkg are perfectly
> okay with maintainers changing the defaults,
>
> So what do you guys think if we make our implicit standards available
> somewhere on the wiki. This would make it more transparent on how we
> build stuff, how TUs should package and give a guideline for AUR
> maintainers, as they might not know about some details like this.
>
The best way to
>
> You mean the source files that you downloaded and then hashed...
>
Yes. If the source files are being modified via a MITM attack (which is
trivial if the host uses HTTP) the checksum is still useful.
>
> I agree that we should use a strong hash by default where it makes
> sense. But in the absense ob effective validation of upstream packages,
> this is meaningless.
>
It would at least indicate that the source file has been tampered with in
some way. Even though there would be no way to know
> Morning. Try this, sudo pacman -Syu --force.
Please do not run that command unless the Arch site specifically recommends
it. Forcing a full system upgrade is extremely dangerous.
The safe solution is to force only ttf-dejavu.
>
> Do you Have any pointer to good opensource hardware ?
Not exactly open-source/FSF-endorsed but https://system76.com/ sells
laptops with Ubuntu-preinstalled so those are also guaranteed to run Arch.
On Thu, Sep 22, 2016 at 7:12 AM, mike lojkovic via arch-general <
arch-general@archlinux.org> wrote:
> I'm in favor of the merge as well. For beginners there are plenty of
> Youtube videos that cover common desktop setups. That should be more than
> enough for users who are first learning how to
16 matches
Mail list logo
