如果您想了解即使具有管理员权限，也无法将R-4.1.0安装到Windows10的相关知识，那么本文是一篇不可错过的文章，我们将为您提供关于AlpineLinux安装到RaspberryPi、cento

如果您想了解即使具有管理员权限，也无法将 R-4.1.0 安装到 Windows 10的相关知识，那么本文是一篇不可错过的文章，我们将为您提供关于Alpine Linux 安装到 Raspberry Pi、centos – 安装到/ opt / rh的RPM、ESP32 - 连接到 MCP23009即使连接返回成功，也无法将 OUTPUT 设为 HIGH ( 0 )、ext3grep 安装到 make 时报错的有价值的信息。

本文目录一览：

• 即使具有管理员权限，也无法将 R-4.1.0 安装到 Windows 10
• Alpine Linux 安装到 Raspberry Pi
• centos – 安装到/ opt / rh的RPM
• ESP32 - 连接到 MCP23009即使连接返回成功，也无法将 OUTPUT 设为 HIGH ( 0 )
• ext3grep 安装到 make 时报错

即使具有管理员权限，也无法将 R-4.1.0 安装到 Windows 10

如何解决即使具有管理员权限，也无法将 R-4.1.0 安装到 Windows 10

我拥有桌面的管理员权限。但是马上，安装程序给了我这个警告： You should be logged in as an administrator when installing R

我在 Program Files 中创建了 R 文件夹，但安装程序仍然声称它无法创建文件。你们中有人有解决方案吗？

谢谢。

Alpine Linux 安装到 Raspberry Pi

Alpine Linux 安装到 Raspberry Pi

This tutorial will help you install Alpine Linux on your Raspberry Pi.

Preparation

This section will help you format and partition your SD card:

1. Download Alpine for Raspberry Pi tarball which is named as alpine-rpi-<version>-armhf.rpi.tar.gz. You will need version 3.2.0 or greater if you have a Raspberry Pi 2.
2. Mount your SD card to your workstation
3. Use gnome-disks or fdisk to create a FAT32 partition. If you are using fdisk, the FAT32 partition type is called W95 FAT32 (LBA) and its ID is 0xC.
4. Mark the newly created partition as bootable and save
5. Mount the previously created partition
6. Extract the tarball contents to your FAT32 partition
7. Unmount the SD Card.

Note: Due to a bug (#7024), you might want to add a "usercfg.txt" file (which is included by config.txt) with enable_uart=1 written in it. Otherwise, the error message "Can''t open /dev/ttyS0" will repeatedly be written to the console.

Installation

Alpine Linux will be installed as diskless mode, hence you need to use Alpine Local Backup (lbu) to save your modifications between reboots. Follow these steps to install Alpine Linux:

1. Insert the SD Card into the Raspberry Pi and turn it on
2. Login into the Alpine system as root. Leave the password empty.
3. Type setup-alpine
4. Once the installation is complete, commit the changes by typing lbu commit -d

Type reboot to verify that the installation was indeed successful.

Post Installation

Update the System

Upon installation, make sure that your system is up-to-date:

apk update apk upgrade

Don''t forget to save the changes:

lbu commit -d

Clock-related error messages

During the booting time, you might notice errors related to the hardware clock. The Raspberry Pi does not have a hardware clock and therefore you need to disable the hwclock daemon and enable swclock:

rc-update add swclock boot # enable the software clock rc-update del hwclock boot # disable the hardware clock

Since Raspberry Pi does not have a clock, the Alpine Linux needs to know what the time is by using a Network Time Protocol (NTP) daemon. Make sure that you a NTP daemon installed and running. If you are not sure, then you can install NTP client by running the following command:

setup-ntp

Busybox NTP client might be the most lightweight solution. Save the changes and reboot, once the NTP software is installed and running:

lbu commit -d reboot

After reboot, make sure that the date command outputs the correct date and time.

X11 Setup

Here are what you need if you want to try and run a single X11 application like a browser kiosk or maybe even a desktop: ​

setup-xorg-base ​apk add xf86-video-fbdev xf86-input-mouse xf86-input-keyboard dbus ​set​xkbmap rc-update ​​add dbus

Also edit the default X11 module config: /etc/X11/xorg.conf.d/20-modules.conf

Section "Module" Load "fbdevhw" Load "fb" Load "shadow" Load "shadowfb" Load "dbe" Load "glx" Disable "dri" EndSection

Commit your changes:

lbu_commit -d

Now you should be able to run a browser or desktop. (Guides may follow)

If setup-xorg-base gives you an error regarding rc-update that fails to add mdev to sysinit just run:

rc-update mdev sysinit

to add it manually. If you skip this the next time you reboot your Raspberry Pi the screen maybe will not display anything on screen.

Persistent storage

Loopback image with overlayfs

The install is in disk-less mode and forces everything into memory, if you want additional storage we need to create loop-back storage onto the SD mounted with overlayfs.

First make the sd-card writable again and change fstab to always do so:

mount /media/mmcblk0p1 -o rw,remount sed -i ''s/vfat\ ro,/vfat\ rw,'' /etc/fstab

Create the loop-back file, this example is 1 GB:

dd if=/dev/zero of=/media/mmcblk0p1/persist.img bs=1024 count=0 seek=1048576

Install the ext utilities:

apk add e2fsprogs

Format the loop-back file:

mkfs.ext4 /media/mmcblk0p1/persist.img

Mount the storage:

echo "/media/mmcblk0p1/persist.img /media/persist ext4 rw,relatime,errors=remount-ro 0 0" >> /etc/fstab mkdir /media/persist mount -a

Make the overlay folders, we are doing /usr here, but you can do /home or anything else:

mkdir /media/persist/usr mkdir /media/persist/.work echo "overlay /usr overlay lowerdir=/usr,upperdir=/media/persist/usr,workdir=/media/persist/.work 0 0" >> /etc/fstab mount -a

Your /etc/fstab should look something like this:

/dev/cdrom /media/cdrom iso9660 noauto,ro 0 0 /dev/usbdisk /media/usb vfat noauto,ro 0 0 /dev/mmcblk0p1 /media/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,errors=remount-ro 0 0 /media/mmcblk0p1/persist.img /media/persist ext4 rw,relatime,errors=remount-ro 0 0 overlay /usr overlay lowerdir=/usr,upperdir=/media/persist/usr,workdir=/media/persist/.work 0 0

Now commit the changes: (optionally remove the e2fsprogs, but it does contain repair tools)

lbu_commit -d

Remember with this setup, if you install things and you have done this overlay for /usr, you must not commit the ''apk add'', otherwise while it boots it will try and install it to memory and not to the persist storage.

If you do want to install something small at boot you can use `apk add` and `lbu commit -d`.

If it is something a bit bigger then you can use `apk add` but then not commit it, it will be persistent (in /user), but do check everything you need is in that directory and not in folders you have not made persistent.

Traditional disk-based (sys) installation

Warning: This isn''t yet supported by the Alpine setup scripts for Raspberry Pi. It requires manual intervention, and might break.

 

It is also possible to switch to a fully disk-based installation: this is not yet formally supported, but can be done somewhat manually. This frees all the memory otherwise needed for the root filesystem, allowing more installed packages.

Split your SD card into two partitions: the FAT32 boot partition described above (in this example it''ll be mmcblk0p1) , and a second partition to hold the root filesystem (here it''ll be mmcblk0p2). Boot and configure your diskless system as above, then create a root filesystem:

apk add e2fsprogs mkfs.ext4 /dev/mmcblk0p2

Now do a disk install via a mountpoint. The setup-disk script will give some errors about syslinux/extlinux, but you can ignore these: the Raspberry Pi doesn''t need this to boot anyway.

mkdir /stage mount /dev/mmcblk0p2 /stage setup-disk -o /media/mmcblk0p1/MYHOSTNAME.apkovl.tar.gz /stage # (ignore errors about syslinux/extlinux)

Add a line to /stage/etc/fstab to mount the Pi''s boot partition again:

/dev/mmcblk0p1 /media/mmcblk0p1 vfat defaults 0 0

Now add a root=/dev/mmcblk0p2 parameter to the Pi''s boot command line, either cmdline-rpi2.txt or cmdline-rpi.txt depending on model:

mount -o remount,rw /media/mmcblk0p1 sed -i ''$ s/$/ root=\/dev\/mmcblk0p2/'' /media/mmcblk0p1/cmdline-rpi2.txt

You might also consider overlaytmpfs=yes here, which will cause the underlying SD card root filesystem to be mounted read-only, with an overlayed tmpfs for modifications which will be discarded on shutdown.

Beware, though, that the contents of /boot will be ignored when the Pi boots: it will use the kernel, initramfs, and modloop images from the FAT32 boot partition. To update the kernel, initfs or modules, you will need to manually (generate and) copy these to the boot partition or you could use bind mount so that manually copy the files to boot partition is not needed.

echo /media/mmcblk0p1/boot /boot none defaults,bind 0 0 >> /etc/fstab

Persistent Installation on RPi3

See this page : https://wiki.alpinelinux.org/wiki/Classic_install_or_sys_mode_on_Raspberry_Pi

See https://forum.alpinelinux.org/comment/1084#comment-1084

centos – 安装到/ opt / rh的RPM

ESP32 - 连接到 MCP23009即使连接返回成功，也无法将 OUTPUT 设为 HIGH ( 0 )

如何解决ESP32 - 连接到 MCP23009即使连接返回成功，也无法将 OUTPUT 设为 HIGH ( 0 )

我试图让 ESP32 与 I2C 一起工作，因为我有它，所以我带了一个 MCP23009。 Schmeantic 在图像中 Image

我的代码如下：

#include <Wire.h> // specify use of Wire.h library.
#define MCPAddress  0x20 //I2C Address
#define IO_DIR_REG 0x00           // The Output Register
#define GPIO_REG 0x09             // The GPIO Register
#define IOCON 0x05                // Settings
#define SEQOP_REQ 0b00100000      // disable address increment
#define I2C_SDA 21
#define I2C_SCL 22
int error;
void setup() 
{
  Serial.begin(115200); 
  delay(1000);
  Serial.println("Starting Wire");
  Wire.begin(I2C_SDA,I2C_SCL);
  Wire.setClock(100000); //Frequenz
  Wire.beginTransmission(MCPAddress); // Check if connection succesfull
  error = Wire.endTransmission();
  if(error == 0){
    Serial.println("Success");
  }else{
    Serial.println("Failure: ");
    Serial.print(error);
  }
  
  //Serial.println("disable Auto-Address increment!");
  //writeBlockData(IOCON,SEQOP_REQ); //Experimental,didn''t make it work
  
  Serial.println("Setting Outputs!");
  writeBlockData(IO_DIR_REG,0x00);
  
  Serial.println("Writing LOW!");
  writeBlockData(GPIO_REG,0x00);
}
 
void loop() 
{  
  Serial.println("Writing HIGH!");
  writeBlockData(GPIO_REG,0b11111111);
  delay(3000);
  
  Serial.println("Writing LOW!");
  writeBlockData(GPIO_REG,0b00000000);
  delay(3000);
}
int writeBlockData(uint8_t cmd,uint8_t val)
{
  Wire.beginTransmission(MCPAddress);
  Wire.write(cmd);
  Wire.write(val);
  delay(10);
  return Wire.endTransmission();
}

这相当简单，连接工作正常，因为当我读取 Wire.endTransmission() 时我只得到 0，但 LED 永远不会变高。不管我做什么。这是 MCP http://ww1.microchip.com/downloads/en/DeviceDoc/20002121C.pdf 的数据表 如果有人看到我的错误，我将不胜感激！我对使用 I2C 还很陌生，所以我并没有真正看到它。即使使用 Arduino 库也不起作用。

谢谢和问候！

解决方法

ext3grep 安装到 make 时报错

ext3grep 版本：ext3grep-0.10.2.tar.gz  

操作系统 centos 7 

产生原因：测试恢复被删除的文件

产生错误提示如下：

[root@localhost ext3grep-0.10.2]# make
make  all-recursive
make[1]: 进入目录“/data/recovery/ext3grep-0.10.2”
Making all in src
make[2]: 进入目录“/data/recovery/ext3grep-0.10.2/src”
g++ -Iempty.pch.h -DHAVE_CONFIG_H -I. -I..    -g -O2 -DUSE_MMAP=1 -I/usr/include/ext2fs -I/usr/include/et    -include pch.h \
  -c -o pch.h.gch/6145d4709c827f9d2a94d7691c87ab4e ./pch-source.h
In file included from ./pch-source.h:43:0:
./ext3.h: 在成员函数‘__u32 Inode::reserved2() const’中:
./ext3.h:113:42: 错误：‘i_reserved2’在此作用域中尚未声明
     __u32 reserved2(void) const { return i_reserved2; }
                                          ^
./ext3.h: 在成员函数‘void Inode::set_reserved2(__u32)’中:
./ext3.h:115:37: 错误：‘i_reserved2’在此作用域中尚未声明
     void set_reserved2(__u32 val) { i_reserved2 = val; }
                                     ^
make[2]: *** [pch.h.gch/6145d4709c827f9d2a94d7691c87ab4e] 错误 1
make[2]: 离开目录“/data/recovery/ext3grep-0.10.2/src”
make[1]: *** [all-recursive] 错误 1
make[1]: 离开目录“/data/recovery/ext3grep-0.10.2”
make: *** [all] 错误 2

解决方法： （在对应的地方，将 + 后面的内容补充到 ext3.h 中

[root@localhost ext3grep-0.10.2]# vim src/ext3.h 

增加+后面的内容，行号可以参考@@后面的svn差异：

diff -ur ext3grep-0.10.1/src/ext3.h ext3grep-0.10.1.new/src/ext3.h
--- ext3grep-0.10.1/src/ext3.h2008-04-09 11:20:31.000000000 +0000
+++ ext3grep-0.10.1.new/src/ext3.h2011-12-10 07:00:50.000000000 +0000
@@ -24,6 +24,17 @@
 #ifndef EXT3_H
 #define EXT3_H
 
+// this trickery needs to happen before ext2_fs is included so
+// bail out if it has already been included by another path
+#ifdef _LINUX_EXT2_FS_H
+  #error please include this file before any other includes of ext2fs/ext2_fs.h
+#endif
+
+// some versions of the ext2 headers call this s_frags_per_group and some
+// call it s_clusters_per_group, define one to the other so our code works 
+// with both
+#define s_clusters_per_group s_frags_per_group
+
 // Use the header files from e2progs (http://e2fsprogs.sourceforge.net)
 // We can use these headers and then everything named ext2 or ext3.
 #include <ext2fs/ext2_fs.h>// Definitions of ext2, ext3 and ext4.
@@ -110,6 +121,12 @@
     __u32 faddr(void) const { return i_faddr; }
     __u16 uid_high(void) const { return i_uid_high; }
     __u16 gid_high(void) const { return i_gid_high; }
+#ifndef i_reseved2
+    //i_reseved2 has been split into two fields in recent 
+    //versions of the headers, luckilly we can still access
+    //it in one peice through the hurd side of the union
+    #define i_reserved2 osd2.hurd2.h_i_author
+#endif
     __u32 reserved2(void) const { return i_reserved2; }
 
     void set_reserved2(__u32 val) { i_reserved2 = val; }

bug 从参考地址：https://code.google.com/p/ext3grep/issues/detail?id=34 

关于即使具有管理员权限，也无法将 R-4.1.0 安装到 Windows 10的问题就给大家分享到这里，感谢你花时间阅读本站内容，更多关于Alpine Linux 安装到 Raspberry Pi、centos – 安装到/ opt / rh的RPM、ESP32 - 连接到 MCP23009即使连接返回成功，也无法将 OUTPUT 设为 HIGH ( 0 )、ext3grep 安装到 make 时报错等相关知识的信息别忘了在本站进行查找喔。

本文标签：

• Windows_10
• R_4.1.0
• 管理员权限
• 安装失败